Comprehensive System Analysis and Design Report for Allsports Club

This report presents a comprehensive system analysis and design for the Allsports Club, a multipurpose club facing challenges in managing its data and publishing its newsletter. The project aims to design an information system to automate club activities. The report explores two software development methodologies: Waterfall and DevOps, justifying the selection of each. It outlines three data gathering techniques: studying present system documentation, questionnaires, and interviews. Functional and non-functional requirements for the new system are defined, covering member and editor data storage, newsletter generation, and security. The report includes detailed UML diagrams such as class, use case, entity-relationship, data flow, and activity diagrams, along with interface designs. Use case scenarios are provided to illustrate system interactions. The conclusion recommends a standardized, user-focused system aligned with the project's objectives.

Running head: SYSTEM ANALYSIS AND DESIGN
System Analysis and Design
Name of Student-
Name of University-
Author’s Note-

1SYSTEM ANALYSIS AND DESIGN
Table of Contents
Section A.........................................................................................................................................2
Introduction..................................................................................................................................2
Chosen Software Development Methodology.............................................................................2
Data Gathering Techniques.........................................................................................................3
Questionnaire...............................................................................................................................4
Functional and Non-Functional Requirements............................................................................4
Section B..........................................................................................................................................6
1. Class Diagram..........................................................................................................................6
2. Use Case Diagram...................................................................................................................7
3. Use Case scenarios..................................................................................................................8
4. Entity Relationship Diagram.................................................................................................10
5. Data Flow Diagram................................................................................................................11
6. Activity Diagram...................................................................................................................12
7. Interface.................................................................................................................................13
Conclusion.................................................................................................................................15
References......................................................................................................................................16

2SYSTEM ANALYSIS AND DESIGN
Section A
Introduction
Allsports club is better known as multipurpose club dealing with wide number of
members and many sporting activities. The club publishes a newsletter every week written by the
club member. But the present is facing difficulty to maintain the data and thus resulting in delay
in publishing the newsletter. The aim of this project is to design an information system software
for the club so that all the activities can be done automatically and keep a track on it.
The objectives of this project are:
 To suggest two system development approaches for the new system.
 To suggest three techniques to gather requirement data for the project.
 To define the functional and the non-functional requirement of the new proposed system.
 To design the UML diagrams of the systems.
Chosen Software Development Methodology
To make the project successful, methodologies are to be used for developing the new
system. The developer of the new computer system needs to examine all the methodologies and
select the best methodology for carrying out the system development (Abrahamsson et al., 2017).
Two of the methods are explained below.
Waterfall Methodology: This is the traditional methodology and includes a rigid model
having many sequential phases. In waterfall model, each phases are to be accomplished to
proceed to the next level (Vijayasarathy & Butler, 2015). If the developer team is less
experienced, waterfall model works the best.

3SYSTEM ANALYSIS AND DESIGN
DevOps Methodology: This approach is centered mainly on the organizational change
that helps to increase the collaboration that are between the departments that are responsible in
different segments of system development.
Reasons to choose the above models: With the waterfall model, the objective in
developing the computer system gets clears and developers find easy to fulfil the objective of the
project (Matharu et al., 2015). The DevOps approach is selected because is mainly focuses on
improvement of time. This method lowers the failure rate and helps efficient fixing of the
problems identified.
Data Gathering Techniques
Three investigation techniques that are to be used for investigating the information
system are explained below:
Studying present system documentation: For developing the new system, the
documentation of the present system is to be studied thoroughly so that the developer will get to
know about the present system and work on the improvement of the present system (Pourtaghi et
al., 2016). Without knowing the flaws of the current system, it is not possible to improve the
system or update the system.
Questionnaires: Most convenient technique of investigation technique is the using
questionnaire method (Idreos, Papaemmanouil & Chaudhuri, 2015). Questions are distributed
among the target audiences and the respondents are given time to attend the questionnaire. This
process can be carried out in printed forms, over the phone or in email.

4SYSTEM ANALYSIS AND DESIGN
Interviews: By interview process, the respondents feel safe and secure to give their
respondents (Dhaka & Johari, 2016). For complex issues, interviews technique is used and is
more suitable compared to other data collection techniques.
Questionnaire
1. What is role you have in the Allsports club sporting activities?
2. What particular system you are using for the current working process?
3. Are you satisfied with the system that is carried out in the system?
4. Please mention some particular features that you want to include in the new computer
system.
5. Which group of people is going to use the computer system? Is it only for the
management group or for the club members as well?
6. What features you want in the back end of the new developed computer system?
7. Do you face some problem regarding the security issues of the present working system?
8. What are the platforms in which the computer system is to be used? Is it only for a
desktop version, or will be used in mobile and tablets also?
9. In how much time do you expect the new computer system to be completed?
10. Do you need any raining related to the new computer system developed for Allsports
club?
Functional and Non-Functional Requirements
Functional requirements:
1. New computer system has the ability to store the details of the club members.
2. The data related to the selected editors are also stored by new system.

5SYSTEM ANALYSIS AND DESIGN
3. The data related to the newsletter for every week are stored in new system (Eckhardt,
Vogelsang & Fernández, 2016).
4. The president will be able to select an editor from the list of club members.
5. The data related to advertisers and the selected advertisements are stored in new system.
6. Newsletters details will be generated by the new system.
Non-functional requirements:
1. The new system will include usability that is documentation for the system will be
provided and standards of the user interface will also be used.
2. The users can rely on the system as the new system will have security features (Laplante,
2017).
3. The response time of new system is also less and supports many concurrent users.

