IBM迭代需求管理术语
IBM Rational Suite AnalystStudio 进行迭代需求管理术语
Known customer requirements：已知客户需求
Classical requirements definition methods lead to analysis out of line with requirements：经典需求定义方法导致分析与需求不一致
If the project cannot include requirements changes, the solution meets the initial analysis but not the current customer requirements.：如果项目不能包含需求变更，那么解决方案仅满足了最初的分析，而不满足当前的客户需求。
Time：时间
Requirements analysis：需求分析
Analysis：分析
Solution Development：解决方案开发
Release：发布
Meeting business requirements in time without iterative requirements management is difficult：如果没有迭代需求管理想及时满足业务需求将是一件很困难的事情。
What the business requests：业务要求什么
What the solution does, according to the cost and deadline：解决方案按照成本和时限做了什么
Resources spent on low priority requirements：资源花费在低优先级的需求上
High priority requirements not met：高优先级需求没有被满足
In short deadlines, focusing on high priorities is difficult：在短时限中，很难专注于高优先级的项目。
Collecting and changing the requirements：收集和变更需求
Deciding the scope of requirements to process：决定要处理的需求的范围
Propagating and processing the requirements：传播和处理需求
Checking the coverage of requirements：检查需求的覆盖
No requirements management：没有需求管理
Text processor：文本处理器
Database：数据库
Text processor and database：文本处理器和数据库
Requirements management solution：需求管理解决方案
Integrated requirements management solution：集成需求管理解决方案
Requirements management approaches and their limits：需求管理方法以及它们的限制
The solution to keep developments in line with requirements is iterative requirements management：保持开发与需求一致的解决方案就是迭代需求管理。
Analysis：分析
Design：设计
Collection Change：收集变更
Decision：决定
Development cycle：开发周期
Requirements(initial, new, changed)：需求（初始、新的和变更过的）
Propagation Process：传播过程
Check：检查
Developme