Krypto Project Strategy

Cycle 1: Learning Cycle:(approx. 9/5/2000 - 10/25/2000)

·Perform strategy meeting and planning meeting

oReview strategy document

oFirm up cycle 1 goals and activities

oAssign activities to team members

oDevelopment estimates for cycle 1 activities

·Solidify requirements

·Perform strategy meeting and planning meeting

·Get familiar with NDBS materials

·Install NDBS

·Test existing NDBS

·Get certificates/public/private keys

·Focus on Berkeley DB

oGet information on Berkeley DB

oPoints of contact, web URLs, source codes, etc.

oFocus on problem/issues in making Berkeley DB, 100% Java

·Develop areas of concentrations for each team member

·Develop educational program 

Cycle 2: Documents Cycle (approx. 10/30/2000 - 11/31/2000)

·Semester required documentations

oSOW [Grace ] 

§Draft - Oct. 12, 2000

§Version 1.0 - Dec. 6, 2000

§Review with Tech Writer - Oct. 12, 2000

§Inspection of Document - Oct. 25, 2000

oSPMP [Pisey – lead, Ming]

§Draft - Nov. 16, 2000

§Version 1.0 - Dec. 6, 2000

§Review with Tech Writer - Nov. 14, 2000

§Inspection of Document - Dec. 4, 2000

oSRS[Ming – lead]

§Draft - Nov. 30, 2000

§Version 1.0 - Dec. 6, 2000

§Review with Tech Writer - Nov. 30, 2000

§Inspection of Document - Dec. 4, 2000

oESOP [Pisey]

§Draft Dec. 6, 2000

§Presentation Dec. 12, 2000

§Review with Tech Writer - Dec. 6, 2000

§Dry-run- Dec. 8, 2000

§Dry-run with Linda Pesante

Cycle 3:Design Cycle (approx. 1/15/2001 - 3/23/2001)

·Mini-Risk Management Meeting

·Produce conceptual design of Krypto project

·Risk Reduction Prototype

·High level architecture

· QA Plan 

· CM Plan 

· SOW Revision 

· SPMP Revision 

Cycle 4:Design Review Cycle (approx. 4/02/2001 - 5/04/2001)

·Produce detailed design

·Draft Technical Note

·Desgn Documents

·Coding Standard

·EOSP

·SRS revision

·Design review

Cycle 5:Code Cycle (approx. 5/21/2001 - 6/30/2001)

·Perform code review

·Compile

·Code inspection

·Produce required documentation for semester

Cycle 6:Test Cycle (approx. 7/1/2001 - 7/31/2001)

·Perform unit testing

·Produce required documentation for semester

·System test

·Build and integration

·Document deliverable to client

·Postmortem

Benefits

·Incremental development and plan for completeness

·Allow prioritize of items needed to complete

·Allow us to estimate and design

·Keeps us focus on project completion

Strategy Overview

What are we going to do this semester?

What do we need to accomplish this semester?

What does the client wants from us this semester?

Strategy Criteria

What should be the team goal(s) for this semester?

Where do we want to be as a team at the end of this semester?

What type of experience do we each want to have?

What are our risks this semester?

Need all requirements known by the end of this semester?

Is there a possibility of prototyping this semester?

What problem do we want to understand better from the client?

Strategy Exit

Assign action items to team members.

Schedule dates for the cycle this semester.

Agreement on scheduled documentation due dates.