Calculus Review Project Team 9 Presentation 1 February 13, 2003

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

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

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

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

Progress this Quarter Week# Effort Completed Items Meetings, Web Site Up Configuration Management Plan Feasibility Report, UI Prototypes, Project Plan Use Cases Webspace Setup, Reqs. Draft Reqs Specifications Reqs. Update, More Prototypes Implementation, Presentation

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...

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.

Requirements: Problem Domain Model

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

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

Requirements: Maintainability Problem Adder Subject Adder Moderator Controls

Requirements: Security Forum Controls Professor Access Limits Student Access

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

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

Design: Main Page – Topics & Subtopics

Design: Gaining Knowledge in a Forum

Design: Asking for Help and Answering

Design: Practice Problem Database

Things We Learned Shorter meetings are better than long ones Rushed meetings are worse than leisurely meetings Communication through 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)

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?

Questions? Thank you for your time. More information about the Calculus Review Project can be found at