6SYSTEM ANALYSIS AND DESIGN
Section B
1. Class Diagram
Figure 1: Class Diagram of new computer system
(Source: Created by Author on Visio)

7SYSTEM ANALYSIS AND DESIGN
2. Use Case Diagram
For Member Login
Figure 2: Use Case for Club Member Login
(Source: Created by Author on Visio)

8SYSTEM ANALYSIS AND DESIGN
Use Case for Advertisement Selecting
Figure 3: Use Case for Advertisement Selecting
(Source: Created by Author on Visio)
3. Use Case scenarios
Overview
Title Club Member Login
Description The club member having a user id and password has to login in the
system so that they can upload the articles related to their sports choice.
The login is approved by the administrator. The administrator also

9SYSTEM ANALYSIS AND DESIGN
collects the articles that are uploaded by the club members.
Actors Involved Club members and administrator
Pre- Conditions Before login, the club members needs to sign up in the system by
entering their personal details.
Post- Conditions The club members can upload articles after login.
Exceptions:
1. With wrong user id or password, the login process is not successful.
2. The user needs to provide proper password, otherwise click on the forgot password option.
Overview
Title Advertisement Selecting
Description The advertisers uploads the advertisements that they want to be in the
week’s newsletter. The editor then selects the advertisement and gets
approved by the president. According to the duration of the
advertisement, payment is charged and advertiser makes the payment.
Actors Involved Advertiser and the editor.
Pre- Conditions The advertiser needs to sign up before uploading the advertisement in
the system.
Post- Conditions Advertisement are printed on week’s newsletter.
Exceptions:
1. The advertisers need to provide proper password, otherwise click on forgot password option.

10SYSTEM ANALYSIS AND DESIGN
4. Entity Relationship Diagram
Figure 4: Entity Relationship Diagram of new computer system
(Source: Created by Author on Visio)

11SYSTEM ANALYSIS AND DESIGN
5. Data Flow Diagram
Figure 5: Data Flow Diagram of new computer system
(Source: Created by Author on Visio)

12SYSTEM ANALYSIS AND DESIGN
6. Activity Diagram
Figure 6: Activity Diagram of new computer system
(Source: Created by Author on Visio)

13SYSTEM ANALYSIS AND DESIGN
7. Interface
Sign Up Interface
Login Interface

14SYSTEM ANALYSIS AND DESIGN
Select Editor Interface
Advertiser Interface

15SYSTEM ANALYSIS AND DESIGN
Conclusion
The above report details the new information system for the Allsports Club. There is a
need of new information system for carrying out the activities of the club and the report details
different activities that are to be carried out to develop the new automated system for the club.
There is a need to have a development methodology to build the computer system for the club
and the two development methodologies are explained in the report above. In this report, three
investigation techniques are also explained that is needed to investigate the new computer system
for the Allsports Club. The techniques that are examined above are the interviews, group
sessions and questionnaires that can be used to collect data regarding the requirement of the
system. The new computer system has functional requirements as well as no-functional
requirements. All those are listed in this report above.
It is recommended to develop a computer system that is standardize and follows all the
rules and regulations of standardization used in development of a software. The objectives of the
designing the computer system is also to be maintained and should be made according to the
requirement gathered from the users.

16SYSTEM ANALYSIS AND DESIGN
References
Abrahamsson, P., Salo, O., Ronkainen, J., & Warsta, J. (2017). Agile software development
methods: Review and analysis. arXiv preprint arXiv:1709.08439.
Dhaka, P., & Johari, R. (2016, April). CRIB: Cyber crime investigation, data archival and
analysis using big data tool. In 2016 International Conference on Computing,
Communication and Automation (ICCCA) (pp. 117-121). IEEE.
Eckhardt, J., Vogelsang, A., & Fernández, D. M. (2016, May). Are" non-functional"
requirements really non-functional? an investigation of non-functional requirements in
practice. In 2016 IEEE/ACM 38th International Conference on Software Engineering
(ICSE) (pp. 832-842). IEEE.
Idreos, S., Papaemmanouil, O., & Chaudhuri, S. (2015, May). Overview of data exploration
techniques. In Proceedings of the 2015 ACM SIGMOD International Conference on
Management of Data (pp. 277-281). ACM.
Laplante, P. A. (2017). Requirements engineering for software and systems. Auerbach
Publications.
Matharu, G. S., Mishra, A., Singh, H., & Upadhyay, P. (2015). Empirical study of agile software
development methodologies: A comparative analysis. ACM SIGSOFT Software
Engineering Notes, 40(1), 1-6.
Pourtaghi, Z. S., Pourghasemi, H. R., Aretano, R., & Semeraro, T. (2016). Investigation of
general indicators influencing on forest fire and its susceptibility modeling using different
data mining techniques. Ecological indicators, 64, 72-84.

17SYSTEM ANALYSIS AND DESIGN
Vijayasarathy, L. R., & Butler, C. W. (2015). Choice of software development methodologies:
Do organizational, project, and team characteristics matter?. IEEE software, 33(5), 86-94.