The appropriate software architecture-reading experience

Five years of work, management and design work have been done, the next stage of the main work in the framework design, team technical training, recently met to read a few books, such as "appropriate software architecture", something more, pick some important notes below.

1. Shall not be allowed to do so;

A good fit for architecture design or development, and is consistent with the concept of agile development.

2. Package boundaries are key skills in software architecture design

The key reason for this is that only the encapsulated, defined boundaries of the module or component, module or component itself can be freely modified without affecting the user.

3. Risk-driven software architecture

4. What the system does not do, and what the system does is equally important

To ensure the quality attributes of a system, you must impose constraints to express things that you cannot do, and this has many advantages:

4.1 Can embody judgment without passing on the complete knowledge of other personnel

4.2 Promoting the integrity of the concept

4.3 Reduction of complexity

4.4 Understanding run-time behavior

The appropriate software architecture-reading experience