Architecture Process Overview of software architects

The software architecture is a high-level structure of the software system. It shows the layout of components after the system is decomposed and the relationship between components. A good architecture description should contain multiple perspectives of the architecture, Component Design and expansion descriptions, and design principles to meet functional and non-functional requirements.
Generally, the software architecture is divided into five steps,
1. Create an architecture task and form an architecture team.
2. establish and document the architecture requirements.
3. Design Architecture
4. Verify that the architecture meets the requirements
5. Release the architecture to the development team and then let us elaborate on these five steps
First, the architecture needs to be targeted, generally to meet long-term business needs. Then define the task and define the milestones. Let everyone in the architecture group clearly define the objectives of the architecture and the relationship between task execution and task. The overall architecture concept needs to come out at this time. The idea of key components should also be available.
Second, we need to sort out the architecture requirements according to the goal. At first, there may be a lot of demand indexes. Each index is expressed in one or two sentences. A simple description of the index is required. The requirements need to be refined after the Index Review, which is a more detailed requirement arrangement. In addition to text descriptions, you can also configure images. The next step is to set up use cases to cover these needs.
Third, the design architecture can be divided into outline design and detailed design stages. The outline design requires a more outline design description, which can be used to briefly describe the use case through these design elements, and the story is complete in general. Then review and enter the detailed design stage. The detailed design is more complete and close to implementation. We also need a story-telling process to make the use case more vivid and vivid through the detailed design elements. Then implement and integrate.
Fourth, the verification process is a test process. Many test plans and use cases are established in the requirement stage. Scan the demand to see if the implementation has reached the commitment.
Fifth, after continuous testing and feedback, stable versions can be released to the development team.
For more information.
Architecture Design
1. More emphasis should be placed on the Composition decomposition and interface relationships between components. The interface features and usage descriptions of components are more prominent than general software design processes. Component function list, lifecycle, concurrency description, communication message format, and so on.
2. Components in the architecture have a unified architecture philosophy and principles. Components must be constrained.
3. The component must provide sample code, typical application scenarios, exceptions, and test instructions.
4. Components are sometimes mapped to processes in the physical view.
5. Focuses on the dynamic characteristics of the architecture system and the collaboration between components