1. | What is the most challenging and difficult aspect of requirements engineering? |
Discuss |
Answer: (a).Getting a complete description of the problem to be solved
Explanation:The most challenging and difficult aspect of requirements engineering is to get a complete description of the problem to be solved.
|
2. | What is the main focus of the requirements engineering phase? |
Discuss |
Answer: (a).Identifying and documenting the user’s requirements for the future system
Explanation:The main focus of the requirements engineering phase is to carefully identify and document the user’s requirements with respect to the future system.
|
3. | What is a requirement according to IEEE 610? |
Discuss |
Answer: (a).A condition or capability needed by a user to solve a problem or achieve an objective
Explanation:According to IEEE 610, a requirement is a condition or capability needed by a user to solve a problem or achieve an objective.
|
4. | Who is the main source of information for functional, task-related requirements during requirements engineering? |
Discuss |
Answer: (a).End users
Explanation:The end users will be the main source of information regarding the functional, task-related requirements during the requirements engineering phase.
|
5. | What are the different types of requirements that are taken into consideration during the requirements engineering phase? |
Discuss |
Answer: (d).All of the above
Explanation:These requirements concern both the functions to be provided and a number of additional requirements, such as those regarding performance, reliability, user documentation, user training, cost, and so on.
|
6. | Who may be the source of requirements during the requirements engineering phase? |
Discuss |
Answer: (d).All of the above
Explanation:During requirements engineering, different types of user may be the source of different types of requirements. Hopefully, the end users will be the main source of information regarding the functional, task-related requirements. Other requirements, e.g. those that relate to security issues, may well be phrased by other stakeholders.
|
7. | How does the requirements engineering phase result in a contract between the client and the development organization? |
Discuss |
Answer: (c).By documenting the mutual understanding of the problem in the requirements specification
Explanation:The result of the requirements engineering phase is documented in the requirements specification. The requirements specification reflects the mutual understanding of the problem to be solved between the analyst and the client. It is the basis for a contract, be it formal or informal, between the client of the system and the development organization.
|
8. | What is the purpose of the requirements specification? |
Discuss |
Answer: (d).All of the above
Explanation:The result of the requirements engineering phase is documented in the requirements specification. The requirements specification reflects the mutual understanding of the problem to be solved between the analyst and the client. It is the basis for a contract, be it formal or informal, between the client of the system and the development organization. Eventually, the system delivered will be assessed by testing its compliance with the requirements specification. The requirements specification serves as a starting point for the next phase, the design phase.
|
9. | What are the types of requirements that need to be taken into account during the requirements engineering phase? |
Discuss |
Answer: (b).Additional requirements such as those regarding performance, reliability, user documentation, user training, cost, and so on.
Explanation:During the requirements engineering phase, user's requirements with respect to the future system are carefully identified and documented. These requirements concern both the functions to be provided and a number of additional requirements, such as those regarding performance, reliability, user documentation, user training, cost, and so on.
|
10. | What is a requirement according to IEEE610, 1990? |
Discuss |
Answer: (b).A condition or capability needed by a user to solve a problem or achieve an objective.
Explanation:A requirement is ‘a condition or capability needed by a user to solve a problem or achieve an objective’ (IEEE610, 1990).
|