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