The software design model based on architecture divides the software process into 6 sub-processes of architecture requirements, design, documentation, review, realization and evolution, which are summarized as follows.
1. Architecture requirements. The user is expected to acquire, analyze and process the requirements of software system functions, performance, interface, design constraints, etc., and define each requirement item abstract as a component (a collection of classes).
2, architecture design. That is, the iterative method first chooses a suitable software architecture style (such as C/S, b/s, n layer, Pipeline filter style, C2 style, etc.) as an architectural model, and then maps the component of the requirement phase to the model, analyzes the interaction relationship between the components, and finally forms a tailor-made software architecture.
3. Documentation of the architecture. This is the architecture specification and architecture design manuals that users and developers can read.
4. Review of the system structure. That is, early detection of defects and errors in the design of the architecture, timely labeling and elimination.
5, the implementation of the system architecture. That is, the designers developed the system components, according to the architecture design specifications for the association of Components, synthesis, assembly and testing.
6, Architecture evolution. If the user needs have changed, it is necessary to modify and refine the optimization, adjust the software architecture to adapt to the new changing software requirements.
How to design the software system architecture?