Đang chuẩn bị liên kết để tải về tài liệu:
Chương 6: Requirements Evolution

Every evolution cycle produces a new version of the RD. A new version may be a revision or a variant. | Requirements Engineering From System Goals to UML Models to Software Specifications Axel Van Lamsweerde Chapter 6 Requirements Evolution start Chap. 2: Elicitation Chap. 3: Evaluation alternative options agreed requirements documented requirements consolidated requirements Chap. 4: Specification Chap. 5: Quality assurance Chap.1: RE products and processes Chap. 6: Evolution management Requirements evolution: outline The time-space dimensions of evolution: revisions and variants Change anticipation Traceability management for evolution support Change control: Change initiation/Change evaluation & prioritization/Change consolidation. Runtime monitoring of requirements and assumptions for dynamic change. The time-space dimensions of evolution: revisions & variants Version: Every evolution cycle produces a new version of the RD. A new version may be a revision or a variant. Revision: results from changes made to correct or improve the current version of a single product. Variant: result from changes made to adapt, restrict or extend a master version. Revisions result from evolution over time Variants result from evolution across product lines. The time-space dimensions of evolution: Evolution types and causes Changes in RD may be of different types, caused by different factors, resulting in different types of versions and operated at different phases of software lifecycle. The linking of change causes, types, results and timing there is indicative of the complexity of the evolution process. Change anticipation Anticipation: effective support of changes in system objective, conceptual structures, requirements, assumptions, from the very beginning of the project. Change anticipation: classifying a requirement/assumption as: Stable or Volatile from one system revision to the other. Common or distinct from one system variant to the other. Associates levels of stability or commonality with statements. Ex. Figure 6.2 suggests a feature ranking for the Meeting . | Requirements Engineering From System Goals to UML Models to Software Specifications Axel Van Lamsweerde Chapter 6 Requirements Evolution start Chap. 2: Elicitation Chap. 3: Evaluation alternative options agreed requirements documented requirements consolidated requirements Chap. 4: Specification Chap. 5: Quality assurance Chap.1: RE products and processes Chap. 6: Evolution management Requirements evolution: outline The time-space dimensions of evolution: revisions and variants Change anticipation Traceability management for evolution support Change control: Change initiation/Change evaluation & prioritization/Change consolidation. Runtime monitoring of requirements and assumptions for dynamic change. The time-space dimensions of evolution: revisions & variants Version: Every evolution cycle produces a new version of the RD. A new version may be a revision or a variant. Revision: results from changes made to correct or improve the current version of a single product. Variant: .