IBM Software Group Mastering object-Oriented Analysis and Design With UML Module 1: Best Practices of Software Engineering Rational software
Trace Symptoms to Root Causes Symptoms Root Causes Best Practices Needs not met Insufficient requirements Develop Iteratively Requirements churn F Ambiguous communications Modules do not fit Brittle architectures Manage Requirements Hard to maintain Overwhelming complexity Use Component Architectures Late discovery Undetected inconsistencies Poor quality Poor testing Poor performance Subjective assessment Model Visually(UMI Colliding developers Waterfall development Continuously Verify Quality Build-and-release Uncontrolled change Insufficient automation Manage Change
Practice 1: Develop iteratively Best Practices Process Made Practical Develop Iteratively Manage Requirements Use Component Architectures Model Visually (UML) Continuously Verify Quality Manage Change H
Practice 2: Manage Requirements Best Practices Process Made Practical Develop Iteratively Manage Requirements Use Component Architectures Model Visually (UML) Continuously Verify Quality Manage Change :M
Aspects of Requirements Management ◆ Analyze the problen Understand User needs ◆ Define the Systen ◆ Manage Scope Refine the System Definition Manage Changing Requirements