Project Manager: Rajiv Chalasani Mark Goesmann
Kevin Staake David Nyman
Client : Dr. Lynn Beck Department of Economics
ICABDesign and Plan Presentation
OverviewUser InterfaceMain architectureSubsystems Database Class DiagramDevelopment ToolsLifecycleMilestonesConflict Resolution and RiskActivities and Ethics
User Interface Log in screenMain forms
TabsNavigation paneInput devicesDatabase viewerSequential steps
Out putSummary
Printable Savable Viewable
Prototype
Prototype
Main architectureMinimum Requirements
64mb ram, 512mhz processorWindows 2000 or equivalent Unix OS
Software Requirement (JRE 5)Browser that supports Java Virtual Machine
Subsystems Database
AccessModify
GUITakes inputShows output
Database Class Diagram
Web siteInformation about our projectWeb version of applicationStand alone for downloadHelp
Development ToolsJava
Swing GUI toolkitMySQLNetBeans 6.5.1
Using JDK 6SubversionBugzilla
Lifecycle
Work Distribution
Domain Walkthrough
Design Design Inspection
Code Code Inspection
Promote To Build
1% 40% 3% 45% 10% 1%
MilestonesDate Description
March 27 Have time line, and other diagrams done
April 10 Have a “paper” prototype done and main overall model
April 24 High fidelity prototype - features list and design features
May 8 Have a working high fidelity prototype and final presentation
August 28 User test on high fidelity
September 11 Make changes and start GUI and features A
September 25 GUI done and approved and features B
October 9 Work on background code
October 23 Have a working version of the program and features C
November 6 Web applet done and features D
November 20 User test
December 4 More user test and final touches
December 18 Deliver end product to client and final presentation
GANTT Chart
OrganizationRajiv Chalasani
Planning, Process, WebsiteMark Goesmann
Customer Interface, DesignKevin Staake
Implementation, TestDave Nyman
Quality, Co-Test, Support
Conflict Resolution1. If conflict arises team will vote.2. If vote ends in tie the team leader will
decide best action3. If conflict unresolved go to boss
RiskRisk Likelihood Cost Plan
Temporary Loss of Team member
100% 3-7days Redistribute work evenly to other members
New features wanted by client
10% 3 days Revisit high level design, decide whether the changes are reasonable
Inexperience with Features of Java/Netbeans/mysql
80% 7 days Study documentation on the feature needed to be used.
Activities Learn HTML and CSSLearn JavaLearn MySQLFamiliarize ourselves with NetBeans
EthicsACM Code of ethicsBe respectfulProduce reliable software
Any Questions?
Thank you for your time and consideration