Determining the Lines of System Maturity, System Readiness and Capability Readiness in the System Development Lifecycle.

Abstract

Many systems suffer from major problems with implementation, integration, performance and other lifecycle problems and
\nunexpected and unacceptable behaviour often arises when they are introduced into the real world, yet the systems were believed
\nto be “ready” for use. Often, certain aspects about the real world context are not always appreciated until surprise problems
\narise when the system is introduced and used. This could be thought of as a failure in “systems understanding”. We are not
\ngood enough at understanding system implementation and integration issues (in their widest sense) and the associated Risk
\nissues in assessing a System‟s Maturity and Readiness within a development programme and overall lifecycle. This challenge is
\nincreasing interest and emphasis on System Maturity assessments and in the use of System Readiness Levels and on achieving
\nthe overall Capability of a system in its intended operational environment.
\nIn this paper, we investigate the issues by addressing the following key questions: Why are “Maturity” and “Readiness”
\nimportant in Systems Engineering (SE)? Is there a sufficiently clear distinction between „System Maturity‟ (SM) and „System
\nReadiness‟ (SR)? What do we mean by SM and SR? How is the term „Capability‟ currently being used in SE? Why do we need
\nto assess the Capability of the system? What do we mean by „Capability Readiness‟ (CR)? We define SM, SR and CR and map
\nthese to the System Development and overall Lifecycle and then provide recommendations for further research.