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

12SYSTEM ANALYSIS AND DESIGN
Attribute Sample Data One
admissionID ad102
memberID Mem103
classID class101
joinDate 11/11/2018
lastDate 10/01/2019
Attribute Sample Data One
admissionID ad103
memberID Mem103
classID class102
joinDate 11/09/2018
lastDate 10/11/2018
PresentInClass Table:
Attribute Sample Data One

13SYSTEM ANALYSIS AND DESIGN
attendanceID atndc101
memberID Mem103
classID class102
instructorID in101
classDate 15/09/2018
present Yes
Attribute Sample Data One
attendanceID atndc102
memberID Mem103
classID class102
instructorID in101
classDate 19/09/2018
present No
Attribute Sample Data One
attendanceID atndc103
memberID Mem103

14SYSTEM ANALYSIS AND DESIGN
classID class102
instructorID in101
classDate 23/09/2018
present Yes
Instructor Table:
Attribute Sample Data One
instructorID in101
fullName Xavier McGrath
age 56
address 57 Faunce Crescent, WARGAMBEGAL NSW 2672
salary 4000.00
Attribute Sample Data One
instructorID in102
fullName Jaxon Cole
age 48

15SYSTEM ANALYSIS AND DESIGN
address 84 Woodwark Crescent, DANBULLA QLD 4872
salary 4700.00
Attribute Sample Data One
instructorID in103
fullName Harry Strickland
age 58
address 35 South Street, ELECTRONA TAS 7054
salary 3700.00
Figure 3: Domain Model Class Diagram
(Source: Created by Author)

16SYSTEM ANALYSIS AND DESIGN
Sequence Diagram:
Figure 4: Sequence Diagram for Registration
(Source: Created by Author)
System Selection:
Software Package Comparison:
Name Deployment Company
Size
Platforms Price Reputation
PIXEL8 Cloud
development
Small and
Medium
Windows and
Unix
Low More than
sixty percent
customer
satisfaction
iStart Cloud and In- Medium and Windows, Medium More than

17SYSTEM ANALYSIS AND DESIGN
House Large Unix and
Mac
seventy
percent
customer
satisfaction
Suitability: The PIXEL8 is the information system vendor that provide organization wide
system solutions in a very low cost. The customer satisfaction is a huge factor in system
outsourcing. However, the system development is based on the conventional functions of e-
commerce system and internal operations (Web Solutions | Info Systems | Security Solutions |
Pixel8, 2019). The organization wants the system to be implemented in cloud environment and
PIXEL8 is expert in this domain. The organization provide a very good after sale service. The
cost of the project matches with the proposed cost. Therefore, the overall requirements of You
Can Fit In’s system matches with the services that PIXEL8 provides. Thus, PIXEL8’s software
package is most suitable for You Can Fit In.
Options for New Information System:
In-House System: The in-house states that every process or operations will be executed
within the organization without depending upon any third party organization. The team
responsible for maintaining the process will be hired by You Can Fit In. The system hardware
will be installed within the premise of the organization. The organization will take all the
responsibilities of system development project (Madurapperuma, Ebert and Kuruppuarachchi
2018). In case of in-house system, the upgrades are done by the organization itself. The in-house
system upgrades are very expensive. The system will not be flexible. The organization have to
use the maximum capability of the system no matter how much the pressure is. On the other

18SYSTEM ANALYSIS AND DESIGN
hand, the system will be extremely secure as it cannot be accessed from outside. The in-house
system does not provide remote access to data. In case the organization wants a system that can
be accessed from various locations, outside of organization premise, the cost will increase
significantly.
PIXEL8: The IS solution of PIXEL8 supports Enterprise Resource Planning Structure
along with the most simple user interface. The client organization needs multi-layer permission
and users. PIXEL8 also provides browser application platform. The system will be developed
and deployed by the PIXEL8 (Web Solutions | Info Systems | Security Solutions | Pixel8, 2019).
You Can Fit In will sign a Service Level Agreement with PIXEL8. In case You Can Fit In wants
to upgrade the system or scale it to adjust with the business need, PIXEL8 will be contacted and
new service level agreement will be signed.
Cloud Based System: The cloud based computer system is a part of cloud computing
application. This solution is created based on the shared servers instead of personal devices and
servers. The system will developed by the You Can Fit In and then deployed in a hosted cloud
environment. The host will allow the organization to purchase the service based on the time or
resource. In case of cloud, many organization share the same cloud environment, thus the
efficiency of collaboration increases hugely (Abbas et al. 2015). You Can Fit In can choose
software as a development as the cloud solution. The hired team will complete the project from
the beginning to the end. The Hostgator can be used for hosting the system online. This solution
will allow the organization to access the system remotely using string internet connection.

