1. Word Guess Team (Team #4) October 8, 2002

2. Word Guess Team  Team Members  Chakib Kouhel: ckana74@hotmail.comckana74@hotmail.com  Steve Mattingley: smattingley@cfl.rr.comsmattingley@cfl.rr.com  Albertina Limbangan: arl105@hotmail.comarl105@hotmail.com  Customer  Dr. Beth Young: byoung@mail.ucf.edubyoung@mail.ucf.edu

3. Word Guess: Existing System The current System Word Guess is a web based game that presents a text with every fifth word deleted. It allows students to fill in the blanks of the missing words. The Word Guess program keeps track of each guess and counts the frequency of each guess. After students play the game, they can view a list of results, which includes the original word as well as all the guesses.

4. Word Guess: Existing System Utilizes Perl and CGI Web-based interface Development area at www.prohosting.com Final system resides on a UCF server

5. Word Guess: Existing System

6. Word Guess: New Requirements The new system should be able to handle longer texts (up to 1000 words) The new system should allow the administrator to change the administrator password The new system should allow the administrator to reset user passwords

7. Word Guess: New Requirements The new system should follow 508 guidelines

8. User Sequence Diagram

9. Admin Sequence Diagram

10. Software Lifecycle Process Since the Word Guess program already exists, the team will be using a modified waterfall life-cycle model. This process was selected because it works well for modifying existing systems and it fits well with the required delivery schedule for the course. Requirements Phase Specification Phase Design Phase Implementation Phase Integration Phase Maintenance Phase Retirement

11. Tools and Computing Environment The original Word Guess program was written in Perl and was executed from the cgi-bin of a UNIX based web-server. Although the team’s expertise is with C++ and Java, the team has decided to leave the program in Perl and continue with the CGI approach. Any Perl interpreter which supports the Perl 5.6.0 will be acceptable.

12. Tools and Computing Environment The Perl cgi library cgi-lib v2.18 will be used to interface between the web and perl environments. Cgi-lib was written by Steven E. Brenner and is available for unlimited use as long as it is attributed correctly. It is available at http://cgi- lib.stanford.edu/cgi-lib/

13. Major Risks There is a risk that the group’s lack of expertise with Perl will make the project overly difficult. This is mitigated by the fact that the team members are all proficient programmers and have the ability to learn Perl quickly. Steve Mattingley has worked in Perl (over 5 years ago), so that should also help the learning curve. There is a risk that implementing the 508 guidelines will be outside the scope of this project. The team informed that Dr. Young that they would have to research the 508 guidelines before committing to fully meeting them.

14. Work Packages

15. PERT Chart

16. Technical Progress Metrics Requirements Phase Metrics  Planned vs. Actual Effort (man-hours)  Number of requirements  Number of changed requirements (to be collected in all future phases also) Specification Phase Metrics  Planned vs. Actual Effort (man-hours) Design Phase Metrics  Planned vs. Actual Effort (man-hours)  Number of Perl modules

17. Technical Progress Metrics Implementation Phase Metrics  Planned vs. Actual Effort (man-hours)  Changed Lines of code (relative to the original system)  Added Lines of code (relative to the original system)  Deleted Lines of code (relative to the original system) Integration Phase Metrics  Planned vs. Actual Effort (man-hours)  Number of defects Maintenance Phase Metrics  Planned vs. Actual Effort (man-hours)

18. Testing Environment UNIX based web server (www.prohosting.com) will be the test platform. When the system has passed acceptance testing by the user, it will be moved to a UCF UNIX server.www.prohosting.com Perl 5.6.0 (for CGI) Internet Explorer or Netscape (Any version)

19. Test Cases Test Case 1 - Student's login validation Test Case 2 - Administrator’s login validation Test case 3 - Incorrect Login (student or administrator) Test Case 4 - Take the Test Test case 5 - Submit the Answers Test case 6 - View the results Test case 7 - View Student Records Test case 8 - Change the text for the test Test case 9 - Take the test with a large file

20. Current Assignments Chakib - Working on prototype of the new web layout and interface. Steve - This presentation and design Tina - Design

21. Questions???