QAC020C154S System Analysis and Design

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
The main functional requirement identified for the development of the - Cheltenham
Football Club Information System are listed below:
 To record the details of the club members in the information system such that
their data can be used for the management of the different events organized by
the football club.
 To provide permission to the user to add, remove or delete user account and
manage the information of the players and the staffs
 To automatically manage the renewal of the membership and eliminate the risk of
errors due to manual process.
 To increase the transparency of communication and enable the user to have a
track on their activity and manage their own profile.
 To generate automated notification messages if a player is unable to attend a
game and increase the efficiency of the system
 To enable the managers to search relevant data and produce seasonal report for
finding the errors in the management process and rectify it for increasing the
efficiency
 To manage the schedule of the games and add the player details and type of
tournament for future reference
 The system should also be able to record the training sessions and generate
notification for the managers to manage the training session.
1.2 use case diagram
2

2) use case diagram documentation
Primary use case 1
Use Case Title: User management
Actors: Players under 18 years, Players over 18 years, Admin and
Cheltenham Club database.
Description: The users is responsible for the management of the users
such as adding new client, modification of client records and
deleting the client records.
Precondition The users should have all the information available for
registering with the information system. The information
should be relevant and the system should be able to generate
automated message.
Flow  The use registers with the information system using
their name, contact details, role, date of joining,
leaving date, etc.
 The Admin is responsible with adding the new player
after verification of the details provided by the user.
 If the information is found that are not valid the
account is not created and the information is deleted
from the information system.
 If any of the information is not provided by the user
the admin can set a reminder that notifies the user to
fill the information in order to open their account in
the information system.
 If there is any changes in the information the user can
also edit the details and the account is updated after
the approval.
Primary use case 2
Use Case Title: Players Account management
Actors: Players under 18 years, Players over 18 years, Admin and
Cheltenham Club database.
Description: The manager is responsible for the management of the
accounts of the user and the admission fees, registration fees
are automatically calculated with the adding of the details of
the user. The monthly contribution of the players are recorded
and defaulters are also recorded for suspending the accounts.
Precondition The users should have an pre-registered user account with
the information system and provide all the necessary
information into the information system for the development
3

of the solution.
Flow
 The user of the information system registers with all
the necessary information.
 The information system categorizes the user according
to their age and sets their monthly contribution value
and creates their account.
 The user is asked for the admission fees and on
successful payment the account is activated.
 The monthly payment charges are displayed and a
counter starts for setting calculating the remaining
time available for the user for the renewal of the
account.
 A grace period is given to the user for the renewal and
the user needs to pay a late fine for missing the due
date of renewal
 After missing the grace period the account of the user
is suspended.
 The account of the user is kept for 3 months if no
subscription fees is received and after that the account
is dismissed.
Primary use case 3
Use Case Title: Suspend Account
Actors: Players under 18 years, Players over 18 years, Admin and
Cheltenham Club database.
Description: The account of the user registered with the information
system gets deactivated when it is not renewed for the one
month.
Precondition For the suspension of the account the user needs to be
registered with the information system. The user needs to
have a valid account and make payment based on their
category.
Flow  The admin of the information system manages the
accounts of the users registered with the information
system.
 A counter is set that calculates the time remaining for
the next renewal and a notification is generated for the
user and the admin for reminding the user for renewal
of the account
 If the user misses the renewal time the account of the
user is suspended and the user cannot use the
account.
4

 The user account is managed by the admin and the
account gets dismissed if the user does not renews the
account for the consecutive 3 months.
Primary use case 4
Use Case Title: View Account Details
Actors: Players under 18 years, Players over 18 years, Admin and
Cheltenham Club database.
Description: The user can view the details of the account such as the
matches played, next match, players playing in the matches,
coach information, prize won, etc. by logging into the
information system. The user can also modify the personal
information and add new information from the account.
Precondition The user should be a club member and able to use the digital
management system efficiently and easily. The player should
have all the information available while using the information
system.
Flow  The user should log in with their user ID and password
for the fetching the detailed information about the
activity of the club members, coaches and staffs.
 The admin also needs to log in to view the details of
the players and the other users registered with the
information system
 The accounts should be managed by the admin and
notification should be sent to the user for alerting the
user for any new event or changes in the current
schedule.
Primary use case 5
Use Case Title: Record Details
Actors: Players under 18 years, Players over 18 years, Admin and
Cheltenham Club database.
Description: The details of the user are recorded in the information system
such that it can be used by the admin for the management of
the information system. The details are used by the
administrator for generating monthly reports and reduce the
errors in the management process.
Precondition Relevant and current information should be provided in the
information system. A checking should be applied such that
the no fields are left blank as it can cause error in the
information system while generating the seasonal reports.
5

Flow  The user registers with the information system by
filling a form.
 The form is checked and validated by the admin for
eliminating the risk of error in the information system
and increase the efficiency of the club
 Different proofs such as membership of the user and
the accurate contact information such as valid email,
contact number is verified.
 All the details of the players such as the number of
