系统与软件产品线工程 46p.pptVIP

* Source Code as Gears SPL AssetsFeature-based Software Development * Source file Variation Point with Variants, Logic and Projection * Multi-baseline Management for SPL Key: Alpha release Beta release Public release Asset L Asset 2 Asset 1 Asset 3 ... ... Product A Product B Product N Baseline M ... Baseline 4 Baseline 3 Baseline 2 Baseline 1 SPL AssetManagers ReleaseManager * Gears File-based Variation Points File system extended with Feature-based SPL variation points Optional files Variant files Optional directories Variant directories Variant text transformations Optional text blocks * SPL Requirements Engineeringwith the DOORS/Gears Bridge * Early Generation SPLRequirements Engineering for Product Lines Early generation product-centric approaches lead to exponential complexity Clone-and-own (and requirements branching) For each new product, make a copy of requirements and modify Optionally add links to track commonality and variations Leads to expensive duplication, divergence and merging Attributes, links, scripting Tag each requirement with one or more attributes about product diversity Leads to high overhead Major effort to define and implement attributes, dictionaries, semantics, schemas, scripts and filters Labor intensive to revisit all requirements and attributes during maintenance and portfolio extension One-size-fits-all Write the portfolio variations and diversity directly into the requirements text Leads to complexity and errors interpreting requirements for any particular product * DOORS Requirements as Gears SPL AssetsFeature-based Requirements Engineering * DOORS/Gears Bridge Dual Plugin “Bridge” between DOORS and Gears SPL Framework Gears plugin extensions Automated configuration of DOORS requirements, based on Gears feature profiles DOORS plugin extensions Any requirement can be converted into a first-class Gears variation point BigLever SoftwareGears DOORS/GearsBridge RationalDOORS * DOORS/Gears Variation Points DOORS extended with Fe