Detailed System Analysis and Design Report: FSIRCS Project

This report provides a comprehensive system analysis and design for the Fearless Spiders Indoor Rock Climbing System (FSIRCS). It begins by identifying key stakeholders, including the owner, staff, customers, and service engineers, and then outlines both functional requirements like registration, logi...Read More

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

1
SYSTEMS ANALYSIS AND DESIGN
Table of Contents
Answer to Question 1: List of Stakeholders........................................................................2
Answer to Question 2: Functional and non-functional requirement...................................3
Answer to Question 3: List of Use Case..............................................................................4
Answer to Question 4: Domain Model Class Diagram.......................................................6
Answer to Question 5: CRUD MATRIX............................................................................6
Answer to Question 6: Fully Developed Use Case Description..........................................7
Answer to Question 7: Activity Diagram............................................................................9
Answer to Question 8: System Sequence Diagram...........................................................10
Answer to Question 9: State machine Diagram.................................................................11
Answer to Question 10: Create Usage report....................................................................11
Bibliography......................................................................................................................13

2
SYSTEMS ANALYSIS AND DESIGN
Answer to Question 1: List of Stakeholders
The main stakeholder identified for the development of the Fearless Spiders Indoor Rock
Climbing System (FSIRCS) are listed as follows:
Stakeholder 1 – Ross Hill
He is the owner of the venture and wants the organization to expand with the
implementation of the information system. He wants the information system for monitoring the
activity of the staffs and maintenance of the walls.
Stakeholder 2 – Staffs
The staffs of Fearless Spider works to hold the ropes and works for the maintenance of
the walls. They are also responsible for handling the payment and transactions of the tickets. The
safety induction are given to the clients by the staffs for meeting the safety needs of the clients
and alert them from any accidents that may arise during the wall climbing.
Stakeholder 3 – Customer
The customers and the clients can use the information system for booking and cancelling
their tickets. The customer can be members and save their money by getting membership passes.
Stakeholder 4 – Service Engineer
The service engineer is responsible to check the safety and the comfort of the clients for
each of the sessions. The walls are inspected for meeting the cleanliness and the equipment’s are
checked and the system is updated accordingly.

3
SYSTEMS ANALYSIS AND DESIGN
Answer to Question 2: Functional and non-functional requirement
a. The main functional requirement identified for the development of the information system for
Fearless Spiders are listed as follows:
Registration – The registration option should be available for the customer to use the
different service and book tickets online. The status of the booking can also be shown to the
users using the information system.
Login – The user should be able to find any information about the service and book their
tickets by successfully logging into the system. An unique username and a password
combination is used by the users to login into the system.
Search – The user or the admin can search information about the service, staffs and the
customers from the information system.
Logout – The user needs to logout the system when it is not used for avoiding the risk of
data loss and redirecting to the home page of the information system.
Status – All the information about the customer, payment, maintenance service and the
staff information are inputted in the information system for sending and sending notification to
the users for an event.
Tracking – The admin account can be used for monitoring the activity of the users and
get the details of the customers and the staffs for maintaining the efficiency of the current
business process of the organization.
b. The nonfunctional requirement identified for the development of the information system are
listed as follows:

4
SYSTEMS ANALYSIS AND DESIGN
Security- The security is the main aspect of the information system, the efficiency of the
information system can be improved with the implementation of security mechanism for
securing the user information.
Storage – The storage servers should be used for the storing the data regarding the
maintenance of the walls and the service of the ground. The details of the users and the password
information should be stored in the information system.
Availability – The information system should be available to the users for all the time for
reducing the risk of business loss. The querry response time should also be minimum such that
the system is efficient.
Reliability – The system should never be down and no error data must be inputted in the
information system for increasing the reliability of the information system.
Answer to Question 3: List of Use Case
a. List of use case for the development of the development of the FSIRCS is tabulated below.
Participating Actors Use Case name Brief Use Case Description
Admin Monitor The admin account is created
and the all the details of the
customer can be fetched from
the information system
User Register / Login The user needs to register into
the information system for
booking their ticket for the

