好的实践经验(Best Practices ▣迭代的软件开发(Develop iteratively） ▣需求管理(Manage Requirements) ▣使用基于构件的体系结构(（Use Component Architectures) ▣可视化软件建模(Model Visually） 口验证软件质量(Verify Quality) ▣控制软件的变更(Control Changes)
好的实践经验 (Best Practices) 迭代的软件开发 (Develop iteratively) 需求管理(Manage Requirements) 使用基于构件的体系结构 (Use Component Architectures) 可视化软件建模 (Model Visually) 验证软件质量 (Verify Quality) 控制软件的变更 (Control Changes)
Develop iteratively 为什么要迭代开发？以前的瀑布模型有什么问题呢？ ◆ Delays confirmation of critical risk resolution Waterfall Process ◆ Measures progress by assessing work Requirements products that are poor analysis predictors of time-to- Design completion Code and unit test ◆ Delays and aggregates Subsystem integration integration and testing System test ◆ Precludes early deployment ◆ Frequently results in major unplanned iterations
Develop iteratively 为什么要迭代开发？以前的瀑布模型有什么问题呢 ?
Develop iteratively (cont. Iterative Development Produces an executable Requirements Analysis Design Planning Implementation Initial Planning Management Environment Test Evaluation Each iteration Deployment results in an executable release
Develop iteratively (cont.) Iterative Development Produces an executable
Develop iteratively (cont. ▣Risk Profiles Waterfall Risk Risk Reduction Iterative Risk Time
Develop iteratively (cont.) Risk Profiles
Requirements Management Making sure you solve the right problem build the right system by taking a systematic approach to ■eliciting 如何启发、组织所需要的 功能和约束，以及如何为 000 organizing 它们建立文档，如何管理 documenting 各种折衷方案和决策，使 managing 易于表达商业需求和交流 the changing requirements of a software application
Requirements Management 如何启发、组织所需要的 功能和约束，以及如何为 它们建立文档，如何管理 各种折衷方案和决策，使 易于表达商业需求和交流