Requirements Specification (this is a fictional scenario) A young soccer league wants to manage its registrations. The league function based on seasons, like FALL 2020. For each season there is a registration starting date and ending date and also a season starting date and ending date. The league may want to compare FALL seasons in different years. The seasons are FALL, SPRING, WINTER and SUMMER. In each season, the league has several divisions organized based on age (eg U14), players sex (e.g. boys, girls) and rank (e.g. 1, 2). For a division we will keep a unique contact email (of maximum 30 characters) and phone (with the format (999) 999-9999) for the teams to report results. The league has many clubs. For a club we will keep the name of the club (eg Patriots) (of maximum 20 characters), a contact email (of maximum 30 characters) and a phone number (with the format (999) 999- 9999). All clubs have an abbreviation of maximum 5 characters. Some clubs may have the same abbreviation. A club has many teams, and a team belongs to a single club. Teams are organized based on players birth year (eg 2007) and players sex (e.g. boys, girls) and they have a unique name within the club (e.g. BLUE) of maximum 22 characters. All teams have an email and phone contact stored in a similar way with the club contact information. Each season (eg FALL 2020 or SPRING 2019), a registered team is assigned to a given division, that may change in rank based on the results obtained in the previous season. The league wants to keep the history of the membership (registration) over time. When a new season is created, there are no divisions. Then the divisions in the season are created. After that the teams are registered in the corresponding division. When a new club is added there are no teams. Then the teams are added one by one. Your design must support this iterative process.
Requirements Specification (this is a fictional scenario) A young soccer league wants to manage its registrations. The league function based on seasons, like FALL 2020. For each season there is a registration starting date and ending date and also a season starting date and ending date. The league may want to compare FALL seasons in different years. The seasons are FALL, SPRING, WINTER and SUMMER. In each season, the league has several divisions organized based on age (eg U14), players sex (e.g. boys, girls) and rank (e.g. 1, 2). For a division we will keep a unique contact email (of maximum 30 characters) and phone (with the format (999) 999-9999) for the teams to report results. The league has many clubs. For a club we will keep the name of the club (eg Patriots) (of maximum 20 characters), a contact email (of maximum 30 characters) and a phone number (with the format (999) 999- 9999). All clubs have an abbreviation of maximum 5 characters. Some clubs may have the same abbreviation. A club has many teams, and a team belongs to a single club. Teams are organized based on players birth year (eg 2007) and players sex (e.g. boys, girls) and they have a unique name within the club (e.g. BLUE) of maximum 22 characters. All teams have an email and phone contact stored in a similar way with the club contact information. Each season (eg FALL 2020 or SPRING 2019), a registered team is assigned to a given division, that may change in rank based on the results obtained in the previous season. The league wants to keep the history of the membership (registration) over time. When a new season is created, there are no divisions. Then the divisions in the season are created. After that the teams are registered in the corresponding division. When a new club is added there are no teams. Then the teams are added one by one. Your design must support this iterative process.
Computer Networking: A Top-Down Approach (7th Edition)
7th Edition
ISBN:9780133594140
Author:James Kurose, Keith Ross
Publisher:James Kurose, Keith Ross
Chapter1: Computer Networks And The Internet
Section: Chapter Questions
Problem R1RQ: What is the difference between a host and an end system? List several different types of end...
Related questions
Question
Please Design an Entity Diagram for the following Fictional Scenario using entities: SEASON, LEAGUE, DIVISION, CLUB and TEAM. Also, please show the relationship type and datatype. Thank You!
Transcribed Image Text:Requirements Specification (this is a fictional scenario)
A young soccer league wants to manage its registrations.
The league function based on seasons, like FALL 2020. For each season there is a registration starting
date and ending date and also a season starting date and ending date. The league may want to compare
FALL seasons in different years. The seasons are FALL, SPRING, WINTER and SUMMER.
In each season, the league has several divisions organized based on age (e g U14), players sex (e.g.
boys, girls) and rank (e.g. 1, 2). For a division we will keep a unique contact email (of maximum 30
characters) and phone (with the format (999) 999-9999) for the teams to report results.
The league has many clubs. For a club we will keep the name of the club (eg Patriots) (of maximum 20
characters), a contact email (of maximum 30 characters) and a phone number (with the format (999) 999-
9999). All clubs have an abbreviation of maximum 5 characters. Some clubs may have the same
abbreviation.
A club has many teams, and a team belongs to a single club. Teams are organized based on players
birth year (e g 2007) and players sex (e.g. boys, girls) and they have a unique name within the club (e.g.
BLUE) of maximum 22 characters. All teams have an email and phone contact stored in a similar way
with the club contact information.
Each season (eg FALL 2020 or SPRING 2019), a registered team is assigned to a given division, that
may change in rank based on the results obtained in the previous season. The league wants to keep the
history of the membership (registration) over time.
When a new season is created, there are no divisions. Then the divisions in the season are created. After
that the teams are registered in the corresponding division. When a new club is added there are no
teams. Then the teams are added one by one. Your design must support this iterative process.
Expert Solution
This question has been solved!
Explore an expertly crafted, step-by-step solution for a thorough understanding of key concepts.
This is a popular solution!
Trending now
This is a popular solution!
Step by step
Solved in 2 steps with 1 images
Recommended textbooks for you
Computer Networking: A Top-Down Approach (7th Edi…
Computer Engineering
ISBN:
9780133594140
Author:
James Kurose, Keith Ross
Publisher:
PEARSON
Computer Organization and Design MIPS Edition, Fi…
Computer Engineering
ISBN:
9780124077263
Author:
David A. Patterson, John L. Hennessy
Publisher:
Elsevier Science
Network+ Guide to Networks (MindTap Course List)
Computer Engineering
ISBN:
9781337569330
Author:
Jill West, Tamara Dean, Jean Andrews
Publisher:
Cengage Learning
Computer Networking: A Top-Down Approach (7th Edi…
Computer Engineering
ISBN:
9780133594140
Author:
James Kurose, Keith Ross
Publisher:
PEARSON
Computer Organization and Design MIPS Edition, Fi…
Computer Engineering
ISBN:
9780124077263
Author:
David A. Patterson, John L. Hennessy
Publisher:
Elsevier Science
Network+ Guide to Networks (MindTap Course List)
Computer Engineering
ISBN:
9781337569330
Author:
Jill West, Tamara Dean, Jean Andrews
Publisher:
Cengage Learning
Concepts of Database Management
Computer Engineering
ISBN:
9781337093422
Author:
Joy L. Starks, Philip J. Pratt, Mary Z. Last
Publisher:
Cengage Learning
Prelude to Programming
Computer Engineering
ISBN:
9780133750423
Author:
VENIT, Stewart
Publisher:
Pearson Education
Sc Business Data Communications and Networking, T…
Computer Engineering
ISBN:
9781119368830
Author:
FITZGERALD
Publisher:
WILEY