System Analysis and Design Solution Template for Cheltenham Football Club Information System

This solution template provides a detailed analysis and design of the Cheltenham Football Club Information System, including use case diagrams, class diagrams, interaction diagrams, and flowcharts. It covers topics such as registration, login, payroll, maintenance, view profile, and more.

System Analysis and Design Solution Template
Academic year and term: 2017/2018 – Semester-2, Year 1
Module title: System Analysis and Design
Module code: QAC020C154S
Module Convener: Hassan Baajour
Module Tutor: PLEASE ENTER YOUR TUTOR NAME HERE
Student Id: PLEASE ENTER YOUR STUDENT ID HERE
Deadline: 16-07-18 (no later than 2pm)
Coursework 1: System Design
1

Use case diagram
1.1 Functional requirements
For the development of the information system for the football club the following
requirement are listed below:
 A list of the club members should be created with all the details such that the
efficiency of the digital management system can be improved.
 The admin should be able to add, modify or delete a user account after analysing
all the details of the users.
 Management of the monthly contribution of the members and eliminate the
manual process for reducing the risk associated with the management of the
system.
 Management of the game schedules with all the details like number of
participants, coaches, venue, date, etc.
 Generation of notification for the participants if there is changes in the game
schedule and track the activity of the members
 To generate automated seasonal report by the management of the errors and
increase the efficiency of the system
 Improvement of the communication between the team members and eliminate
the communication gap for the improvement of the current business process
 A separate login account should be used for the users for the management of the
inputs and recording the details in the database.
 To display the club rules, history. Profiles of the players for each of the account
and linking the database with the website for the management of the information
sources.
1.2 use case diagram
2

2) use case diagram documentation
Primary use case 1
Use Case Title: Registration
Actors: Admin, User
Description: The user needs to register with the digital management
system with the data of birth, contact details and the details
of their matches played. The registration of the user is
3

important for getting the details of the user and store them in
the database of the digital management system.
Precondition All the information that is essential for filling the registration
form should be available with the user and it is needed to be
validated by the administrator for opening the account of the
player signing with the club.
Flow The following are the flows of data identified for the development
of the management system.
 A form is filled by the new user providing all the details
such as user name, email address, contact details,
matches played, date of birth, etc. for opening the new
account.
 The administrator verified the details provided by the
user such that no wrong information is inputted in the
management system as it can cause error.
 If any field in the registration form is left empty the
user is notified to fill it with relevant information for
proceeding with the next stage of registration.
 The user can update the details provided by them
during the registration after successfully opening the
account from the edit details section in the
management system.
 After successfully completing the registration process
the user is provided with a username and password
using which the player can login into the digital
management system.
Primary use case 2
Use Case Title: Login
Actors: User, digital management system
Description: The user such as the admin, player, coaches and the other
club members can use the digital management system by
successfully login into the system. The user should have a valid
username and password for logging in and use the digital
management system. The player can also
Precondition For using the login feature the user must be registered with
the information system and should have a valid username and
password. The account of the user should be in active state for
successfully log into the information system.
Flow  The user should have an valid username and password
that can be used for opening the new account and
login into the information system.
 The account state of the user must be in active state
4

such that it can be used for logging into the system.
 The user should use a strong password with the
combination of special character, alphabet and
numeric for maintaining security of the account
 The login information are shared with the user using
the email and if the password is forgotten by the user
the user can use the forget password option for
starting the recovery of the account.
 A password reset link is shared with the user in the
registered email id from where the user can change
the password.
 The user should logout of the information system or
the system automatically logs out the user after
analysing 30 minutes of inactivity.
Primary use case 3
Use Case Title: Maintenance
Actors: Admin, Cheltenham Football Club Information System
Description: The maintenance of the information system is necessary for
deleting the old records such as the suspended accounts for
more than 6 months and free up space in the database for
adding new members in the database. The maintenance also
helps in increasing the efficiency and add new feature in the
information system and attract more number of user to use
the digital management system.
Precondition For carrying out the maintenance of the information system
the administrator should have proper knowledge about the
codes and the process that is necessary for eliminating errors
and increasing the efficiency of the information system.
Flow
 The admin logs in into the information system with the
