ELP Helper MSE Project Presentation I Aghsan Ahmad Major Professor: Dr. Bill Hankley

Presentation Outline Project Overview Data Flow Diagram (Current System) Use case Project Requirements Class diagram Cost Estimate Gantt chart Task breakdown Questions

Project Overview The motivation of the project comes from the English Language Program’s desire to have a software which facilitates the input of data and places international students into proper levels. This should be done automatically by the computer instead of manually, making the process easier and requiring less time and work.

Data Flow Diagram (Current System)

The EPT Scores are: Listing score Reading score Writing score Essay score

Data Flow Diagram

The general guideline EPT Score136 level138 level140 level150 level152 levelKSU Support Classes Total Score Part ScoreNA EssayNA Table 1

Data Flow Diagram

Testing Database

Data Flow Diagram

The EPT score report

Data Flow Diagram

The recommendation and achievement score Days attended Homework done Tests taken Credit /Not Credit Class Achievement

The recommendation and achievement report

Data Flow Diagram

The EPT Evaluation report

Use Case

Project Requirements(1) Placement Of New Students Purpose: New students will be placed in a level of the ELP based on their English Proficiency Test (EPT) score. Input: The user will select “import from Excel” button to invoke EPT score from the Excel file that is provided by the library. Processing: The software will calculate the total score which is the overall guiding factor for the new student. Output: Place new students in a suitable level based on their EPT score.

Project Requirements

Project Requirements(2) Placement Of Returning Students Purpose: The purpose of this part of the application is to enable the user to place the returning students in the appropriate level based on three criteria. Input:1-EPT Score from the test taken at the end of the previous semester. 2-Achievement test score given in every class at the end of every semester. 3-Positive teacher recommendations. Processing: The ELP Helper first checks the EPT test, If the EPT test has not been changed to let a student move up to higher level, it checks the teacher recommendations and achievement test score. Output: Place students in the suitable level, either they move up to another level or stay in the same level.

Project Requirements

Project Requirements(3) Divide levels in subgroups Purpose: The purpose of this part of the application is to enable the user to divide up a big level into many sections so that teachers can recommend their students via the internet. Input: Select students’ name, group’s name, level, and current year. Processing: The ELP Helper divides up the level into groups depending on the user selection. Output: Each student will be placed in his/her group in his/her level.

Project Requirements(3)

Project Requirements(4) Teacher's recommendation Purpose: The purpose of this part of the application is to enable teachers to recommend and enter the achievement score of their returning students via the internet. Input: A teacher enters password and username to login, they then fill in boxes, and enter percentage for the students score. Processing: Save these scores in the database to use for student placement and see if the achievement score is less than or greater than 80%. Output: Place students into the propel level based upon their EPT score, recommendation, and achievement score then print the class achievement report.

Project Requirements(4)

Class Diagram

Cost Estimate The COCOMO model developed by Barry Boehm will be used to estimate project effort and project time. The ELP Helper will be an application of average complexity but with an extensive database. The COCOMO model classifies such projects as “organic” and provides the following equations to calculate effort and time: Effort = 3.2* EAF (size)^1.05 Time (in months) = 2.5(Effort)^0.38 Where Effort = number of staff months (PM) EAF = effort adjustment factor Size = number of lines of code for completed product. It is measured in KLOC (thousands of lines of codes) Time = total number of months

Cost Estimate(2) The EAF value based on the adjustment factors being assumed evaluated to 0.9. I estimated the size to be 2000 LOC based on the current prototype and similar examples. The effort evaluates to: Effort = 3.2*0.9*2.0^1.05 = 5.9 staff months The time can now be calculated as: Time = 2.5*5.9^0.38 = 4.9 months

Gantt Chart

Task breakdown Inception Phase(Phase 1 ) Vision Document SQA Plan Project Plan Prototype Phase 1 PresentationDate: March 6th 2008 Elaboration Phase (Phase 2) Revise Vision Document Revise SQA Plan Revise Project Plan Develop Formal Requirement Specification Architecture Design Develop Test Plan Formal Technical Inspection Develop Prototype Phase 2 Presentation Date: April 14th 2008

Task breakdown (2) Production Phase(Phase 3) Develop Code Testing Functional Testing Evaluate Test Result Documentation Write Test Report Write User Manual Final Presentation Preparation Phase 3 Presentation Date: Jul 7th 2008

Questions ?