Talk:System Lifecycle Process Drivers and Choices

From SEBoK
Revision as of 19:57, 30 August 2011 by Dholwell (talk | contribs)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)

Jump to navigation Jump to search

Scott J:

A key driver for system life cycle processes and choices is structural complexity (see Glossary). Structual complexity causes emergent properties that need to be determined. Iterative design is required to achieve the desired level of emergent properties.

Rick Adcock review:

This is a well written and referenced article, which describes a logical view of a number of lifecycle approaches which can be applied to different situations. However, it describes a life cycle language most common to defence, and does not generalise it to commercial products, or services.

The article which comes after this one ("Representative System Life Cycle Process Models") identifies a wider range of lifecycle models, using a similar but different language. This articile also includes some dscussion of when to apply different models.

The "How to apply a Systems Approach" article in Part 2 also talks about life cycle approaches, giving a simpler distinction between sequential (single life cycle) increments (several upgardes of the same system) and evolution (multiple system solutions to explore the problem and refine requirements).

Maybe the "Representative System Life Cycle Process Models" topic can come first, and expalin what evolutionary means and how it differs from sequential and incremental; the part 2 article can be modified if needed to get the laguage right; and then this article could focus on drivers for chosing between them? To be honest, if time is short I might even suggest hiding this topic in 0.5, and focusing on the "Representative System Life Cycle Process Models" topic instead; and then returning to this later.