I have heard of the job of an architect before, and I always feel that it is very tall, and the salary is good. It is also a dream job that I think has been out of reach
If you think about it carefully, they are actually people. Maybe I can be qualified for this job, but not now, but it is still possible in the future.
Definition of pre-architecture
Pre-architecture is the earliest stage of architecture design. Its work objectives include: understanding requirements, establishing the overall view of requirements, and determining the direction of architecture design.
Although the pre-architecture stage is a stage of foreshadowing, it is of great significance to the practice of architecture.
Pre-Architecture: Preparing the architecture
In the preparation phase, the most important thing is to figure out what to do, that is, to master user requirements. It should be said that the entire preparation stage revolves around "demand".
Described as the following process: demand-> constraints-> quality-> key functions
1. Demand
Business-level requirements: Contains business goals, expected investment, and construction period requirements that customers or funders need to achieve, as well as constraints such as which standards to be met and which legacy systems to integrate;
User-level requirements: What tasks do users use the system to assist with? What are the quality requirements? What are the special requirements of the user group and the use environment?
Development-level requirements: What do developers need to achieve? What are the quality considerations during development and maintenance? What situations in the development team will in turn affect the architecture?
2. Constraints
As mentioned earlier, the entire stage revolves around "demand", and the next "constraints" and "quality" limit the demand. So what is "constraint"?
Constraint: Factors restricting the development of the project.
First of all, the constraints come from and restrict the requirements. For example, the "user-level requirements" mentions the "user group characteristics" constraints, which means that this product must consider which user groups to do. To make a children's education software, just The complex theories and logic of adults should not be involved. This is the constraint!
3. Quality
Quality, similar to "constraint", pays more attention to the attributes of a certain thing. Of course, sometimes quality attributes can be used as constraints, such as portability, which can be viewed as quality or as a constraint.
4 Key functions
The key functions include the following four aspects: 1. Core functions; 2. Required functions; 3. High-risk functions; 4. Unique functions.
Five views
That is logical view, development view, running view, physical view, data view.
Each of the five views has a "thinking foothold":
division of responsibilities (logical view).
Program unit organization (development view).
Control flow organization (running view).
Physical node arrangement (physical view).
Persistent design (data view).