matches played, score, wins, prizes won should be
recorded in the information system
 The information should be kept up to dated and the
system should be able to send notification to the users
10 use cases - brief description
Use case 1: Add Client – The use case add client is used by the admin for adding new user
in the information system after checking the information provided by the user and
validating the information.
Use case 2: Modify Client Records – It is used for the modification of the records of the
clients and if the client provides wrong information the option is used for rectification.
The modification option also helps the user to update their profile and increase the
efficiency of the information system.
Use case 3: Manages Player accounts - The manager is responsible for the management of
the accounts of the user and the admission fees, registration fees are automatically
calculated with the adding of the details of the user. The monthly contribution of the
players are recorded and defaulters are also recorded for suspending the accounts.
Use case 4: Admission Fees – It is used for the management of the entries of the user and
opening the new account of the user in the information system.
Use case 5: Registration Fees - The user needs to pay a registration fee for opening the
new account and a checking is done on the age of the user for setting the registration
fees. The registration fee is different for the different category of user and it needs to be
paid by the user for the management of the information system.
Use case 6: Monthly Contribution - The details of the user are recorded in the information
system such that it can be used by the admin for the management of the information
system. The details are used by the administrator for generating monthly reports and
reduce the errors in the management process.
Use case 7: Defaulter – It is used by the admin to mark a user if he misses the payment for
a month and the user is marked as defaulter for 3 months and after that the account of
the user is dismissed.
Use case 8: Suspended Account - For the suspension of the account the user needs to be
registered with the information system. The user needs to have a valid account and make
payment based on their category.
6

Use case 9: View Account Details - The user can view the details of the account such as
the matches played, next match, players playing in the matches, coach information, prize
won, etc. by logging into the information system. The user can also modify the personal
information and add new information from the account.
Use case 10: Record Details - The details of the user are recorded in the information
system such that it can be used by the admin for the management of the information
system. The details are used by the administrator for generating monthly reports and
reduce the errors in the management process.
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
Player It is used for recording the detail of the players registered with the
information system.
Coach
It is used for recording the details of the coach assigned for providing
training to the user connected with the information system.
Record Detail The details of the events, players and the coach are recorded in the
information system such that the user can have all the details of the
football club.
Account It is used for management of the payment made by the user to use the
information system and management of the monthly payments.
Account State The account can be sent to suspended state on not receiving the
payment on time and the class is used for storing the data of the
suspended account state.
Staffs The details of the staffs are recorded such that it can be used for
searching the availability of the staffs and management of the monthly
8

payments of the staffs.
4) Interaction diagram
Sequence Diagram
Sequence Diagram - description and justifications
The sequence diagram is used for the demonstration of the flow of information between the
different elements of the information system. The player data is fetched from the
information system for reservation of the player for the new match and create a new team.
If the payers are unavailable new player is booked from the reservation list and the name is
removed from the reservation list.
Collaboration Diagram
Collaboration Diagram: description and justifications
It is used for demonstration of the relationship between the interractions and management of the
roles and responsibility of the objects. The objects are demonstrated as rectangles and labled for the
deonstration of the flow.
Flowchart/Activity Diagram
9

Flowchart Diagram Description and Justifications
The activity diagram is used for the demonstraton of the flow of one activity to another and
management of the control flow for inquiry account and checking the details of the user from the
database of the information system.
10

Appendix
11

References
Azar, A. T., & Vaidyanathan, S. (Eds.). Chaos modeling and control systems design, 2015, 581.
Germany: Springer.
Buede, D. M., & Miller, W. D. The engineering design of systems: models and methods. John Wiley &
Sons, 2016.
Endsley, M. R. Designing for situation awareness: An approach to user-centered design. CRC press,
2016.
Ha, E, "Building design thinking system through the design type of analysis.". in KOREA
SCIENCE & ART FORUM, 20, 2015, 475.
Kan, T., Nguyen, T. D., White, J. C., Malhan, R. K., & Mi, C. C. A new integration method for an
electric vehicle wireless charging system using LCC compensation topology: analysis and
design. IEEE Trans. Power Electron, 2017, 322, 1638-1650.
Montgomery, D. C. Design and analysis of experiments. John wiley & sons, 2017.
Munzner, T. Visualization analysis and design. AK Peters/CRC Press, 2014.
Oinas-Kukkonen, H., & Harjumaa, M. Persuasive systems design: key issues, process model and
system features. In Routledge Handbook of Policy Design (pp. 105-123). Routledge, 2018.
Pedrycz, W. Granular computing: analysis and design of intelligent systems. CRC press. 2016.
Phillips, C, H Nagle, & A Chakrabortty, Digital control system analysis & design. in . 2015,
p.45.
Romiszowski, A. J. Designing instructional systems: Decision making in course planning and
curriculum design. Routledge, 2016.
Valacich, J., George, J., & Hoffer, J. Essentials of systems analysis and design. Prentice Hall Press.
2014.
12