I used to think that the architect is a job that is not expected, and it is impossible to receive relevant knowledge in this life. However, in the first-line architect's practice guide, through the description of the architect's work in the book and the analysis of its implementation process, the gap between the architect and the architect is gradually narrowed from the thought. The architect is also Mortal, he also does what human beings can do, but only from a different standpoint. He can look at the whole problem at a height that ordinary people can't reach, and he can plan for the system as a whole with precautionary thinking.
The third chapter mainly introduces the actual role of pre-architecture. Pre-architecture is a stage in the admems method. The following is the definition of it in the book.
What is 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.
This stage can solve the following problems:
Analyze the derivative needs behind business needs and constraints
Discover missing requirements
Identify key functions
Determine key quality
Weighing the contradictory relationship between attributes
In the pre-architecture stage, it can help the architect to excavate the three requirements levels of business, user, and development in its construction process, and the three types of requirements of function, quality, and constraints are more and deeper. Requirements, this process is of great significance to the practice of architecture, so in the pre-architecture stage, the analogy of its image in the book is to sharpen the knife before cutting wood, which helps the architect to clear its process during the construction process. The context of requirements, to better understand the clear and deep requirements, so as to increase the probability of success in the architecture.
The basis of architectural design thinking: different requirements affect different principles of architecture
This means that requirements determine architecture, but different requirements affect different principles of architecture. This process mentioned the critical requirements determination architecture in the previous chapter, and the rest of the process of verifying the architecture of the requirements is the same idea. The different principles that affect the architecture of different requirements are summarized in the book.
Function is the basis for discovering responsibilities
Quality is the driving force for perfecting architectural design
The impact of constraints on the design of the architecture is divided into several categories
Functions : The impact on architecture design among them is also clearly defined in the book: each function is completed by a "responsibility collaboration chain". The architect assigns the responsibility to the function by planning the responsibility collaboration chain for the function Subsystems, defining interfaces for subsystems, determining interface-based architecture design
Quality: (must) based on the current intermediate results of the architectural design, further consider the specific quality requirements, refine, adjust, or even reverse the intermediate results of the architectural design, step by step to improve the architectural design
Quality and function together affect the architecture design, it is impossible to design the architecture based on the quality requirements aside from the function
Constraint: A multiplier that directly restricts design decisions (for example, "the system runs on a Unix platform")
Transform into constraints of functional requirements (for example, "the bank system implements the current interest rate" leads to the "interest rate adjustment" function)
Reformulated as a constrained demand quality attribute (e.g., "computer teller average level is not high," Easy extraction with requirements)
Chapter 4 mainly analyzes the structure of demand and the impact of analysis constraints
The first two steps of pre-architecture:
I.e. demand structuring and analysis of constraints
Why do you need to structure the requirements? Because the requirements are structured, the admems method for the process of requirements structure is a real practice of architectural design. Through the admems matrix thinking tool, you can fully understand the various levels of the requirements and the original requirements The meaning of is multi-faceted and displayed three-dimensionally, that is, the metaphor in the demand is excavated to restore the more original demand relationship.
Although the specifications explain the specifications in detail, they are not the decree pursued by the architect in the specifications. The perspective of the architect station is at a higher level. The demand changes are frequent, and the demand must be rationally analyzed. Then choose to add.
Why analyze constraint effects:
Because there are a lot of risk factors hidden in the demand, if you don't think about it, then it is sometimes fatal for the overall architecture.
The description in the book is: Once you forget it, he will come to the door to create trouble.
As far as architecture design is concerned, if you feel like introducing it, you can deal with these troubles. During the pre-architecture stage, it is necessary to analyze the influence of constraints. This is a kind of proactive thinking.
There is a theory of constraint classification in admems. He asked us to understand the business environment, the use environment, and the construction environment to consider customer users and developers.
For specific problems, to carry out targeted considerations, for multi-party users often need to consider such a process.
Constraints are the context of architectural design, that is, the joints in architectural design that connect the entire part of the architecture.
As the book says: it is impossible to become an architect without a big picture. Constraints are the context in which architecture design must resolve problems
Architects must understand the overall situation at a higher level than ordinary people, otherwise it may be fatal to the overall design, or it will directly lead to overall failure. For this environment, there are many aspects High-level detailed analysis and consideration of the system, environment, and stakeholders
During the analysis, derivation, leak detection and other methods can be used.