Understanding Quality Attributes 3.1 Functionality 3.2 Quality Attribute Considerations 3.3 Specifying Quality Attribute Requirements: Quality Attribute Scenarios 3.4 Achieving Quality Attributes through Architectural Patterns and Tactics 3.5 Designing with Tactics 3.6 Analyzing Quality Attribute Design Decisions: Tactics-Based Questionnaires 3.7 Summary 3.8 For Further Reading 3.9 Discussion Questions 4. Why Is Software Architecture Important? 2.1 Inhibiting or Enabling a System’s Quality Attributes 2.2 Reasoning about and Managing Change 2.3 Predicting System Qualities 2.4 Communication among Stakeholders 2.5 Early Design Decisions 2.6 Constraints on Implementation 2.7 Influences on Organizational Structure 2.8 Enabling Incremental Development 2.9 Cost and Schedule Estimates 2.10 Transferable, Reusable Model 2.11 Architecture Allows Incorporation of Independently Developed Elements 2.12 Restricting the Vocabulary of Design Alternatives 2.13 A Basis for Training 2.14 Summary 2.15 For Further Reading 2.16 Discussion Questions 3. What Is Software Architecture? 1.1 What Software Architecture Is and What It Isn’t 1.2 Architectural Structures and Views 1.3 What Makes a “Good” Architecture? 1.4 Summary 1.5 For Further Reading 1.6 Discussion Questions 2.
0 Comments
Leave a Reply. |