COMS309Review1

COMS309Review1 - COMS 309 Weiss Fall 2010 Review1 Software...

Info iconThis preview shows pages 1–11. Sign up to view the full content.

View Full Document Right Arrow Icon

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
This is the end of the preview. Sign up to access the rest of the document.

Unformatted text preview: COMS 309 Weiss Fall 2010 Review1 Software Product-Line Engineering: A Family- Based Software Development Process: Review David Weiss [email protected] COMS 309 Weiss Fall 2010 Review1 Product Engineering Environment A FAST Process Domain Engineering Product Engineering Products Feedback Investment Payback 2 Domain Model System Composition Mapping COMS 309 Weiss Fall 2010 Review1 The Domain Model • Conceptual Framework – Family Defnition • Commonalities and Variabilities Among Family Members • Common Terminology ¡or the Family • Decision Model – Economic Analysis – Product Line Architecture – Optional: Application Modeling Language (AML): Language ¡or stating requirements • Mechanism ¡or generating products – Composer or Compiler (AML) 3 COMS 309 Weiss Fall 2010 Review1 The Conceptual Framework (1) • Qualify The Domain – Is it economically viable? – Artifact: Economic Model • De¡ne The Family – What do members of the family have in common and how do they vary? – Artifact: The Commonality/Variability Analysis • De¡ne The Decision Model – What decisions must be made to identify a family member? – Artifact: The Decision Model Table 4 COMS 309 Weiss Fall 2010 Review1 The Conceptual Framework (2) • Create The Architecture – What is a good modular structure. a good uses structure, and a good process structure? – Artifacts: Module Guide, Interface Speci¡cations, Uses Relation, Process Structure • Design The System Composition Mapping – What modules are needed for which decisions? – Artifacts: System Composition Mapping, Uses Relation • Design The Product Engineering Environment – What are good mechanisms for using the decision model to produce products or to generate products from the AML? – Artifacts: Decision Model GUI, Generator or Compiler (AML) 5 COMS 309 Weiss Fall 2010 Review1 Architecture for the Product Line • Purpose: Enable product generation through composition of modules, each module hiding a parameter of variation • Apply information hiding to create a modular architecture – Each variability is the hidden decision of a module • DeFne interface speciFcations for each module • DeFne a uses relation among programs that appear on module interfaces • DeFne a process structure 6 COMS 309 Weiss Fall 2010 Review1 The Product Engineering Environment: Specifying A Product Using The Decision Model 7 COMS 309 Weiss Fall 2010 Review1 Decision Model and System Composition Mapping 8 COMS 309 Weiss Fall 2010 Review1 The Decision Model • The set of decisions needed to specify a product in the product line, the ordering of the decisions, and the constraints on and among the decisions 9 COMS 309 Weiss Fall 2010 Review1 The Decision Model • What decisions must I make to specify a product in the product line?...
View Full Document

This document was uploaded on 10/16/2010.

Page1 / 49

COMS309Review1 - COMS 309 Weiss Fall 2010 Review1 Software...

This preview shows document pages 1 - 11. Sign up to view the full document.

View Full Document Right Arrow Icon
Ask a homework question - tutors are online