Passed Review
Relationships
Contents
Practice: Evolutionary Architecture
Practice: Iterative Development
Practice: Two-Level Project Planning
Architectural Constraints
Architectural Goals
Architectural Mechanism
Architecturally Significant Requirements
Coding Standard
Construction Phase
Developer Testing
Elaboration Phase
Executable Architecture
Key Abstractions
Metrics
Micro-Increments
Pattern
Phase Milestones
Project Lifecycle
Refactoring
Risk
Software Architecture
Transition Phase
Whole Team
Architecture Notebook
Developer Test
Implementation
Iteration Plan
Project Plan
System-Wide Requirements (FURPS+)
Test Case
Test Script
Use-Case Model
Work Items List
Agile Estimation
Assign Changes to an Iteration
Daily Meetings
Detail Use Cases and Scenarios
Iteration Planning
Layering
Maintain a Sustainable Pace
Refactoring
Self-Organize Work Assignments
Software Reuse
Staffing a Project
Test Ideas
Iteration Burndown Report
Project Burndown Report
Project Plan
Work Items List
[Project Definition and Scope]
[Project Work]
[Software Implementation]
[Technical Specification]
Architecture Notebook
DeveloperTest
Implementation
Project Plan
Risk List
System-WideRequirements
Test Case
Use Case
Vision
Iteration Burndown
Project Burndown
Architecture Notebook
Iteration Plan
Project Plan
System-Wide Requirements Specification
Use-Case Specification
Work Items List
Use Rational Method Composer to Update the Process
Create Test Cases
Detail Use-Case Scenarios
Identify and Outline Requirements
Implement Tests
Outline the Architecture
Refine the Architecture
Run Tests
Architect
How to adopt the Evolutionary Architecture practice
How to Adopt the Two-Level Project Planning Practice
Whole Team