System Analysis and Design

This document provides a comprehensive guide to system analysis and design. It covers the chosen software development methodology, data gathering techniques, and functional and non-functional requirements. It also includes class diagrams, use case diagrams, entity relationship diagrams, data flow diagrams, and activity diagrams. The document concludes with insights into the interface and a summary of the system. Perfect for students studying system analysis and design.

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............................................................................5
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
The case study depicted here deals with the Allsports Club that has many members as
publishes a newsletter in all weeks containing about the sporting activities that were held in the
previous week. For publishing the newsletters the president and the editor of the club is
responsible for. The editor is selected every week by the club’s president and the editors selects
the articles that are submitted by the members of the club related to their respective sports. But
this system is facing problem to handle this system as because the selection of article does not
synchronizes and the advertisements also gets mixed up wile selecting. So, to track the working
process, the club’s president has decided to design a system software which will be capable of
handling the system of the club. This report include some objectives that are to be addressed for
developing the application. The objectives are:
 To study two approaches of software development that will help to develop the system.
 To analyze three data gathering techniques to develop the system.
 To develop the FR (Functional Requirements) and the NFR (Non-Functional
Requirements) associated with the system.
 To develop system analysis design for the new system to be developed.
Chosen Software Development Methodology
For carrying out the research in the system, project methodology is needed in the project
for developing the system. The system to be built in the project needs proper methodology for
developing the information system. The best methodologies are to be chosen by the system
developer so that the system can be delivered successfully.

3SYSTEM ANALYSIS AND DESIGN
Waterfall Methodology: Water model is considered to be a traditional model for
developing a system software. This is a rigid model that does not allow any changes if a phase is
already completed (Vijayasarathy & Butler, 2015). The waterfall methodology instructs the
project manager to complete a particular phase and then proceed to next phase and does not
allow returning to the previous phase. If there is a need of back tracking, the project needs to
start from beginning. This methodology can work with less experienced team members.
DevOps Methodology: Development with information technology methodology is
known as a centered methodology that includes changes in the organization (Matharu et al.,
2015). This particular methodology when used in projects increases the collaboration between
the departments that carried out different work in developing the system.
Justification for choosing above methodologies: The waterfall methodology in this
project will help the developer to fulfil the objective of the project that is defined at the
beginning of the project (Abrahamsson et al., 2017). This methodology helps to make objective
clear. The other methodology helps to focus on developing time of the project. This methodology
will increase the success rate of the project and problem associated with the project can be solved
using this methodology.
Data Gathering Techniques
The techniques of data gathering that can be used for developing the system are explained
below:
Analysing the present documents: To develop new system software for Allsports club,
all previous documents are to be studies so that the present system can be analysed and work

4SYSTEM ANALYSIS AND DESIGN
accordingly to improve the present system (Lochrie, Curran & Gorman, 2015). The pitfall of the
present system are to be known so that it can be improved accordingly.
Questionnaires: The most common technique that can be used for gathering the data is
the questionnaires (Akber et al., 2018). This method helps the developer to gather user
requirements so that the software can be developed according to the demand of user and fulfil the
requirements of the user. Questionnaires can be carried out through email, phone or in printed
forms.
Interviews: Interview is the most convenient method that can be used in gathering data.
In this technique, the results can be analysed immediately and this method is more secured and
safe as face to face interview is held in this method (Frey & Fontana, 2019). Interview method is
most appropriate for complex projects.
Questionnaire
1. How are you connected with Allsports Club?
2. What is the system that you are presently working in the system?
3. Is the working process in the system is proper way to carry out the work?
4. What are the problems that you are facing in the system of Allsports Club?
5. What features you want to be included in the new system?
6. Who will be users of the new developed information system for the Allsports Club?
7. Do you need the information system for users as well as administrators?
8. Is there any security issue that you are facing with the current system used for working?
9. Is the new system will be used only in desktop, or there is a need of mobile and tablet
version also?

