NHL Hockey Team with Arena Database Management Project Proposal
NHL Hockey Team with Arena Database Management Project Proposal
Project Title: Flying Elbows Database Management Proposal
Project Designers Information (Sweta Gondaliya, 2859976@vikes.csuohio.edu, +1-216-301-9701)
Submitted to: Dr. Chengfor IST 634 (Enterprise Databases) Fall 2022 Project
Proposal date: September 12, 2022
Topic Research and Executive Summary
Online Arena management business for NHL Hockey Team is made through desktop application called Flying Elbows. The 23 teams developed the National Hockey League (NHL), a non-profit organization, to run the league. Logistics for the league, broadcasting, television, team services, corporate communications, public relations, and special events are handled by its offices. Users can also enjoy special offers and vouchers while online booking as well as premium ticket holders get some extra rewards. The National Hockey League Enterprise (NHLE) is the league's for-profit marketing branch. Currently, the sources of money for NHL come from gate collections, media, stadium related revenues, licensing, and merchandising.
Statement Of Work
Project Description:
To assist the conception and development of league-wide NHL projects and to curate material to improve the fan experience in this new environment, we are looking for a Project Manager/Asset Manager to join the NHL's Studios team. Content curation, video editing, metadata tagging, asset management, and content delivery are all necessary for this profession. The ideal applicant will be highly driven, well-organized, and capable of performing admirably under pressure. The ideal candidate would be well-versed in the history, organizations, athletes, and coaches of the NHL as well as in sports in general. The ideal team player must be able to manage several aspects of media content development to succeed in this job. This is an exciting new chance to influence the NHL's.
Challenges:
Maintaining the live server will be our biggest problem.
Another difficulty I can encounter is the possibility of data loss with each new update as I attempt to integrate new features.
Retrieving data would be a difficulty for me in case of system failure. Handling heavy traffic on the desktop application can also be a challenge that I may encounter.
Finally, I need to develop programming skills like C# (if the applications coding will do in C#)
Another challenge is that:
Ticketing Interface
Slot Management: close bookings
Consumer cancellation option for reservation
Calendar-based booking management: via calendar
Streaming online booking process
Project Management Approaches, Schedule, and Milestones
I have more than 2 years IT experience at Private Company as Software Quality Analyst. My project was one of the widely used social media application. We worked on a Task Tool to perform all operations such as Bug Tracking, Bug Filling, Test Case Design and so on. I also trained 2 trainees under my observation. I gained a lot of knowledge about managing a team and getting work from a coworker there. My projects' major pillars are time management. I can't wait to add my expertise and experience to this project and see it through to the end.
The Project Schedule and Task Gantt Chart is as follows:
Analysis: Identify the business model and needs. (NHL Hockey Team with Arena)
Logical Diagram: Use connection database with the admin database with the users, it means admin have all access for all databases.
Physical Diagram: Main issues is that how to connect database with the source code.
Prototype: In this section I need to design a fronted and choose best templet for my desktop application and then design a form for take data user. Secondly design a how to show data in admin panel.
Performance Evaluation: Firstly, I need to check database connection is perfect or not if connection is proper then check CRUD queries.
Methodology and Implementation Plan
This project will employ the (RAD) Rapid Application Development approach. In the software development business, rapid application development (RAD) is a well-liked agile project management technique. Quick project turnaround is a RAD approach's key benefit, which makes it a desirable option for workers working in a hectic setting like software development. RAD divides the numerous activities into manageable chunks that may be finished rapidly. The implementation and methodology phase are one of the most important parts of database design because it defines the logic phase. A good strategy is needed to implement a database to store user data. Implementations are affected by available operating systems, database management systems, and database tools. The plans involve the implementation of the database and the database engines. User data is stored in a user-defined, user-entered database. Management tasks related to the entire data business component are supported. The logic of the implementation requires a detailed understanding of the functions provided by database systems. One of the challenges I faced was the need to design with the right implementation.
At the end of the project, users can easily book tickets from the application
You can use calendar-based booking for pre-booking
Consumers can also book meals from the application
Users can also watch live broadcasts from the application
Data Flow Diagram:
Expected Results: The Deliverables
Flying Elbows can expect to receive an application executable file and an Access Database file.
User can book tickets for the upcoming hockey match as well as can see the schedule of upcoming matches. Ticket buyer can also get cancellation ticket option and refund options according to terms and condition. User can see broadcasting from the application. Users can order food from premises restaurant.
Personnel
I have completed my undergraduate in Information Technology in the year of 2020 from India with the CGPA of 3.4. I have a more than 2 years of experience as a Software Quality Analyst in Private company on widely used social media application project. I am interested in Quality Assurance because I believe that customer should get defect free application. I am currently pursuing masters degree in Information Systems (MIS) from Cleveland State University and expected to graduating by 2024.
Supporting Facilities
Supporting Facilities for this endeavor includes Microsoft Access Database (DB Design and Implementation), Visual Studio (C#), Visio and Frontend Coding (HTML, CSS).
Project Progressive Report
Reporter: Sweta Gondaliya
Progressive Description & Milestones:
Analysis:
Identify the Business Models (09/16/2022): Advantage of the NHL Hockey Team with Arena Is user can enjoy live broadcasting by sitting at their comfort zone and users can also enjoy special offers and vouchers while online booking as well as premium ticket holders get some extra rewards. It will be hard to manage all players data and visitors have to wait in a long line to buy tickets if this online application does not develop. Another drawback is that people who are not able to come at stadium not able to enjoy match due to absence of live broadcasting.
Business Investigation (09/16/2022): Through our desktop application users can buy ticket from anywhere without standing in line and can also order food while watching a match at stadium at their place by using any kind of E-payment method such as mobile money and banking service. We are developing and operating systems that allow inquires and prebooking for upcoming matches. For many people, it is difficult to visit inquiry office of stadium to get information about matches.
Defining the Mission Statement (09/18/2022): The Database management system is intended to handle queries about the NHL Hockey Team with Arena and the operational process to make it more user-friendly for all types of users. The business operations involving customers, equipment, and employees. It keeps data organized rather than on paper, reducing duplication and boosting efficiency concerning data security.
Dialogue to support Mission Statement (09/20/2022): The Vice President of Flying Elbows was interviewed to determine operational needs and define a mission statement.
Me: Could you please explain why you believe you require database?
Manager: The NHL requires a database to track information about its teams and games. It will also keep track of all the information on screenings, ticketing, and seating also with the arena and spectators details. I would also like to keep track on the ongoing ticket sales and forthcoming events.
Me: what is the main goal of this project?
Manager: The main purpose of that project is developing convenient online facility to buy tickets of matches for users and provide live broadcasting to users so they can watch from anywhere without leaving their comfort zone.
Me: How are assets managed?
Manager: Same as paperback document. By managing these resources and scheduling them digitally, you can avoid a lot of the hassle and lost revenue of scheduled tickets.
Me: Why user come online to buy ticket and use your application?
Manager: Our Desktop Application is user friendly, moreover users will not face any inconvenience while buying tickets.
Me: Tell me about your worries about ensuring the success of your operation.
Manager: To begin with, customers purchasing tickets is a must (Hahaha). Furthermore, a portion of each slot is used to cover operational costs. Cost is a major concern for us. To reach the masses, we must conduct extensive offline and online marketing. We are paying close to 60% of our revenue between the upcoming event and the final payment before we can see any profit. We need to make the most of every game played in the arena.
Me: Thank you so much for your time, patience, and consideration.
Manager: Appreciate.
Defining the Mission Objectives (09/20/2022):
Provide best customers policies.
Maintain a data of upcoming matches.
Maintain a data of players.
Keep track of ticket sales.
Maintain a quality of live broadcasting of matches.
To keep the track of snack sales in the arena.
Allow price adjustments to be saved and applied to ticket sales based on purchase and sale dates.
Maintain equipment which are available at arena.
Maintain arena according to different events.
Maintain floor(grass) in arena.
Dialogue to support Mission Objectives (09/21/2022): We consulted with the representative Operations Manager at Flying Elbows to determine specific objectives that would help the development team achieve the goals outlined in the mission statement.
Me: What are your expectations in terms of the requirements?
Manager: As the manager, In the event of a complaint, I should be able to examine and verify all payments. Additionally, I want to make sure that everything is in its proper location and that all the information is accurate.
Me: What do you expect from your employees?
Manager: I sincerely hope they are at ease with the system and with the paper and pen that the changes go smoothly.
Me: How are the tickets priced?
Manager: There is a base charge for each stand in the arena. Additional charges include Taxes and fees. Nevertheless, there is an additional cost adjustment based on how close the hockey game is to the scheduled date. Based on expected demand, we can alter the pricing. (Where the time of year and climate also have a big impact.) Despite appearing to be quite complicated on paper, this is a feature that adds some value for us, and believe me, we use it frequently.
Logical Design:
The List of Subjects (09/21/2022):
Arena
Customers
Team
Coach
Players
Games
Sponsors
Ticket Sales
Live Broadcasting
Employee
Agent
Pay Roll
Maintenance
Food & Beverages
Equipment
Suppliers
Inventory
F&B Billing
Invoice
Dialogue to Support List of Subjects (09/21/2022):
Me: How user can find upcoming matches list and availability of food in restaurant?
Manager: First, user can go into Matches field there will be a list of matches and by going to the one particular match they can buy ticket and get other information and from the Restaurant field they can find food and drink menu including price.
Me: How user can contact you if they face any problem while buying ticket or accessing application.
Manager: User can find the contact details in the Contact Us field and call us on given contact number or you can also send your problem through email also.
Me: Would your NHL Hockey Team with Arena framework business data be protected and cannot be addressed by outsiders?
Manager: Yes, the sender is prohibited from violating our database's safeguarded data.
The List of Characteristics (09/28/2022):
Employee Id
First Name
Last Name
Email Id
Contact
Address
City
State
Zip Code
Job Position
Work Shift
Gender
Customer Id
Arena Id
Arena Name
Ticket Id
Price
Quantity
Date & Time
Sponsor Id
Coach Id
Team Id
Player Id
Agent Id
Game Records
Inventory Name
Supplier Id
Description
Maintenance Id
Category
Comments
Product Id
Total Amount
Payment Type
Invoice Id
Total Salary
Deduction
Equipment Id
Dialogue to Support List of Characteristics (09/28/2022):
Me: How will you go about keeping track of your customers' information?
Manager: All our customers' relevant paperwork will be stored in the database, making it simple to track down and keep track of their records.
Me: What criteria do you use when hiring new employees?
Manager: By keeping an eye on each employee's reputation for prior years of experience, we can determine which of them is qualified to perform in their positions.
Me: How do you attract your clients?
Manager: At Arena, we offer fantastic customer service, including coupons, competitive pricing, and excellent consumer policies.
Me: Thank you for sharing your plan.
The Preliminary Field List (09/29/2022):
Arena Id
Arena Name
Arena Address
Arena City
Arena State
Arena Zip Code
Product Id
Product Name
Product Category
Product Price
Product Quantity
Customer Id
Customer First Name
Customer Last Name
Customer Email Id
Customer Phone Number
Customer Address
Customer City
Customer State
Customer Zip Code
Customer Gender
Employee Id
Employee First Name
Employee Last Name
Employee Email Id
Employee Phone Number
Employee Address
Employee City
Employee State
Employee Zip Code
Employee Gender
Employee Job Position
Employee Working Shift
Team Id
Team Name
Coach Id
Coach First Name
Coach Last Name
Player Id
Player First Name
Player Last Name
Number of Games
Team Id
Sponsor Id
Sponsor Name
Invoice Id
Total Amount
Payment Type
Payment Date & Time
Live Broadcasting
Equipment Id
Equipment Name
Equipment Quantity
Agent Id
Agent First Name
Agent Last Name
Agent Email Id
Agent Phone Number
Payroll Id
Payment Date
Total Salary
Final Amount Paid
Ticket Id
Ticket Price
Ticket Quantity
Ticket Date & Time
Inventory Name
Inventory Quantity
Date of order
Inventory Description
Maintenance Id
Maintenance Date
Maintenance Category
Equipment Id
Equipment Name
Equipment Quantity
Equipment Category
Supplier Id
Supplier Name
Supplier Email Id
Supplier Phone Number
Supplier Address
Supplier City
Supplier State
Supplier Zip Code
Supplier Category
Billing Id
Billing Date
Final Preliminary Field List (09/30/2022):
Arena Id
Arena Type
Arena Name
Arena Address
Arena City
Arena State
Arena Zip Code
Product Id
Product Name
Product Category
Product Price
Product Quantity
Customer Id
Customer First Name
Customer Last Name
Customer Email Id
Customer Phone Number
Customer Address
Customer City
Customer State
Customer Zip Code
Customer Gender
Employee Id
Employee Type
Employee First Name
Employee Last Name
Employee Email Id
Employee Phone Number
Employee Address
Employee City
Employee State
Employee Zip Code
Employee Gender
Employee Job Position
Employee Working Shift
Team Id
Team Name
Coach Id
Coach First Name
Coach Last Name
Player Id
Player First Name
Player Last Name
Player Position
Team Wins
Team Tie
Team Losses
Number of Games
Team Id
Sponsor Id
Sponsor Name
Invoice Id
Total Amount
Total Quantity
Payment Type
Payment Date & Time
Live Broadcasting
Equipment Id
Equipment Name
Equipment Quantity
Equipment Category
Agent Id
Agent First Name
Agent Last Name
Agent Organization
Agent Email Id
Agent Phone Number
Payroll Id
Payment Date
Total Salary
Total Deductions
Final Amount Paid
Ticket Id
Ticket Price
Ticket Type
Ticket Quantity
Ticket Date & Time
Inventory Name
Inventory Quantity
Date of order
Inventory Description
Maintenance Id
Maintenance Date
Maintenance Category
Maintenance Comments
Maintenance Pending
Equipment Id
Equipment Name
Equipment Quantity
Equipment Category
Supplier Id
Supplier Name
Supplier Email Id
Supplier Phone Number
Supplier Address
Supplier City
Supplier State
Supplier Zip Code
Supplier Category
Billing Id
Billing Date
Value Field List (10/01/2022):
Arena Type(Big, Medium, Small), Employee Type(Ticket Checker, Cleaner, Security, Goods checker, Arena Checker), Gender(Male, Female), Ticket Type(Silver, Gold, Platinum, Diamond), Payment Verification (Paid, Not Paid, Pending, In Transaction), Maintenance Pending(Scheduled, Finished, To be completed by the end of the day), Games(Scheduled, Yet to be scheduled and the finished ones).
Calculate Field List (10/01/2022):
There are the types of calculate list in this database which are Arena Tax Revenue, Ticket Price = Ticket tax price + Ticket food price + Ticket adjustment price, Subtotal of assets.
The Preliminary Table List (10/04/2022):
Arena
Team
Sponsors
Invoice
Ticket Sales
Employee
Customers
Final Table List (10/04/2022):
Name Type Description
Arena Data Table will be used to keep track the all-match data and arena details.
Team Data The database contains all the teams that will play in each league.
Sponsors Data The database contains sponsors name and its brand who are going to sponsor match.
Invoice Data The table will be used to manage the payment confirmation using Ticket ID.
Employee Data Table will be used to manage the employee details. The employees include the maintenance staff, management staff, etc.
Customers Data Table will be used manage all customers details. The customer are the people who visit the arena for entertainment purpose.
Supplier Data Table will be used to maintain supplier record. Also we can track all kind of information regarding supplier and order of products.
Table Structure List (10/08/2022):
Customer Employee Invoice Sponsors Team Supplier Arena
Customer ID (PK) Employee ID (PK) Invoice ID (PK) Sponsor ID (PK) Team ID (PK) Supplier ID (PK) Arena ID (PK)
Customer First name (CK) Employee First name (CK) Ticket ID (FK) Sponsor Name (CK) Team Name (CK) Supplier Name (CK) Arena Name (CK)
Customer Last name (CK) Employee Last name (CK) Total Amount Team Name (FK) Player ID (FK) Email ID Address
Email Id Email ID Total Quantity Coach ID (FK) Phone Number City
Phone Number Phone Number Payment Type Employee ID (FK) Address State
Address Address Payment Date & Time Arena ID (FK) City Zip Code
City City Employee ID (FK) State Employee ID (FK)
State State Zip Code Arena Type (CK)
Zip Code Zip Code Supplier Category Gender Job Description Product ID (FK) Employee ID (FK) Work Shift Employee ID (FK) Gender Employee Type (CK) PK Primary Key
CK Candidate Key
FK Foreign Key
Physical Design:
Field Specification Sheet
Customer Table
FIELD SPECIFICATIONS
General Elements:
Field Name: Customer ID Specification Type: Unique Generic
Replica
Parent Table: Customer Source Specification:
Alias (es): Shared By:
Description: A certain number assigned to each customer in our company. Customer ID provides a unique id that identifies the customers from others.
Physical Elements:
Data Type: Number Character Support:
Letters (A-Z) Keyboard (&*?)
Numbers(0-9) Special()
Length: 5 Decimal Places: 0 Logical Elements
Key Type: Non Primary
Foreign Candidate Edit Rule:
Enter Now, Edits Allowed
Enter Now Edits, Not Allowed
Enter Later, Edits Allowed
Enter Later, Edits Not Allowed
Not Determined At This Time
Key Structure: Simple
Composite Uniqueness: Unique
Non-Unique Null Support: No Nulls
Nulls Allowed Value Entered By: User
System Required Value: Yes
No Range Of Values: 00000 - 99999
FIELD SPECIFICATIONS
General Elements:
Field Name: Customer First Name, Customer Last Name Specification Type: Unique Generic
Replica
Parent Table: Customer Source Specification:
Alias (es): Shared By:
Description: Customer First Name and Last Name are two unique fields and it is allotted to customers to fill the details.
Physical Elements:
Data Type: Short Text Character Support:
Letters (A-Z) Keyboard (&*?)
Numbers(0-9) Special()
Length: 35 Decimal Places: 0 Logical Elements
Key Type: Non Primary
Foreign Candidate Edit Rule:
Enter Now, Edits Allowed
Enter Now Edits, Not Allowed
Enter Later, Edits Allowed
Enter Later, Edits Not Allowed
Not Determined At This Time
Key Structure: Simple
Composite Uniqueness: Unique
Non-Unique Null Support: No Nulls
Nulls Allowed Value Entered By: User
System Required Value: Yes
No Range Of Values: A Z each
Employee Table
FIELD SPECIFICATIONS
General Elements:
Field Name: Employee ID Specification Type: Unique Generic
Replica
Parent Table: Employee Source Specification:
Alias (es): Shared By: Ticket Sales, Maintenance, F & B Billing
Description: A certain number assigned to each employee in our company. Employee ID provides a unique id that identifies the employee from others.
Physical Elements:
Data Type: Numbers Character Support:
Letters (A-Z) Keyboard (&*?)
Numbers(0-9) Special()
Length: 5 Decimal Places: 0 Logical Elements
Key Type: Non Primary
Foreign Candidate Edit Rule:
Enter Now, Edits Allowed
Enter Now Edits, Not Allowed
Enter Later, Edits Allowed
Enter Later, Edits Not Allowed
Not Determined At This Time
Key Structure: Simple
Composite Uniqueness: Unique
Non-Unique Null Support: No Nulls
Nulls Allowed Value Entered By: User
System Required Value: Yes
No Range Of Values: 00000 - 99999
FIELD SPECIFICATIONS
General Elements:
Field Name: Employee First Name, Employee Last Name Specification Type: Unique Generic
Replica
Parent Table: Employee Source Specification:
Alias (es): Shared By:
Description: Employee First Name and Last Name are two unique fields and it is allotted to employee to fill the details.
Physical Elements:
Data Type: Short Text Character Support:
Letters (A-Z) Keyboard (&*?)
Numbers(0-9) Special()
Length: 35 Decimal Places: 0 Logical Elements
Key Type: Non Primary
Foreign Candidate Edit Rule:
Enter Now, Edits Allowed
Enter Now Edits, Not Allowed
Enter Later, Edits Allowed
Enter Later, Edits Not Allowed
Not Determined At This Time
Key Structure: Simple
Composite Uniqueness: Unique
Non-Unique Null Support: No Nulls
Nulls Allowed Value Entered By: User
System Required Value: Yes
No Range Of Values: A Z each
Invoice Table
FIELD SPECIFICATIONS
General Elements:
Field Name: Invoice ID Specification Type: Unique Generic
Replica
Parent Table: Invoice Source Specification:
Alias (es): Shared By:
Description: The ID generated on the payment invoice as and when the payment is confirmed, this unique code is generated to the customer from our system which is Invoice ID.
Physical Elements:
Data Type: Numbers Character Support:
Letters (A-Z) Keyboard (&*?)
Numbers(0-9) Special()
Length: 5 Decimal Places: 0 Logical Elements
Key Type: Non Primary
Foreign Candidate Edit Rule:
Enter Now, Edits Allowed
Enter Now Edits, Not Allowed
Enter Later, Edits Allowed
Enter Later, Edits Not Allowed
Not Determined At This Time
Key Structure: Simple
Composite Uniqueness: Unique
Non-Unique Null Support: No Nulls
Nulls Allowed Value Entered By: User
System Required Value: Yes
No Range Of Values: 00000 - 99999
FIELD SPECIFICATIONS
General Elements:
Field Name: Ticket ID Specification Type: Unique Generic
Replica
Parent Table: Invoice Source Specification:
Alias (es): Shared By: Ticket Sales
Description: Once the payment is confirmed on our system, the ID generated is issued to the customer which is the Ticket ID.
Physical Elements:
Data Type: Number Character Support:
Letters (A-Z) Keyboard (&*?)
Numbers(0-9) Special()
Length: 9 Decimal Places: 0 Logical Elements
Key Type: Non Primary
Foreign Candidate Edit Rule:
Enter Now, Edits Allowed
Enter Now Edits, Not Allowed
Enter Later, Edits Allowed
Enter Later, Edits Not Allowed
Not Determined At This Time
Key Structure: Simple
Composite Uniqueness: Unique
Non-Unique Null Support: No Nulls
Nulls Allowed Value Entered By: User
System Required Value: Yes
No Range Of Values: 000000000 999999999
Sponsors Table
FIELD SPECIFICATIONS
General Elements:
Field Name: Sponsor ID Specification Type: Unique Generic
Replica
Parent Table: Sponsor Source Specification:
Alias (es): Shared By:
Description: A certain number assigned to each sponsor of our company. Sponsor ID provides a unique id that identifies the sponsors from others.
Physical Elements:
Data Type: Number Character Support:
Letters (A-Z) Keyboard (&*?)
Numbers(0-9) Special()
Length: 5 Decimal Places: 0 Logical Elements
Key Type: Non Primary
Foreign Candidate Edit Rule:
Enter Now, Edits Allowed
Enter Now Edits, Not Allowed
Enter Later, Edits Allowed
Enter Later, Edits Not Allowed
Not Determined At This Time
Key Structure: Simple
Composite Uniqueness: Unique
Non-Unique Null Support: No Nulls
Nulls Allowed Value Entered By: User
System Required Value: Yes
No Range Of Values: 00000 - 99999
FIELD SPECIFICATIONS
General Elements:
Field Name: Sponsor Name Specification Type: Unique Generic
Replica
Parent Table: Sponsor Source Specification:
Alias (es): Shared By:
Description: A particular name of a brand who is going to sponsor any game.
Physical Elements:
Data Type: Short Text Character Support:
Letters (A-Z) Keyboard (&*?)
Numbers(0-9) Special()
Length: 35 Decimal Places: 0 Logical Elements
Key Type: Non Primary
Foreign Candidate Edit Rule:
Enter Now, Edits Allowed
Enter Now Edits, Not Allowed
Enter Later, Edits Allowed
Enter Later, Edits Not Allowed
Not Determined At This Time
Key Structure: Simple
Composite Uniqueness: Unique
Non-Unique Null Support: No Nulls
Nulls Allowed Value Entered By: User
System Required Value: Yes
No Range Of Values: A - Z
Team Table
FIELD SPECIFICATIONS
General Elements:
Field Name: Team ID Specification Type: Unique Generic
Replica
Parent Table: Team Source Specification:
Alias (es): Shared By: Player, Game Record
Description: A certain number assigned to each team in our company. Team ID provides a unique id that identifies the team from others.
Physical Elements:
Data Type: Number Character Support:
Letters (A-Z) Keyboard (&*?)
Numbers(0-9) Special()
Length: 5 Decimal Places: 0 Logical Elements
Key Type: Non Primary
Foreign Candidate Edit Rule:
Enter Now, Edits Allowed
Enter Now Edits, Not Allowed
Enter Later, Edits Allowed
Enter Later, Edits Not Allowed
Not Determined At This Time
Key Structure: Simple
Composite Uniqueness: Unique
Non-Unique Null Support: No Nulls
Nulls Allowed Value Entered By: User
System Required Value: Yes
No Range Of Values: 00000 - 99999
FIELD SPECIFICATIONS
General Elements:
Field Name: Team Name Specification Type: Unique Generic
Replica
Parent Table: Team Source Specification:
Alias (es): Shared By:
Description: A unique name given to the team.
Physical Elements:
Data Type: Short Text Character Support:
Letters (A-Z) Keyboard (&*?)
Numbers(0-9) Special()
Length: 15 Decimal Places: 0 Logical Elements
Key Type: Non Primary
Foreign Candidate Edit Rule:
Enter Now, Edits Allowed
Enter Now Edits, Not Allowed
Enter Later, Edits Allowed
Enter Later, Edits Not Allowed
Not Determined At This Time
Key Structure: Simple
Composite Uniqueness: Unique
Non-Unique Null Support: No Nulls
Nulls Allowed Value Entered By: User
System Required Value: Yes
No Range Of Values: A - Z
Supplier Table
FIELD SPECIFICATIONS
General Elements:
Field Name: Supplier ID Specification Type: Unique Generic
Replica
Parent Table: Supplier Source Specification:
Alias (es): Shared By: Inventory
Description: A certain number assigned to each supplier of our company. Supplier ID provides a unique id that identifies the supplier from others.
Physical Elements:
Data Type: Number Character Support:
Letters (A-Z) Keyboard (&*?)
Numbers(0-9) Special()
Length: 5 Decimal Places: 0 Logical Elements
Key Type: Non Primary
Foreign Candidate Edit Rule:
Enter Now, Edits Allowed
Enter Now Edits, Not Allowed
Enter Later, Edits Allowed
Enter Later, Edits Not Allowed
Not Determined At This Time
Key Structure: Simple
Composite Uniqueness: Unique
Non-Unique Null Support: No Nulls
Nulls Allowed Value Entered By: User
System Required Value: Yes
No Range Of Values: 00000 - 99999
FIELD SPECIFICATIONS
General Elements:
Field Name: Supplier Name Specification Type: Unique Generic
Replica
Parent Table: Supplier Source Specification:
Alias (es): Shared By:
Description: Name of a brand which supplies product to our company known as supplier name.
Physical Elements:
Data Type: Short Text Character Support:
Letters (A-Z) Keyboard (&*?)
Numbers(0-9) Special()
Length: 35 Decimal Places: Logical Elements
Key Type: Non Primary
Foreign Candidate Edit Rule:
Enter Now, Edits Allowed
Enter Now Edits, Not Allowed
Enter Later, Edits Allowed
Enter Later, Edits Not Allowed
Not Determined At This Time
Key Structure: Simple
Composite Uniqueness: Unique
Non-Unique Null Support: No Nulls
Nulls Allowed Value Entered By: User
System Required Value: Yes
No Range Of Values: A - Z
Arena Table
FIELD SPECIFICATIONS
General Elements:
Field Name: Arena ID Specification Type: Unique Generic
Replica
Parent Table: Arena Source Specification:
Alias (es): Shared By:
Description: Arena ID helps to locate the exact location of the arena with respect to the stadium, its country, city, state and town it is situated for legal purpose.
Physical Elements:
Data Type: Number Character Support:
Letters (A-Z) Keyboard (&*?)
Numbers(0-9) Special()
Length: 7 Decimal Places: 0 Logical Elements
Key Type: Non Primary
Foreign Candidate Edit Rule:
Enter Now, Edits Allowed
Enter Now Edits, Not Allowed
Enter Later, Edits Allowed
Enter Later, Edits Not Allowed
Not Determined At This Time
Key Structure: Simple
Composite Uniqueness: Unique
Non-Unique Null Support: No Nulls
Nulls Allowed Value Entered By: User
System Required Value: Yes
No Range Of Values: 0000000 - 9999999
FIELD SPECIFICATIONS
General Elements:
Field Name: Arena Name Specification Type: Unique Generic
Replica
Parent Table: Arena Source Specification:
Alias (es): Shared By:
Description: A unique name given to the arena.
Physical Elements:
Data Type: Short Text Character Support:
Letters (A-Z) Keyboard (&*?)
Numbers(0-9) Special()
Length: 35 Decimal Places: 0 Logical Elements
Key Type: Non Primary
Foreign Candidate Edit Rule:
Enter Now, Edits Allowed
Enter Now Edits, Not Allowed
Enter Later, Edits Allowed
Enter Later, Edits Not Allowed
Not Determined At This Time
Key Structure: Simple
Composite Uniqueness: Unique
Non-Unique Null Support: No Nulls
Nulls Allowed Value Entered By: User
System Required Value: Yes
No Range Of Values: A - Z
Analyzing Table Relationship in Database:
Identify Relationship Table Matrix
Customer Employee Invoice Sponsors Team Supplier Arena
Customer 1:N 1:N Employee 1:1 1:N 1:1
Invoice 1:1 Sponsors Team 1:N 1:N 1:1
Supplier Arena 1:1 1:1 Identify all of keys
Primary Keys:
Customer Table: Customer_ID
Employee Table: Employee_ID
Invoice Table: Invoice_ID
Sponsors Table: Sponsors_ID
Team Table: Team_ID
Supplier Table: Supplier_ID
Arena Table: Arena_ID
Foreign Keys:
Invoice Table: Ticket_ID
Sponsors Table: Team_Name
Team Table: Player_ID, Coach_ID
Supplier Table: Product_ID
Arena Table: Employee_Table
Candidate Keys:
Customer Table: Customer_First-Name, Customer_Last-Name
Employee Table: Employee_First-Name, Employee_Last-Name, Employee_Type
Sponsors Table: Sponsors_Name
Team Table: Team_Name
Supplier Table: Supplier_Name
Arena Table: Arena_Name, Arena_Type
Analyzing Business Rules in Database:
Identify Business Rule in Database:
The Relationship specific and Field specific business rules for each field on the tables are defined below. There are a total of 7 tables defining one each for the fields given.
Customer Table: The Customer_ID is used to authorize and identify the Customers identity for security purposes. The Customer_ID is unique for one customer, it cannot be deleted, and it has to be present in the database.
Business Rule Specifications
113665129540Rule Information
00Rule Information
984252197913Structures affected
00Structures affected
Statement: Customer_ID field should be compulsory to identify the customers.
Constraint: The customer field must be filled out; it cannot be left blank and Customer_ID should be used to identify the customer and their details.
Type:
Database Oriented
Application Oriented Category:
Field Specific
Relationship Specific
Test On:
Insert
Update
Delete
Field Name: Customer_ID
Table Name: Customer
11366576200Field elements affected
00Field elements affected
Physical elements
Data Type Length Character Support
Logical elements
Key Type
Key Structure
Uniqueness Null Support
Values Entered By
Required Value Range of Values
Edit Rules
12890527940Relationship Characteristics allowed
00Relationship Characteristics allowed
Deletion Rule Type of Participation Degree of Participation
135890342900Action Taken
00Action Taken
Type of Participation Allowed
Degree of Participation (1:N)
Employee Table: The Employee_ID is used to authorize and identify the Employees identity for security purposes. The Employee_ID is unique for one employee, it cannot be deleted, and it has to be present in the database.
Business Rule Specifications
113665129540Rule Information
00Rule Information
984252197913Structures affected
00Structures affected
Statement: Employee_ID field should be compulsory to identify the customers.
Constraint: The customer field must be filled out; it cannot be left blank and Employee_ID should be used to identify the employee and their details.
Type:
Database Oriented
Application Oriented Category:
Field Specific
Relationship Specific
Test On:
Insert
Update
Delete
Field Name: Employee_ID
Table Name: Employee, Customer, Arena, Team, Invoice, Supplier
11366576200Field elements affected
00Field elements affected
Physical elements
Data Type Length Character Support
Logical elements
Key Type
Key Structure
Uniqueness Null Support
Values Entered By
Required Value Range of Values
Edit Rules
12890527940Relationship Characteristics allowed
00Relationship Characteristics allowed
Deletion Rule Type of Participation Degree of Participation
135890342900Action Taken
00Action Taken
Type of Participation Allowed
Degree of Participation (1:1), (1:N)
Invoice Table: The Invoice_ID is used to authorize and identify the particular customers invoice for security purposes.
Business Rule Specifications
113665129540Rule Information
00Rule Information
984252197913Structures affected
00Structures affected
Statement: Invoice_ID should be compulsory to identify the invoice.
Constraint: Invoice_ID number should be used to identify the customer purchase and their details.
Type:
Database Oriented
Application Oriented Category:
Field Specific
Relationship Specific
Test On:
Insert
Update
Delete
Field Name: Invoice_ID
Table Name: Invoice, Customer, Employee
11366576200Field elements affected
00Field elements affected
Physical elements
Data Type Length Character Support
Logical elements
Key Type
Key Structure
Uniqueness Null Support
Values Entered By
Required Value Range of Values
Edit Rules
12890527940Relationship Characteristics allowed
00Relationship Characteristics allowed
Deletion Rule Type of Participation Degree of Participation
135890342900Action Taken
00Action Taken
Deletion Rule: Not Allow
Degree of Participation (1:1)
Team Table: The Team_ID is used to authorize and identify the Teams identity for security purposes. The Team_ID is unique for one team, it cannot be deleted, and it has to be present in the database.
Business Rule Specifications
113665129540Rule Information
00Rule Information
984252197913Structures affected
00Structures affected
Statement: Team Table is compulsory to identify the team details.
Constraint: The team field must be filled out; it cannot be left blank and Team_ID should be used to identify the Team and their details.
Type:
Database Oriented
Application Oriented Category:
Field Specific
Relationship Specific
Test On:
Insert
Update
Delete
Field Name: Team_ID
Table Name: Team
11366576200Field elements affected
00Field elements affected
Physical elements
Data Type Length Character Support
Logical elements
Key Type
Key Structure
Uniqueness Null Support
Values Entered By
Required Value Range of Values
Edit Rules
12890527940Relationship Characteristics allowed
00Relationship Characteristics allowed
Deletion Rule Type of Participation Degree of Participation
135890342900Action Taken
00Action Taken
Deletion Rule: Not Allow
Type of Participation: Mandatory Degree of Participation (1:1), (1:N)
Supplier Table: This table is used to authorize and identify the particular supplier detail for security purposes.
Business Rule Specifications
113665129540Rule Information
00Rule Information
984252197913Structures affected
00Structures affected
Statement: Supplier Table is compulsory to identify the all equipment supplier details.
Constraint: Supplier_ID should be used to identify the product supplier details for order purpose.
Type:
Database Oriented
Application Oriented Category:
Field Specific
Relationship Specific
Test On:
Insert
Update
Delete
Field Name: Supplier_ID
Table Name: Supplier, Employee
11366576200Field elements affected
00Field elements affected
Physical elements
Data Type Length Character Support
Logical elements
Key Type
Key Structure
Uniqueness Null Support
Values Entered By
Required Value Range of Values
Edit Rules
12890527940Relationship Characteristics allowed
00Relationship Characteristics allowed
Deletion Rule Type of Participation Degree of Participation
135890342900Action Taken
00Action Taken
Deletion Rule: Deny
Type of Participation: MandatoryDegree of Participation (1:N)
Sponsors Table: The Sponsors_ID is used to authorize and identify the sponsors identity for security purposes. The Sponsor_ID is unique for one sponsor, it cannot be deleted, and it has to be present in the database.
Business Rule Specifications
113665129540Rule Information
00Rule Information
Statement: Sponsor_ID field should be compulsory to identify the customers.
Constraint: The sponsor field must be filled out; it cannot be left blank and Sponsor_ID should be used to identify the customer and their details.
Type:
Database Oriented
Application Oriented Category:
Field Specific
Relationship Specific
Test On:
Insert
Update
Delete
115359911225Structures affected
00Structures affected
Field Name: Sponsor_ID
Table Name: Sponsor, Team
11366576200Field elements affected
00Field elements affected
Physical elements
Data Type Length Character Support
Logical elements
Key Type
Key Structure
Uniqueness Null Support
Values Entered By
Required Value Range of Values
Edit Rules
12890527940Relationship Characteristics allowed
00Relationship Characteristics allowed
Deletion Rule Type of Participation Degree of Participation
135890342900Action Taken
00Action Taken
Deletion Rule: Deny
Type of Participation: AllowDegree of Participation (1:N)
Arena Table: This table is used to authorize and identify the particular arena detail.
Business Rule Specifications
113665129540Rule Information
00Rule Information
Statement: Arena Table is compulsory to identify the all arena details.
Constraint: Arena Name should be used to identify the arena details.
Type:
Database Oriented
Application Oriented Category:
Field Specific
Relationship Specific
Test On:
Insert
Update
Delete
174625927947Structures affected
00Structures affected
Field Name: Arena Name
Table Name: Arena, Team, Employee
11366576200Field elements affected
00Field elements affected
Physical elements
Data Type Length Character Support
Logical elements
Key Type
Key Structure
Uniqueness Null Support
Values Entered By
Required Value Range of Values
Edit Rules
12890527940Relationship Characteristics allowed
00Relationship Characteristics allowed
Deletion Rule Type of Participation Degree of Participation
135890342900Action Taken
00Action Taken
Deletion Rule: Deny
Type of Participation: MandatoryDegree of Participation (1:1)
ER Diagram:
Analyzing View in Database:
View Specifications
113775129484General Information
00General Information
Name: Ticket Price Type: Data Aggregate Validation
Description: This View gives more details about the customers. It also validates and confirms the customers reservation and payment details. It also indicates how the Ticket relates to the Customer, Ticket Sales, Invoice and Food & Beverages Tables.
1136651795569Basic Table
00Basic Table
Customer, Ticket Sales, Invoice and Food & Beverages
11366550165Calculated Field Expression
00Calculated Field Expression
Field Name Expression
Customer
Ticket Sales
Invoice
Food & Beverages Customer_ID
Ticket Price, Ticket tax price, Ticket food price, Ticket adjustment price
Invoice_ID
Product_ID
11303054822Filter
00Filter
Field Name Condition
Ticket Price Ticket Price = Ticket tax price + Ticket food price + Ticket adjustment price
Ticket Detail View:
Application Implementation:
10/23/2022
The study will be carried out using techniques for gathering data from both primary and secondary data sources, including questionnaires, observations, and interviews as well as the examination of secondary data and reports. The physical processes under investigation are viewed from various angles Theoretical, Practical, Theory, Technology. The data gathering procedure is quantitatively completed at several phases from various data sources using the methods mentioned above. Below are descriptions of each data collection tool used.
Questionnaire
This approach was chosen because it enables us to rapidly gather a great deal of data from a huge number of people in a brief period. He can easily handle several themes at once in one location. Written in English for professionals, executives, and support employees. In this process, a questionnaire is delivered to the data subject, who is asked to complete it and return it. The respondents themselves must react to questions. This approach was chosen because it is inexpensive and has unbiased interviewers. The respondents give ample time to formulate serious responses, and the solution is the term for the respondents. This happened during the researcher's one-week work period, during which she visited the target site in person and gave the respondents the questionnaire.
Interviews
This technique is used to verify data gathered through surveys. Additionally, other people might notice things that researchers can't. The face-to-face engagement allowed the researchers to get information from the respondents directly by asking focused, well-defined, open-ended questions. Support personnel, supervisors, and administrators must attend interviews. To choose which workers to interview, researchers utilized a targeted sample strategy. Researchers can extract additional information from the data they collect by using targeted sampling.
Observation
Direct observation is one of the methods used by researchers to gather the data they want. It is a methodical, deliberate, and focused approach of keeping an eye on and listening to activity as the actual work is being done. This tool was utilized by researchers to learn more about the Flying Elbows' existing functioning process system. Additionally, it supports the legitimacy of the views expressed by survey and interview participants. The following checklist was used to make direct observations.
Quality standards and management activities, human resources and development, information technology systems, setting standard time requirements for each process, management skills, branch management. Therefore, the project ran this tool to review the data collected, remove bias, and observe what is currently happening in the flying elbow case.
Document Review
Researchers used document data from files, office manuals, circulars, and policy papers to provide additional information on competing concepts as needed. Surveying all business stakeholders revealed what they thought was important to their business and helped us identify priority areas for the system. Based on this information, we created a requirements specification to guide the development phases of the database.
Database Tabel Screenshots:
Customer Table:
Employee Table:
Arena Table:
Database Implementation (10/23/2022):
Interviews conducted at an early stage to further continue the database application implementation process and analyze the company's existing database to obtain an accurate list of objectives, subjects and characteristics, and a preliminary list of fields along Corporate requirements were recorded during the procedure. A table list is obtained during this process. The value list of fields and the calculated field list are also separated after the final interim field list is obtained. A data table for all subjects with a mandatory field list has been pre-recorded.
This phase of database implementation involves linking data tables according to the relationships between them, and is a key aspect of database design. Data tables are linked to each other according to the relationships each data table has to each other. It is very important that each data table has the proper relationships with other data tables, only then can the data be accessed as needed.
Different types of keys used to link data tables are now specified in the data table fields. The types of keys in the above relational model are Candidate Key, Primary Key, Candidate Composite Key, and Foreign Key.
Relation tuples (or rows) can be defined by a number of properties defined by the database management system (DBMS). It is called a key and uniquely identifies it. (or table). Many tables and columns in a relational database can be related to each other using keys. A key value is a specific value contained in a key.
Candidate Keys:
Candidate keys are minimal features that can successfully identify a tuple. A candidate key with a null value cannot be a primary key because the primary key of a table cannot have null values. A table can have multiple candidate keys, but only one primary key.
Primary key:
A candidate key with NULL values cannot be a primary key because the primary key of a table cannot contain NULL values. There can be multiple candidate keys, but only one primary key in the table. It's a special key. Only one tuple (record) can be identified at a time. Contains only unique values. No duplicates. Must not be empty.
Foreign Key:
An attribute is a foreign key to an attribute that you reference when you can only get a value that already exists as a value for another attribute. A referenced relationship is called a referenced relationship, a corresponding attribute is called a referenced attribute, and a relationship that references the referenced relationship is called a referenced relationship and a referenced attribute. The referenced attribute of the referenced relation must act as the primary key.
Composite key: A composite key is a combination of two or more properties,
where each tuple in the table is uniquely identified. Viewed in isolation, the quality of the set may not stand out. However, combining them guarantees uniqueness. Another name for a composite key is a "concatenated key".
Using the above keys, design your database using the techniques of the relational database model. Design entity relationships between data tables before implementing a database. This allows you to succinctly and error-free connect data tables and find the keys associated with various tuples in your database. With the help of the above data table entity-relationship diagram, the design and implementation of the database in the Microsoft Access database will begin, further improvements will be made accordingly, and bugs will be fixed during the implementation stage.
Programming Implementation (10/23/2022):
The following NHL Hockey Team with Arena database application should be designed with the .Net framework in Visual Studio. The challenge before starting to implement the application is to familiarize yourself with the C# programming language and the Windows framework to create a seamless application. To develop applications, learn the programming language necessary to meet the needs of your project through various online websites, and gain hands-on experience in designing databases, making the application implementation process easier later. Become. The required database is complete.
(11/12/2022)
A DBMS system requires multiple steps to set up, maintain, and perform many actions. These critical processes include collecting relevant data, interpreting it, and running the database. Interacting with users to understand their needs is a necessary step in the data collection process. The actual look and feel of the software must be coded for the interface and application implementation. Prototypes should be created to quickly reproduce the desired application results. This makes it easier for users to interact with the database.
DBMS systems require multiple steps to set up, maintain, and perform many actions. These critical processes include collecting relevant data, interpreting it, and running the database. Interacting with users to understand their needs is a necessary step in the data collection process. The actual look and feel of the software must be coded for the interface and application implementation. Prototypes should be created to quickly reproduce the desired application results. This makes it easier for users to interact with the database.
Application frontend started in C#. The coding was saved in Visual Studio according to agreed business rules. Product maintenance, user information, payment details and rental details are all contained in the application. A DBMS system requires multiple steps to set up, maintain, and perform many actions. These critical processes include collecting relevant data, interpreting it, and running the database. Interacting with users to understand their needs is a necessary step in the data collection process. The actual look and feel of the software must be coded for the interface and application implementation. Prototypes should be created to quickly reproduce the desired application results. This makes it easier for users to interact with the database.
At the same time, the database backend is coded and connected to MS Access using the C# programming language. The database creation is also in progress, so the backend coding is not yet complete. The various fields and table structures specified in progressive reports are implemented in the database in terms of business rules. Prototypes will be included in future progressive reports. You should be careful this implementation helped him create the front end user interface for the application. The backend is also he written in C#. The first part of the backend is to create a database using MS Access which is a work in progress. As a first step in the backend, an MS Access database is currently being created.
I also learned to create a database UI for MS Access on YouTube and now understand the core concepts of creating a C# database.
