SWR302_combined
1. Which of the following is NOT a good characteristic well written of a software
requirements specification?
A. Ranked
B. Redundant
C. Consistent
D. Verifiable -
B
3. Which is NOT the most important characteristics of product backlog?
A. Ranking of features is done based on business value, technical value, risk management or
strategic fitness
B. Lowest ranking items are decomposed into smaller stories during release planning so that
they can be completed in future iterations
C. Highest ranking items are decomposed into smaller stories during release planning so that
they can be completed in future iterations
D. Multiple teams can work on a single product backlog
E. Each product should have one product backlog which can have a set of large to very large
features -
B
4. A key tool for software designer, developer and their test team is to carry out their
respective tasks is defined by:
A. Technical documentation
B. User document
C. Software design documentation
D. Requirement documentation -
D
5. What is a best practice for change control?
A. Submit multiple changes at one time
B. Open and honest communication
1|Page
,C. Give overviews of the changes
D. Hold change meetings -
C
6. Which is(are) the skills of business analyst on Agile project?
A. Understanding of the business area that the project is involved with
B. Understanding of the agile development process
C. Ability to facilitate a team to consensus on scope, design decisions, and implementation
decisions
D. All of the mentioned
E. Ability to document requirements formally or informally depending on the need of the
project -
D
8. As requirements are elicited, what source is most likely to impose previously unidentified
user processes?
A. Stakeholders
B. The operational environment
C. Application domain specialists
D. The organizational environment -
D
9. What is a software requirements specification (SRS) document?
A. A document listing the time it takes to execute the existing manual processes
B. A document detailing software requirements and specifications
C. A document which features instructions for how to install new software and test it for
errors
D. A document used while testing the software code for validity -
B
10. Requirement elicitation is communication intensive and should be aligned with:
A. The cost-benefit analysis
B. The business case
2|Page
,C. The stakeholders' needs and constraints
D. The requirement management plan -
C
12. Giving an example of quality requirements: "After performing a file backup, the system
shall verify the backup copy against the original and report any discrepancies". This is a
(an)______
A. Robustness requirement
B. integrity requirement
C. performance requirement
D. interoperability requirement -
B
13. Which is NOT a reuse success factor?
A. Organizational culture
B. National culture
C. Quality
D. Terminology
E. Repository
F. Interactions -
B
14. If requirements are easily understandable and defined then which software process model
is best suited?
A. Waterfall model
B. Agile model
C. Spiral model
D. Prototyping model -
A
15. Which is NOT a technique to find missing requirements?
A. Check boundary values for missing requirements
3|Page
, B. Trace system requirements, user requirements, event-response lists, and business rules to
their corresponding functional requirements to make sure that all the necessary functionality
was derived.
C. Create a checklist of common functional areas to consider for your projects
D. Check a list of tasks corresponding with end users
E. Decompose high-level requirements into enough detail to reveal exactly what is being
requested -
D
16. Which is NOT the helpful of product backlog?
A. It helps in planning the roadmap for the product
B. It helps in managing the demands of stakeholders
C. It helps in determining what to prioritize first. Team ranks the item and then builds value.
D. It helps in re-ranking the features so that more value can be added to the product.
E. It is prepared so that estimates can be given to each and every feature -
B
17. Which activities are NOT belong to requirements status tracking?
A. Tracking the status distribution of all requirements
B. Recording the status of each requirements
C. Defining possible statuses
D. Tracking individual requirements versions -
D
18. To depict the complex logic, which representation technique should be used?
A. Decision tree
B. Context diagram
C. Swimlane diagram
D. State-transition diagram
E. Data flow diagram
F. Data dictionary -
A
4|Page
1. Which of the following is NOT a good characteristic well written of a software
requirements specification?
A. Ranked
B. Redundant
C. Consistent
D. Verifiable -
B
3. Which is NOT the most important characteristics of product backlog?
A. Ranking of features is done based on business value, technical value, risk management or
strategic fitness
B. Lowest ranking items are decomposed into smaller stories during release planning so that
they can be completed in future iterations
C. Highest ranking items are decomposed into smaller stories during release planning so that
they can be completed in future iterations
D. Multiple teams can work on a single product backlog
E. Each product should have one product backlog which can have a set of large to very large
features -
B
4. A key tool for software designer, developer and their test team is to carry out their
respective tasks is defined by:
A. Technical documentation
B. User document
C. Software design documentation
D. Requirement documentation -
D
5. What is a best practice for change control?
A. Submit multiple changes at one time
B. Open and honest communication
1|Page
,C. Give overviews of the changes
D. Hold change meetings -
C
6. Which is(are) the skills of business analyst on Agile project?
A. Understanding of the business area that the project is involved with
B. Understanding of the agile development process
C. Ability to facilitate a team to consensus on scope, design decisions, and implementation
decisions
D. All of the mentioned
E. Ability to document requirements formally or informally depending on the need of the
project -
D
8. As requirements are elicited, what source is most likely to impose previously unidentified
user processes?
A. Stakeholders
B. The operational environment
C. Application domain specialists
D. The organizational environment -
D
9. What is a software requirements specification (SRS) document?
A. A document listing the time it takes to execute the existing manual processes
B. A document detailing software requirements and specifications
C. A document which features instructions for how to install new software and test it for
errors
D. A document used while testing the software code for validity -
B
10. Requirement elicitation is communication intensive and should be aligned with:
A. The cost-benefit analysis
B. The business case
2|Page
,C. The stakeholders' needs and constraints
D. The requirement management plan -
C
12. Giving an example of quality requirements: "After performing a file backup, the system
shall verify the backup copy against the original and report any discrepancies". This is a
(an)______
A. Robustness requirement
B. integrity requirement
C. performance requirement
D. interoperability requirement -
B
13. Which is NOT a reuse success factor?
A. Organizational culture
B. National culture
C. Quality
D. Terminology
E. Repository
F. Interactions -
B
14. If requirements are easily understandable and defined then which software process model
is best suited?
A. Waterfall model
B. Agile model
C. Spiral model
D. Prototyping model -
A
15. Which is NOT a technique to find missing requirements?
A. Check boundary values for missing requirements
3|Page
, B. Trace system requirements, user requirements, event-response lists, and business rules to
their corresponding functional requirements to make sure that all the necessary functionality
was derived.
C. Create a checklist of common functional areas to consider for your projects
D. Check a list of tasks corresponding with end users
E. Decompose high-level requirements into enough detail to reveal exactly what is being
requested -
D
16. Which is NOT the helpful of product backlog?
A. It helps in planning the roadmap for the product
B. It helps in managing the demands of stakeholders
C. It helps in determining what to prioritize first. Team ranks the item and then builds value.
D. It helps in re-ranking the features so that more value can be added to the product.
E. It is prepared so that estimates can be given to each and every feature -
B
17. Which activities are NOT belong to requirements status tracking?
A. Tracking the status distribution of all requirements
B. Recording the status of each requirements
C. Defining possible statuses
D. Tracking individual requirements versions -
D
18. To depict the complex logic, which representation technique should be used?
A. Decision tree
B. Context diagram
C. Swimlane diagram
D. State-transition diagram
E. Data flow diagram
F. Data dictionary -
A
4|Page
