ITSS 4330 Exam 1 | UPDATED Questions with 100%
Verified Answers
Q1: Agile Development
A: an information systems development process that emphasizes flexibility to anticipate new
requirements during development
Q2: Iterative Development
A: an approach to system development in which the system is "grown" piece by piece
through multiple iterations
Q3: Work Breakdown Structure
A: defines the hierarchy of project tasks, subtasks, and work packages
Q4: use case diagram
A: Diagrams that show how different types of users will interact with the system
Q5: Class diagram
A: A visual representation of the relationships between classes.
Q6: Technology Architecture
A: a set of computing hardware, network hardware and topology, and system software
employed by an organization
Q7: Application Architecture
A: The information systems that supports the organization
Q8: Functional Requirements
A: The activities that the system must perform
Business uses, functions the users carry out
Can be shown as use cases
Q9: Non-Functional Requirements
A: other system characteristics
Constraints and performance goals
User Interface
Ease of use
Failure rate
Q10: Stakeholders
, A: Persons who have an interest in the successful implementation of the system
Q11: Internal Stakeholders
A: Persons within the organization
Q12: External Stakeholders
A: Persons outside the organization
Q13: Operational Stakeholders
A: Persons who regularly interact with the system
Q14: Executive Stakeholders
A: Persons who don't interact directly with the system but who either use information
produced by the system or have a significant financial or other interest in its operation
and success
Q15: Workflow
A: Sequence of processing steps that completely handles one business transaction or
customer request
Q16: Activity Diagram
A: a UML diagram that describes user (or system) activities, the person or component that
completes each activity, and the sequential flow of these activities
Q17: System Analysis
A: Defining system requirements, functional and non-functional
Q18: Analysis Activities Include
A: Gather detailed information
Define Requirements
Prioritize Requirements
Develop User-Interface dialog
Evaluate requirements with users
Q19: FURPS+
A: Functional, usability, reliability, performance and security requirements
Q20: Unified Modeling Language (UML)
A: A standard format for communicating and documenting software design.
Q21: User Story
Verified Answers
Q1: Agile Development
A: an information systems development process that emphasizes flexibility to anticipate new
requirements during development
Q2: Iterative Development
A: an approach to system development in which the system is "grown" piece by piece
through multiple iterations
Q3: Work Breakdown Structure
A: defines the hierarchy of project tasks, subtasks, and work packages
Q4: use case diagram
A: Diagrams that show how different types of users will interact with the system
Q5: Class diagram
A: A visual representation of the relationships between classes.
Q6: Technology Architecture
A: a set of computing hardware, network hardware and topology, and system software
employed by an organization
Q7: Application Architecture
A: The information systems that supports the organization
Q8: Functional Requirements
A: The activities that the system must perform
Business uses, functions the users carry out
Can be shown as use cases
Q9: Non-Functional Requirements
A: other system characteristics
Constraints and performance goals
User Interface
Ease of use
Failure rate
Q10: Stakeholders
, A: Persons who have an interest in the successful implementation of the system
Q11: Internal Stakeholders
A: Persons within the organization
Q12: External Stakeholders
A: Persons outside the organization
Q13: Operational Stakeholders
A: Persons who regularly interact with the system
Q14: Executive Stakeholders
A: Persons who don't interact directly with the system but who either use information
produced by the system or have a significant financial or other interest in its operation
and success
Q15: Workflow
A: Sequence of processing steps that completely handles one business transaction or
customer request
Q16: Activity Diagram
A: a UML diagram that describes user (or system) activities, the person or component that
completes each activity, and the sequential flow of these activities
Q17: System Analysis
A: Defining system requirements, functional and non-functional
Q18: Analysis Activities Include
A: Gather detailed information
Define Requirements
Prioritize Requirements
Develop User-Interface dialog
Evaluate requirements with users
Q19: FURPS+
A: Functional, usability, reliability, performance and security requirements
Q20: Unified Modeling Language (UML)
A: A standard format for communicating and documenting software design.
Q21: User Story
