Model-Based Product Line Architecture and Analysis. SEDC 2014 Conference Friday, 04 April 2014. Sean McGervey Systems Architect Sean.McGervey@jhuapl.edu. Acknowledgements. Tamara Valinoto Chairperson of Northrop Grumman’s MBE Community of Practice Sounding board
Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author.While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server.
Model-Based Product Line Architecture and Analysis
SEDC 2014 Conference
Friday, 04 April 2014
During Product Development, system attributes captured in the system model can be parametrically related to technical measures and analyzed by an integrated MDAO framework
Kernel Use Case
Optional Use Case
Failing to appreciate that can result in unforeseen time and money modifying a component to fit a new product context
Reusing a component means reusing all the requirements and architectural decisions that drove its development
Development starts with specifying the new product in terms of the product line’s architecture constraints, and determining which components are already provisioned and which must be developed.
New components are developed using the domain specific modeling language for the product line, and their design is verified using the integrated MDAO framework.
Verified components are added to the collection of provisioned components for the product line, and can be used in future product development.