Carnegie Mellon University
Browse
A_Strategy_for_Component_Product_Lines-Report_2.pdf (3.81 MB)

A Strategy for Component Product Lines: Report 2: Specification Modeling for Components in a Component Product Line

Download (3.81 MB)

This report is the second in a series to establish a strategy for creating and managing a component product line (CPL); to define a modeling approach for specifying components; and to describe a governance method for making decisions to select a product line, determine the feature sets, and maintain the supplier–user relationship. The strategy considers who creates models, how they are represented, who uses them, and how they are evaluated for use. This report introduces the concept of a “model chain” to describe the models used in specifying a CPL. The model chain concept extends to show relationships between models, how they evolve, and the realization of architecture requirements through the creation–evolution process. The report applies the principles of this framework to three example governance scenarios based on a specification of a common industry standard. The examples include specification views to support the model understanding that a CPL specifier must provide and to create feature, function, and other model analysis attributes so that the supplier and potential users can assess whether or how well a CPL satisfies its specification. The analysis results become key factors in the decision-making process of component selection for integration into a weapon system. 

History

Publisher Statement

This material is based upon work funded and supported by the Department of Defense under Contract No. FA8702-15-D-0002 with Carnegie Mellon University for the operation of the Software Engineering Institute, a federally funded research and development center. The view, opinions, and/or findings contained in this material are those of the author(s) and should not be construed as an official Government position, policy, or decision, unless designated by other documentation. References herein to any specific commercial product, process, or service by trade name, trademark, manufacturer, or otherwise, does not necessarily constitute or imply its endorsement, recommendation, or favoring by Carnegie Mellon University or its Software Engineering Institute. This report was prepared for the SEI Administrative Agent AFLCMC/AZS 5 Eglin Street Hanscom AFB, MA 01731-2100. NO WARRANTY. THIS CARNEGIE MELLON UNIVERSITY AND SOFTWARE ENGINEERING INSTITUTE MATERIAL IS FURNISHED ON AN "AS-IS" BASIS. CARNEGIE MELLON UNIVERSITY MAKES NO WARRANTIES OF ANY KIND, EITHER EXPRESSED OR IMPLIED, AS TO ANY MATTER INCLUDING, BUT NOT LIMITED TO, WARRANTY OF FITNESS FOR PURPOSE OR MERCHANTABILITY, EXCLUSIVITY, OR RESULTS OBTAINED FROM USE OF THE MATERIAL. CARNEGIE MELLON UNIVERSITY DOES NOT MAKE ANY WARRANTY OF ANY KIND WITH RESPECT TO FREEDOM FROM PATENT, TRADEMARK, OR COPYRIGHT INFRINGEMENT. [DISTRIBUTION STATEMENT A] This material has been approved for public release and unlimited distribution. Please see Copyright notice for non-US Government use and distribution.

Copyright Statement

Copyright 2023 Carnegie Mellon University.

Usage metrics

    Exports