adplus-dvertising
frame-decoration

Question

What is the purpose of establishing traceability from requirements to code and vice versa?

a.

To make the relation between requirements and solutions explicit

b.

To establish a hierarchical organization

c.

To sort news items

d.

To freeze the requirements early

Posted under Software Engineering

Answer: (a).To make the relation between requirements and solutions explicit Explanation:The purpose of establishing traceability from requirements to code and vice versa is to make the relation between requirements and solutions explicit, allowing us to trace where requirements are realized and why certain solutions are chosen.

Engage with the Community - Add Your Comment

Confused About the Answer? Ask for Details Here.

Know the Explanation? Add it Here.

Q. What is the purpose of establishing traceability from requirements to code and vice versa?

Similar Questions

Discover Related MCQs

Q. What is the main problem with design space analysis?

Q. Why has design rationale by and large failed to transfer to practice?

Q. Who is best served by a requirements specification document that uses the language of the application domain?

Q. What kind of language is used in a requirements specification document if the system is described in the user's language?

Q. What is the purpose of a requirements specification document for the designer?

Q. What kind of language is used in a requirements specification document if the expert language of the software engineer plays a central role?

Q. What kind of techniques can be used to check a requirements specification document phrased in a formal language?

Q. Who does the requirements specification serve?

Q. What kind of document is the best for the user?

Q. What kind of document is best for the designer?

Q. What kind of language is used if the system is described in the user's language?

Q. What language is best used for the requirements specification?

Q. What are the drawbacks of using natural language for the requirements specification according to Meyer (1985)?

Q. What is the risk of trying to be too literary in the requirements specification?

Q. What does "forward references" refer to in the context of the requirements specification?

Q. What is the goal of the requirements specification in software development?

Q. What language is best used in the requirements specification to serve the user in software development?

Q. What language is best used in the requirements specification to serve the designer in software development?

Q. What are the seven sins listed by Meyer that may beset the analyst when using natural language in a requirements specification?

Q. What is the alternative given by Meyer to the use of natural language in the requirements specification?