Software Engineering Development Document Writing Tutorial (14) - Outline Design Book Contents


  • The original author of this article: Brother Gu’s younger brother
  • Author blog address: http://blog.csdn.net/lfdfhl
  • Reference materials for this article: "Software Documentation Writing Tutorial" by Electronic Industry Press, edited by Ma Ping and Huang Dongmei

Contents of the outline design book

insert image description here

The general design phase has left the customer's perspective and returned to the developer's perspective, and entered the substantive development work of the software system.

Every software system is composed of programs and data, so data is the basis of software systems, and software is to complete the work that human beings want by operating data. For most of today's systems, the database becomes the warehouse for data storage, so one of the tasks that must be completed in the outline design phase is the database design. It is clear how to store data, what structure to store it in, and once the form of data is determined, the next detailed design stage can be based on this. Therefore, the initial database design should be included in the outline design book.

The final result of the requirements analysis stage——all the functions of the system recorded in the requirements analysis document become the raw materials processed in the outline design stage, and are the basis for the system's organizational structure and subsystem division. A large system should be divided as much as possible into several modules with moderate size, high cohesion, and low coupling. The purpose of this is on the one hand, easy to understand, and on the other hand, it is easy to develop. Therefore, the software system should be divided scientifically and rationally in the outline design stage, and the functions and requirements of each department after division should be recorded in the outline design document to prepare for the next detailed design.

Architecture, interface design, error handling design, determination of development environment and other issues that affect the main structure and performance of the entire software system must be designed in the outline design stage. These issues are to the system what the trunk is to the whole tree.

The interface of the system should be included in the outline design book, which can be the simplest interface drawn even in Excel, or a prototype developed with tools such as Dreamweaver. These prototype interfaces simply and clearly show the function and style of the system, and the relationship between each subsystem, and become the layout standard for future interface design.

In the outline design stage, we also need to formulate specifications, including code system, interface rules, and naming rules. This is the foundation of software development. With development specifications, interface rules, and methods, developers will have a common working language and a common working platform, so that the entire software development work can be carried out in a coordinated and orderly manner.

Guess you like

Origin blog.csdn.net/lfdfhl/article/details/131117656