Skip to end of metadata
Go to start of metadata

Description

In the Inception phase, our work is intended to prove something, not build something. At the end of iteration 2, we must be able to show that the architecture makes sense. It is not necessary to show that we have a working system achieving that architecture.

The focus of the Design Period of Iteration 2 is to refine the iteration task list per development team, based on risk assessment, prioritization and resource availability; to perform a task allocation to development team members; and to develop the necessary designs for the remainder of the iteration in the context of the overarching release architecture. The results must satisfy the deliverables required for the Life Cycle Objectives review, which is held immediately following Iteration 2.

The Design Period is the two-week period that begins an iteration. Coming out of it, we have created or built upon a picture of the entire Release architecture, subject to all the things we will learn during the remaining iterations. During the Design Period of Release 1 Iteration 2, we want to use our improved understanding of the target system to align the following components:

  • Integrated Observatory Architecture
    • Overall Final Product
    • Release 1 elements
  • Task Definitions
    • Release 1 Task Definitions ('RT' in Google doc)
    • Iteration 2 subtask definitions ('IT' in Google doc)
      • = Jira task definitions for Iteration 2

It is expected that the activities of Iteration 2 will involve close collaboration between developers and architects, and that 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 1 should be so identified.

Required Before Starting

  1. Input task lists: This will get revised during the two weeks Architecture COI CEI DM SA Implementation (pending)
  2. Existing requirements and open requests/suggestions from each IPT
  3. Architecture development support tools in place:
    1. Confluence page organization (and best practices, if there is a page to capture these)
    2. Enterprise Architect (configured for SVN integration)
    3. Jira (note Implementation and Architecture IPTs are in CI Dev)
    4. EtherPad/GoogleDocs/other as needed
    5. Drawings: OmniGraffle + Visio
      1. best practice: upload both original and png to Confluence
    6. Remote collaboration tools - as needed/decided by each team
    7. Team contact lists with roles, organization, and availability (leads can augment)
  4. Expected resources availability to accomplish tasks

Intended Products

The primary focus is on the tasks and materials for the current Phase, but products and outcomes should allow for the entire Release product where possible.

  1. Updated tasks & subtasks lists (using good engineering judgment)
    1. Described
    2. Prioritized
    3. Estimated effort required/allocated
    4. Reviewed by Architecture Lead
  2. Change and clarification requests for requirements documentation
  3. Drawings and related artifacts labeled with acceptance/approval level
    1. Interaction roles, message types
    2. Updated (or new) UML diagrams representing component/service interactions
    3. Articulation of use cases/stress cases/usage scenarios AND/OR Sequence diagrams
  4. Discussion/analysis/report documents in Confluence (import an archival copy from other collaboration tools as needed)
    1. Put temporary/provisional work in the relevant iteration for that subsystem
    2. Put 'mainline progress' in the main documents area for that subsystem
    3. Integrate progress into "the master document" (TBS) for the subsystem (process to be determined)
  5. Tasks/action items/bugs in Jira, assigned and prioritized
  6. Make sure the correct access/edit permissions exist on all the tools/repositories by all the participants
  7. Technology integration list/assessment (update strawman list, reflect acceptance/approval)
  8. Dependencies list (on other subsystem components, in particular)

Proposed Process

Wm.n indicates task to be accomplished by day n in week m. Note that the first day of this Iteration is Thursday, 12/3. The last day is Wednesday, 12/16.

The IPTs are the 4 subsystem teams, the Implementation Team, and the Architecture Team.

The Development Leads are the IPT Leads, Architects, and any other senior personnel deemed necessary.

The Management Team is the Project Manager, System Development Manager, and Sr System Architect.

Most progress will be achieved by team members under the leadership of the IPT Lead. Team members may work together or independently, as appropriate to the tasks.

  1. (W1.1-Th) System Development Manager: Identify availability of team members (optionally, recruit more)
  2. (W1.1-Th) IPT Leads: Identify issues requiring attention of Architecture or other teams; forward to those teams
  3. (W1.1-Th) System Architect: Distribute spreadsheets containing Release Tasks in Google doc format
  4. (W1.2-Fr) Architecture Team: Determine proposed approach (priorities/schedule) for resolving Arch issues with IPTs.
  5. (W1.2-Fr) Development Team: Initiation Telecon (schedule review, team membership review, issue identification)

  6. (W1.3-Mo) IPT Leads: Produce schedule of IPT meetings/activities for week, and deliver to Michael, John
  7. (W1.3-Mo) IPTs: Complete outline of strategy for accomplishing goals (prioritize issues received)
  8. (W1.3-Mo) IPTs: Placeholder products on Confluence
  9. (W1.4-Tu) Development Leads: Progress Assessment Telecon (status, best practices, dependencies)
  10. (W1.5-We) IPTs: Preliminary task lists and priorities complete
  11. (W1.5-We) IPTs: Planned drawings and artifacts identified
  12. (W1.5-We) IPT Leads: Issues assessment (and promotion of major issues to Development Leads) complete
  13. (W1.5-We: IPTs: Architecture changes, reflecting current designs, discussed with Architecture Team
  14. (W2.1-Th) Development Leads: Progress Assessment Telecon (status, best practices, dependencies)
  15. (W2.2-Fr) IPTs: Task lists prioritized and estimated
  16. (W2.2-Fr) IPTs: Drawings and related artifacts largely complete
  17. (W2.2-Fr) IPTs: Technology integration and Dependencies lists complete

  18. (W2.3-Mo) IPTs: All documentation updated and final on Confluence
  19. (W2.3-Mo) IPTs: Task lists finalized in Google docs
  20. (W2.3-Mo) IPT Leads: Send mail to System Development Manager on completion of above tasks
  21. (W2.4-Tu) Management Team: review task lists, Confluence documents
  22. (W2.5-We) Iteration 2 task lists transferred to Jira
Enter labels to add to this page:
Please wait 
Looking for a label? Just start typing.