Transcript Mid-Term Progress

The Fitness Zone Database
CSCI 6838 Team #1
March 1st, Spring 2007
Hala Annab
Mark B. Jones
Wei (Lawrence) Liu
Jacqueline M. Matekwa Mbata
Team Information
Team Members




Hala Annab
Mark B. Jones
Wei (Lawrence) Liu
Jacqueline M. Matekwa Mbata
Mentor

Ms. Denise B. Cazes
Professor

Dr. Kwok-Bun Yue
[email protected]
[email protected]
[email protected]
[email protected]
Customer Information
UHCL Student Life Fitness Zone


Denise Cazes, Fitness Zone Coordinator
2700 Bay Area Blvd.
Houston, TX 77058
www.uhcl.edu/fitnesszone
Front Desk: 281-283-2410
Coordinator: 281-283-3328
E-mail: [email protected]
Table of Contents






Introduction
Problem Analysis........................ Lawrence
Design ....................................... Jacqueline
Implementation........................... Hala
Project Management ................. Mark
References
Problem Analysis



Project Abstract
Problem Specification
Constraints and Limitations
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
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.
Problem Specification

Problem of current system
–
–
–
–

Show Stopper
–
–

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
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
Constraints and Limitations

Network
–

Database
–

Access is not optimal choice but have to use
System
–
–
–

Cannot access the system off campus
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
Design



Three tier Web application architecture
Will run locally in the Fitness Zone
Client access via UHCL network
System Architecture
intranet
`
Application Server
Database
DataBase
Use Case Diagram
Update a Password
Add a New Program
Update an Existing Program
Administrator
Manager
Assign a Role
Revoke a Role
Generate a Report
Use Case Diagram
Search for Member
Check Member In
Update Activity Log
Add a Session
Check Member Out
Register a Member
Operator
Update a Membership
View a Report
Update 100 Mile Club Log
Abstract Class Diagram
Member
Program
0..*
100 Mile Club
Yoga
Services
1..*
0..*
Primary Member
0..*
Dependant
1
Rentals
0..n
1
Person
Non-UHCL person is a
UHCL person is a
guests or dependants
of UHCL persons
UHCL Person
persons with
a UHCL ID
Student
Faculty
None UHCL Person
Staff
Alumni
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 )
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)
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)
Implementation

Three Tier Web Application
–
–
–
–
–
Microsoft IIS Web Server
Presentation layer (ASP.NET)
WebControl for creating charts (WebChart)
Business logic (C#)
Database (MS Access)
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.
Mockup Examples
Mockup Examples
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.
Project Management

Development Team
–
–
–

Roles
Major Tasks
Project Plan
Conclusions
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.
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
Development Team (Project Plan)
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
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