1 Sean Aluoto Anthony Keeley Eric Werner

2 Project Plan Overview Project Lifecycle model Time line Deliverables Organization plan Risk management Design decisions Software tools Purchases Development support activities Other project plans Current project status

3 Project Lifecycle Evolutionary Delivery Benefits: Allows for changes to the design with successive versions Provides signs of progress during development to the client Helps ensure we will meet the deadline with a deliverable Help develop the UI to meet the clients expectations

4 Lifecycle Model Evolutionary Delivery Model

5 Time Line

6

7 Deliverables Administrator System Prototype Database Administrator SystemVersions 1 & 2 Testing System Formal Documentation(User Manual, etc.)

8 Organization Plan Each team member has a field they focus on but all members are programmers, testers, and technical writers. Decision Making All non-trivial decisions are discussed via , telephone, or in face to face meetings. Final decisions are made at team meetings, after each team member gives their input. The consensus answer is chosen.

9 Organization Plan Conflict Resolution Parties involved will meet with the team and explain their concerns or their views on a decision made. If one side is not persuaded by the other's argument, a compromise will be reached. If a compromise cannot be reached in a reasonable amount of time, an equitable time limit will be put in place and the most equitable solution chosen.

10 Risk Management We used the ACM “One Minute Risk Assessment Tool” Communications of the ACM Volume 47, No. 11

11 Risk Management Our assessment ranks as “moderately low” risk We will recalculate our score weekly, based on current events

12 Design Decisions What type of architecture to use? Client / Server architecture Web based or desktop application? Desktop application What programming language to use? Visual Basic.NET 2005 What DBMS to use? MySQL

13 Design Decisions What level of security to implement? IP security for network communication RSA encryption for local file storage

14 Software Tools Microsoft Visual Studio 2005 – Visual Basic Testing and Administrator interfaces Database: MySQL Additional Tools: Microsoft Office Microsoft Visio TortoiseSVN Gantt Project

15 Purchases No purchases are required Open source solutions will be utilized MySQL On implementation, necessary hardware will be available through our client, Instructional Services

16 Development Support Activities Learning new technology Reading about how to solve programmatic issues outside of the realm of our experience Using new software TortoiseSVN Gantt Project Meetings Meeting with our client and other entities involved in the development process

17 Development Support Activities Documentation Keeping track of the time we spend on the project Composing different development documentation

18 Other Project Plans Test Plan Documentation Plan Review Plan Deployment Plan

19 Test Plan Usability Testing Unit Testing Integration Testing

20 Usability Testing A prototype will be created for the Instructional Services System (admin) Our client will review it in structured and non structured settings

21 Unit Testing Testing will be completed after: Each milestone A testing plan is created by the programmer who spent the most time on a milestone The plan is then reviewed at the next team meeting A team member is assigned the job of testing a milestone based on their workload Completion of each module Informally done by the module's programmer

22 Integration Testing Testing will be done after: Completion of each integrated modules Will be completed by the lead programmer with the team present Issues/Conflicts will then be addressed by the team

23 Documentation Plan Logs Code documentation follows the coding guidelines document User Manual Aspects of each document are assigned to each team member

24 Review Plan Group Reviews Field Reviews Sean – Team and Design Tony – Documentation Eric – Programming

25 Deployment Plan Systems Database server Will reside in Instructional Services office Instructional Services System Administrative functionality Installed on Instructional Services PCs Placement Test System Testing functionality Installed in a selected lab

26 Deployment Plan Academic Computing will be responsible for installation and maintenance of all systems

27 Current Project Status Requirement Analysis Document is currently being revised. System Design Document is nearing completion. Project Plan Document is currently being worked on. Preliminary schedule has been completed.

28 Questions?