Life Cycle Model

From apppm
(Difference between revisions)
Jump to: navigation, search
(Development Phase)
(Case Example Development Phase)
Line 23: Line 23:
  
 
==== Case Example Development Phase ====
 
==== Case Example Development Phase ====
The case company A, experiences unpleasant feedback from their customers on one of their products. The need for change is recognised and the decision to improve the situation is taken (proposal to system design). The company asses the extend of the problem. Internal as well as external factors are included in order to pinpoint the origin of the problems. The key stakeholders are identified and the area of solution defined. The search for solutions trough creative methods leads to the creation of concepts which are evaluated, which may be evaluated using tools such as Cost-Benefit Analysis or an evaluation matrix with a specific set of criteria (preliminary study)
+
The case company A, experiences unpleasant feedback from their customers on one of their products. The need for change is recognised and the decision to improve the situation is taken (proposal to system design). The company asses the extend of the problem. Internal as well as external factors are included in order to pinpoint the origin of the problems. The key stakeholders are identified and the area of solution defined. The search for solutions trough creative methods leads to the development of concepts, which may be evaluated by using tools such as Cost-Benefit Analysis or an evaluation matrix with a specific set of criteria (preliminary study).
 +
The preferred concept is specified and analysed in detail to establish the effect that can be expected to influence the system (main study). Finally each of the systems parts are studied in detail in order to ensure that the concept addresses all issues raised in the first step in a high quality.
  
 
=== Realisation Phase ===
 
=== Realisation Phase ===

Revision as of 15:37, 13 November 2014

The Life cycle model is one of two methodical concepts that build the basis for system engineering. Next to the Problem-Solving concept, which deals with the challenge of developing solutions for project management challenges, the Life Cycle Model aims to structure the life of an engineering system. The model divides the life cycle in four phases, which include development, realisation, utilisation and disposal. Each phase is defined by a distinct a set of criteria, purpose and expected results. This allows for evaluation of technical systems according to their current life cycle phase.

Contents

Historic Background

The Life Cycle Model can not be clearly attributed to a single author (ref Bonnal). A range of similar models have been presented by A Guide to the Project Management Body of Knowledge (PMBOK® Guide) (PMI Standards Committee 1996) and the Project Management Handbook (Cleland & King, 1988). This articel is based on the work of Rainer Züst and Peter Troxler (ref), who propose the use of the Life Cycle Model in a Systems Engineering Context.

The Life Cycle Phases

Development Phase

Puzzle globe
Influence vs knowledge of engineering system

This early phase in the life cycle is crucial for the development of any Engineering System. Decisions are taken which will influence the whole life cycle while at the same time the inlfuence on the system itself is decreasing. (ref 5) The development phase consists of four steps:

  • Proposal for systems design

The proposal for systems design originates at the recognition of a need for change. The change may require an improvement of an Engineering System or its new development. Based on an assessment of the need, the decision wether or not to solve the challenge is taken.

  • Preliminary study

The preliminary study aims to provide a broad picture of the challenge. It might include elements like stakeholder investigation and system demarcation. The target of the preliminary study is a clear problem description and a set of objectives which shall be addressed by a potential solution. Concept proposals are developed which will be concretised during the main study.

  • Main study
  • Detailed study


Case Example Development Phase

The case company A, experiences unpleasant feedback from their customers on one of their products. The need for change is recognised and the decision to improve the situation is taken (proposal to system design). The company asses the extend of the problem. Internal as well as external factors are included in order to pinpoint the origin of the problems. The key stakeholders are identified and the area of solution defined. The search for solutions trough creative methods leads to the development of concepts, which may be evaluated by using tools such as Cost-Benefit Analysis or an evaluation matrix with a specific set of criteria (preliminary study). The preferred concept is specified and analysed in detail to establish the effect that can be expected to influence the system (main study). Finally each of the systems parts are studied in detail in order to ensure that the concept addresses all issues raised in the first step in a high quality.

Realisation Phase

Utilisation Phase

Disposal Phase

Alternate Use of Life Cycle Models

Life Cycle Models are usually featuring similar phases as described above, but as their use-context and perspectives differ, the content of each phase might be subject to change. Following examples make use of the Life Cycle Model but are not related to Systems Engineering.

  • Life Cycle Model in a sustainability context. It creates the basis for Life Cycle Sustainability Assessments and Life Cycle Management. Does include the stage of material extraction and is focussed on environment, business and social impacts of a product system (ref 3).
  • Product Life Cycle. The life cycle from a business point of view. May include issues such as innovation diffusion, maturity of product/market (ref 2)

References:

how do I make those work?

  1. Züst, Rainer, and Peter Troxler. “No More Muddling Through: Mastering Complex Projects In Engineering and Management”. No More Muddling Through: Mastering Complex Projects in Engineering and Management (2006): 1-185. Web.
  2. Klepper, S. (1996). Entry, exit, growth, and innovation over the product life cycle. AMERICAN ECONOMIC REVIEW, 86(3), 562-583.
  3. UNEP-SETAC. Towards Life Cycle Sustainability Assessment. 2011
  4. Bonnal, Pierre, Didier Gourc, and Germain Lacoste. “The Life Cycle of Technical Projects.”. Project Management Journal 33.1 (2002): 12. Print.
  5. Haberfellner R. et al., 2002, Systems Engineering. Daenzer, W. et al. (Publisher). 11. Auflage, Verlag Industrielle Organisation, Zürich.
Personal tools
Namespaces

Variants
Actions
Navigation
Toolbox