Southern Cross University - ISY00243: System Analysis Report

This report presents a system analysis and design for the "You Can Fit In" fitness centers, addressing the limitations of their current accounting package. The report begins with an introduction to information systems and data modeling, followed by a detailed exploration of fact-finding techniques, including sampling of existing documentation, research, observation, and questionnaires. It then outlines the system's use cases, covering member registration, invoice checking, sales reporting, and payment processing, along with a comprehensive use case diagram. The core of the report includes an Entity Relationship Diagram (ERD) and a Domain Model Class Diagram to represent the system's data structure, accompanied by detailed attribute descriptions for each entity. Furthermore, the report features system sequence diagrams to illustrate the interactions within the system. A comparative analysis of software packages and options for a new information system is also provided, concluding with recommendations for system implementation. The provided solution is for the course ISY00243, Systems Analysis and Design, from Southern Cross University.

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:........................................................................................................................................6
Entity Relationship Diagram and Domain Model Class Diagram:.................................................9
Sequence Diagram:........................................................................................................................13
System Selection:...........................................................................................................................13
Software Package Comparison:.................................................................................................13
Options for New Information System:......................................................................................14
Conclusion:....................................................................................................................................15
Recommendations:........................................................................................................................16
Bibliography:.................................................................................................................................18
Appendices:...................................................................................................................................21
Appendix One: First Interview..................................................................................................21
Appendix One: First Interview..................................................................................................21

2SYSTEM ANALYSIS AND DESIGN
Introduction:
The information system can be considered as the set of several pieces of software
application that are involved in information dissemination. A typical information system is a
collection of software, hardware, computer network, human resources and more. An information
system can be of many types like management information system, transaction processing
system, knowledge management system, office automation system and many more (Laudon and
Laudon 2016). The management information system is the most powerful and most popular
among all the information systems. The management information system is a computerized data
storage system that consist of financial data of an organization and process those data to generate
information and knowledge (Schomburg et al. 2017). The data models are used in the system
design for representing the data requirements. The entity relationship model does the same along
with describing the nature of the data. Domain model class diagram describes the static structure
of the object oriented system. In order to complete the ERD and class diagram, gathering the
requirements of the system is essential (Al-Masree 2015). The fact finding methods allows the
system analysts to gather the system requirement related data.
The report is based on the case study of You Can Fit In. The organization is currently
using OnAllAccounts accounting package. This package is not able to cope with the expansion
of You Can Fit In. The fact finding techniques other than the interviews has been described. The
data models have been presented through ERD and domain model class diagram. The sequence
diagrams have been created based on the information provided in the use cases.

3SYSTEM ANALYSIS AND DESIGN
Add Assignment 1:
Fact Finding Documents:
The requirement analysis is considered to be the process of identifying investigation,
documentation and evaluation of system requirements. The requirement analysis has a part
named fact finding technique that guides the actions of the system analysts while collecting
system requirement data (Alipour et al. 2016). The fact finding can be referred to the process of
collecting information and data based on the methods that include examples of present
documents, research, questionnaire, observation, prototyping, joint requirement planning and
interviews. The system analyst can use single or a set of appropriate fact finding methods for
developing and implementing the proposed information system (Bahill and Madni 2017). After
the essential facts are being collected, applying tools for converting the facts into information in
software development life cycle is important. It is because the tools cannot be utilized accurately
and efficiently if the system related information is not extracted from the collected facts. The
fact-finding methods are applied software development life cycle’s early stages like system
analysis, designing phases along with the late phase like post implementation (Ciochina,
Paleologu and Benesty 2016). The facts of the information system can be evaluated on the basis
of three individual processes like process-function for performing the system objectives, data-
facts for generating meaningful information and interface-design for interacting with the
potential end users of system.
The fact-finding methods are of various types. Each fact-finding method has its own
features, processes and conditions. There are total seven fact-finding methods that can be used
for gathering the system requirement information (Hu et al. 2015). These techniques are Joint

4SYSTEM ANALYSIS AND DESIGN
requirements planning, Questionnaires, Sampling of existing documentation, forms and
databases, Observation of the work environment, Prototyping, Interviews and Research and Site
visits. The detailed description of the fact finding methods have been provided in the following
section.
Sampling of existing documentation, forms and databases: The Sampling of existing
documentation, forms and databases allows the system analyst to evaluate the existing
OnAllAccounts accounting package for collecting facts from the present documentation other
than the human resources. Many types of documents can be used for collecting the facts from
present documents such as the e-mails, reports, suggestion box notes and customer complaints
(Dick, Hull and Jackson 2017). The reports can contain the reviews on the area of problem along
the issues in the organization performance. The collected manual forms can also be used for
collecting the facts. Computerized forms like Google forms or spreadsheet forms can be used too
as fact finding documents. After analyzing all the documents, the system analyst will create
several diagrams like flow charts, UML models, data models and more. Based on the generated
models, the program documentation and the user training manual is done. The sampling methods
are done by the system analysts for managing the above mentioned documentations (Ciochina,
Paleologu and Benesty 2016). The sampling method can be stated as the process of collaborating
the documents that represents the samples, records and forms. The sampling method entails that
two types of sampling methods exists such as stratification and randomization. The stratification
can be stated as the systematic procedure for deducting the modification of sampling data. On the
other hand, the randomization is the procedure of choosing the sample data indiscriminately. The
analyst can have better understanding of the proposed information system of You Can Fit In as

