1. Project Manager: Rajiv Chalasani Mark Goesmann Kevin Staake David Nyman Client : Dr. Lynn Beck Department of Economics

2. Overview User Interface Main architecture Subsystems Database Class Diagram Development Tools Lifecycle Milestones Conflict Resolution and Risk Activities and Ethics

3. User Interface Log in screen Main forms Tabs Navigation pane Input devices Database viewer Sequential steps Out put Summary Printable Savable Viewable

4. Prototype

6. Main architecture Minimum Requirements 64mb ram, 512mhz processor Windows 2000 or equivalent Unix OS Software Requirement (JRE 5) Browser that supports Java Virtual Machine

7. Subsystems Database Access Modify GUI Takes input Shows output

8. Database Class Diagram

9. Web site Information about our project Web version of application Stand alone for download Help

10. Development Tools Java Swing GUI toolkit MySQL NetBeans 6.5.1 Using JDK 6 Subversion Bugzilla

11. Lifecycle

12. Work Distribution Domain Walkthrough Design Design Inspection Code Code Inspection Promote To Build 1%40%3%45%10%1%

13. Milestones DateDescription March 27Have time line, and other diagrams done April 10Have a “paper” prototype done and main overall model April 24High fidelity prototype - features list and design features May 8Have a working high fidelity prototype and final presentation August 28User test on high fidelity September 11Make changes and start GUI and features A September 25GUI done and approved and features B October 9Work on background code October 23Have a working version of the program and features C November 6Web applet done and features D November 20User test December 4 More user test and final touches December 18Deliver end product to client and final presentation

14. GANTT Chart

15. Organization Rajiv Chalasani Planning, Process, Website Mark Goesmann Customer Interface, Design Kevin Staake Implementation, Test Dave Nyman Quality, Co-Test, Support

16. Conflict Resolution 1. If conflict arises team will vote. 2. If vote ends in tie the team leader will decide best action 3. If conflict unresolved go to boss

17. Risk LikelihoodCostPlan 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/mys ql 80%7 daysStudy documentation on the feature needed to be used.

18. Activities Learn HTML and CSS Learn Java Learn MySQL Familiarize ourselves with NetBeans

19. Ethics ACM Code of ethics Be respectful Produce reliable software

20. Any Questions? Thank you for your time and consideration