adplus-dvertising
frame-decoration

Question

What is the result of not documenting the design decisions in architecture?

a.

The reasoning behind the design decisions is lost forever.

b.

The reasoning behind the design decisions is easily accessible.

c.

The reasoning behind the design decisions is stored in the heads of a few people associated with them.

d.

The reasoning behind the design decisions is documented and stored somewhere.

Posted under Software Engineering

Answer: (a).The reasoning behind the design decisions is lost forever. Explanation:Much of the rationale behind the solutions is usually lost forever, or resides only in the head of the few people associated with them, if they are still around.

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 result of not documenting the design decisions in architecture?

Similar Questions

Discover Related MCQs

Q. What is the main issue with undocumented design decisions in architecture?

Q. What is the reason for not documenting the reasoning behind design decisions in architecture?

Q. What is an illusion in regards to documenting design decisions?

Q. What is a design decision in Software Architecture?

Q. What is the rationale for a design decision?

Q. What is the purpose of a decision tree in regards to design decisions?

Q. What is the main purpose of a software architecture?

Q. Can a single representation of the software architecture serve all stakeholders?

Q. How is the software architecture representation for different stakeholders similar to civil engineering?

Q. What is the purpose of the IEEE standard 1471 for software architecture representations?

Q. What are the main elements of the IEEE standard 1471 for software architecture representations?

Q. Who determines which representations are appropriate for a software architecture?

Q. What is the purpose of a viewpoint in software architecture representation?

Q. Does the IEEE standard 1471 provide a specific set of viewpoints for all software architectures?

Q. What is the purpose of the stakeholder element in the IEEE standard 1471 for software architecture representations?

Q. What is the purpose of a view in the IEEE standard 1471?

Q. What is the purpose of a viewpoint in the IEEE standard 1471?

Q. What is the purpose of the library viewpoint in the IEEE standard 1471?

Q. What type of view do module viewpoints give of a system?

Q. What type of view do component and connector viewpoints give of a system?