System Analysis and Design Task 2022

Running head: SYSTEM ANALYSIS AND DESIGN
SYSTEM ANALYSIS AND DESIGN
Name of the Student
Name of the University
Author Note

SYSTEM ANALYSIS AND DESIGN
1
Table of Contents
Task 1 - Gantt chart.........................................................................................................................2
Task 2 – System Requirement.........................................................................................................3
Actors...........................................................................................................................................3
Functional Requirement...............................................................................................................3
Non-Functional Requirement......................................................................................................4
MoSCoW classification...............................................................................................................4
Task 3 – Use Case Diagram and Use Case description...................................................................5
Task 4 – Class Diagram.................................................................................................................10
Task 5 – Additional Functionality.................................................................................................10
Bibliography..................................................................................................................................12

SYSTEM ANALYSIS AND DESIGN
2
Task 1 - Gantt chart
ID Task
Mode
Task Name Duration Start Finish
1 SystemsAnalysis & DesignPortfolio5.5days Mon3/23/20Mon3/30/20
2 SystmRequirement Analysis 1.25days Mon3/23/20Tue 3/24/20
3 Identification of Actors 3hrs Mon 3/23/20Mon 3/23/20
4 Requirement Gathering 4hrs Mon 3/23/20Mon 3/23/20
5 PrioritizingRequirements 3hrs Mon 3/23/20Tue 3/24/20
6 Milestone 0 0days Tue 3/24/20Tue 3/24/20
7 Use Case Modelling 1.63days Tue 3/24/20Wed3/25/20
8 identification of Use Cases 5hrs Tue 3/24/20Tue 3/24/20
9 Development of Use case Diagram4hrs Tue 3/24/20Wed 3/25/20
10 Use Case descriptions 4hrs Wed 3/25/20Wed 3/25/20
11 Milestone 1 0days Wed 3/25/20Wed 3/25/20
12 Class Diagram 1.13days Wed3/25/20Thu 3/26/20
13 Identification of class,
attributes and methods
4hrs Wed
3/25/20
Thu
3/26/20
14 DefiningRelationship
between classes
5hrs Thu
3/26/20
Thu
3/26/20
15 Milestone 2 0days Thu 3/26/20Thu 3/26/20
16 Additional FunctionalityAnalysis1.5days Fri 3/27/20Mon3/30/20
17 Identification of additional
features
5hrs Fri 3/27/20Fri 3/27/20
18 Explanation of actor
associated with new
features
4hrs Fri 3/27/20Mon
3/30/20
3/24
3/25
3/26
S M T W T F S S M T W T F S S M T W T F S S M T W T F S S
Mar 15, '20 Mar 22, '20 Mar 29, '20 Apr 5, '20 Apr 12, '20
Figure 1: Gantt chart
Source: created by author
Task 2 – System Requirement
System requirement gathering is a vital phase of the system development. It helps in
further designing the system structure and architecture (Coronel and Morris 2016). The
Identification of actors, functional and non-functional requirements are given below.

SYSTEM ANALYSIS AND DESIGN
3
Actors
Customer: Customer role is to book tickets online or visiting box office. The process includes
selection of performance by a production, selection of date-time, selecting number of tickets and
purchasing tickets via online or at box office using debit/credit card.
TicketOfficeAssistance: The Role of Ticket Office Assistance is to sell and print tickets for the
customers off-line at box office.
BoxOfficeManager: The Role of Box Office Manager is to add new productions, allocate new
date-time for them and generate ticket sales report.
Functional Requirement
i. The system should allow its users to login using user credentials and logout after a
session.
ii. The system should allow user to browse through productions, Performances and tickets.
iii. The customer must be able to purchase ticket using credit/debit card details.
iv. Customer should be able to register into the system using basic details.
v. Ticket office Assistant must be able to print tickets offline at box office.
vi. Box Office Manager must be able to book new productions.
vii. Box Office Manager must be able to allocate date-time to new productions.
viii. Box Office Manager must be able to allocate ticket price for new productions.
ix. Box Office Manager must be able to generate ticket sales report in the system.
Non-Functional Requirement
x. The system should have high capacity to handle large number of customers at an instant
of time.