The Fitness Zone Database CSCI 6838 Team #1 March 1 st , Spring 2007

1. The Fitness Zone DatabaseCSCI 6838 Team #1March 1st, Spring 2007 Hala Annab Mark B. Jones Wei (Lawrence) Liu Jacqueline M. Matekwa Mbata

2. Team Information Team Members • Hala Annab halaannab@yahoo.com • Mark B. Jones Mark.B.Jones@uth.tmc.edu • Wei (Lawrence) Liu lawrence_liu@hotmail.com • Jacqueline M. Matekwa Mbata MatekwaMbataJ2428@uhcl.edu Mentor • Ms. Denise B. Cazes Professor • Dr. Kwok-Bun Yue

3. Customer Information UHCL Student Life Fitness Zone • Denise Cazes, Fitness Zone Coordinator2700 Bay Area Blvd.Houston, TX 77058 • www.uhcl.edu/fitnesszoneFront Desk: 281-283-2410Coordinator: 281-283-3328E-mail: cazes@uhcl.edu

4. Table of Contents • Introduction • Problem Analysis........................ Lawrence • Design ....................................... Jacqueline • Implementation........................... Hala • Project Management ................. Mark • References

5. Problem Analysis • Project Abstract • Problem Specification • Constraints and Limitations

6. Project Abstract • The UHCL Fitness Center needs an application to track facility usage, program participation, and use of services. • Designing a three tier Web application • The application will be • Easy to support • Scalable

7. Problem Specification • The UHCL Fitness Center runs several programs and services • Fitness Zone membership • 100 Mile Club • locker rental • for students, faculty, staff, alumni, and family of faculty and staff. • FZ needs an application to track facility usage, program participation, and use of services. • This application will be supported by a Computer Science Student Assistant • needs to be scaleable to support future programs and direct access by members.

8. Problem Specification • Problem of current system • Some modules are not executing • Data are not saved to a centralized database • Look and feel is not user-friendly • Documentation and user guide are not sufficient • Show Stopper • Crystal report shots exception and cannot run • User has to punch the data into MS Excel instead • Conclusion from end user • Project was not complete

9. Constraints and Limitations • Network • Cannot access the system off campus • Database • Access is not optimal choice but have to use • System • Need UCT to set up IIS • Need to migrate from .NET framework 1.1 to 2.0 • Need UCT to grant administrator access • Project Scope • Fulfill user’s requirements and set up a good architecture • Leave space for future improvement • Not enough time or resources to elaborate and resolve all issues

10. Design • Three tier Web application architecture • Will run locally in the Fitness Zone • Client access via UHCL network

11. System Architecture

12. Use Case Diagram

13. Use Case Diagram

14. Abstract Class Diagram

15. Database Schema - 1 • Persons (personID, firstName, lastName, addressID, birthDate, gender, username, password, driverLicence, uhclID, typeID) • PersonType (typeID, description) • Employees(employeeID, personID, departmentName, category, addressID) • StudentEmployee (studentEmpID, personID, employeeID, departmentName, category, addressID ) • Students(studentIndex, personID, major, addressID) • Alumni (alumniID, employerName, personID, addressID) • Dependants (dependantID, personID, uhclID) • Guests (guestID, checkInDate, personID, relationship, programID, timeIn, timeOut )

16. Database Schema - 2 • Programs (programID, programName, description, offered, fee) • Services (serviceID, serviceName, description, offered, fee) • MemberPrograms (programID, memberID, startDate, endDate, progress) • MemberServices (serviceID, memberID, startDate, endDate, progress) • Membership (memberID, lockerID, joinDate, endDate, membershipStatus, personID, membershipTypeID, medicalCondition, tuitionPaymentStatus, membershipFeePayment) • MembershipType (membershipTypeID, description)

17. Database Schema - 3 • Addresses (addressID, street, city, state, zipCode, country) • Phonebook (phonebookID, workPhone, mobilePhone, faxNumber, emailAddress, pager, personID) • EmergencyContacts (contactID, firstName, lastName, email, phoneNumber, personID) • Lockers (lockerID, number, rented) • Sessions (sessionID, personID, date, timeIn, timeOut) • Rentals (rentalID, rentalType, memberID, lockerID, fee) • RentalTypes (rentalTypeID, description) • MedicalCondition (medicalConditionID, memberID, description) • MemberMedicalCondition (medicalConditionID, memberID)

18. Implementation • Three Tier Web Application • Microsoft IIS Web Server • Presentation layer (ASP.NET) • WebControl for creating charts (WebChart) • Business logic (C#) • Database (MS Access)

19. Implementation Issues • Problems Encountered: • Old Version of .NetFramework (1.1) • IIS is not installed • Using Charts is not direct. The need to come with a solution to develop a webchart. • Techniques used to overcome: Ask Mentor and the UCT to do the following: • Update the .NetFrameWork to version 2. • Install the IIS Web Server. We found a solution to develop a webchart with ASP.NET. We have tried a small application to make sure it works.

20. Mockup Examples

21. Mockup Examples

22. Future Directions • The vision for the future • move to a public Web server • members will access the system directly. • This should reduce the work load for the manager and staff • Add services and convenience for members. • As the system grows it may also be necessary to migrate to a more robust database such as MS SQL Server, Oracle, or MySQL. • The system will be designed with the future in mind • application will scale as usage increases • additional functionality can be added easily.

23. Project Management • Development Team • Roles • Major Tasks • Project Plan • Conclusions

24. Development Team (Roles) • Team Leader (Mark) • organize team efforts • ensure that the team is satisfying all course requirements. • Webmaster (Mark, Jacqueline) • maintain the Project Web site. • DBA (Jacqueline, Hala) • design, document, implement, and maintain the project database. • Lead Programmer (Lawrence, Hala) • design the structure of the application modules • guide the coding efforts of other team members. • System Administrator (Hala, Lawrence) • evaluating the computers in the Fitness center & install software. • Technical Writer (Mark, Hala) • edit the documents produced by the team.

25. Development Team (Major Tasks) • Determine Requirements • Evaluate existing application • Choose Technologies for Implementation • Design and Implement Prototype • Create complete and detailed documentation • Install system and train Fitness Zone staff

26. Development Team (Project Plan)

27. Conclusions • The project is going according to schedule • The Requirements Analysis Phase is complete and the Design Phase is well underway • Implementation constraints encountered have been resolved by consulting with our client, UCT officials and our advisor. • With MS IIS, ASP .NET with C#, and Access database, the team expects to develop an application that fully meets the user requirements. • The database may be migrated to a more robust system such as the SQL Server in the future

28. References • Project Requirement -- Original Project Description • Group 3, Summer 2006 -- Previous Project Website • User’s Website -- UHCL Fitness Zone Home Page • Future reporting tool -- Third Party ASP.Net controls – WebChart • Program Standard -- C# Coding Standards