What is software low level design ?
Filed Under Design, Development, Model, Software, Techniques | Posted on September 27, 2007
The low level design document for a project should provide a complete and detailed specification of the design for the software that will be developed in the project, including the classes, member and non-member functions, and associations between classes that are involved. By the end of the Low Level Design stage, the code should be “all but written”.
The low level design document should contain a listing of the declarations of all the classes, non-member-functions, and class member functions that will be defined during the implementation stage, along with the associations between those classes and any other details of those classes (such as member variables) that are firmly determined by the low level design stage. The low level design document should also describe the classes, function signatures, associations, and any other appropriate details, which will be involved in testing and evaluating the project according to the evaluation plan defined in the project’s requirements document.
More importantly, each project’s low level design document should provide a narrative describing (and comments in your declaration and definition files should point out) how the high level design is mapped into its detailed low-level design, which is just a step away from the implementation itself. This should be an English description of how you converted the technical diagrams (and text descriptions) found in your high level design into appropriate class and function declarations in your low level design. You should be especially careful to explain how the class roles and their methods were combined in your low level design, and any changes that you decided to make in combining and refining them.
|
|
|
If you are interested in software processes, find this post informative, and want to learn more, why not subscribe ?
Subscribe in a readerSubscribe to get updates by Email
Leave a Reply
