By "engineer", we mean all of the activities involved in planning, producing, delivering, deploying, sustaining, and retiring products. PLE works by considering a portfolio as a single entity to be managed, as opposed to a multitude of separate products to be managed individually.
By bringing a PLE Factory approach to systems and software engineering, organizaions can achieve order-of-magnitude improvements in engineering cost, time to market, productivity, product line scalability, and product quality. This report describes the concepts needed when creating core assets with included variability.
These concepts provide guidelines to core asset creators on how to model the variability explicitly, so it is handled consistently throughout the product line and managing the variability becomes feasible. Software Engineering Institute. Publisher: Software Engineering Institute. Abstract A software product line is a set of software-intensive systems that share a common, managed set of features satisfying the specific needs of a particular market segment or mission and that are developed from a common set of core assets in a prescribed way.
Benefits Product lines can help organizations overcome the problems caused by resource shortages. Example organizational benefits include: Improved productivity Increased quality Decreased cost Decreased labor needs Decreased time to market Ability to move into new markets in months, not years This collection includes two decades of SEI work on software product lines.
Collection Contents. Results per page 5 10 Northrop , Paul C. Bergey , Gary Chastek , Sholom G. Cohen , Patrick Donohoe , Lawrence G. Jones , Robert W. Krut, Jr. Clements This report describes the experience of a company that builds large, complex, embedded, real-time shipboard command-and-control systems as a product line.
Jones , Linda M. Northrop Presented: June read. Bergey , Matt Fisher , Brian P. Gallagher , Lawrence G. Northrop This report provides background information to inform other reports in an SEI-published series of reports designed to provide concise and usable information about product line acquisition practices.
Cohen This case study describes a DoD weapon system development effort and compares the current way of developing software systems to the product line approach. Clements , Sholom G. Cohen , Patrick Donohoe , Linda M. Northrop This report is a case study of the Control Channel Toolkit CCT , a software asset base for a software product line of ground-based spacecraft command and control systems built under the direction of the NRO.
Bergey , Wolfhart B. Goethert This report describes the approach a DoD organization used to develop alternative acquisition strategies and analyzes the pros and cons of each. Bergey , Lawrence G. Jones Some basics of software product line practice, the challenges that make product line acquisition unique, and three basic acquisition strategies are all part of this white paper.
Bergey , Dennis B. Rather, it makes engineering assets from across the entire lifecycle — requirements, designs, test cases, user documentation, project plans, and more — first-class citizens, and encompasses not only software-based systems, but also systems in which software plays a diminished or no role.
With pragmatic 2GPLE approaches, languages for expressing variation are more uniform and simpler, reflecting only what is needed in practice. Automation to support asset and product derivation from shared assets has moved out of the research labs and into real-world industrial-strength application, gaining robustness, simplicity, and usability. The best resource for learning about 2GPLE is www.
Additional resources include:.
0コメント