Premium
Thoughts About Life Cycle Phases
Author(s) -
Lake Jerome G.
Publication year - 1997
Publication title -
incose international symposium
Language(s) - English
Resource type - Journals
ISSN - 2334-5837
DOI - 10.1002/j.2334-5837.1997.tb02224.x
Subject(s) - premise , systems development life cycle , domain (mathematical analysis) , confusion , set (abstract data type) , perspective (graphical) , product life cycle management , computer science , software development process , operations research , software development , engineering , psychology , epistemology , software , mathematics , artificial intelligence , philosophy , mechanical engineering , mathematical analysis , psychoanalysis , programming language
The question “What are the life cycle phases that a system must go through?” has been one of interest and confusion to many folks involved with engineering systems. The problem is that a set of life cycle phases is established from the perspective of a singular domain without consideration or knowledge of other domain life cycles. Thus, when a discussion is held with someone outside a particular domain, the life cycle phases are found to differ significantly by number, name, and purpose. These differences create confusion, misunderstanding, and often conflict. This paper is designed to put some order to the various domains of thought about life cycles. Four kinds of life cycles are discussed: Acquisition, Project, Development , and P roduct . The key life cycle of these four is Development. How this life cycle relates to the other three is a focus of this paper. The Development Life Cycle is akin to the spiral model and incremental builds approach used for software development. The premise is that life cycle phases are defined and implemented to manage the inherent risks involved with engineering a system.