System Analysis and Design Report: Swinburne Guru Consulting INF60010

This report provides a detailed analysis of the current system of Swinburne Guru Consulting, a small business operating in Hawthorn. It begins with an executive summary and introduction, outlining the need for an information system to address the challenges of manual data management. The report covers the company's background, the scope of the project, and both functional and non-functional requirements. It then delves into the use case identification techniques, including interviews and questionnaires, and provides comprehensive documentation, including a data dictionary, data flow descriptions, and data element descriptions. The core of the report includes process descriptions at both high and low levels, an event table, DFD fragments, context and level 0/1 DFDs, and an ER diagram. The analysis highlights the current system's flaws and proposes improvements through the implementation of an information system to enhance business efficiency and client satisfaction. The report concludes with a bibliography of cited sources.

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

1
SYSTEM ANALYSIS AND DESIGN
Executive Summary
The report provides the details of the current system of the Swinburne Guru consultation
organization. The development of the information system and the need for the development of
the system is described in this report. The analysis reveals the current manual process in the
system and hence, the identification of the flaws in the current system of the organization is
easily discoverable with this report. The report along with the description of the processes
currently followed in the organization also provides some illustrations that would help them in
the identification of the procedures and the flows in the business procedures of the organization.

2
SYSTEM ANALYSIS AND DESIGN
Table of Contents
Introduction......................................................................................................................................4
Company/Organization Background...............................................................................................4
Scope of the Current System...........................................................................................................5
Functional Requirements.............................................................................................................5
Non-Functional Requirements.....................................................................................................6
Use case identification techniques...............................................................................................7
Documentation.................................................................................................................................7
Data Dictionary............................................................................................................................7
Data Flow Descriptions...........................................................................................................7
Data Element Description........................................................................................................9
Process Description...................................................................................................................11
High level processes (plain English).....................................................................................11
Low level process (Structured English).................................................................................12
Event table.............................................................................................................................12
DFD Fragments.....................................................................................................................15
Context Diagram....................................................................................................................16
Level 0 DFD..........................................................................................................................17
Level 1 DFD..........................................................................................................................18
ER Diagram...........................................................................................................................19

3
SYSTEM ANALYSIS AND DESIGN
Bibliography..................................................................................................................................20

4
SYSTEM ANALYSIS AND DESIGN
Introduction
In this new era of technology, functional and operational activities are referred to as very
essential activities those collectively helps any business organization to gain commercial revenue
and competitive advantages as well. This report depicts the details operational procedures of
Swinburne Guru Consulting. It has been found that, traditional or manual data management
approach was constantly interrupting the success line of Swinburne Guru Consulting.
In order to resolve theses operational challenges the company is focused on implementing
an Information System. The details descriptions of the Information System (IS) along with its
functional and non functional requirements are elaborated in this report. The background of the
company, scope of the project, functional requirements, non-functional and details description
are also elaborated in this report. Information storing and information accessing both will
become much easier with te implementation of the Information System (IS).
Company/Organization Background
The nominate business organization Swinburne Guru Consulting operates small
businesses in the Hawthorn city. In the month of January, 2012 this organization was established
and all its operations are done from the office itself and office itself is located in the Hawthorn
city. The name of the owner of this company is Emily Soda Pop and the collaborative
operational activities are performed by the owners and the other four employees associated to the
company. The coaches of the company act as the sub contractors during the project progress
period. Emily soda Pop runs the home based business and the work is delivered successfully by
taking support from the recommendation agencies and all other company associates.

