Premium
A Life Cycle for Commercial and Aerospace Systems Discovery
Author(s) -
Oliver David W.
Publication year - 1994
Publication title -
incose international symposium
Language(s) - English
Resource type - Journals
ISSN - 2334-5837
DOI - 10.1002/j.2334-5837.1994.tb01776.x
Subject(s) - waterfall model , product lifecycle , aerospace , systems development life cycle , computer science , product life cycle management , waterfall , systems engineering , system lifecycle , rapid prototyping , process (computing) , engineering , new product development , software development process , software , software development , operating system , history , programming language , aerospace engineering , mechanical engineering , archaeology , marketing , business
This paper defines a life cycle that is tailorable to either commercial or aerospace system developments. The tailorability is accomplished by separately describing the product life cycle, the acquisition cycles, and the technical steps used in performing the systems engineering. In addition this life cycle is based on the discovery of issues. The life cycle described here differs from both the Waterfall Model, (Royce 1987), and the Spiral Model, (Boehm 1986), in significant ways that make it applicable to the work that occurs on time and cost sensitive projects. The waterfall model defines a set of phases through which the project passes, but does not describe the manner in which actual projects loop back to prior phases when issues are discovered which require revisiting prior work. The spiral model defines progress through a series of prototypes, but does not root the prototypes in particular engineering goals. In the discovery life cycle a set of normal forward phases is defined. The process for handling issues is described as a separate Change Management process which may be initiated at any step of engineering and may lead to any other step of engineering for resolution. In the discovery life cycle prototyping is associated with particular activities: Rapid prototyping to define and demonstrate product function to operators and users to verify and refine requirements Early prototyping to remediate risk by demonstrating feasibility. Sequential release of products in a product line. Sequential build designed to facilitate early stimulus/response thread validation through the system as it is integrated.