5
SYSTEMS ANALYSIS AND DESIGN
climbing session
Login Book Ticket The user can book a ticket
after successfully logging into
the information system
Log out Main page The user is redirected to the
home page of the information
system after clicking the
logout button.
Admin and User Generate Notification Notification is generated for
an event and sent to the user
for reminding the task.
b. The event decomposition technique is used for finding the additional use cases associated with
the development of the information system.
Event: Book a ticket
Type of Event: user for a climbing session
Trigger: Availability of the tickets
Use case name: Book climb session
Brief Description:
The user can book a ticket after registering into the information system and choose the type of
climbing wall from the walls offered by the organization. The price of the tickets and the other
information like availability can also be fetched from the information system.

6
SYSTEMS ANALYSIS AND DESIGN
Answer to Question 4: Domain Model Class Diagram
Answer to Question 5: CRUD MATRIX
Entity
Function
Book Ticket
Make Booking C
Booking Confirmation RU
Accept Cancellation D
Issue Tickets RU
Where,

7
SYSTEMS ANALYSIS AND DESIGN
C = Create
R = Read
U = Update
D = Delete
Answer to Question 6: Fully Developed Use Case Description
Use Case Name: Book a climbing session
Scenario: Book a ticket
Triggering Event: The user needs to login into the information
system
Brief Description: The user can book a ticket after registering
into the information system and choose the
type of climbing wall from the walls offered
by the organization. The price of the tickets
and the other information like availability can
also be fetched from the information system.
Actors: User and ticketing system
Stakeholders: Owner, Staffs, Service Engineer and
Customer
Preconditions: The user should have an account registered
with the information system for accessing the
resources and check the availability pf the

8
SYSTEMS ANALYSIS AND DESIGN
tickets or choosing a plan.
Post conditions: On booking of the tickets they have to pass a
health checkup and finally climb on the walls.
Flow of Activities: Actor System
1. Register into the
information system
2. To display the
service and products
offered by FS.
3. To book a ticket
for climbing session
1. The system
generates a user ID
and password and
stores in the database
of the organization.
2. The fetch data
from the database and
display it to the user
4. Check the
availability and
generate a receipt for
the user
Exception Conditions: If the user is a member the user can enter the
FS using thee pass and thus they are
exempted from ticket booking
The use of the service can be cancelled if the
health problem is found and the ticket is
cancelled

9
SYSTEMS ANALYSIS AND DESIGN
Answer to Question 7: Activity Diagram

10
SYSTEMS ANALYSIS AND DESIGN
Answer to Question 8: System Sequence Diagram

11
SYSTEMS ANALYSIS AND DESIGN
Answer to Question 9: State machine Diagram
Answer to Question 10: Create Usage report
a. First Cut Sequence Diagram
b. Design Class Diagram

12
SYSTEMS ANALYSIS AND DESIGN

13
SYSTEMS ANALYSIS AND DESIGN
Bibliography
Dennis, A., Wixom, B. H., & Tegarden, D. (2015). Systems analysis and design: An object-
oriented approach with UML. John Wiley & Sons.
Gorod, A., White, B. E., Ireland, V., Gandhi, S. J., & Sauser, B. (Eds.). (2014). Case studies in
system of systems, enterprise systems, and complex systems engineering. CRC Press.
He, Y. Y., & Dey, S. (2014). Sum rate maximization for cognitive MISO broadcast channels:
Beamforming design and large systems analysis. IEEE Transactions on Wireless
Communications, 13(5), 2383-2401.
Li, Y., Lee, P. P., & Lui, J. (2013). Stochastic modeling of large-scale solid-state storage
systems: analysis, design tradeoffs and optimization. ACM SIGMETRICS Performance
Evaluation Review, 41(1), 179-190.
Mahmoud, M. S. (2016). Networked control systems analysis and design: An overview. Arabian
Journal for Science and Engineering, 41(3), 711-758.
Rosenblatt, H. J. (2013). Systems analysis and design. Cengage Learning.
Valacich, J. S., George, J. F., & Hoffer, J. A. (2015). Essentials of systems analysis and design.
Pearson Education.
Zhang, C., Duan, Z., Yu, B., Tian, C., & Ding, M. (2016). A Test Case Generation Approach
Based on Sequence Diagram and Automata Models. Chinese Journal of Electronics,
25(2), 234-240.