administrator account and password for starting the
maintenance work.
 The information system is set to down for all the users
during the maintenance period
 The administrator opens the database application for
the management of the database and clears the junk
files.
 The suspended account that have reached the time
limit are found by running a querry and it is deleted for
increasing space in the hard disk
5

 The errors in the connection and identified and they
are troubleshooted for increasing the efficiency of the
information system.
 A logical design of the information system is created
and the program components are identified for
checking the errors in the codes and connecting the
different modules with each other.
 The feedback of the users are analysed and the
modification that can be made on the interface are
identified for the management of the inputs and the
outputs of the information.
Primary use case 4
Use Case Title: Payroll
Actors: Player, Admin, Cheltenham Football Club Information System
Description: The use of the payroll feature in the information system helps
in creating a centralized management on the payments of the
players, deductions and recording the profits of the club.
Precondition The admin would only have the access of the payroll system
for the management of the payments of the players and
generating invoice and eliminate the errors that can be caused
due to manual process. The administrator should have proper
accounting knowledge for using the payroll features such that
no wrong data is inputted in the information system.
Flow
 The admin uses the payroll feature for different
purpose after login into the admin account.
 The time and attendance of the player can be tracked
with the system and the payroll information are
maintained.
 It is used for the optimization of the process and
eliminated the risk of human error and reduces the
paper works
 The payments made by the player are recorded and
the accounts are renewed or suspended
 It generates a notification for the admin if any of the
player misses to renew the account and the player is
marked as defaulter
 The accounts of the defaulter is ten suspended by the
admin and notified for renewing the account.
Primary use case 5
Use Case Title: View Profile
Actors: Player, Admin, Cheltenham Football Club Information System
6

Description: The user logs into the information system with their valid
username and password for viewing their profile and manage
the schedule and the different activity of the user. The player
is responsible for editing the details and update their profile
time to time for getting more opportunity and play more
matches with Cheltenham Football Club.
Precondition The precondition for viewing the profile is that the account
must be in active state and the user must be registered with
the Cheltenham Football Club Information System.
Flow  The user should have registered with the Cheltenham
Football Club Information System with current
information and have an account name and password.
 The user should have logged in with the information
system using their mobile or computers for logging.
 The user search the information system with the player
name for getting the information of different player
that is stored in the database of the information
system
 The search result shows the profiles of different
players with the photos and the user can select the
appropriate result for viewing the details.
10 use cases - brief description
Use case 1: Registration
Use case 2: Login
Use case 3: Payroll
Use case 4: Maintenance
Use case 5: View Profile
Use case 6: View payroll
Use case 7: Authentication
Use case 8: Feedback
Use case 9: Claims by the player
Use case 10: Account state
7

3) Class diagram including conceptual classes and associations, generalization, aggregation
and/or composition if applicable with a brief description
Class Diagram
Provide brief description of all key classes and main attributes:
Class name Description
Payment The payment class is created for recording the details of the payment
made by the player for opening the new account and pay the monthly
subscription fees for using the digital management system. The
payment is recorded with the payment ID for using it in future and
management of the transaction between the user and the Cheltenham
Football Club Information System.
Player The date of joining, number of matches played are used for selection of
the player and generating a report for the management of the activity
of the user. The player class is used for the management of the data of
the player and can be shared with the admin for reducing the manual
effort of the staffs and getting all the information form the information
system.
Account
The account class is created for the management of the account of the
different types of players and it helps the admin to get all the details of
the account status and manage the active or the suspended accounts.
8

The validity of the account and the activity of the players can be
tracked from the information system and it is connected with the
interface for allowing the admin to mange the accounts of the multiple
player from a single screen.
receipt The receipt class is a sub class of the payment class and it manages the
payment information and used for generating an invoice and maintain a
good communication with the players registered with the information
system. The receipt helps in maintaining transparency with the
members of the club and eliminated the risk of wrong transaction.
Record Details The details of the players such as the personal information and the
account information are recorded in a table with a player ID such that it
can be used for management of the information residing in the
information system. The user can get all the details of their profile by
searching the specific data with the means of the interface of the
information system.
Staffs The information of the staffs are recorded in the database and thus the
class is created for recording the details of the staffs and the other
members of the club. The details are recorded such that it can be used
for management of voluntary activity and management of different
event organized by the Cheltenham Football Club.
4) Interaction diagram
Sequence Diagram
9

