Skip to end of metadata
Go to start of metadata
This page provides some background information, definitions, and deliverable expectations for the Construction Plan pages.

Source Documents

The authoritative source for the CI project deliverables and their time phasing is the schedule (in MS Project server) as part of the OOI program Integrated Master Schedule (IMS). This schedule gets updated regularly and has undergone substantial change in the program-wide replan ending April 2011.

The core structure of the schedule is the Work Breakdown Structure (WBS). Each item in the schedule has a unique WBS identifier (for instance the entire CI development effort is 1.2.3). The WBS Dictionary is the list of all WBS identifiers and their definition. The WBS structure remains static. It got updated (new elements added, existing elements deprecated) in the OOI replan April 2011.

The authoritative source for the CI system design is the Integrated Observatory Architecture specification. This is a living document aggregating all essential design knowledge about the system.

The authoritative source for the CI release product descriptions is the Product Specification. Among other things, it contains the Product Description for each release of the system (Product Description Release 2), which specifies the scope of functionality for that release in the form of use cases.

Structure

One Construction Plan page exists per subsystem and release (e.g. COI Release 2 Construction Plan)

Each Construction Plan page is structured as following (see below for definitions of terms):

  • Subsystem level WBS items and scheduled work begin and end dates
  • Table of Service Groups (with links to detailed sections)
  • Team Members
  • Service Group Definitions (for each service group)
    • Description summary statement
    • Table of Service Components with title, description and marks if deliverables exist for LCO, LCA and IOC
    • Table of Product Description Use Cases with title, description and marks if deliverables exist for LCO, LCA and IOC

Definitions

Term Definition
Service Group A schedule/WBS summary account, representing a high-level group of services in a subsystem, from a deliverable point of view. The grouping is done by functionality. An example is "COI Identity & Policy Management Services".
Notes:
  • The same Service Group may exist in subsequent releases. In this case the aggregate set of service components and use cases determines the scope associated with the service group for each release.
  • One service group may cover more than one high-level service in the system architecture
  • One high-level service in the system architecture may be implemented in one release service group and extended in a subsequent release service group
Service Component A deliverable, part of a service group. Service components include services, infrastructure components, specification models and user interface components.
Each service component undergoes the following realization stages:
  • Planned: The CI system architecture identifies the service component and its dependencies to other service components
  • Designed: A fine design exists, specifying behavior, interfaces, integrated technologies and implementation
  • Prototyped (optional): An executable prototype exists showing the most critical technologies integrated and functional behavior exposed
  • Architecturally integrated: The service is integrated prototypically as part of one system-wide prototype.
  • Production level implemented: The service component is implemented and successfully unit tested as production quality code.
  • System integrated: The service component is integrated as part of the release system and successfully integration and system tested.
Use Case
A deliverable, representing a distinct, user visible part of the system functionality, expressed in form of a scenario description with steps. Note: users in this case may be end users, operators or higher level system services.

Deliverables

Life Cycle Objectives (LCO) Milestone Review

See the description of the LCO milestone and review as part of the Spiral Development process.

Deliverables for service components and use cases:

Applies to ALL service components Applies to service components marked LCO
Applies to ALL use cases Applies to  use cases marked LCO
Product content Produced to these criteria In this artifact
X   X   related Use Cases, Service Components and Requirements mapped formal mapping exists by category
Use cases on Confluence reference primary service group. Service group linked from L3 requirements in DOORS (implicitly applied to L4 requirements)
X       any risks associated with the component are updated reflecting results of work performed on component during phase Risk register in SAF
X   X   any required User Interfaces are named sufficient description to fully anticipate the User Interface
UX requirements and specifications
  X
  X
any required User Interfaces have wire-frames or mock-ups
wire-frames or mock-ups sufficient for external review UX requirements and specifications
X
      the System Architecture Specification updated with high level architecture and component interfaces
reviewed and baselined for milestone
Architecture Specification in Confluence and Enterprise Architect
X
      any technologies identified that are determined or candidates for integration, as design reference or as compliance specification
reviewed and baselined for milestone Technology List
    X
  refined use case scenarios and steps
reviewed and baselined for milestone Release Product Description
X       required Integration Tests listed for LCA
sufficient description to fully anticipate the required tests (level of build out is assumed different for LCA and IOC tests; performance tests are included)
Test procedures and reports
  X
    prototypes described and assigned as part of the iteration planning
associated with risk; note: prototypes can be design prototypes
Iteration task plan
  X     working prototype code and unit tests checked in or detailed design documented
all tests pass; stubs/remaining work noted; or design analyzed and reviewed
Unit tests documented in Confluence task definition page; Confluence design page
  X   X item's pending tasks are named broken out as explicit iteration tasks according to process
Iteration task specifications

Life Cycle Architecture (LCA) Milestone Review

See the description of the LCA milestone and review as part of the Spiral Development process.

Deliverables for service components and use cases:

Applies to ALL service components Applies to service components marked LCA
Applies to ALL use cases Applies to use cases marked LCA
Product content Produced to these criteria In this artifact
X   X   related Use Cases, Components and Requirements mapped formal mapping exists following our described process Use cases on Confluence linked from requirements in DOORS linked to services and their elements on Confluence (baselined at end of elaboration)
X       any risks associated with the component are updated reflecting results of work performed on component during phase Risk register in SAF
X   X   required User Interfaces mocked up, reviewed, coded initial user review has taken place; code viable (but not integrated) UX specifications
    X   end-to-end function of use case is allocated to components sequence diagram exists showing components involved Enterprise Architect
X       changes and refinements to system architecture and technology list as found out by prototyping and implementation
reviewed and baselined for milestone Architecture Specification in Confluence and Enterprise Architect
X       Integration Test descriptions for LCA and IOC tests complete reviewed and baselined for milestone Test Plan

X     required LCA level Integration Tests complete
integration test code or scenario written and passes Integration tests documented in ?
  X     working integrated core code and unit tests checked in all unit and integration tests pass; stubs/remaining work detailed Unit tests documented in Confluence design page for task; integration tests documented in ?
  X   X item's pending tasks are fully described described as explicit DesignITs of 5d scope Iteration task specifications
  X   X related User/Operator documentation outlined outline includes main topics to address Document Register

Initial Operating Capability (IOC) Milestone Review

See the description of the IOC milestone and review as part of the Spiral Development process.

Deliverables for service components and use cases:

Applies to ALL service components Applies to ALL use cases Product content Produced to these criteria In this artifact
X X complete working code and unit tests checked in all tests pass; stubs/remaining work detailed Test Plans, Procedures and Reports
X   component's pending tasks are detailed (if Iterations remain) described as explicit TestITs of 5d scope, assigned to iteration Iteration task specifications
X   related Use Cases Components and Requirements mappe; formal mapping exists following our described process Use cases on Confluence linked to requirements in DOORS linked to services and their elements on Confluence
X   all Integration Tests completed
test written and passes Test Procedures and Reports
X X related User/Operator documentation complete component functionality visible in UI fully documented Document Register
X X required User Interfaces coded, integrated, reviewed, and tested reviews of both mockup and functional code complete UX specification
X   any risks associated with the component are updated reflecting results of work performed on component during phase Risk register in SAF
X
  changes and refinements to system architecture and technology list as found out by production quality implementation and integration
reviewed and baselined for milestone Architecture Specification in Confluence and Enterprise Architect

Enter labels to add to this page:
Please wait 
Looking for a label? Just start typing.