Skip to end of metadata
Go to start of metadata


In the Inception phase, we must show that the architecture makes sense and is in hand. (It is not necessary to show that we have a working system achieving that architecture.) The results must satisfy the deliverables required for the Life Cycle Objectives review, which is held immediately following Iteration 2.

The Design Period of Inception 2 must refine the iteration task list per development team, based on risk assessment, prioritization and resource availability; perform a task allocation to team members; and develop necessary designs for the remainder of the iteration.

The activities of Inception 2 will involve close collaboration between developers and architects, and the architecture documents will be collaboratively updated to reflect the best known design information. Elements of the architecture that are targeted for implementation after Release 2 should be so identified.

Required Before Starting

  1. Input task lists (below). This will get revised during the two weeks
  2. Existing requirements and open requests/suggestions from each IPT
  3. Architecture development support tools in place

Unique to this iteration


  • Design Experts' input to complete the Task List for each subsystem.

Design Review Presentations

Instructions and other documentation for the Design Period can be found at the Design Period Activities page.

Planning Documents

Documents to Update

Task Lists on Google docs

Detailed instructions for updating this document are at the Design Period Activities page.

The R2I2 Architecture Tasks are distributed throughout the other task lists above, in the Overarching Inception Period Tasks for each subsystem.

Technology List

The Technology List will be updated, to reflect the technologies that are currently targeted for use in the system.

Reference Documents

Iteration Pages

Scoping Activities

The architecture team and design experts spent time scoping the activities for the next iteration.  The results of that work are at the following links. (These are intended to be used primarily by the Senior Developers during Design Period.)

  • COI R2I2 Scoping
  • CEI R2I2 Scoping
  • DM R2I2 Scoping
  • SA R2I2 Scoping
  • AS R2I2 Scoping
  • EOI R2I2 Scoping
  • UX R2I2 Scoping

Product Description

The Product Description contains a list of different scenarios that reflect the capabilities of the Release 2 product. This document provides context for all the Release 2 work. If you don't see how a given task fits into the Product Description, this is an issue and should be raised with a Senior Developer or the Senior System Architect or System Development Manager.

Design Period Overview

The Design Period Activities page contains an overview of what we're doing and how to do it. See in particular the Task Checklist.

Meeting Notes:

R2 Weekly Forum Mtg 2011-06-29
R2 Weekly Forum Mtg 2011-07-06

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