ISY00243 System Analysis and Design: You Can Fit In Requirements

This report details the system analysis and design process for You Can Fit In, a fitness center company. It covers fact-finding techniques such as questionnaires, prototyping, and site visits, outlining their advantages and disadvantages. The report includes a use case diagram illustrating user interactions with the system, a domain model representing the static structure, and a sequence diagram showing the dynamic nature of the registration process. An entity-relationship diagram (ERD) is used to model data requirements. Furthermore, the report compares different software packages, ultimately recommending PIXEL8 for its suitability. It also discusses options for new information systems, including in-house development versus outsourcing, and concludes with recommendations for the company. This student-contributed assignment is available on Desklib, where students can find similar solved assignments and resources.

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

1SYSTEM ANALYSIS AND DESIGN
Table of Contents
Introduction:....................................................................................................................................2
Add Assignment 1:..........................................................................................................................3
Fact Finding Documents:.................................................................................................................3
Use Cases:........................................................................................................................................4
Entity Relationship Diagram and Domain Model Class Diagram:.................................................7
Sequence Diagram:........................................................................................................................16
System Selection:...........................................................................................................................16
Software Package Comparison:.................................................................................................16
Options for New Information System:......................................................................................17
Conclusion:....................................................................................................................................20
Recommendations:........................................................................................................................21
Bibliography:.................................................................................................................................23

2SYSTEM ANALYSIS AND DESIGN
Introduction:
The information system development can be referred to the organization approach of
implementing a new technology in organization environment. The entire development process is
guided by the set of rules defined in the respective software development lifecycle
(Abrahamsson et al. 2017). The system analysis and design is a very important part of the system
development. These two activities can be considered as the base of system implementation. The
system analysis the process of gathering business and user requirements of the system and
evaluating those requirements to generate system requirements (Alshamrani and Bahattab 2015).
In order to gather requirements, the system analyst have to communicate with the potential end
users and organization top management. There are various ways analyst can collect user and
business requirement related data from many sources. However, applying all the methods in a
system analysis task is not possible. That is why only a few methods are selected for collecting
requirements. The system analysis phase of the project ensures that all the users and functions of
the system is taken into account before design phase starts (Fernandez-Saez et al. 2015). The
system design, on the other hand, is for visualizing the software through various diagrams like
use case, domain model, sequence and many more. The UML diagram is the most popular
among the system designers because it can represent both the structured and behavioral element
of the system (Torre et al. 2018). The data models are very essential for capturing the data
requirements. The ERD is the most common data model among all.
The report is created based on the requirements of You Can Fit In. The report present a
detailed report on the used fact-finding techniques. The description of the fact finding techniques
along with its advantages and disadvantages are provided. Use case diagram is included for
showing the interaction of the users with the system. Domain model, on the other hand, shows

3SYSTEM ANALYSIS AND DESIGN
the static structured. The Sequence diagram shows the extreme dynamic nature of a specific use
case. The data model is represented in the report through the entity relationship model.
Add Assignment 1:
Fact Finding Documents:
In order to study the system, the analyst will gather adequate amount of information of
the user and business requirements. These information are called facts. The process of collecting
the facts must be guided by several rules (Ryglicki and Hodyss 2016). Many ways are available
for collecting the facts and each of those has different rules and processes. In this report, the
description of three fact-finding methods is given. These methods are chosen such way that gaps
of each method can be filled. These methods are well configured and able to collect the facts in a
very different ways. The selected fact-finding methods are questionnaire, prototyping and site
visits.
Questionnaire: The questionnaires are one of the most used fact-finding methods. The
questionnaire is used when the number of users are large. The questionnaire allows the
organizations to collect data from numerous participants simultaneously, thus reducing the
amount of time required. All the questions in the questionnaire must be related to the proposed
system. The questionnaire can be categorized as free and fixed format question (Ryglicki and
Hart 2015). The advantage of the questionnaire is collecting data from the participant freely. It is
an inexpensive process. The time required for executing this method is small. The biggest
disadvantage is that collected forms can have inaccurate information. The analyst does not have
any control over answers.