Sequence Diagram - description and justifications
The above sequence diagram is shown for sending notification to the user and completion
of the payment process and the sequence are shown with the means of a vertical lines also
known as lifelines. The process are displayed as horizontal arrows and the arrows contains a
written message that helps in identification of the interaction. The synchronous messages
are represented with the means of solid arrows while the asynchronous messages are
displayed with the help of open arrow heads. The reply messages are shown with the help
of dashed lines and the user needs to wait for the synchronous message until the message is
done. For the asynchronous message the user does not need to wait for the response.
Collaboration Diagram
Collaboration Diagram: description and justifications
The collabortaion diagram is created after the identification of the relationship between the
componnets and it porteays the functionality, roles behaviour of the individual objects used for the
development of the digital management system. The objects in the collaboration diagram are
demonstarted as rectangles and named properly. The rectangles are connected with each other with
an arrows that represents the message sequence and the interraction between the different objects.
It helps in displaying the simple interraction with the smaller objects. The above collaboration
diagram helps to identify the roles of the domain class objects with the system. It cannot represent
the flow of the process and it helps in development of the pages needed for interracting with the
information system.
Flowchart/Activity Diagram
10

Flowchart Diagram Description and Justifications
The flowchart is created for the identification of the flow of information between the different
modules of the Cheltenham Football Club Information System. The relation of the user of the
information system and the system class objects are demonstrated in the above diagram. The user
can inquiry for an account and check the details from the system class objects and retrieve the
details of the account. The items are displayed to the user and the account details are selected. The
action of the player is recorded in the information system and the system responds according to the
action of the user. For example if a user clicks on the renew option the validity of the account and
the last renewal date is displayed to the user and from there the user can click the payment option
for proceeding with the payment. After the completion of the payment process the system
generates an automated invoice and sends it to the registered email ID of the user.
Appendix
11

References
Benveniste, A., Caillaud, B., Nickovic, D., Passerone, R., Raclet, J.B., Reinkemeier, P., Sangiovanni-
Vincentelli, A., Damm, W., Henzinger, T.A. and Larsen, K.G., 2018. Contracts for system
design. Foundations and Trends® in Electronic Design Automation, 12(2-3), pp.124-400.
Buede, D.M. and Miller, W.D., 2016. The engineering design of systems: models and methods. John
Wiley & Sons.
Cascio, W., 2018. Managing human resources. McGraw-Hill Education.
Chang, J.F., 2016. Business process management systems: strategy and implementation. CRC Press.
Chapman, W., 2018. Engineering modeling and design. Routledge.
Coronel, C. and Morris, S., 2016. Database systems: design, implementation, & management.
Cengage Learning.
Dennis, A., Wixom, B.H. and Tegarden, D., 2015. Systems analysis and design: An object-oriented
approach with UML. John wiley & sons.
Eastman, C.M., 2018. Building product models: computer environments, supporting design and
construction. CRC pres
Galliers, R.D. and Leidner, D.E. eds., 2014. Strategic information management: challenges and
strategies in managing information systems. Routledge.
Giachetti, R.E., 2016. Design of enterprise systems: Theory, architecture, and methods. CRC Press.
Hammer, M., 2015. What is business process management?. In Handbook on Business Process
Management 1 (pp. 3-16). Springer, Berlin, Heidelberg.
Laudon, K.C. and Laudon, J.P., 2016. Management information system. Pearson Education India.
Shaikh, P.H., Nor, N.B.M., Nallagownden, P., Elamvazuthi, I. and Ibrahim, T., 2014. A review on
optimized control systems for building energy and comfort management of smart sustainable
buildings. Renewable and Sustainable Energy Reviews, 34, pp.409-429.
Valacich, J., George, J. and Hoffer, J., 2014. Essentials of systems analysis and design. Prentice Hall
Press.
Welford, R., 2016. Corporate environmental management 1: Systems and strategies. Routledge.
Wiegmann, D.A. and Shappell, S.A., 2017. A human error approach to aviation accident analysis: The
human factors analysis and classification system. Routledge.
12