Architecture Design __ Architecture Design

This topic
First, what is the structure
Ii. role in the project
Iii. responsibilities and work content of the architect
Iv. Architecture Workflows
Five, the architect growth path
VI. Architecture Competency Model
Vii. Expansion of knowledge

First, what is the structure
Architecture is the blueprint of the system, describing the structure and key decisions of the system. Including the functional and non-functional requirements of the system, how to implement, how the system and subsystem are divided, how the system communicates, how the system functions are designed and interacted.
Contains important architectural decisions, system composition, functional design, technology selection, cost analysis, etc.
The architecture is based on the design of systems that meet customer needs, including functionality, non-functional, and quality and constraints.

Ii. role in the project
Customer: People who pay for system development pay attention to the business value of the system.
Users: People who use the system, pay attention to whether to meet the functional requirements, improve efficiency and usability, and so on.
Project manager: Responsible for project management, organization, coordination, communication and other management work.
Demand analyst: Responsible for requirements related work, such as business analysis, demand acquisition, demand research, demand management, writing requirements specifications, etc.
System Architect: Responsible for the overall system analysis, architecture planning, technology selection, core functional requirements and non-functional requirements of the architectural design.
System Designer: On the basis of architecture model, the detailed design of core function and Non-core function is carried out.
Developer: Coding and unit testing are done according to the architecture design and detailed design to achieve the measurement standard.
Testers: Verify that development capabilities meet requirements, such as functional testing, integration testing, performance testing, stress testing, safety testing, regression testing, etc.
Operational personnel: Responsible for the deployment of the environment, deployment and day-to-day maintenance.

Third, architect responsibilities and work content
The architect plays a connecting role in the project. The proposal participates in the whole process of the system construction process. The responsibilities of the
Architect are as follows:
1 support pre-sales or requirements phase, provide conceptual framework or technical consultation;
2) system analysis, architecture design, technology selection, output architecture solution;
3 Guide Project team members to complete, develop, test and publish in accordance with architectural design. 4) development or design of the development framework, develop coding/programming specifications, Design architecture prototypes, validate schema prototypes,
5) organize technical or architectural training, grasp technical/architectural direction,
6 program balance (Implementation and cost), stakeholder communication, technical risk management, technology leader, etc.
by project phase, Brief description of the work, as follows:
Pre-sales phase, give business support, provide system solutions and architecture consulting. The
requirements phase, together with the requirements analyst, participates in demand communication and assists in the completion of technical/business consulting and requirements models. (A good architect is a business expert at the same time)
Architecture phase: Carry on the system analysis and design, carry on system abstraction, design system model, carry on the technical prototype, develop the architecture prototype and so on
design stage: Instruct the design person to complete the detailed design;
Development phase: Instruct the developer to implement the design and solve the technical problems.
Test phase: Directs testers to test work, especially non-functional requirements.
Publish phase: Directs the deployment personnel to deploy in accordance with the deployment architecture, answering or responding to the architectural issues during the trial run in a timely manner.
Other work: Technology selection, personnel training, technical guidance

Iv. Architecture Workflow
The architecture workflow is a process and method of how a system is from the requirements, the architecture to the implementation.
A good architecture requires the architect to have good (rich) business knowledge in addition to technical and architectural design capabilities. From the perspective of software engineering, architects are required to participate in the requirements analysis phase, development, testing, release, commissioning phase, in addition to participating in the architecture design phase of the system.
This section describes the process of schema work from the requirements model and solution model. The
mainly includes requirements model, architecture model, design model, solution model, four aspects.
Requirements Model: Participate in requirements analysis and requirements model design, provide technical advice or guide requirements definition, provide solution guidance.
Main participants: requirements analyst, business Analyst
Helper: Architect, designer
Architecture model: According to the requirement model, output architecture model.
1) Select the Schema object: Key processes, core use cases, and non-functional requirements;
2) Process modeling: Combing the key requirements process, analyzing business objects, subsystems, modules, designing the interactive process of the system;
3 Domain Modeling: Carding the objects involved in the business process, subsystem modules, dividing subsystems, Modules, core objects, communication mechanisms, transaction models, etc.
4) output overall architecture: According to the domain model and business process model, combining component architecture, deployment architecture, communication mechanism, output system body architecture scheme.
5) Schema validation: Validates schema availability, and can be reviewed or validated by actual testing in the form of a review or schema prototype.
Main participants: Architects, architecture Committee
Helper Participants: System architect, developer, tester
Design Model: Under the guidance of architects, complete subsystems, modules, functions, interfaces, or detailed designs, based on the system architecture.
Main participants: System architect, senior Engineer
Helper Participant: Architect
Solution Model: Architecture model, design model, architecture prototype, etc. unified Architecture solution.
A complete system architecture should include: overall architecture, subsystems, modules, functional overviews or detailed design, communication mechanisms, transaction mechanisms, interface definition (internal, external), domain model, business process, database design, middleware, component architecture, deployment architecture, etc.
System Architecture solution Standard
1 to meet the functional and non-functional requirements of the system,
2) meet the requirements of the project scale and cost,
3 to meet development, testing and release requirements;

Five, architect growth path
Nature: Learning, practice, summarization, personal progress and the process of capacity growth.
Development Engineer: Mainly under the guidance of the development or independent development of simple functions. The core of this stage is to learn the technology itself, do some more projects, diligence, thinking, summary. This is the time to learn, practice to improve their skill level continuously. Free time can learn some design patterns, software engineering knowledge, used to expand horizons and prepare for senior engineers.
When your technical ability, project experience, coding level, design capability to a certain extent, you can upgrade to a senior engineer.
A Word: Write code, accumulate experience.
Senior Engineer: can independently or lead the engineer to be responsible for the design and development of a module/system, have certain experience in technology and project. This stage can be based on their own career objectives to choose in-depth technology or learning management knowledge.
Learning Directions: depth of technology, breadth of technology, distribution, architecture knowledge and management knowledge.
A Word: Technology in-depth comprehensive, thinking about the perfect system design.
System Architect (Technical expert): In a certain aspect of technology to reach a certain depth, in some ways have their own insights and independent problem-solving capabilities. Can lead a technical team to carry out development and management work. Can complete the requirements analysis, system design, technology selection, architecture design, development and management work.
A word: Technical experts, architecture practices and management capabilities.
Senior Architect: Experienced in large projects, multiple project requirements analysis, system architecture, System design, project management, etc. In the breadth and depth of technology, business knowledge has professional achievements.
Word: Large projects, domain experts and solutions.
Technical Director, CTO, vice President of Technology: responsible for the company's overall technical planning, technical management, grasp the technical direction, proficient in business and technology, with good communication, organization and coordination capabilities.
A word: direction, process, system, specification, management.
The above is a personal summary of the position and ability, for reference.

VI. Architect Competency Model
From the macroscopic point of view and the specialized field, the architect's competency model is briefly introduced.
6.1 Macroscopic angle
Depth: Having a certain depth in one or more technical fields, mastering the characteristics of the technology, adapting to the scenes and disadvantages
Breadth: A number of technologies, mastering non technical knowledge, such as requirements, projects, management, etc.
6.2 Specialized Fields
Technology: Proficient in one or more aspects of technology, have their own insights and practical experience;
Business: Proficient in the field of business knowledge, to achieve or basically reach the field of expert level;
Architecture: Proficient in requirements analysis, system architecture, design model, architecture model, rich experience in architecture;
Management: Proficient in technical management, project management and general management knowledge and ability;

VII. Architecture Extension Knowledge
The following can be filled by the brain.
1. Software Engineering
2. Demand Engineering
3. Project Management
4. Stakeholders, stakeholder