1. Calculus Review Project Team 9 Presentation 1 February 13, 2003

2. About Us Matt Stupca Court Caldwell Zach Lute Alex Kutsenok Steve Hoelle Tim Jasko Chris Scribner

3. Presentation Overview Introduction Our Approach Progress Made Requirements Specifications Design Lessons Learned What’s Next Questions

4. Introduction Our client: Dr. Finn from RHIT’s Math Department Our task: Create an on-line calculus review site It must contain –notes and other review materials –sample problems and solutions –a forum for students and professors Allow professors to keep track of student activity on the site

5. Our Approach Start with a simple system –provides basic functionality –one area of Calculus –shows previously entered info –no mathematical notation –try to get it done by the end of the quarter Add features iteratively –all other areas of Calculus –deal with problems and solutions –deal with teacher-student interaction –mathematical notation –recording and displaying statistics

6. Progress this Quarter Week# Effort Completed Items 1 795 Meetings, Web Site Up 2 1355 Configuration Management Plan 3 2430 Feasibility Report, UI Prototypes, Project Plan 4 2720 Use Cases 5 1025 Webspace Setup, Reqs. Draft 6 1005 Reqs Specifications 7 1610 Reqs. Update, More Prototypes 8 925 Implementation, Presentation

7. Other Metrics 554 lines of code, 12 hours spent on implementation 114 pages of documentation 25% of time spent in meetings 53 hours spent on Requirements Analysis Speaking of Requirements...

8. Requirements Analysis Some design before requirements analysis. Birth of the Content Controller. Actual requirements analysis was very time consuming. Consistent documentation template for all requirements analysis documents.

9. Requirements: Problem Domain Model

10. Requirements: User Environment and Characteristics Student –A Rose-Hulman student –Looking for a refresher on calculus material –Seniors taking exams. Faculty –Rose-Hulman math faculty –Create content and moderate system Skills –Basic computer skills, –Familiarity with standard internet navigation Environment –PC with internet connection –Guaranteed to work with Internet Explorer

11. Requirements: Logical Database User Profile Database –Frequently accessed –Fast response time –Data integrity important, yet not vital Topics, Examples, and Practice Problems DB –Frequently accessed –Fast response time –Data integrity vital

12. Requirements: Maintainability Problem Adder Subject Adder Moderator Controls

13. Requirements: Security Forum Controls Professor Access Limits Student Access

14. Requirements: Performance User Limits Response Time Web Page-esque Behavior And now for the design...

15. Design: Prototypes Nonfunctional Prototype –Decided on Forum System –Topics and Subtopics –Gaining Information –Asking for Help –Getting Practice Problems Functional Prototype

16. Design: Main Page – Topics & Subtopics

17. Design: Gaining Knowledge in a Forum

18. Design: Asking for Help and Answering

19. Design: Practice Problem Database

20. Things We Learned Shorter meetings are better than long ones Rushed meetings are worse than leisurely meetings Communication through e-mail and the forum is a good idea Doing things ahead of time reduces stress and errors Separation of Church and State (Requirements Analysis and Design)

21. What’s Next? Dealing with math notation Problems and Solutions Implementing the Student/Teacher Interaction System User profile tracking Executing the Test Plan –Do we have a quality product? –Does our quality product do what it is supposed to?

22. Questions? Thank you for your time. More information about the Calculus Review Project can be found at http://www.rose-hulman.edu/Class/cs/cs414/Projects/team9/web/