0% found this document useful (0 votes)
117 views4 pages

Project 1

The document proposes a sports web application that allows users to view sports teams and players. It will follow an MVC design pattern and include tables for sports, teams, players, and divisions with primary and foreign keys to link them. Administrators can add, modify, and delete data while users can navigate between sports and view team and player information.

Uploaded by

api-427618266
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
117 views4 pages

Project 1

The document proposes a sports web application that allows users to view sports teams and players. It will follow an MVC design pattern and include tables for sports, teams, players, and divisions with primary and foreign keys to link them. Administrators can add, modify, and delete data while users can navigate between sports and view team and player information.

Uploaded by

api-427618266
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 4

Sports Engine

by Yauheniya Nikulyak, Thach Doan, Lacey Sikes


Main Project Idea:
Sports page for sports fans to view teams and players from various sports.

Approach:
- Elements of MVC (model view controller) design pattern for web app.

Potential Users:
- Users (sports fans)
- System administrators

System-wide interactions:
- Users:
- Navigate sports, divisions, teams, and view players
- Admins:
- Add, delete, modify sports, divisions, teams, players.

Tables and their properties:


- Sports:
- Sport_id (primary key)
- Sport_name
- sport_description

- Team
- Team_id (primary key)
- Team_name
- Sport_id (foreign key)
- Division_id (foreign key)

- Team_members
- Team_id (foreign key)
- Player_id (foreign key)

- Player
- Player_id (primary key)
- Player_first_name
- Player_last_name
- Player_position

- Division:
- Division_id (primary key)
- Division_name
- sport_id (foreign key)

Admin:
- Admin_id (primary key)
- Admin_first_name
- Admin_last_name
- Admin_user_name
- Admin password
E-R Diagram

Normalization
Our table is normalized. We have organized our tables in such a way that reduces
redundancy. Our tables have been reduced in size and are linked by id’s to provide
appropriate relationships between them.

You might also like