19SYSTEM ANALYSIS AND DESIGN
Feasibility Study:
The operational feasibility can be measured in terms of the service, proposed system
solution can provide You Can Fit In. It measures the satisfaction of the end users. It also counts
how many requirements, defined in the requirement evaluation phase, is satisfied by the system.
Through the proposed information system, You Can Fit In can provide many opportunities to the
members and staff.
Economic Feasibility: This feasibility study allows You Can Fit In to determine whether
the project can satisfy the investment. The cost of project is $67,600.00. The system can improve
the customer relationship and attract new potential customers. The social media marketing can
create new ways of revenue for the organization. The cost of project can be retrieved by the
system within one year. The system is a suitable solution in terms of economic feasibility.
Scheduling Feasibility: The scheduling feasibility directly determine the success of the
project. The project needs total 27 days to be completed. As the project is small and easy, which
will include only the conventional functions of a system, the system may not face any major
deadline issues. You Can Fit In can implement the system into environment within one month of
its project initiation and this makes the project suitable as per schedule.
Technical Feasibility: The system will be developed and deployed by the NetSuite
Corporation. For this reason, to build the system, You Can Fit In will not buy any hardware or
software resources.
Legal Feasibility: The proposed project does not violate any legal requirements such as
social media, data protection and zoning laws. The project will maintain the state and national

20SYSTEM ANALYSIS AND DESIGN
cyber laws for developing the system. During its lifetime, the system will process all the data and
execute its functions by following every possible laws.
Conclusion:
The above study concludes that the proposed system for You Can Fit In is capable of
managing the works of the organization. The processes will be more efficient and effective. The
system will collect data from various input nodes like staff computers, customer devices and
store those data into the database for later usage. The database is an integral part of the
information system which stores the data in structured, semi structured or unstructured database.
The fact-finding techniques has been discussed very accurately in the report. The selected fact-
finding methods fills the gaps of each other and provide a complete requirement gathering
approach. However, the system does not provide detailed information of who will conduct the
fact-finding techniques and how it will be completed. The data models and the UML diagrams
illustrates that fact-finding methods are capable of collecting all the data properly. The system
interaction requirements have been collected accurately and the developed use case is capable of
capturing all the system behavior related data. The use case is done considering the members and
the management. Along with them the staff of the organization is also considered to show how
the system will be used by the organization internally. The provided use case description is
complete and accurate. The system provides the details of the classes and relationship among
them using the domain model class diagram. The use case, domain model class and sequence
diagram perfectly captured the structural and dynamic nature of the proposed system.

21SYSTEM ANALYSIS AND DESIGN
Recommendations:
Service Level Agreement: The service level agreement or SLA agrees to the service
customer, You Can Fit In, will receive from the supplier, PIXEL8. The service level agreement
must include the details of the services to be provided by the supplier. You Can Fit In must
provide all the possible information of services. If PIXEL8 breaches the SLA because all the
information is not available, the supplier will not receive any penalty. The service level
agreement must include the conditions of service availability, specifics of the proposed services
and many more SLA elements. The client organization must ask the provider to make the SLA
statistics available in online so that You Can Fit In can check the agreements are met or not. The
metrics that must be included into the SLA are service availability, business results, security,
technique quality and defect rates. The defect rates defines the error percentage in terms of major
deliverables. Miss deadlines can also be inserted into the SLA. The SLA must include the fact
the service provider will update the security patches and install antivirus in the system.
Change Management: The implementation of a new information in You Can Fit In can
create employee issues. The existing customers will also face issues when the conventional
processes will change. The employees have to develop new skills and learn about new things.
For managing this issue, the organization can create a manual training process. This training will
allow the employees to learn about how they can perform their job on the system. During this
training period they can learn about how to cope with changed environment and job description.
The change management must be initiated at the top level of You Can Fit In. The owner of You
Can Fit In must appreciate the change, otherwise they cannot make employees believe in the
system. The project must include each type of employees in the organization so that everyone
can feel like they are part of the project.

