This is the two-week period that begins the second Iteration of Release 1 Construction phase. So coming out of that, we need to have a picture of the entire Release 1 architecture, subject to all the things we will complete during the Construction phase (and thereafter).
- Input task lists (link downloads document) This will get revised during the two weeks
- Existing requirements and open requests/suggestions from each IPT
- Architecture development support tools in place
Some adjustments have been made for this iteration.
- focus on 'topics' on entering Design Period
- intent to engage developers
- any difference versus nominal procedures
- usual products on time for majority of developers; some issues will need more time
- we don't want sticky issues to derail entire process
- for specific presentations identify customizations for Implementation activities (IPAA, EOI, CyberPoPs)
Many of the presentations will follow an outline meant to provide all the key information from Iteration 1 and planned for Iteration 2.
On Wednesday at 10 AM ... details to be provided.
These are the activities ongoing during the CI R1 E3 (iteration 3 of Elaboration) Design Period. Instructions and other documentation for the Design Period can be found at the [Design Period Activities] page.
Detailed instructions for updating this document are at the [Design Period Activities] page.
The Technology List should be updated, to reflect the technologies that are currently targeted for use in the system.
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.)
The Product Description contains a list of different scenarios that reflect the capabilities of the Release 1 product. This document provides context for all the Release 1 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.
The [Design Period Activities] page contains an overview of what we're doing and how to do it. See in particular the Task Checklist.