Word Guess Team (Team #4) October 8, 2002. Word Guess Team  Team Members  Chakib Kouhel:  Steve Mattingley:

Slides:



Advertisements
Similar presentations
1 Copyright © 2002 Pearson Education, Inc.. 2 Chapter 1 Introduction to Perl and CGI.
Advertisements

Point of Sale (POS) Client & Back Office Server. Operational Concept What is our Objective? What is our Objective? What are our Goals? What are our Goals?
Configuration management
Software Quality Assurance Plan
2003 Mateusz Żochowski, Marcin Borzymek Software Life Cycle Analysis.
Software Engineering CSE470: Process 15 Software Engineering Phases Definition: What? Development: How? Maintenance: Managing change Umbrella Activities:
Software Delivery. Software Delivery Management  Managing Requirements and Changes  Managing Resources  Managing Configuration  Managing Defects 
CSCU 411 Software Engineering Chapter 2 Introduction to Software Engineering Management.
Software project management Module 1 -Introduction to process management Teaching unit 1 – Introduction Ernesto Damiani Free University of Bozen-Bolzano.
Software Engineering. How many lines of code? Average CS1004 assignment: 200 lines Average CS4115 project: 5000 lines Corporate e-commerce project: 80,000.
R R R CSE870: Advanced Software Engineering (Cheng): Intro to Software Engineering1 Advanced Software Engineering Dr. Cheng Overview of Software Engineering.
Software Engineering.
VDK-RIT InserterVision Report System Adam Beck Greg Dicheck Kassidy Gerber Mike Young.
Copyright 2002 Prentice-Hall, Inc. Modern Systems Analysis and Design Third Edition Jeffrey A. Hoffer Joey F. George Joseph S. Valacich Chapter 15 Finalizing.
1 CMPT 275 Software Engineering Requirements Analysis Process Janice Regan,
Distributed Software Development
Maintain and Modify By: Sahar Aftab (1253 ) and Mehboob Nazim (1085) Central Library.
The What Why and How.  MCTS  These certifications provide the foundation for Microsoft Certification  MCITP  These certifications build on the technical.
FINAL DEMO Apollo Crew, group 3 T SW Development Project.
Dillon: CSE470: SE, Process1 Software Engineering Phases l Definition: What? l Development: How? l Maintenance: Managing change l Umbrella Activities:
Managing the development and purchase of information systems (Part 1)
Page 1 MODEL TEST in the small GENERALIZE PROGRAM PROCESS allocated maintenance changes management documents initial requirement project infrastructure.
Creating a Web Site to Gather Data and Conduct Research.
Team Members David Haas Yun Tang Robert Njoroge Tom Kerwin Clients Facilities Management Don Anderson Rick Klein.
Software Engineering Project: Research Expert Prabhavathi Kumarasamy Joshua Thompson Paul Varcholik University of Central Florida.
Configuration Management (CM)
Statistics Monitor of SPMSII Warrior Team Pu Su Heng Tan Kening Zhang.
PROJECT SECME1 Carthik A. Sharma Juan Carlos Vivanco Majid Ali Khan Santhosh Kumar Grandai Software Engineering Fall 2002.
16 1 Installation  After development and testing, system must be put into operation  Important planning considerations Costs of operating both systems.
1 Software Process Models-ii Presented By; Mehwish Shafiq.
Verb Expansion Game Team 3 Bryan Bloss Jeremy Comardelle Gordon Gable Gleyner Garden Sponsored By: Dr. Beth Young.
Software Development Cycle What is Software? Instructions (computer programs) that when executed provide desired function and performance Data structures.
Project Presentation eProcurement System. M.TECH S16- Team S03 Institute of Systems Science Table of Content Project Background Project Requirement User.
Student Curriculum Planning System MSE Project Presentation I Kevin Sung.
INFO 637Lecture #101 Software Engineering Process II Review INFO 637 Glenn Booker.
Distributed Software Development QR Marks The Spot Beta Prototype Vadym Khatsanovskyy, Nicolas Jacquemoud.
KS3 Phase4 Client Server Monitoring System October 1, 2008 by Stephen, Seema, Kam, Shpetim.
FreeShell Live Final Presenation Jonathan Birch | Greg Chabala | Bryan Kimbro | Mark Sparks.
REAL TIME GPS TRACKING SYSTEM MSE PROJECT PHASE I PRESENTATION Bakor Kamal CIS 895.
Historical Aspects Origin of software engineering –NATO study group coined the term in 1967 Software crisis –Low quality, schedule delay, and cost overrun.
Topics Covered Phase 1: Preliminary investigation Phase 1: Preliminary investigation Phase 2: Feasibility Study Phase 2: Feasibility Study Phase 3: System.
© 2006 ITT Educational Services Inc. SE350 System Analysis for Software Engineers: Unit 10 Slide 1 Chapter 13 Finalizing Design Specifications.
Chapter 6 CASE Tools Software Engineering Chapter 6-- CASE TOOLS
Advanced S/w Eng - s/w productivity issues 1 Software Productivity Issues Why do software projects fail? Advanced Software Engineering COM360 University.
Enigma Mutiara Sdn Bhd Computer Based Learning (CBL) HSE Procedures.
Software Development Life Cycle (SDLC)
07/21/97 MOSS Project Introduction and Definition -Senior Project-
The Juggernaut Team Tyler Douthitt  Project Manager  Lead Website Developer Mike Harman  Lead Programmer Eric Rakers  Lead Documenter  Lead Analyst.
Process Asad Ur Rehman Chief Technology Officer Feditec Enterprise.
Unit 15: SDLC I October 12, Systems Development.
ANALISA & PERANCANGAN SISTEM Disusun Oleh : Dr. Lily Wulandari Program Pasca Sarjana Magister Sistem Informasi Universitas Gunadarma.
Timesheet training Version: Introduction Duration: 1.5 hours Purpose: Guide on how to use Timesheet.
1 Sean Aluoto Anthony Keeley Eric Werner. 2 Project Plan Overview Project Lifecycle model Time line Deliverables Organization plan Risk management Design.
CS 501: Software Engineering Fall 1999 Lecture 22 (a) Managing the Software Process (b) Software Reuse.
Slide 3.1 © The McGraw-Hill Companies, 2002 SOFTWARE LIFE-CYCLE MODELS.
Software Engineering Modern Approaches Eric Braude and Michael Bernstein 1.
Advanced Software Engineering Dr. Cheng
Advanced Higher Computing Science
Software Development - Methodologies
Architecture Review 10/11/2004
Chapter 15 Finalizing Design Specifications
Chapter 15 Finalizing Design Specifications
V-Shaped SDLC Model Lecture-6.
Chapter 15 Finalizing Design Specifications
Course: Module: Lesson # & Name Instructional Material 1 of 32 Lesson Delivery Mode: Lesson Duration: Document Name: 1. Professional Diploma in ERP Systems.
Ensuring Project Success with SpiraTeam & Rapise
AD642 Project Communication: Intro
Lightweight tools for on-line course development
Presentation transcript:

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

Word Guess Team  Team Members  Chakib Kouhel:  Steve Mattingley:  Albertina Limbangan:  Customer  Dr. Beth Young:

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.

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

Word Guess: Existing System

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

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

User Sequence Diagram

Admin Sequence Diagram

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

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 will be acceptable.

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 lib.stanford.edu/cgi-lib/

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.

Work Packages

PERT Chart

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

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)

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

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

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

Questions???