1 / 33

The Fitness Zone Database CSCI 6838 Team #1 April 10 th , Spring 2007

The Fitness Zone Database CSCI 6838 Team #1 April 10 th , Spring 2007. Hala Annab Mark B. Jones Wei (Lawrence) Liu Jacqueline M. Matekwa Mbata. Team Information. Team Members Hala Annab halaannab@yahoo.com Mark B. Jones Mark.B.Jones@uth.tmc.edu

dinah
Download Presentation

The Fitness Zone Database CSCI 6838 Team #1 April 10 th , Spring 2007

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. The Fitness Zone DatabaseCSCI 6838 Team #1April 10th, 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 application needs to track: • facility usage • program participation • use of services. • Designing a three tier Web application • The application needs to 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 • FZ needs an application to track facility usage, program participation, and use of services. • 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 is not saved to a centralized database • Look and feel is not user-friendly • Documentation and user guide are not sufficient • Show Stopper • Crystal reports will not run • User has to type 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 • MS Access is sufficient but not an enterprise solution • System • Needed from UCT • Install IIS • Upgrade to .NET framework 2.0 • 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. Database Design

  15. Database Schema - 1 • Persons • personID, … , typeID • PersonType • typeID, description • Some person type descriptions: • Employees • Student Employee • Students • Alumni • Dependants • Guests

  16. Database Schema - 2 • Programs • programIndex, programName, startDate, endDate, … • MemberPrograms • programIndex, personIndex • startDate, endDate, progress • fee, • goals

  17. Database Schema - 3 • Membership • lockerID, joinDate, endDate • membershipStatus, termIndex, • medicalCondition • tuitionPaymentStatus, membershipFeePayment, … • Sessions • date, timeIn, timeOut • Rentals • rentalIndex, termIndex, membershipIndex, lockerIndex, fee

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

  19. Implementation Issues • Problems Encountered: • Old Version of .NET Framework (1.1) • IIS was not installed • Needed a solution for developing graphical reports • Solutions: Worked with Mentor and UCT to: • Update the .NET Framework to version 2.0 • Install the IIS Web Server. We found a third party tool for developing graphical reports with ASP.NET.

  20. Previous Application

  21. User Interface

  22. User Interface

  23. User Interface

  24. Project Screenshots

  25. Prototype Evaluation • More intuitive and User Friendly • Employee work flow and repetitive tasks were considered in UI design • Scaleable / easy to maintain • All features are not yet complete • Complete features are independent, useful, and immediately useable

  26. Vision for the Future • Move to a public Web server • Members will access the system directly • Reduce the work load for the manager and staff • Add services and convenience for members. • Migrate to a more robust database • MS SQL Server, Oracle, or MySQL. • The system is designed with the future in mind • The application will scale as usage increases • Additional functionality can be added easily

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

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

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

  30. Development Team (Project Plan)

  31. Conclusions • The project has been successful • Detailed Requirements were documented • Database design is vastly improved • User Interface is more intuitive • Available features are fully functional • System architecture is moreflexible, scalable, and maintainable • System documentation is improved

  32. Suggested Next Steps • Complete the Program management features • Create a new program • Create participation report • Automated email messages to participants • Complete the group email report • Send mail to “locker renters” or “expiring members” • Streamline the User Interface

  33. References • Project Requirement -- Original Project Description • Group 3, Summer 2006 -- Previous Project Website • User’s Website -- UHCL Fitness Zone Home Page • Reporting tool -- ASP.NET control – WebChart • Program Standard -- C# Coding Standards

More Related