2. CryptKeeper Project Plan 1 CryptKeeper Project Plan

3. CryptKeeperProject Plan2 Lifecycle Model  Agile Model:  Time-box driven deadline goal per phase.  Avoiding Feature Creep.  Risk:  Possibility of overly optimistic schedule.

4. CryptKeeperProject Plan3 Timeline  Using the Agile Lifecycle Model:  The time box will be set to one week intervals.  First half will be spent on research.  Second half will be spent on implementation.  By end of spring – implementation of Visual Basic and C#.  During summer – learn Java coding.  By early fall – implementation of Java and Visual C++  By early winter – end document. **Specific details provided on page 3 and 4 on CryptKeeper Project Plan document.

5. CryptKeeperProject Plan4 Gantt Charts Spring and Summer Semester

6. CryptKeeperProject Plan5 Gantt Chart cont. Fall Semester

7. CryptKeeperProject Plan6 Organization Plan  Team Member Logs  Team Logs  Team Blog  Timeline  Gantt Chart

8. CryptKeeperProject Plan7 Decision Making  Majority Rules  Else…  Stance Presentation, revote  Direct to department head or Brad  Compromise  Research outside sources  Project Manager or Client

9. CryptKeeperProject Plan8 Team Member Responsibilities Brad:  Leader (analysis, liaison, final review)  Design (review, file management, interviews)  Programming (event driven, database, files) Mike:  Lead Design (prototypes, interviews, flexibility)  Programming (game play relating to design) John:  Programming (algorithms, clarity, consistency, conciseness)  Design (review, miscellaneous, interviews)

10. CryptKeeperProject Plan9  Major Risks:  Java Programming  Web Development  C++ Programming  New Programming Development Suites Risk Plan

11. CryptKeeperProject Plan10 “The One-Minute Risk Assessment Tool” Project Characteristic Question RatingXWeight=Total Fit between the chosen methodology and type of project 7X3.0=21 Level of customer involvement 8X1.9=15.2 Use of formal management practices 5X1.7=8.5 Similarity of previous projects 7X1.5=10.5 Project simplicity(lack of complexity) 6X1.1=6.6 Stability of project requirements 9X0.8=7.2 Overall Project Score =69

12. CryptKeeperProject Plan11 Test Plan  A test plan will be created for each module.  The goal is to keep each module as generic as possible.  A system will be done at end of each language version.  If additional modules are needed for certain version, then a test plan will be created for that module as well.

13. CryptKeeperProject Plan12 Documentation Plan  Assigned documentation assignments  Blogs and logs  Code documentation  Help system  End document  Detailed comparison and contrast of learning curves for each aspect. Installation Plan  Online and Offline versions  Install wizard

14. CryptKeeperProject Plan13 Software Tools Needed  The following tools are requested in the development of the CryptKeeper project.  Java Studio Creator - http://developers.sun.com/prodtech/javatools/jscreat or/index.jsp http://developers.sun.com/prodtech/javatools/jscreat or/index.jsp http://developers.sun.com/prodtech/javatools/jscreat or/index.jsp  Similar interface with Visual Studios  Possible usage of future classes taught in Java.  Reference Guides on each language  Quicker navigation instead of toggling between multiple windows.

15. CryptKeeperProject Plan14 Review Plan  Peer Reviews  Area Reviews  John Programming  Mike Design  Brad Team and Documents

16. CryptKeeperProject Plan15 Summary RRRRequirement Phase Complete UUUUser Interface in final stage of design TTTTwo databases narrowed down to one. SSSSemester Deliverables discussed and agreed upon.

17. CryptKeeperProject Plan16 Questions?