cryptkeeper project plan 1 cryptkeeper project plan

CryptKeeperCryptKeeper Project PlanProject Plan 11

CryptKeeper CryptKeeper Project PlanProject Plan


Lifecycle ModelLifecycle Model

Agile Model:Agile Model: Time-box driven Time-box driven

deadline goal per deadline goal per phase.phase.

Avoiding Feature Avoiding Feature Creep.Creep.

Risk:Risk: Possibility of overly Possibility of overly

optimistic schedule.optimistic schedule.

1. Requirements Elicitation

2. Requirements Analysis

3. System Design

4. Language/Version Implementation (i)

5. Create User Interface

6. Create Database

7. Implement Encryption Algorithm

8. Implement High Score Tracking Algorithm

9. Implement Desktop Version (create download installer).

10. Implement Online Version

11. Usability Testing

13. Create End Document

12. Iteration Complete?

14. Release

Yes

No

Language/Version Iteration:

Visual BasicC#JavaVisual C++


TimelineTimeline

Using the Agile Lifecycle Model:Using the Agile Lifecycle Model: The time box will be set to one week intervals.The time box will be set to one week intervals.

First half will be spent on research.First half will be spent on research. Second half will be spent on implementation.Second half will be spent on implementation.

By end of spring – implementation of Visual Basic By end of spring – implementation of Visual Basic and C#.and C#.

During summer – learn Java coding.During summer – learn Java coding. By early fall – implementation of Java and Visual C+By early fall – implementation of Java and Visual C+

++ By early winter – end document.By early winter – end document.**Specific details provided on page 3 and 4 on CryptKeeper Project Plan **Specific details provided on page 3 and 4 on CryptKeeper Project Plan

document.document.


Gantt ChartsGantt Charts

Spring and Summer SemesterSpring and Summer Semester


Gantt Chart cont.Gantt Chart cont.

Fall SemesterFall Semester


Organization PlanOrganization Plan

Team Member LogsTeam Member Logs Team LogsTeam Logs Team BlogTeam Blog TimelineTimeline

Gantt ChartGantt Chart


Decision MakingDecision Making

Majority RulesMajority Rules Else…Else…

Stance Presentation, revoteStance Presentation, revote Direct to department head or BradDirect to department head or Brad CompromiseCompromise Research outside sourcesResearch outside sources Project Manager or ClientProject Manager or Client


Team Member Team Member ResponsibilitiesResponsibilities

Brad:Brad: Leader (analysis, liaison, final review)Leader (analysis, liaison, final review) Design (review, file management, interviews)Design (review, file management, interviews) Programming (event driven, database, files)Programming (event driven, database, files)

Mike:Mike: Lead Design (prototypes, interviews, flexibility)Lead Design (prototypes, interviews, flexibility) Programming (game play relating to design)Programming (game play relating to design)

John:John: Programming (algorithms, clarity, consistency, Programming (algorithms, clarity, consistency,

conciseness)conciseness) Design (review, miscellaneous, interviews)Design (review, miscellaneous, interviews)


Major Risks:Major Risks: Java ProgrammingJava Programming Web DevelopmentWeb Development C++ ProgrammingC++ Programming New ProgrammingNew Programming

Development SuitesDevelopment Suites

Risk PlanRisk Plan


““The One-Minute Risk The One-Minute Risk Assessment Tool” Assessment Tool”

Project Characteristic QuestionProject Characteristic Question RatingRating XX WeightWeight == TotalTotal

Fit between the chosen methodology and Fit between the chosen methodology and type of project type of project

77 XX 3.03.0 == 2121

Level of customer involvementLevel of customer involvement 88 XX 1.91.9 == 15.215.2

Use of formal management practicesUse of formal management practices 55 XX 1.71.7 == 8.58.5

Similarity of previous projects Similarity of previous projects 77 XX 1.51.5 == 10.510.5

Project simplicity(lack of complexity) Project simplicity(lack of complexity) 66 XX 1.11.1 == 6.66.6

Stability of project requirementsStability of project requirements 99 XX 0.80.8 == 7.27.2

Overall Project ScoreOverall Project Score == 6969


Test PlanTest Plan A test plan will be created A test plan will be created

for each module.for each module. The goal is to keep each The goal is to keep each

module as generic as module as generic as possible.possible.

A system will be done at A system will be done at end of each language end of each language version.version.

If additional modules are If additional modules are needed for certain version, needed for certain version, then a test plan will be then a test plan will be created for that module as created for that module as well.well.


Documentation PlanDocumentation Plan Assigned documentation assignmentsAssigned documentation assignments Blogs and logsBlogs and logs Code documentationCode documentation Help systemHelp system End documentEnd document

Detailed comparison and contrast of learning Detailed comparison and contrast of learning curves for each aspect.curves for each aspect.

Installation PlanInstallation Plan Online and Offline versionsOnline and Offline versions Install wizardInstall wizard


Software Tools NeededSoftware Tools Needed

The following tools are requested in the The following tools are requested in the development of the CryptKeeper project.development of the CryptKeeper project. Java Studio Creator - Java Studio Creator - http://http://

developers.sun.com/prodtech/javatools/jscreator/inddevelopers.sun.com/prodtech/javatools/jscreator/index.jspex.jsp Similar interface with Visual StudiosSimilar interface with Visual Studios Possible usage of future classes taught in Java.Possible usage of future classes taught in Java.

Reference Guides on each languageReference Guides on each language Quicker navigation instead of toggling between multiple Quicker navigation instead of toggling between multiple

windows. windows.


Review PlanReview Plan

Peer ReviewsPeer Reviews Area ReviewsArea Reviews

John ProgrammingJohn Programming Mike DesignMike Design Brad Team and DocumentsBrad Team and Documents


SummarySummary

Requirement Phase CompleteRequirement Phase Complete User Interface in final stage of designUser Interface in final stage of design Two databases narrowed down to one.Two databases narrowed down to one. Semester Deliverables discussed and Semester Deliverables discussed and

agreed upon. agreed upon.


Questions?Questions?

cryptkeeper project plan 1 cryptkeeper project plan

Documents

cryptkeeper project

client slide

cryptkeeperproject plan10

test plan

fall semester slide

summer semester slide

installation plan

cryptkeeperproject plan11