5
SYSTEM ANALYSIS AND DESIGN
Scope of the Current System
The scope of the project is to improve its business effectiveness and efficiency as well.
The issues of overrunning cost and time consumption will be reduced if this innovation
successfully implemented in the business organization. The company would be able to offer
coaching to their clients regardless of time and location. The clients will be able to ask for
personal tutors to learn any organization even beyond the learning context. The independent
coaching platform will also allows all the clients to interact with each other any time from any
location. They can even ask for their queries any time. The scope of the project is to build an
online coaching class whereas per desires the clients would be able to take tuition. The online
class also recruits coach for individual subjects based on their skills and knowledge.
Functional Requirements
The functional requirements are referred to as the features possessed by the information
System itself. In order to accomplish the IS implementation project firstly the functional
requirements for the project are needed to be identified at the very initial phase. The users would
be able to access the information system with accurate registration (in terms of login and
password). No unauthorized users will be capable of access the information stored in the server.
In case of need for new coach recruitment the company also gives advertisements. In order to
keep the system associates alert regarding the functional and operational activities the system
also offers verifiers. The other functions that are offering by the system include proper request
for required course, it allows proper coach to proper subject. As soon as the course gets
completed the clients are allowed to give feedback regarding the process. Positive feedback will

6
SYSTEM ANALYSIS AND DESIGN
attract more numbers of clients to their system o the other hand, negative feedback will ensure
that further change management approaches are being implemented in the Information system
(IS). In other words, for further clarification invoice system can be used by the clients.
Non-Functional Requirements
The non-functional requirements identified for the system are confidentiality, integrity,
reliability, scalability, security, accessibility, maintainability and availability. In order to
understand the behavior of the possessed system each of these requirements are very essential.
Confidentiality: The personal and financial information about the clients and the learners are
needed to keep secured from the external unwanted users. Encryption is the best suited
mechanism used to maintain the information confidentiality.
Availability: The time up to which system would be available to the clients is referred to as the
system availability. The system offers anytime services to their client which implies that clients
can ask for their course booking and tutor any time with the help of this newly developed system.
Security: Encryption, application firewall, DMZ are best suited application can be used by the
system developer to keep the operational activities secured from external users and hackers.
Usability: The system is required to be completely user friendly to allow all the clients easy
handling capabilities. The interface designed for the system needs to attractive and easy
operating.
Scalability: The system is also needed to scalable which detects the system functionalities are
meeting all the clients expectation and requirements.

7
SYSTEM ANALYSIS AND DESIGN
Use case identification techniques
In order to collect all needful information use case techniques are used by the system
developers. Similarly for this project also the use case model is used by the developers to gather
information. In order to understand the operational and functional activities the Swinburbe Guru
Consulting the interview is very essential. Either with the help of questionnaires or interview
data can be eventually gathered and applied as well. Thus, it can be said that it offers better
managing capabilities to the working employees.
Questionnaire: The two different types of questionnaire offered to gather information are fre
format and fixed format
Observation: The observation technique for the system include system analyst to ensure that the
system is performing all professionally and as pr the clients demand.
Interview: The interview process will help the developers to gather information from the
nominated interview participants.
Documentation
Data Dictionary
Data Flow Descriptions
Data dictionary of the Clients
Name of the data structure/ element Clients
Alias: None
How/where used: As an entity

8
SYSTEM ANALYSIS AND DESIGN
Description: clientID = int
username = String
password = String
phoneNumber = int
Source: Phone call
Destination: Tutor request page
Data dictionary of the Coaches
Name of the data structure/ element Coaches
Alias: Tutor
How/where used: As an entity
Description: tutorID = int
username = String
password = String
tutorSpecialization = courseID
Source: Login
Destination: Assignment Page
Data dictionary of the payments
Name of the data structure/ element Payment
Alias: None
How/where used: As a process
Description: paymentID = invoiceID

9
SYSTEM ANALYSIS AND DESIGN
paymentDate = DATE
Amount = currency
Source: Clients
Destination: Accounts
Data Element Description
Clients
Attributes Datatype Size Key
clientID Int Primary key
fullName Varchar 100
Username Varchar 50
Password Varchar 50
Address Varchar 100
phoneNumber Int
Coaches
Attributes Datatype Size Key
coached Int Primary key
coachName Varchar 100
Email Varchar 100
Address Varchar 40
Contact Int
CourseID Int Foreign Key

