Project Plan Presentation

1. Project Plan Presentation Team Juggernaut InterFAQs

2. Overview • Lifecycle • Gantt Chart • Deliverables • Team Organization • Risk Management • Plans Team Juggernaut InterFAQs

3. Overview (cont) • Design Decisions • Development Tools • Hardware/Software • Development Activities • Current Status • Questions Team Juggernaut InterFAQs

4. Lifecycle • Modified Waterfall (Shashimi) Team Juggernaut InterFAQs

5. Lifecycle (cont) • Modified Waterfall (Shashimi) Fits Because • Requirements already (fairly) well laid out • Interfaces already created • Ready for coding and debugging Team Juggernaut InterFAQs

6. Web Client Implementation Admin Module Implementation Testing Training Gantt Chart Team Juggernaut InterFAQs

7. Gantt Chart (cont) Web Client Team Juggernaut InterFAQs

8. Gantt Chart (cont) Admin Module

9. Gantt Chart (cont) Testing & Training Team Juggernaut InterFAQs

10. Deliverables • Feb. 25th, 2005 • InterFAQs Version .25 • Web Client Complete • Apr. 1st, 2005 • InterFAQs Version .75 • Admin Module Complete • Apr. 11th, 2005 • InterFAQs Version 1 Beta • Apr. 29th, 2005 • InterFAQs Version 1 Final Release Team Juggernaut InterFAQs

11. Team Organization • Lead Programmer • Make sure everything works • Lead Analyst • Make sure it does what the client wants it to do • Project Manager • Make sure both get done and keep client happy • Each team member fully responsible for tasks in Gantt chart assigned to him • May ask for assistance, but ultimately responsible Team Juggernaut InterFAQs

12. Team Organization • Conflict Resolution Procedure • In the event that the InterFAQs team cannot come to a consensus on any particular decision, the following procedures will be followed in a timely manner. • If there are exactly two courses of action • A vote will be taken by all three team members, and each team member will vote for exactly one of the possible actions to be taken. • The course of action with the majority of votes will be taken. • If there are three of more courses of action • The person primarily responsible for each course of action will be given up to ten uninterrupted minutes to speak his or her case. • If after these cases have been presented there is still no resolution, it is the Project Manager’s discretion as to which resolution shall be accepted. • If after at least one of these events has occurred and a team member or members are still dissatisfied with the decision, he or she may request the Project Manager arrange a meeting between the InterFAQs team and the Upper Management.  The Project Manager must arrange said meeting.  During this meeting, a representative from each side of the case will be given up to ten uninterrupted minutes present his or her case.  After this, questions may or may not be asked by the Upper Management to each case’s representative.  The Upper Management will then decide on the appropriate course of action to be taken, and this will be accepted and enforced by the Project Manager. Team Juggernaut InterFAQs

13. Risk Management • Search algorithm • Trouble with implementation, efficiency • Remote Access • Ability to access database from outside engineering building • Delay in Client Communication • How well clients respond when info is needed • Delay of Database Questions • We’re depending on client to supply • Schedule Overrun • Deadline at end of Spring 2004 semester set in stone Team Juggernaut InterFAQs

14. Code Review Plan Team Juggernaut InterFAQs

15. Documentation Plan Team Juggernaut InterFAQs

16. Testing Plan • Developer testing will be conducted by each team member in an attempt to find major logic or syntax errors. The purpose of end-user testing is to discover any logic or syntax errors missed by the developers. Another goal of end-user testing is to get reaction to the interface given to the user. End-user testing is essential to creating a stable system that is easy to use. Team Juggernaut InterFAQs

17. Testing Plan (cont) • Standards for Testing • No code changes will be made during testing. After each test, any bug discovered by the tester will be documented and forwarded to the team leader for verification. • Testing will be performed by one team member at a time to avoid documenting a single bug multiple times which could cause some confusion. Each team member will be given a time to test the system, either alone or with another team member present. • Upon receiving documentation of a bug in the system, the Team Leader will assign a team member to fix the bug, most likely the person in charge of that particular part of the system. This assignment will be documented by the Team Leader • Once a team member has decided a bug is fixed, he/she will notify the Team Leader of their completion of the task. Once the fix is verified, the date it was fixed is documented and the bug is considered ‘dead’. Team Juggernaut InterFAQs

18. Testing Plan (cont) • If Bugs are found • Once a bug is found it will be reported to the Team Leader who will verify the existence of the bug, or will pass the verification to another team member if he/she does not have time available to verify the bug. • Once a bug is verified the Team Leader will determine the person responsible for that part of the system and will assign the task of fixing the bug to that team member. If for some reason that team member is not available to fix the bug, another team member will be assigned the task. • If a team member cannot find a solution to the problem posed by a bug he/she may contact another team member for assistance, though this should be considered a last resort due to possible unavailability of other team members. • Once a team member believes they have fixed a bug, the Team Leader will be notified so he/she can either test the system themselves or assign another team member to do so. • Once the additional testing is completed, if the bug is fixed, it is considered ‘dead’ and documented as such. Otherwise, the team member who was assigned the fix will be notified and the process will repeat. Team Juggernaut InterFAQs

19. Installation Plan • Installation Location • The InterFAQs application will be delivered and installed on the financial aid servers in Founders Hall at Southern Illinois University Edwardsville. • Product Delivery • The source code and database dump will be compressed and combined into a zip file. • Said zip file will be emailed to Martin Mokoosio who will (or appoint someone to) copy said files into the appropriate web directory. • Also included in the zip file will be a setup script. This script, when run, will prompt the user whether the database structure will need to be updated as well as the source code files installed. If the database structure has been modified since the last release, it will be well-documented and made apparent to the installer of the software. • ProductInstallation • The application will also contain functionality to import an existing database. This function will be used to import the database dump emailed along with the script. Team Juggernaut InterFAQs

20. Design Decisions Team Juggernaut InterFAQs

21. Development Tools • PHP • MySql • HTML • Macromedia Dreamweaver • License in the works Team Juggernaut InterFAQs

22. Development Activities • Need to Learn • Dreamweaver • PHP • HTML • Financial Aid • Need to install PHP and MySql • Development Location • www.interfaqs.com Team Juggernaut InterFAQs

23. Project Status • In the Works • ERD Diagram Approval • PHP and MySql installed • Ready for implementation Team Juggernaut InterFAQs

24. Questions??? Team Juggernaut InterFAQs