5SYSTEM ANALYSIS AND DESIGN
the evaluation of the present documents, files and forms are associated to the present information
system.
Research and Site Visits: The fact finding method that evaluates the issues that had been
already solved through other sources like documents or human is known as the research and site
visits. In order to provide a solution to the issue of requirements, the analyst will visit another
organization that had previously dealt with the similar issues. Moreover, the analyst may also
recognize the information from the reference books, database, internet and case studies
(Englehardt and Narayanan 2016). The main advantage of research and site visits is the time
required to solve an issue. As the analyst will follow the procedure that has been established, the
time required for providing the requirements of proposed solution is significantly less. The
researches always have the detailed information regarding the current development system. The
disadvantages of research and site visits are related to the restriction to access information as
those information is of another organization. If the previous solution is not documented
accurately and properly then this method cannot be implied.
Observation of the work environment: Another important fact-finding method is the
observation of the work environment. Observation of the work environment method states that
the system analyst take part in the business and studies the documentation flow. The system
analyst will apply the present system and extensively interact with the potential end user in this
fact-finding method. In case the user point of view is the main focus of the project then
observation can be considered as the most suitable fact-finding method (Nagorny et al. 2016).
The observation method can integrate the sampling method if needed. In this technique, the
sampling method is called work sampling. Through the utilization of the observation method, the

6SYSTEM ANALYSIS AND DESIGN
system analyst can easily identify how the employees and management of You Can Fit In work
on daily basis.
Questionnaire: Another useful fact finding method is the questionnaire. This method
allows the analyst to collect data from a vast amount of users simultaneously. Each user will
have a set of questions that can differ based on the purpose they will use the system. After they
fills the answers to those questions, the participants will send the form back to analyst. The
questionnaire method is extremely time saving technique because the system analyst will not
communicate with the participants individually thus the time needed to complete questionnaire
becomes less (Hong and Chen 2019). One thing that analyst must remember is that only the
system requirement related questions should be asked. If the questions are not related to the
requirements then the whole project would fail. Questionnaires can be of two types such as free-
format questionnaire and fixed-format questionnaire.
Use Cases:
The main functions are the registration of the members, collecting payments, creating
invoices, generating reports and monitoring attendance.
The roles that will be interacting with the system are members, accounting staff,
receptionist staff, management and admin staff.

7SYSTEM ANALYSIS AND DESIGN
Figure 1: Use Case Diagram
(Source: Created by Author)
Register: A new member will register first to the system to purchase membership. The
new member will provide all the personal details to the system. The system will provide a login
id and password after registration is complete.
Check Invoice: The accounting staff will check the invoice generated by the system. The
system will create invoice based on the membership. Another invoice is created based on the
purchases of merchandise.

8SYSTEM ANALYSIS AND DESIGN
Sales Report: The sales report will include the new membership and old member renew
membership. The sales report will include the sales of the merchandise.
Make Payment: The member make payment for every purchase they make. The payment
can be done in cash or online. The website of You Can Fit In will have a payment gateway that
can accept online payment.
Name Registration
Use case id Member1
Actor(s) Member
Stakeholder(s) Member, You Can Fit In
Pre-conditions The member must not have any active membership
Activities The member will access the website
The member will click on register button
The system will redirect the customer to registration section
The member will input all the valid data
The system will verify all the entered data
If a data is not valid then system asks to re-enter the data
The customer confirm registration
The system stores the information and create a new membership
The system generate a login id and password
The system share the login credentials with the member
Post-conditions The membership of the member is activated for the time period selected
by the member
Alternative path The member can contact receptionist physically and request the

9SYSTEM ANALYSIS AND DESIGN
receptionist to generate membership
Exception The member is banned
The member has due payments
Entity Relationship Diagram and Domain Model Class Diagram:
Figure 2: Entity Relationship Diagram

10SYSTEM ANALYSIS AND DESIGN
(Source: Created by Author)
The format for all the primary keys in the tables is varchar (200).
Member
Attribute Sample Data One Sample Data Two Sample Data Three
memberID Dylan8644 Alex7489 Tyler9997
firstName Dylan Alex Tyler
middleName
lastName Goodman Stansfield Patteson
contactNum
ber
[phone] (08) 8717 7489 (03) 6275 9997
email DylanGoodman@telewor
m.us
AlexStansfield@telewor
m.us
TylerPatteson@dayrep.
com
address 84 Cedar Street,
LANNERCOST QLD
4850
20 Gadd Avenue,
BUNGAMA SA 5540
70 Jones Street,
JACKEYS MARSH
TAS 7304
age 43 34 23
sex Male Male Male
weight 87 99 78
height 178 182 170
Classes
Attribute Sample Data One Sample Data Two Sample Data Three

11SYSTEM ANALYSIS AND DESIGN
classID 101 102 101
classNam
e
Aerobics Yoga Gym
startTime 10:30 06:00 17:45
endTime 12:30 07:30 19:00
days Monday, Wednesday ,
Friday
Sunday, Thursday Everyday
Fee 750.00 500.00 1500.00
Instructor
Attribute Sample Data One Sample Data Two Sample Data Three
InstructorID 101Harry 102Ali 103Austin
class 101 101 103
fullName Harry McCrea Ali Tovell Austin Mackie
dateOfBirth March 15, 1945 May 17, 1978 April 4, 1967
address 9 Sunnyside Road,
LYRUP SA 5343
1 Cedar Street,
LUCINDA QLD 4850
11 Frouds Road,
ENSAY VIC 3895
salary 3400.00 3100.00 3500.00
Attendance
Attribute Sample Data One Sample Data Two Sample Data Three
classID 101 101 101
memberID Dylan8644 Alex7489 Dylan8644