1. ELP Helper MSE Project Presentation II Aghsan Ahmad Major professor: Dr. Hankley

2. Presentation Outline: Action Items from Presentation I Architecture Design Test Plan Formal Requirements Specification Architecture Prototype Formal technical inspection letters Questions

3. Action Item(1)Verifications - Each student has a unique test number. - No recommendation for new students - If there is a null level for a student that implies there is no grade neither recommendation. for new students: students placement level matches their Excel sheet --> According to the TestNo. for returning students placement level matches their Excel sheet --> According to the TestNo. and a teacher recommendation.

4. Action Item (2) Forms and Reports In my project I will use Crystal Reports for Visual Studio.NET to generate reports; these reports will be printed by the clerk. My project scope covers printing students’ reports, not sending them to students by email.

5. Action Item (3) Generating data ELP will give me data testing to test my program besides using generator data tool to generate random data (EMS Data Generator). The tool will generate 1000 of record for student information and their scores.

6. Action Item (4) COCOMO model estimates I followed these steps to estimate the cost and the size of the my project Determine and count five information domain characteristics: inputs, outputs, inquiries, files, and external interfaces. Compute the Function Points following the formula: FP =  UFP  [0.65 + 0.01   (Fi)], which Fi are “complexity adjustment values”. Calculate the Source Lines of Code with the help of the AFP and the Language Factor (LF). After that I applied the COCOMO formula for the application program.

7. COCOMO model estimates The COCOMO formula for the application program: Delivered Source Instructions (KDSI) = 1.7655 K Programmer Effort (PM) = 2.4 × (KDSI) ^1.05 = 4.4 programmer-month Development Time in month (TDEV) = 2.5 × (PM) 0.38 = 4.4 months

8. Architecture Design for the client application (Clerk) The Architecture Design for the client application is based on a two-tier architecture which contains of 1- Presentation and Business Tier 3- Data Tier.

9. Page flow diagram for the client application (Clerk) C#.NET Application forms

10. Architecture Design for the web application (Teacher) The Architecture Design for the web application is based on a three-tier architecture which contains of three logic tiers: 1- Presentation 2- Business 3- Data.

11. Page flow diagram for the web application (Teacher)

12. Domain Model

13. Domain Model(2)

14. Sequence Diagrams (Add a New Student)

15. Sequence Diagrams (Search)

16. Sequence Diagrams (Teacher Login)

17. Sequence Diagrams (Teacher Recommendation)

18. Test Plan Type of testing Unit testing, using NUnit testing tool. Performance testing using JMeter tool.

19. Test Plan The following items will be tested

20. Adding new students

21. Import EPT scores

22. Placement returning students

23. Formal Requirements Specification Constraints Each student has a unique test number. No recommendation for new students If there is a null level for a student that implies there is no grade neither recommendation. for new students: students placement level matches their Excel sheet --> According to the TestNo. for returning students placement level matches their Excel sheet --> According to the TestNo. and a teacher recommendation.

24. Formal Requirements Specification (1) Each student has a unique test number. context Student inv UniqueTestNo: Student.allInstances -> forAll(S1, S2 |S1 <> S2 implies S1.TestNo <> S2.TestNo)

25. Formal Requirements Specification (2) - No recommendation for new students context s: Student inv noRecomNewStudents: s.status = #new implies s.recommendation -> isEmpty()

26. Formal Requirements Specification (3) If there is a null level for a student that implies there is no grade neither recommendation. context s: Student inv nulLevelNoGradeNoRec: s.curr_level= #null implies s.recommendation-> isEmpty() and s.grade -> isEmpty()

27. Formal Requirements Specification (4) for new students: students placement level matches their Excel sheet --According to the TestNo. for returning students placement level matches their Excel sheet --> According to the TestNo. and a teacher recommendation.

28. context s: Student inv Placement : if s.status = #new and s.flagImportCurrentSeme= #yes then lookup (s.grade)->forAll(sc|sc.l = curr_level) --not a new student else (lookup(s.grade)->forAll(sc|sc.l = curr_level) ) (if sc.l == s.placed= #curr) then (if (s.recommendation.AchivementScore >= 80) ) then ( (s.placed = #newLevel) ) else (s.curr_level= #newLevel) endif

29. Prototype

30. Formal technical inspection The letters are submitted by 2 MSE students : Reshma Sawant Vamsi Mummaneni Letters are posted online at

31. Question