22SYSTEM ANALYSIS AND DESIGN
Robust Solution Design: If the organization is small and implementing a very small scale
application then the install, configure and deploy can work. In order to make medium seized
information system that expands throughout the organization, the robust system solution is
essential. Most of the carelessly designed systems does not meet the business and user
requirements just because those systems are not robust.

23SYSTEM ANALYSIS AND DESIGN
Bibliography:
Abbas, A., Bilal, K., Zhang, L. and Khan, S.U., 2015. A cloud based health insurance plan
recommendation system: A user centered approach. Future Generation Computer
Systems, 43, pp.99-109.
Abrahamsson, P., Salo, O., Ronkainen, J. and Warsta, J., 2017. Agile software development
methods: Review and analysis. arXiv preprint arXiv:1709.08439.
Alshamrani, A. and Bahattab, A., 2015. A comparison between three SDLC models waterfall
model, spiral model, and Incremental/Iterative model. International Journal of Computer
Science Issues (IJCSI), 12(1), p.106.
Chong, G. and Jun, Z., 2017. Analysis and Design of Internet-based Library Management
System Based on UML. INNOVATION AND MANAGEMENT.
Fernandez-Saez, A.M., Genero, M., Chaudron, M.R., Caivano, D. and Ramos, I., 2015. Are
Forward Designed or Reverse-Engineered UML diagrams more helpful for code
maintenance?: A family of experiments. Information and Software Technology, 57,
pp.644-663.
Madurapperuma, S., Ebert, L.J. and Kuruppuarachchi, D., 2018. In-house development &
implementation of ‘corebrain’warehouse management system: a case study. In About the
2nd International Conference in Technology Management, iNCOTeM 2018 (p. 67).
Matharu, G.S., Mishra, A., Singh, H. and Upadhyay, P., 2015. Empirical study of agile software
development methodologies: A comparative analysis. ACM SIGSOFT Software
Engineering Notes, 40(1), pp.1-6.

24SYSTEM ANALYSIS AND DESIGN
Medina, A.A., Johnson, J.A., Eastman, J.D. and Cargile, P.A., 2018. Techniques for Finding
Close-in, Low-mass Planets around Evolved Intermediate-mass Stars. The Astrophysical
Journal, 867(1), p.32.
Pathan, M., Patkar, A. and Surve, S., 2016. Automatic Partial Code Generation Using Class and
Sequence Diagrams. International Journal on Recent and Innovation Trends in
Computing and Communication, 4(3), pp.365-368.
Ryglicki, D.R. and Hart, R.E., 2015. An investigation of center-finding techniques for tropical
cyclones in mesoscale models. Journal of Applied Meteorology and Climatology, 54(4),
pp.825-846.
Ryglicki, D.R. and Hodyss, D., 2016. A deeper analysis of center-finding techniques for tropical
cyclones in mesoscale models. Part I: Low-wavenumber analysis. Journal of Applied
Meteorology and Climatology, 55(3), pp.531-559.
Shin, K., Hwang, C. and Jung, H., 2017. NoSQL database design using UML conceptual data
model based on Peter Chen’s framework. International Journal of Applied Engineering
Research, 12(5), pp.632-636.
Torre, D., Labiche, Y., Genero, M., Baldassarre, M.T. and Elaasar, M., 2018. UML diagram
synthesis techniques: a systematic mapping study. In 2018 IEEE/ACM 10th International
Workshop on Modelling in Software Engineering (MiSE) (pp. 33-40). IEEE.
Wanchai, V., Patumcharoenpol, P., Nookaew, I. and Ussery, D., 2017. dBBQs: dataBase of
bacterial quality scores. BMC bioinformatics, 18(14), p.483.

25SYSTEM ANALYSIS AND DESIGN
Web Solutions | Info Systems | Security Solutions | Pixel8. 2019. Information System Package |
Pixel8 Web Solutions. [online] Available at:
https://www.pixel8websolutions.com/information-system-package/#av_section_2
[Accessed 30 Jan. 2019].
Xia, Y.W., Lv, S.D. and Liu, D.X., 2017. Research of Operation Semantic and PI
Transformation Based on UML Sequence Diagrams. Journal of Software
Engineering, 11, pp.47-53.
Zhang, F., Ma, Z.M. and Cheng, J., 2016. Enhanced entity-relationship modeling with
description logic. Knowledge-Based Systems, 93, pp.12-32.