adplus-dvertising
frame-decoration

Question

What are the different ways in which requirements engineering and design are related?

a.

They are strictly separated in time

b.

They are not related

c.

They are related in that requirements specification is very formal and can be viewed as a high-level design specification of the system to be built.

d.

They are related in that preliminary design is done after an initial set of requirements has been determined.

Posted under Software Engineering

Answer: (c).They are related in that requirements specification is very formal and can be viewed as a high-level design specification of the system to be built. Explanation:The notion ‘specification’ thus has several meanings. To prevent confusion, we will always use the prefix ‘requirements’ if it denotes the result of the requirements engineering phase. In some cases, the requirements specification is very formal and can be viewed as a high-level design specification of the system to be built.

Engage with the Community - Add Your Comment

Confused About the Answer? Ask for Details Here.

Know the Explanation? Add it Here.

Q. What are the different ways in which requirements engineering and design are related?

Similar Questions

Discover Related MCQs

Q. What is the purpose of using the prefix 'requirements' when referring to the result of the requirements engineering phase?

Q. What is the primary goal of requirements engineering?

Q. How are requirements engineering and design generally separated in time?

Q. What role do social and cognitive aspects play in requirements engineering?

Q. What are some well-known techniques used to structure and document both requirements specifications and designs?

Q. What is the main purpose of requirements engineering in the context of a university's library automating its operation?

Q. What are some examples of user requirements that may be raised during the requirements engineering phase for a university's library automation project?

Q. What are some well-known techniques used to structure and document both requirements specifications and designs in software development?

Q. What is one of the main problems with the current system of ordering books in the library?

Q. What is one of the reasons for automating the library's operation?

Q. What are some of the requirements that will be raised during the requirements engineering phase for the library system?

Q. What are some possible future requirements of the library system?

Q. What are some of the stakeholders in the library system?

Q. What should be considered when trying to group user requirements into categories?

Q. How can a layered scheme in both the formulation of user requirements and their subsequent realization help to circumvent problems that beset software development projects?

Q. What are some examples of future requirements that could be predicted for a library system?

Q. Who are the stakeholders in a library system?

Q. What are some other matters that should be addressed during the requirements engineering phase for a library system?

Q. Why is it beneficial to use a layered scheme in the formulation of user requirements?

Q. What are some of the non-technical repercussions of introducing an automated system in a library?