4SYSTEM ANALYSIS AND DESIGN
Prototyping: The prototyping can be referred to as most effective fact-finding technique
for collecting proposed system’s requirement facts. The prototypes can be referred to the pre-
design of the proposed system. These prototypes are clickable and provide an idea of how the
system will work (Medina et al. 2018). The advantage of the prototype is that users of the system
can have proper idea of the system before it is complete. The disadvantage is that users are not
able to understand features and reliability.
Site Visits: The site visit is capable of collecting the business requirements more
effectively than any other fact-finding technique. This process states that the analyst will access
the organization’s information directly. An assistant, who is an existing employee of You Can Fit
In, will be assigned to analyst to help understand the business data (Ryglicki and Hart 2015). The
advantage is collecting core business related requirement with utmost quality. The disadvantage
is that analyst can misunderstand the business data can create wrong system requirements.
Questionnaire Questions: The selected participant is the member.
i. How would you like to access the system?
ii. Would you like to have your own account?
iii. Would you like to feature your image in the account?
iv. Would you like to send queries from the website?
v. Would you like to make payment from the website?
Use Cases:
The sign up and sign in the most basic functions of the system. The service booking and
payment are the most important functions of the proposed system.

5SYSTEM ANALYSIS AND DESIGN
The staff, member and management are the main roles who will interact with the system
mostly.
Figure 1: Use Case Diagram
(Source: Created by Author)
Membership: The membership is accessed by the staff and member. Staff can access the
membership of every member. However, the member can check only their membership. In order
to check the membership, the member have to login to the system first.
Sign In: The authentication policy is employed in the system through this Sign In
function. The member will sign in to the website/system to see their purchase details, invoices,
make payments or do other authorized things. To sign in to the system, the member will use the
login credentials provided to them during registration.

6SYSTEM ANALYSIS AND DESIGN
Pay: The members will access this use case. There will be a payment gateway through
which the payment will be done. The system will store the invoices. For each unpaid invoice, the
member can pay the cost through this system.
Change Member Details: After the member registers, they cannot change their details.
This implies a great way of securing data into the system. In order to change the details, they
have to contact staff of You Can Fit In. The staff will verify the reason for changing details. If
the reason is verified, the staff will update the details.
Name Check Membership
Use case id MemberStaff1
Actor Member and Staff
Stakeholder Member, Staff and You Can Fit In
Pre-conditions The member must be registered into the system and has an active
membership
Activities The member will open the website
The member will click on the membership detail button
The system check if the member is logged in
If the member is not logged in then member will login
The system will redirect the member to membership detail page
Post-conditions The membership details are shown on the screen
Alternative path In case the member cannot access their account, they can ask the staff to

7SYSTEM ANALYSIS AND DESIGN
check details on their behalf
Exception The member data is corrupted
Entity Relationship Diagram and Domain Model Class Diagram:
Figure 2: Entity Relationship Diagram
(Source: Created by Author)
Varchar (80) is the default format for all the primary keys of all the entities.

8SYSTEM ANALYSIS AND DESIGN
Member Table:
Attribute Sample Data One
memberID mem101
fullName Sam Ford
contactNumber [phone]
email [e-mail]
address 53 Bellion Drive, DUNSBOROUGH WA 6281
age 58
sex Male
weight 93
height 167
creditScore 300.00
availableCreditScore 230.00
Attribute Sample Data One
memberID mem102
fullName Brock Sutherland
contactNumber [phone]
email [e-mail]
address 70 Plug Street, OLD MILL NSW 2369
age 24

9SYSTEM ANALYSIS AND DESIGN
sex Male
weight 67
height 170
creditScore 300.00
availableCreditScore 230.00
Attribute Sample Data One
memberID mem103
fullName Joseph Shoobridge
contactNumber [phone]
email [e-mail]
address 33 Norton Street, DANGAR ISLAND NSW 2083
age 44
sex Male
weight 78
height 181
creditScore 370.00

10SYSTEM ANALYSIS AND DESIGN
availableCreditScore 30.00
Class Table:
Attribute Sample Data One
classID class101
className Yoga
timeStart 10.30
duration 120
daysOfWeek Sunday, Thrusday
cost 1300.00
Attribute Sample Data One
classID class102
className Aerobics
timeStart 13.30
duration 180
daysOfWeek Sunday, Thrusday

11SYSTEM ANALYSIS AND DESIGN
cost 2300.00
Attribute Sample Data One
classID class103
className Pilates
timeStart 17.00
duration 90
daysOfWeek Monday, Wednesday, Friday
cost 1500.00
Booking Table:
Attribute Sample Data One
admissionID ad101
memberID Mem102
classID class101
joinDate 11/12/2018
lastDate 10/02/2019