Definition of a schema: 1, according to the problem to be solved, on the boundary of the target system to define; 2, and a target system according to the principle of segmentation performed; 3. 2, enabling organic connection between the parts , and assemble as a whole, all the work of the target system.
Architect of six classic puzzles: four practical problems confusion: the system is divided into modules, how to be more reasonable? Large system architecture design, how to get started? Always feel demand is very bad influence architecture design! Important non-functional requirements, but how to design? Confused two career development: architecture novice: lack of guidance, architecture design at a loss. Architecture veteran: the lack of summary, still "fear" next project
4 core architecture proposition: methodology is the trend, question-driven architecture, multi-stage and multi-view, built-in best practices. Practice essentials: functional requirements affect the basic principles of architecture: collaboration duty chain; basic principles of quality requirements affect architecture: further questioning; analysis of constraints affect the basic principles of architecture: direct constraints into a function or quality requirements