System Analysis and Design PDF

System Analysis and Design 1
System Analysis and Design
By [Name]
Course
Professor’s Name
Institution
Location of Institution
Date
Table of Contents
List of figures...................................................................................................................................4
1.0 Introduction................................................................................................................................5
1.1 Scope.................................................................................................................................5

System Analysis and Design 2
1.2 Functional System requirements.......................................................................................5
1.3 Use case diagram..............................................................................................................8
2.0 Use case diagram documentation.........................................................................................8
2.1 Description of use case.....................................................................................................8
2.1.1 Player registration use case...........................................................................................12
2.1.2 Staff registration use case.............................................................................................13
2.1.3 Coach registration use case...........................................................................................13
2.1.4 Staff login use case.......................................................................................................13
2.1.5 Member modification use case.....................................................................................13
2.1.6 Player search use case...................................................................................................14
2.1.7 Game cancel use case...................................................................................................14
2.1.8 Report printing use case................................................................................................14
2.1.9 Payments use case.........................................................................................................14
2.1.10 Accounts use case.......................................................................................................15
3.0 Conceptual class diagram...................................................................................................16
3.1 Classes.............................................................................................................................16
3.2 Class descriptions and main attributes............................................................................16
4.0 Interaction diagrams................................................................................................................19
4.1 Sequence diagrams: Description and justification..........................................................19
4.1.1 How to register a player................................................................................................19
4.1.2How to dismiss a player.................................................................................................20
4.2 Activity diagram; Description and justification..............................................................21
4.3 Collaboration diagrams; Description and justification...................................................22
4.4 Conclusion......................................................................................................................23
References......................................................................................................................................24

System Analysis and Design 3

System Analysis and Design 4
List of figures
Figure 1: Use case Diagram.............................................................................................................5
Figure 2: Sequence Diagram.........................................................................................................14
Figure 3: Activity Diagram............................................................................................................15
Figure 4: Collaboration Diagram...................................................................................................16
1.0 Introduction
Due to the expanding requirement for the administration of the recorded inside the Cheltenham
Football Club for the 5 groups being overseen here, there emerges a need to build up a
framework that will help in the running of the program in a day by day movement of the club.
Every one of these tasks can be put into an efficient record to facilitate the recovery of the data.
In light of this examination, a paper should convey to our concentration to the advancement of
the made-reference to a framework with the investigation and the structure all consolidated.
1.1 Scope
The framework in the survey will be of significance to the Cheltenham Football Club. From the
general arranging stage, the framework is set to give a very much overseen set of records for
every one of the players inside the club. The most extreme club limits are to permit the
enlistment of new individuals, refresh the current points of interest permitting changes of various
sorts. With this prominent, the group designers need to comprehend the prerequisites of the club
to guarantee they meet the base expressed goals through the improvement of their performance
(Cox and Bobrowski, 2016).
1.2 Functional System requirements
Damning is one noteworthy issue that can emerge using any given framework. With the end goal
to maintain a strategic distance from this, each designer needs a genuine picture of what
precisely the framework is relied upon to do and the conceivable manners by which it tends to be
created to permit more changes later on. We are given the practical necessities of the framework
as the primary perspective before any advancement procedure is started. Given the way that they
can't be dropped mostly, every one of the partners must have a reasonable comprehension of the
considerable number of procedures included (Blanchette et al., 2017).