5SYSTEM ANALYSIS AND DESIGN
10. Do you need training for running the new information system?
Functional and Non-Functional Requirements
Functional requirements:
1. The new system will securely store the personal details of the member associated with the
club.
2. Data that are related with the editors selected by the president are to be stored by the
system.
3. The newsletter articles are stored in the system as per date they are published.
4. From the list of club members, the present can select an editor for that week.
5. Advertisements that are used in the newsletter are stored in the system and can be
checked by the editor and the president.
6. Users wants to receive newsletter in two ways. The users desiring to get e-newsletter has
to give their email address which is stored by the system and for other, proper mailing
address is stored in the system.
Non-functional requirements:
1. All standards and documentation will be provided by the developer for developing the
new system.
2. The system will have an easy and secured interface so that the users can use it efficiently.
3. The system response time is less and is capable to support multiple users.

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

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

8SYSTEM ANALYSIS AND DESIGN
Use Case for Advertisement Selecting
Figure 3: Use Case for Selecting Advertisement
(Source: Created by Author on Visio)
3. Use Case scenarios
Overview
Title Login for club members
Description The members associated with the club needs to first register themselves
and then have to login to upload the articles related to their respective
sports. Without login they cannot access the system. The can also view

9SYSTEM ANALYSIS AND DESIGN
previous articles that were submitted by them in the previous weeks.
Actors Involved Members of club and the administrator
Pre- Conditions Before carrying out the login use case, the user needs to sign up with
the system and become a member of the club.
Post- Conditions The articles can be uploaded after completing the login process.
Exceptions:
1. If the users cannot login in the system, the user needs to check the login credentials.
Overview
Title Selecting Advertisement
Description The advertisers has to login in the system for uploading the
advertisements that they want to publish. Of the editor selects their
advertisements, notification is sent to the advertisers so that they can
make the payment for publishing the advertisement.
Actors Involved Advertiser registered for the system and editor.
Pre- Conditions There is name registering process before login. Without registering
they cannot login.
Post- Conditions Printing the advertisements in the weekly newsletter.
Exceptions:
1. Proper used id and passwords are to be given to the login.

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

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

12SYSTEM ANALYSIS AND DESIGN
6. Activity Diagram
Figure 6: Activity Diagram of Allsports Club 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 report above explains the information system that is to be built for tracking the
working operations of the Allsports Club. The activities that are carried out in the club are not
synchronized and the president and the editor is not able the handle all the activities manually.
So, the president has decided to develop the automated system that will help to keep track on all
the working activities related to printing of newsletter and printing of advertisement in the
newsletter. This report above describes all the procedure and methodologies that are to be taken
by the developer to develop the system. Two such system development methodologies are
explained followed by thee data gathering techniques used to build the system. Data gathering
questionnaire is to be distributed among the users, and this report lists ten such sample questions
that can be used for gathering the data. The system has FR and NFR and all those requirements
are listed in this report.
As a recommendation for developing the system for the Allsports Club, it can be said that
all the FR and the NFR should be satisfied for developing the system. The system should meet
all the requirements of the user and proper validation and verification technique should be
carried out before launching the system. The system design should include follow all the
standard regulations for developing the system.

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
Akber, S. M. A., Khan, I. A., Muhammad, S. S., Mohsin, S. M., Khan, I. A., Shamshirband, S.,
& Chronopoulos, A. T. (2018, June). Data Volume Based Data Gathering in WSNs using
Mobile Data Collector. In Proceedings of the 22nd International Database Engineering
& Applications Symposium (pp. 199-207). ACM.
Frey, J. H., & Fontana, A. (1991). The group interview in social research. The Social Science
Journal, 28(2), 175-187.
Lochrie, S., Curran, R., & O’Gorman, K. (2015). Qualitative Data Gathering
Techniques. Research Methods for Business and Management.
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.
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.