Part 1 of 1 -
Question 1 of 20
95.0/ 100.0 Points
5.0/ 5.0 Points
Which of the following order stage is compatible with requirement change process?
A. Change analysis and costing ->
Problem analysis and change specification ->
Change implementation.
B. Change implementation ->
Problem analysis and change specification ->
Change analysis and costing.
C. Problem analysis and change specification ->
Change analysis and costing ->
Change implementation.
D. Problem analysis and change specification ->
Change implementation ->
Change analysis and costing.
Question 2 of 20
Verification is to check
A. whether we are building the right product
5.0/ 5.0 Points
B. the methodology of software development
C. whether we are building the product right
D. ensure you comply with processes.
Question 3 of 20
5.0/ 5.0 Points
During program development, software requirements specify
A. how to divide the task into subtasks
B. how the program will accomplish the task
C. what the task is that the program must perform
D. how to test the program when it is done
Question 4 of 20
How to requirement clarifying?
A.Discuss with other members to clarify or confirm your understanding.
5.0/ 5.0 Points
B.Using SRS review checklist
C.Clarify unclear item(s) using Q&A
D.Self study related materials.
Question 5 of 20
5.0/ 5.0 Points
The work products produced during requirement elicitation will vary depending on the
A. size of the product being built
B. stakeholders needs
C. size of the budget
D. software process being used
Question 6 of 20
0.0/ 5.0 Points
Which of the following is not one of the context-free questions that would be used during project
inception?
A. Who will use the solution?
B. Who is behind the request for work?
C. What will be the economic benefit from a good solution?
D. Who will pay for the work?
Question 7 of 20
5.0/ 5.0 Points
SRS document is for
A. How to design the system?
B. “What”of a system?
C. System’s requirement.
D. Costing and scheduling of a system
Question 8 of 20
Which of the following stage is done to:
- Detect and resolve conflicts between requirements ?
A. Develop SRS
5.0/ 5.0 Points
B. Manage Requirement Changes
C. Validate Requirements
D. Elicit & Analyze Requirements
Question 9 of 20
5.0/ 5.0 Points
Which of the following role uses requirement documents to:
- check that they meet their needs ?
A. System maintenance engineers
B. System engineers
C. System customer
D. System test engineers
Question 10 of 20
Requirements models depict software in which three domains?
A. architecture, interface, component
5.0/ 5.0 Points
B. cost, risk, schedule
C. information, function, behavior
D. None of the above
Question 11 of 20
5.0/ 5.0 Points
It includes a set of ________ that describe all the interactions the users will have with the software.
A. Unified Modeling Language
B. IBM Rational Unified Process
C. Ivar Jacobson
D. Use case
Question 12 of 20
Product features are related to:
A. Functional requirements
5.0/ 5.0 Points
B. Non functional requirements
C. Interface requirement
D. None of the above
Question 13 of 20
5.0/ 5.0 Points
What type of characteristics of good SRS describes that it should has only one interpretation (to both
creator & user)?
A. Traceable
B. Unambiguous
C. Correct
D. Verifiable
Question 14 of 20
In collaborative requirements gathering the facilitator
A. controls the meeting
5.0/ 5.0 Points
B. can not be a customer
C. must be an outsider
D. arranges the meeting place
Question 15 of 20
5.0/ 5.0 Points
What type of characteristics of good SRS describes that no conflict between individual requirements ?
A. Complete
B. Correct
C. Consistent
D. Unambiguous
Question 16 of 20
5.0/ 5.0 Points
The result of the requirements engineering task is an analysis model that defines which of the following
problem domain(s)?
A. information
B. functional
C. behavioral
D. all of the above
Question 17 of 20
5.0/ 5.0 Points
Which of the following role uses requirement documents to:
- develop validation tests for the system ?
A. Manager
B. System customer
C. System test engineers
D. System engineers
Question 18 of 20
To validate requirement, what type of checking answers the question of
- Does the system provide RIGHT functionalities as customer’s NEED?
A. Realism check
5.0/ 5.0 Points
B. Completeness check
C. Validity check
D. Consistency check
Question 19 of 20
5.0/ 5.0 Points
Requirements elicitation means
A. Gathering of requirements
B. Capturing of requirements
C. Understanding of requirements
D. All of the above
Question 20 of 20
Requirements review process is carried out to
A. Spend time in requirements gathering
5.0/ 5.0 Points
B. Improve the quality of SRS
C. Document the requirements
D. None of the above
Part 1 of 1 -
Question 1 of 20
95.0/ 100.0 Points
5.0/ 5.0 Points
Outcome of requirements specification phase is
A. Design Document
B. Software requirements specification
C. Test Document
D. None of the above
Question 2 of 20
Software requirement should not be
5.0/ 5.0 Points
A. functional
B. complete
C. ambiguous
D. consistent
Question 3 of 20
5.0/ 5.0 Points
What type of characteristics of good SRS describes that no conflict between individual requirements ?
A. Complete
B. Correct
C. Consistent
D. Unambiguous
Question 4 of 20
Which of the following is not an objective for building a requirements model?
5.0/ 5.0 Points
A. define set of software requirements that can be validated
B. develop an abbreviated solution for the problem
C. describe customer requirements
D. establish basis for software design
Question 5 of 20
5.0/ 5.0 Points
To validate requirement, what type of techniques describes that it develops tests for requirements to
check testability?
A. Prototyping
B. Test-case generation
C. Requirements Review
D. Model Validation
Question 6 of 20
Which of the following role uses requirement documents to:
- plan a bid for the system and to plan the system development process ?
5.0/ 5.0 Points
A. System engineers
B. Manager
C. System customer
D. System test engineers
Question 7 of 20
5.0/ 5.0 Points
Non-functional requirements are requirements which impose constraints on the design or
implementation (such as ________ requirements, quality standards, or design constraints).
A. Functional specification
B. Requirements analysis
C. Performance engineering
D. Systems Development Life Cycle
Question 8 of 20
One reason to involve everyone on the software team in the planning activity is to
5.0/ 5.0 Points
A. understand the problem scope
B. adjust the granularity of the plan
C. control feature creep
D. get all team members to "sign up" to the plan
Question 9 of 20
5.0/ 5.0 Points
Which one is not a step of requirement engineering?
A. Requirements elicitation
B. Requirements design
C. Requirements analysis
D. Requirements documentation
Question 10 of 20
SRS stands for ?
5.0/ 5.0 Points
A. Software Requirement Specification
B. Software Requirement Solution
C. System Requirement Solution
D. None of the above
Question 11 of 20
5.0/ 5.0 Points
Which of the following stage is done to:
- Elaborate system requirements to derive software requirements ?
A. Manage Requirement Changes
B. Elicit & Analyze Requirements
C. Validate Requirements
D. Develop SRS
Question 12 of 20
How to requirement clarifying?
5.0/ 5.0 Points
A.Discuss with other members to clarify or confirm your understanding.
B.Using SRS review checklist
C.Clarify unclear item(s) using Q&A
D.Self study related materials.
Question 13 of 20
5.0/ 5.0 Points
To validate requirement, what type of checking answers the question of
- Does the system provide RIGHT functionalities as customer’s NEED?
A. Realism check
B. Completeness check
C. Validity check
D. Consistency check
Question 14 of 20
Validation is to check
5.0/ 5.0 Points
A. whether we are building the product right
B. whether we are building the right product
C. ensure you comply with processes.
D. the methodology of software development
Question 15 of 20
0.0/ 5.0 Points
The work products produced during requirement elicitation will vary depending on the
A. size of the product being built
B. stakeholders needs
C. size of the budget
D. software process being used
Question 16 of 20
Who we must work with to elicit:
- the services that the system should provide.
- the constraints that the system should satisfy.
5.0/ 5.0 Points
A. Software Project Manager
B. Software Programmer
C. Customers
D. Software tester
Question 17 of 20
5.0/ 5.0 Points
To validate requirement, what type of checking answers the question of
- Can requirement be TESTED?
A. Completeness check
B. Verifiability check
C. Realism check
D. Validity check
Question 18 of 20
Which is not a characteristic of a good SRS?
5.0/ 5.0 Points
A. Brief
B. Complete
C. Consistent
D. Correct
Question 19 of 20
5.0/ 5.0 Points
Which of the following stage is done to:
- Make sure that the requirements define the system that the customer really wants ?
A. Validate Requirements
B. Manage Requirement Changes
C. Elicit & Analyze Requirements
D. Develop SRS
Question 20 of 20
5.0/ 5.0 Points
What type of documents used to track the status, relationship and change of requirements during the
whole project?
A. SRS – Software requirement specification
B. Requirement Management Sheet
C. DDD - Detail Design Document
D. URD - User Requirement Definition
Part 1 of 1 -
84.17/ 100.0 Points
Question 1 of 20
5.0/ 5.0 Points
Requirements elicitation means
A. Gathering of requirements
B. Capturing of requirements
C. Understanding of requirements
D. All of the above
Question 2 of 20
The work products produced during requirement elicitation will vary depending on the
0.0/ 5.0 Points
A. size of the product being built
B. stakeholders needs
C. size of the budget
D. software process being used
Question 3 of 20
5.0/ 5.0 Points
Which of the following stage is done to:
- Develop use cases, system requirement ?
A. Elicit & Analyze Requirements
B. Manage Requirement Changes
C. Validate Requirements
Question 4 of 20
Verification is to check
A. whether we are building the right product
0.0/ 5.0 Points
B. the methodology of software development
C. whether we are building the product right
D. ensure you comply with processes.
Question 5 of 20
5.0/ 5.0 Points
One reason to involve everyone on the software team in the planning activity is to
A. understand the problem scope
B. adjust the granularity of the plan
C. control feature creep
D. get all team members to "sign up" to the plan
Question 6 of 20
Validation is to check
A. whether we are building the product right
5.0/ 5.0 Points
B. whether we are building the right product
C. ensure you comply with processes.
D. the methodology of software development
Question 7 of 20
1.67/ 5.0 Points
Three things that make requirements elicitation difficult are problems of
A.scope
B.volatility
C.budgeting
D.understanding
Question 8 of 20
5.0/ 5.0 Points
To validate requirement, what type of techniques describes that it develops tests for requirements to
check testability?
A. Prototyping
B. Test-case generation
C. Requirements Review
D. Model Validation
Question 9 of 20
5.0/ 5.0 Points
A Non-Functional Software testing done to check if the user interface is easy to use and understand
A. Security Testing
B. Usability Testing
C. Block Box Testing
D. Unit testing
Question 10 of 20
Software requirement should not be
A. functional
5.0/ 5.0 Points