Advocated requirements process: Step 1: structural requirements, Step 2: Effect of Constraints, Step 3: Identify the critical mass, Step 4: identify key features.
Define profile architecture: meet the "architecture + interaction = Component" basic definition; for high-level components of "responsibility" in general defines and gives the relationship between high-level components; should not deal with interface details. Industry Status: mistakenly "outline framework" is equivalent to "ideal architecture"; architectural design is functional demand-driven, right? Architecture design is the use case-driven, right? In fact, the driving force of architecture: function + Quality + constraints. Mistake "stage" when the "view." SUMMARY architecture phase or conceptual view? Phase relationship has reflected the view reflected in a parallel relationship; outline architecture phase to form a stable high-level architecture design based on the results of the major needs, special needs, high risk requirements.
Practice Essentials: Shaping summary of significant demand architecture. SUMMARY architecture phase of three steps: preliminary design key features based on comprehensive preliminary design determine the high-level segmentation. Consider non-functional requirements make the appropriate decisions.
Summary preliminary design architecture. 1, the preliminary design goal is to discover responsibilities, the use of "cooperation responsibility chain" principle draw robust map. Preliminary design principle: the preliminary design goal is to "find responsibility" lay the foundation for the high-level segmentation; preliminary design "is not" necessary, but "pending design system" for architects did not have much direct experience in terms of time, it is strongly recommended that the preliminary design; based on key features (but not all functions), with robust map (instead of sequence diagram) preliminary design.