Architecture Organization Management

Five Principles of architecture organization management: Conception, rhythm, foresight, collaboration and Simplification

Three Concepts of architecture organization: Principles, models, and anti-patterns

Guidelines: Implementation Details are required to apply the principles to practice. The principle translates a wide range of principles into details about whether and how to execute them.

Mode: Describes the solutions to common problems that may occur when developing or using the software architecture.

Anti-pattern: Describe the traps that organizations may encounter in practice, describe what they should not do, or use solutions in the context of errors.

I. Conception

Explains how to describe a consistent, constrained, and flexible future picture to the beneficiaries of the architecture. Vision requires consistency and coordination (flexibility ).

[In fact, it is consistent with the customer and development team, while considering expansion, to better ensure consistency, you can use the "4 + 1 architecture View" (logical view [user], implementation view [software development engineer], use case view [system analyst], and process view of RUP. [software integration engineer], deployment view [software engineer ])]

[Understand the urgent value of the customer; map the customer value into a solution to solve the problem; convert the above problems into a specific set of constraints]

 

Verification concept criteria:

1. the architect's conception is consistent with that expected by the initiator, user, and end customer.

Anti-pattern: Post-risk [first analyze the problem to identify the possible problems and determine the feasibility. We should take the initiative to provide an option to the upper layer]

Mode: consistent [architecture is used by multiple users. A specific user needs specific functions but may damage the quality and stability of the architecture. The superior should be pulled into the architecture conception to let them know the risks]

2. the implementers trust and use the architecture.

Anti-pattern: Daemon. [after determining the architecture, we should hold a seminar to review the newly added functions for any addition to the architecture, to avoid developers' distrust of the architecture, the acceptance should be fulfilled in a timely manner]

Mode: Three stinks: [the architecture idea is not just for your own architects. advanced ideas are provided, architecture platforms are left to architects, and implementation details are left to developers]

3. The hidden knowledge about architectures and components is visible to users.

Anti-pattern: full coverage [Knowledge Sharing (training, special discussion, and enabling knowledge management platform )]

Mode: Work in turn

[CONCLUSION: The idea is the key to building the architecture, and we are also ideologically determining how to achieve the goal of the architecture. The key to this step is to mobilize the superiors and subordinates, determine the objectives of the superiors, and determine the details of the subordinates, ensure that the requirements are consistent and correct. Finally, knowledge sharing increases team cohesion. Create a team that combines learning applications, and work rotation (learning and Management) when necessary )]

 

Ii. Rhythm

Rhythm principle: depicts a degree of coordination within the entire organization, that is, regular inspection and Planning of product production based on predictable speed, content and quality.

[Rhythm is a recurring and predictable workpiece exchange activity within an architecture group and between it and customers and suppliers, in fact, it is to control the progress of architecture development and solve problems and customers and development teams]

Principles:

1. reevaluate, synchronize, and adjust the architecture on a regular basis. [Regular discussion meetings to discuss and solve problems in a timely manner]

Anti-pattern: One-step success [the release of an architecture is not only for the current or specific features, it should be a complete and systematic architecture. If there is a market opportunity, you can first release a function around the specific, use this topic to seize the market. Release the system version again]

Mode: Release Board

2. The architecture user has a high degree of confidence in the architecture release progress and content.

Anti-pattern: Ultra-agile [organizational behavior cannot be strictly observed when the actions of senior management change organizational behavior more directly]

Mode: Xie bingbao Shuai [when an architecture cannot be released as expected, we should actively communicate with the customer to move less important features to the subsequent release cycle]

3. Clear activities through rhythm coordination

Anti-pattern: Selling untested products [problems cannot be accumulated, regular establishment should be successful]

Mode: synchronous release [determine the order of delivery architecture features with partners]

 

[CONCLUSION: The rhythm emphasizes a plan. The problem cannot be accumulated, and the problem should be solved immediately. When there is a conflict of time, the personnel should be well-trained, and the system should be strictly enforced (the architecture should be evaluated regularly to avoid high-level changes). The architecture should be stable for a long period of time]

 

3. Prediction

Balance between predicting the future and checking and adapting to the current situation

Principles:

1. foresight of risks, foresight of customers, foresight of customer needs, foresight of market-driven standards and evolution of technology, and foresight of changes in strategic business directions

Anti-pattern: missing details (in fact, the demand is not comprehensive, so it is important to involve professional businesses and research coverage]

Mode: Demonstration Zone [conduct an experiment before large-scale promotion]

2. evaluate technical and business risks and opportunities through rapid review and development cycle

3. Adjust the function features and budget in a timely manner when the key estimates or assumptions are incorrect.

[CONCLUSION: in fact, foresight refers to the prediction of the knowledge and market related to the current architecture and architecture, as well as the management of architecture projects]

 

Iv. Collaboration

1. Architects constantly learn who are the most critical beneficiaries, how they contribute value, and what they need

Anti-pattern: simply say no

Mode: Understand your beneficiaries

2. A clear and mandatory contract is concluded between beneficiaries.

Reverse mode: no discussion results are recorded

Mode: mutual benefit

3. Strengthen cooperation through social behavior systems and informal norms.

Anti-pattern: Informal time for formal work

Mode: prevent unexpected events. [early reminders should be given during changes]

Mode: work closely with HR

[CONCLUSION: collaboration is actually about managing and dealing with customers, understanding their needs, and strengthening (recording) the contract to be achieved. In addition, collaboration with lower-level developers and collaboration with various adjacent resources]

 

V. Simplified

Simplification refers to the clever understanding and minimization of the Organizations and environments in which they act, forming an organizational structure and thinking about the architecture.

Principles:

1. developers use the architecture for a long time to reduce the total cost and complexity

Reverse mode: simple replication and Modification

Mode: slow and fast

2. The architecture team clearly understands the key and minimum requirements and constructs them into the core elements of multi-application sharing.

Anti-pattern: lack of effective abstraction [avoid Banyan and root hypertrophy each time you join]

Mode: migration path

3. Long-term budgets and actions ensure that related elements are removed from the core when they are not shared, complexity is increased, or when there are clear business reasons.

Anti-pattern: code is greater than the architecture. [the chief architect's ticket is reasonably allocated to implement new features and adjust the architecture, so that the most competent engineer can lead the implementation of new features]

Mode: statistics component changes

[CONCLUSION: Simplified actually focuses on code simplification and can be abstracted using design patterns]