|Excerpt from the CI System Life Cycle Plan|
With reference to Figure 2, the initial stage in the system life cycle is the Inception phase that has a 4 month duration in the CI IO system life cycle. The overarching purpose of the Inception phase is reaching consensus among the stakeholders on the objectives for a release.
The principal goals of the Inception phase are:
- Establishing the software scope and interfaces at the level of an operational concept,
- Defining detailed use cases for the release and candidate requirements that will force design trade-offs,
- Demonstrating one or more candidate architectures that fulfill the critical use cases and candidate requirements,
- Providing clear definition and prototyping of the critical risks that require early mitigation.
Critical use cases are defined as those that describe a core capability of the release. Critical risks are defined as ones that will block a core capability of the release if realized. Candidate requirements specify all of the service components in the release, but may not define their detailed functionality.
The major activities of the Inception phase are:
- Elicitation of use cases and requirements that circumscribe the user (scientific, educational and marine operator) and system views of the release, and their capture in documents and the requirements repository,
- Elaboration of user workflows that capture the processes and procedures utilized by the target audience for a given release,
- Elaboration of the critical risks and the definition of tasks that mitigate them at the earliest opportunity,
- Carrying out design trade-offs, resolving design ambiguities and evaluating candidate technologies at a level that is sufficient to synthesize at least one candidate architecture, and demonstration that the candidate architectures are feasible. Such demonstration is typically achieved through successful exploratory vertical prototyping of key parts of candidate architectures and integration of critical technologies,
- Preparing for the Elaboration phase, including risk definition and management as defined in 1007-00000 Risk and Opportunity Management Plan OOI, and initial planning for the Elaboration iterations
During the Inception phase, it is anticipated that new use cases and requirements will be discovered, and that the existing requirements baseline will be evaluated for accuracy and completeness. Evolution of the use cases and requirements will formally be managed through change control boards as defined in 2110-00001 Configuration Management Plan. Careful attention to risk identification is another major focus. Prototyping of critical aspects of the architecture is also carried out. The Product Manager has primary responsibility for managing Inception phase activities, with the Senior System Architect maintaining responsibility for the architecture. The Chief System Engineer is responsible for the system engineering processes of requirements definition, change and risk management. These roles are assisted by Design Experts engaged for their technical abilities in critical areas and the subsystem Senior Developers.
At the end of the Inception phase, the Life Cycle Objectives (LCO) milestone review by a representative external board is convened by the Chief System Engineer. The entry criteria for LCO are completion of the review artifacts.