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 clients 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.