Object Oriented Software Engineering   View all facts   Glossary   Help
subject > representation > document > design document
Next documentdomain analysis document    Updocument    Previous documentcatalog of reusable components   

design document
subjectfact 
design documentallows a group of people to review the design and therefore to improve it2001-08-30 14:55:16.0
contains every design decision along with the reasoning that went into making the decision2001-08-30 14:55:16.0
has definition Documentation produced as a result of the design process2001-08-30 14:55:16.0
describes the priorities used to guide the design process2001-08-30 14:55:16.0
describes what system or part of the system this design document describes2001-08-30 14:55:16.0
discusses the important issues that had to be resolved, the possible alternatives that were considered, the final decision and the rationale for the decision2001-08-30 14:55:16.0
ensures traceability by making reference to the requirements that are being implemented by this design2001-08-30 14:55:16.0
forces a designer to be explicit and to consider the important issues before starting implementation2001-08-30 14:55:16.0
has purpose
  • to encourage designers to make good design decisions
  • to communicate the design to others
2001-08-30 14:55:16.0
has suggested structure
  1. purpose
  2. general priorities
  3. outline of the design
  4. major design issues
  5. other details of the design
2001-08-30 14:55:16.0
includes a high-level description (or diagram) of the design that allows the reader to quickly get a general feeling for it2001-08-30 14:55:16.0
includes the information its readers need to learn2001-08-30 14:55:16.0
includes the rationale for the design which allows the reader to better understand the design, helps reviewers to determine whether good decisions were made, and helps the maintainers determine how to change the design2001-08-30 14:55:16.0
is a subtopic of 9.1 - The Process of Design2001-08-30 14:55:16.0
is a kind of document2001-08-30 14:55:16.0
makes reference to the requirements that are being implemented by this design2001-08-30 14:55:16.0
see also design2001-08-30 14:55:16.0
should be written for
  • Those who will be implementing the design, i.e. the programmers
  • Those who will need, in the future, to modify the design
  • Those who need to create systems or subsystems that interface with the system being designed
2001-08-30 14:55:16.0
should not include 2001-08-30 14:55:16.0

Next documentdomain analysis document    Updocument    Previous documentcatalog of reusable components