10
SYSTEM ANALYSIS AND DESIGN
Courses
Attributes Datatype Size Key
coursed Int Primary key
courseName Varchar 100
Description Varchar 100
Staffs
Attributes Datatype Size Key
Staffed Int Primary key
staffName Varchar 100
phoneNumber int
Salary Int
Assignments
Attributes Datatype Size Key
assignmentID Int Primary key
clientID Int Foreign key
coursed Int Foreign key
Staffed Int Foreign key
coached Int Foreign key
Schedule DATE/TIME

11
SYSTEM ANALYSIS AND DESIGN
Payment
Attributes Datatype Size Key
payID Int Primary key
invoiceID Int Foreign key
Fee Number
Invoice
Attributes Datatype Size Key
invoiceID Int Primary key
assignmentID Int Foreign key
Amount Number
Process Description
High level processes (plain English)
The high-level processes that are to be considered for the current system are described
below:
 Coach request: The clients would be able to log in to the system and request for the tutors
for their assignments. The request is submitted in the system manually after a phone call
to the organization.

12
SYSTEM ANALYSIS AND DESIGN
 Assign coach: The staffs in the organization receives a request for the assignment from
the client and then the staffs searching for the coaches currently available. After the staffs
find a coach, he assigns the coach for the assignment.
 Store assignments: After a coach is assigned for an assignment, the client is called and
confirmed about the assignment. The staffs then records the data of the client and the
coaches in the system and stores the details of the assignments in their data recording
systems.
Low level process (Structured English)
The payment process has been described here in this report:
If (paymentDate< Assignment date)
AssignmentID = True
Else
AssignmentID = False
Event table
Event Event
Type
Trigger Source Activity/Use
Case
System
Response/
Output
Destination
Coach
request
External
event
Phone call client Coach
Request
The call is being
handled by the
receptionist
Receptionist
Assignment
creation
Internal
event
The details
of the
Receptionist Create The system
stores that data
System

13
SYSTEM ANALYSIS AND DESIGN
customers
are recorded
into the
system
assignment of the
assignment in
the data store
Submit
request
External
event
Checking
client
records
Receptionist Submit
request
Checks the
client history
with the name of
the client and
updates if the
client has called
in before or adds
a new client.
Coaching
specialist
Cancel
assignment
External
Event
2 weeks
after the
completion
of the coach
searching
process
Coaching
Specialist
Cancel
assignment
Generate a client
notification.
client
Assignment
confirmation
External
Event
Call coach Verifier Confirm
assignment
A notification is
sent to the coach
informing them
about the
upcoming
assignment
coach
Notifying the
client
External
Event
Assignment
Complete
Client
relations
Client follow Checking with
the client if the
client

14
SYSTEM ANALYSIS AND DESIGN
officer up client wants to
go through the
process or not.
Invoice
sending
process
External
Event
Assignment
complete
Book keeper invoice Invoice
calculation
client
Payment
process
External
Events
Receiving
invoice
clients payment The payment is
accepted by the
system
Accounts

15
SYSTEM ANALYSIS AND DESIGN
DFD Fragments

16
SYSTEM ANALYSIS AND DESIGN
Context Diagram

17
SYSTEM ANALYSIS AND DESIGN
Level 0 DFD

18
SYSTEM ANALYSIS AND DESIGN
Level 1 DFD

19
SYSTEM ANALYSIS AND DESIGN
ER Diagram

20
SYSTEM ANALYSIS AND DESIGN
Bibliography
Balanis, C.A., 2016. Antenna theory: analysis and design. John wiley & sons.
Dennis, A. and Wixom, B.H., 2018. Systems analysis and design. Wiley.
Gupta, A.K., 2017. Response spectrum method in seismic analysis and design of structures.
Routledge.
Li, C., Gao, J., Yi, J. and Zhang, G., 2018. Analysis and design of functionally weighted single-
input-rule-modules connected fuzzy inference systems. IEEE Transactions on Fuzzy Systems,
26(1), pp.56-71.
Montgomery, D.C., 2017. Design and analysis of experiments. John wiley & sons.
Oinas-Kukkonen, H. and Harjumaa, M., 2018. Persuasive systems design: key issues, process
model and system features. In Routledge Handbook of Policy Design (pp. 105-123). Routledge.