can i get answers please (Essentials of Software Engineering, Fourth Edition) Tr
ID: 3607688 • Letter: C
Question
can i get answers please (Essentials of Software Engineering, Fourth Edition)
True/False
1. All requirements activities are needed in the same degree for all software projects.
2. A software engineering team must plan requirements engineering activities for all software projects.
3. During the requirements elicitation, the list of what the customer wants as the functions for the new
software is not elicited, just what the business needs to do.
4. A use case contains requirement information.
5. Requirements definition involves formally spelling out the requirements.
6.SRS is the artifact that spells out the final specific software requirements from the requirements
engineering activities.
7. Requirements are the “what” and design is the “how.”
8.The requirements engineering activities include review and validation, which are the testing of the
requirements.
9. High-level requirements elicitation serves as the opportunity, needs, and justification for the software
project in the client’s business world.
10. Low-level requirements elicitation uncovers constraints for the software project to be developed.
11. Collection of the detail level information pertaining to data and their formats includes the input and
output data of the software system.
12. The requirements are ordered once they are elicited and collected.
13. The detailed requirements section of the SRS is the shortest section.
Explanation / Answer
1. All requirements activities are needed in the same degree for all software projects.
It depends on the size of the project, the sources of knowledge used and the techniques used in requirements elicitation.
False
2. A software engineering team must plan requirements engineering activities for all software projects.
Requirements engineering gives clarity on the scope of the projct and helps plan better. Though earlier methods focussed on the deliverables.
True
3. During the requirements elicitation, the list of what the customer wants as the functions for the new software is not elicited, just what the business needs to do.
The business needs, risks and assumptions are identified during requirements elicitation. Functional as well as non-functional requirements are part of elicitation.
False
4. A use case contains requirement information.
This provides precise low level details.
True
5. Requirements definition involves formally spelling out the requirements.
False
6.SRS is the artifact that spells out the final specific software requirements from the requirements engineering activities.
True
7. Requirements are the “what” and design is the “how.”
True
8.The requirements engineering activities include review and validation, which are the testing of the requirements.
False
9. High-level requirements elicitation serves as the opportunity, needs, and justification for the software project in the client’s business world.
True
10. Low-level requirements elicitation uncovers constraints for the software project to be developed.
11. Collection of the detail level information pertaining to data and their formats includes the input and output data of the software system.
False
12. The requirements are ordered once they are elicited and collected.
False
13. The detailed requirements section of the SRS is the shortest section.
False
Related Questions
drjack9650@gmail.com
Navigate
Integrity-first tutoring: explanations and feedback only — we do not complete graded work. Learn more.