Which is NOT a purpose of the requirements definition? To give a very high-level
ID: 3676231 • Letter: W
Question
Which is NOT a purpose of the requirements definition?
To give a very high-level explanation of the business requirements
A more precise list of requirements that can be used as inputs to the rest of analysis
Create functional requirements
Create cost/benefit analysis
Create non-functional requirements
Use cases are used to more fully understand and describe _____ of the system.
design
requirements
infrastructure
test cases
management
Parallel methodology is BEST characterized as:
A ‘Quick and Dirty’ system
A method for exploring design alternatives
A method for stressing customer satisfaction
A series of versions
More explicit testing
In the SDLC (Systems Development Life Cycle), what comes after the analysis phase?
Approval phase
Design phase
Development phase
Implementation phase
Planning phase
The definition of use case is:
An informal method of interviews to gather requirements
A diagramming tool
It is a CASE tool
A formal method used by the System Analyst to document the system interaction with its actors
None of the above
Which of the following is probably NOT a method to classify projects?
Size
Risk
Scope
Open source
Economic value
Use cases generally have three parts:
Technical feasibility, economic feasibility, and organizational feasibility
Past, current and future history of the organization
Basic information, inputs and outputs, and details
Inputs and outputs and events
Analysis, design and implementation
John is worried about the company using the new system. This would be considered part of:
Technical feasibility
Organizational feasibility
Economic feasibility
Risk feasibility
Hardware feasibility
One of the most important tasks in developing the use case is:
Identify all the major steps in the use case
Looking up other references
Listing the design process
Implementing the programs
None of the above
Root Cause Analysis tries to find _____.
How long each process takes in the as-in system with an eye at shortening the time
How much each process costs (rather than the time) with an eye at cutting costs
The true problem and not just symptoms of problems and solve that
Technologies that could work
Other companies that have similar processes and attempt to learn from them
Which of the following project roles would focus on new business processes and value?
Systems analyst
Infrastructure analyst
Change management analyst
Business analyst
Project manager
One of the problems when doing requirements determination is:
Exclusion of business users and failure to address the true business needs of the users
Inclusion of data tables
Inclusion of business logic
Inclusion of a list of processes the system needed to perform
Over-reliance on object oriented systems analysis and design
Which of the following is NOT a part of the use case:
Use case name and number
Information of steps
Data Flow Diagram
Importance level
None of the above
Which is generally NOT true about non-functional requirements?
Cultural differences can be considered
Color interpretations on screens and forms may be different in different geographical places
Multi-lingual interfaces many be needed
Systems may need to adapt from global solutions to local realities
Systems may need to have actual expenses from global operations
Peter is doing an economic analysis using today’s dollar values. He is doing:
Cash flow analysis
Return on investment analysis
Net present value analysis
Break-even point analysis
Internal rate of return analysis
Explanation / Answer
This below list of answers are present as of my best knowledge.
Which is NOT a purpose of the requirements definition?
To give a very high-level explanation of the business requirements
A more precise list of requirements that can be used as inputs to the rest of analysis
Create functional requirements
Create cost/benefit analysis
Create non-functional requirements
Ans: To give a very high-level explanation of the business requirements
Use cases are used to more fully understand and describe _____ of the system.
design
requirements
infrastructure
test cases
management
Ans: Design of a System.
Parallel methodology is BEST characterized as:
A ‘Quick and Dirty’ system
A method for exploring design alternatives
A method for stressing customer satisfaction
A series of versions
More explicit testing
Ans: A method for exploring design alternatives
In the SDLC (Systems Development Life Cycle), what comes after the analysis phase?
Approval phase
Design phase
Development phase
Implementation phase
Planning phase
Ans: Design Phase.
The definition of use case is:
An informal method of interviews to gather requirements
A diagramming tool
It is a CASE tool
A formal method used by the System Analyst to document the system interaction with its actors
None of the above
Ans: A formal method used by the System Analyst to document the system interaction with its actors
Which of the following is probably NOT a method to classify projects?
Size
Risk
Scope
Open source
Economic value
Ans: Economic value or Open source.
Use cases generally have three parts:
Technical feasibility, economic feasibility, and organizational feasibility
Past, current and future history of the organization
Basic information, inputs and outputs, and details
Inputs and outputs and events
Analysis, design and implementation
Ans: basic information, inputs and outputs, and details
John is worried about the company using the new system. This would be considered part of:
Technical feasibility
Organizational feasibility
Economic feasibility
Risk feasibility
Hardware feasibility
Ans: Organizational feasibility
One of the most important tasks in developing the use case is:
Identify all the major steps in the use case
Looking up other references
Listing the design process
Implementing the programs
None of the above
Ans: Implementing the programs
Root Cause Analysis tries to find _____.
How long each process takes in the as-in system with an eye at shortening the time
How much each process costs (rather than the time) with an eye at cutting costs
The true problem and not just symptoms of problems and solve that
Technologies that could work
Other companies that have similar processes and attempt to learn from them
Ans: The true problem and not just symptoms of problems and solve that
Which of the following project roles would focus on new business processes and value?
Systems analyst
Infrastructure analyst
Change management analyst
Business analyst
Project manager
Ans: Business analyst
One of the problems when doing requirements determination is:
Exclusion of business users and failure to address the true business needs of the users
Inclusion of data tables
Inclusion of business logic
Inclusion of a list of processes the system needed to perform
Over-reliance on object oriented systems analysis and design
Ans: Inclusion of business logic
Which of the following is NOT a part of the use case:
Use case name and number
Information of steps
Data Flow Diagram
Importance level
None of the above
Ans: Importance level
Which is generally NOT true about non-functional requirements?
Cultural differences can be considered
Color interpretations on screens and forms may be different in different geographical places
Multi-lingual interfaces many be needed
Systems may need to adapt from global solutions to local realities
Systems may need to have actual expenses from global operations
Ans: Systems may need to adapt from global solutions to local realities
Peter is doing an economic analysis using today’s dollar values. He is doing:
Cash flow analysis
Return on investment analysis
Net present value analysis
Break-even point analysis
Internal rate of return analysis
Ans: Return on investment analysis
Related Questions
drjack9650@gmail.com
Navigate
Integrity-first tutoring: explanations and feedback only — we do not complete graded work. Learn more.