What software outline design does and how to do it

What to do in the software outline design and how to do it

from : http://elf8848.iteye.com/

1. The general process of software design:
1. In the previous software requirements analysis stage, the "what problem to be solved" has been figured out, and the output "Software Requirements Manual". At this point everything is ideal.
2. Now enter the outline design stage, focus on clarifying the "overall implementation plan", determine the overall layout of the software system, the functions of each sub-module and the relationship between modules, and the relationship with external systems. There is some research and argumentative content. And output "Software Outline Design Manual". At this point everything is a concept.
3. Finally, enter the detailed design stage, focusing on clarifying "how to do each module", which is the blueprint of the "program", and determines the algorithm, data structure, interface implementation, attributes, and parameters used by each module. And output "software detailed design instructions". At this point everything is realized.


2. General structure of "Outline Design Manual":
   1. General description: requirements or goals (talk about the origin of things), environment, and limitations;
           ---- mainly explain the background and general environment. (non-emphasis)
   2. Overall design: from a global perspective, talk about the overall structure, functions, processing flow, which modules, and the relationship between modules;
           ---- Make readers have a "global" view, and go deep into each module for the next step be prepared.
   3. External interface: General description of external user, software and hardware interfaces (available resources); (this interface is not the interface of java).
           ---- Make readers aware of external resources that can be utilized.
   4. Module design: "what to do" for each module, a brief description of "how to do it" (input, output, processing logic, interface with other modules or systems), and what logical and physical location it is in; (emphasis)
   5. Data structure: logical structure, physical structure (stored in data table or cache); 
   6. Disaster recovery design: error information, error handling; (optional)
   7. Monitoring design: operation module combination, control, time ;(Optional)
   8. User Interface Design: (Optional)
   9. Security Design: (Optional)
   10. Other Designs: (Optional)
   11. Specifications (Appendix): Design principles, code specifications, interface specifications, Naming rules. --It is the basis of collaborative development of the group

3. Module design is the key point, a few words:
   You can write the following:
   1. Module description: explain which modules implement which functions;
   2. Module hierarchy: you can use a certain perspective
   3. Relationship between modules: description of dependencies between modules, description of communication mechanism;
   4. Core interface of module: description of information transmitted by module and structure of information; 5.
   Design of processing method: to say something satisfying Algorithms of function and performance;


4. How to use the outline design:
   1. It is used to evaluate the feasibility of the overall design.
   2. It is used to check whether the designed modules are complete, and ensure that each function has a corresponding module to realize.
   3. It is used to evaluate the development workload and guide the development plan (without writing a detailed design).


V. Final reminder:
   1. It is a misunderstanding that the outline design stage pays too much attention to the business process.
   2. It is a misunderstanding that the outline design stage pays too much attention to the implementation of details.



Reprint please indicate the source: http://elf8848.iteye.com/