Cheltenham Football Club Member Management System Design

System Design 1
System Analysis and Design
By [Name]
Course
Professor’s Name
Institution
Location of Institution
Date

System Design 2
Table of Contents
1.0 Introduction..............................................................................................................................4
1.1 Scope.................................................................................................................................4
1.2 Functional requirements................................................................................................4
1.3 Use case diagram.............................................................................................................6
2.0 Use case diagram documentation......................................................................................6
2.1 Use case description........................................................................................................6
3.0 Conceptual class diagram................................................................................................13
3.1 Classes............................................................................................................................13
3.2 Class descriptions and main attributes.......................................................................13
4.0 Interaction diagrams.............................................................................................................15
4.1 Sequence diagrams: Description and justification.....................................................15
4.1.1 How to register a player.............................................................................................15
4.1.2How to dismiss a player...............................................................................................16
4.2 Activity diagram; Description and justification.........................................................17
4.3 Collaboration diagrams; Description and justification.............................................18
Conclusion................................................................................................................................19
5.0 Appendix.................................................................................................................................20
References.....................................................................................................................................21

System Design 3
List of figures
Figure 1: Use case Diagram..........................................................................................................6
Figure 2: Class Diagram.............................................................................................................14
Figure 4: Registration Sequence Diagram................................................................................15
Figure 5: Sequence diagram for Dismissing a player...............................................................16
Figure 6: Activity Diagram.........................................................................................................17
Figure 7: Collaboration Diagram...............................................................................................18

System Design 4
1.0 Introduction
Due to the increasing need for the management of the recorded information within the
Cheltenham Football Club for the 5 teams being managed, there arises a need to develop a
system that will help in the running of the program in the daily activities of the club. All these
operations can be put into a well-organized record to ease the retrieval of the information. With
this in mind, this research paper ought to bring to our focus the development of the mentioned
system with the analysis and the design all combined (Dennis, Wixom and Tegarden, 2015).
1.1 Scope
The system in review will be of importance to the Cheltenham Football Club. From the general
planning phase, the system is set to provide a well-managed set of records for all the players
within the club. The maximum club boundaries are to allow the registration of new members and
update of the existing details allowing modifications of all kinds. With this noted, the team
developers need to understand the requirements of the club to ensure they meet the minimum
stated objectives (Valacich, George and Hoffer, 2014).
1.2 Functional requirements
Dooming is one major problem that can arise through the use of any given system. In order to
avoid this, every developer needs to have a true picture of what exactly the system is expected to
do and the possible ways in which it can be developed to allow more changes in the future.
According to Gruber et al., (2017), we are provided with the functional requirements of the
system as the main aspect before any development process is commenced. Given the fact that
they can’t be dropped halfway, all the stakeholders must have a clear understanding of all the
processes involved.

System Design 5
a) Adding a player
Input: the user enters all the details of the club member
Output: a message confirming the status of the added member is displayed.
Processing: the system will be able to check if there is any error in the information
entered for a player.
b) Modifying player details
Input: the system user will input the alternatives of the information being modified. For
instance, the phone number or the date the player joined the team.
Output: a confirmation message is displayed showing the result of the process.
Processing: the system checks if the details to be modified really exists. Then for an
existing player the data is updated to the new changed details.
c) Deleting member details
Input: the user will be required to enter the player id to remove from the team
Output: a message with relevant data of the processed data
Processing: the system check if the entered information is correct before removing the
player.

System Design 6
1.3 Use case diagram.
Figure 1: Use case Diagram
2.0 Use case diagram documentation
2.1 Use case description
Use case Description
Player name The match details should be added and the personal team player details.
Level In the design process of a system and the overall development, use case
diagrams falls in the sub-functional level. Once a user has fully
analyzed both the functional and the non-functional requirements, then
there is need to analyze this.