Comprehensive System Analysis and Design Report: Sydney Medical Centre

This report presents a comprehensive system analysis and design for Sydney Medical Centre, aiming to address the increasing work pressure through a new information system. The report details the system requirements, including functional and non-functional aspects, and justifies the selection of fact-finding methods such as questionnaires, prototyping, and interviews. The waterfall model is chosen as the development methodology. Furthermore, the report outlines the data flow and system functionalities, supported by diagrams and descriptions. Development tools like AWS Cloud9 and Microsoft Azure are also discussed. The report covers aspects of managing patient information, including registration, record management, and report generation. The non-functional requirements address security, performance, and maintainability. The fact-finding methods are analyzed for their benefits and drawbacks. The development tools and methods like waterfall model are explained. This report provides a valuable insight into the system analysis and design process for a healthcare setting, with a focus on practical implementation and considerations.

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

1SYSTEM ANALYSIS AND DESIGN
Executive Summary
The report reflects the analysis and development of a new information system at Sydney Medical
Centre. The owner of Sydney Medical Centre wants to develop a new information system to
cope with the current increase is work pressure. The information gathering is done using
questionnaire, prototyping and interview methods. The report also justifies the selection of these
methods. The waterfall model is to be selected for completing the project. The report also
reflects on the data flow of the system and system functionalities using diagrams and brief
description.

2SYSTEM ANALYSIS AND DESIGN
Table of Contents
Introduction......................................................................................................................................3
System Requirements:.....................................................................................................................3
Evaluating the functional requirements:..................................................................................3
Assessing the non-functional requirements:............................................................................4
Fact Finding Methods:.....................................................................................................................5
Prototyping..................................................................................................................................6
Questionnaires.............................................................................................................................6
Interviews....................................................................................................................................7
Development Tools and Methods:...................................................................................................8
Development Tools:.....................................................................................................................8
Development Methods:................................................................................................................9
Conclusion.....................................................................................................................................10
Modelling Exercise........................................................................................................................11
References......................................................................................................................................14

3SYSTEM ANALYSIS AND DESIGN
Introduction
The information system is developed for collecting, processing, storing and fetching data
from a secure location. Information system is accessed by various devices like mobile or PC.
Each information system has one database that stores the data and provide various data operation
opportunity to the system.
The reports consist of the system analysis and design process of Sydney Medical Centre.
The system requirement will be discussed for showing the functionalities of the system. Three
fact finding methods will be selected and brief description of each will be provided. The
development tools and methods will also be described in the report.
System Requirements:
The “Hospital Patient Information Management System” is referred to as the ‘self-
contained” framework. This concentrates on the tasks to manage various tasks in the hospital,
such as dealing with patient information. Here, the list of stakeholders has been included in the
system of patent information of the hospital.
Evaluating the functional requirements:
The main requirements of the system of a hospital management deal with computerizing
every detail about the hospital and patient.
Making registration:
 Adding patient: This new information system in the hospital has been permitting the
employees to be added up the latest patient to the present system.

4SYSTEM ANALYSIS AND DESIGN
 Assigning ID: This permits the front desk employee such that they can provide the patient
with ID and include patient record. It is used by the patents such they can use that across
the overall staying at the hospital.
Checking out:
 Deleting the records of patient ID:
o It is seen that different administrative employees within the ward have been
allowed to delete the total removal of the patient. This is done from a specific
system. This is primarily done at the checkout phase of the specific system takes
place (Groene et al. 2015).
 Inclusion to beds at the available list:
o The employees of the administration at the specific ward. This permits the putting
of beds such that they can be evacuated as the available list of the bed.
Understating the case of report generation:
 Data of the patients:
o The latest information system at the hospital can create the data about the phone
number of patients, patient names bed number and ward names. Apart from this,
the name of the doctor s also found to be assigned here.
 Availability of the bed:
o This type of information system gives rises to various kinds of reports. It must be
as per the bed availability that consists of the information required. This involves
the ward number and bed number (Celesti et al. 2016).

5SYSTEM ANALYSIS AND DESIGN
Assessing the non-functional requirements:
It is helpful to define the attributes of systems. This includes usability, scalability,
maintainability, performances, reliability and security. It is also helpful to assure the
effectiveness and usability of the total system.
Security concerns:
 Information of patient: This primarily needs to determine the individual identity with the
help of PHN.
 Making modifications: Here, the changes such as deletion of a database, insertion
requires o get synchronized and is performed by the administrator at the specific ward
(Zadeh, Haussmann and Barton 2019).
 Rights of administrations: Here, the rights of the administrations are simply seen and
changes in the latest information system.
Performance requirement:
 Response time:
o Here, the system intends to deliver the reaction. This is assuring the internal of
checking every detailed data of the patients (Villacara, Lazar and Regan 2018).
 User-interface:
o The interface of the users of the latest information system has been reacting under
the time-span of the time seconds.
Analysing the maintainability:
 Suitable data for back-up: Here, the system expects to provide every required ability or
the needed data back-up of the vital information.
Errors: Under the specific system, the users have different types of errors.

6SYSTEM ANALYSIS AND DESIGN
Fact Finding Methods:
The fact-finding can be referred to the process of collecting information and raw data
from users, business documents and many other sources regarding the current situation of the
organization and what the organization wants to achieve through the project. There are various
fact finding methods that can applied to the system analysis process such as interview,
questionnaire, prototyping, sampling of existing documentation, forms and databases, site visits,
observation of work environment and many more. The technique helps in the development and
improvement of an already existing system (Hashim et al., 2013). Three of the fact-finding
techniques that has been selected for the project are questionnaire, prototyping and interview.
Prototyping
The technique is based on sampling of the model. The model are small and it is
associated with the information system design. The development of the system is done by the
implementation of the technique at the initial stage. The main method of the technique depends
on specifying the orders to the users (Abrahamsson et al., 20017). The user requirement of the
prototyping is called as discover prototyping.
Benefits of Prototyping: With the help of the prototyping the related developers and the
users are able to check and have a clear understanding about the system before its
implementation. It helps in finding the outcomes before its final implementation so that no
money is wasted for the system. The entire technique is a type of training process. The method
consume less time. With the aid of this technique the constant requirement can be easily
obtained.
Drawbacks of Prototyping: The main requirement is the training of the people associated
with this technique who are known as developers. It is observed that sometimes the people

7SYSTEM ANALYSIS AND DESIGN
associated with the system mistakes the reliability, feature and performance of the prototype
technique as the real outcome (Khan¹, Dulloo and Verma 2014). For this purpose the users must
be well trained so that they have the knowledge that the technique depends upon the entire
system functionality and it must not be mistaken as a complete system. The cost of the
development and planning may vary in the prototyping technique.
Questionnaires
The questionnaires technique is mostly based on the gathering of the data from users. The
number of users is large and the process is generalized. The users are asked to fill up questions
that are given to them by the system analyst. The process is time saving as there is no need for
personal interviews. The answers are filled by the users and submitted to the system analyst
(Brace 2018). The questionnaires is classified into free format and fixed format questionnaires.
In the free format the users are independent to answer the questions without any time limit. The
outcomes helps in finding the feelings and experience of the user giving response to the
questions. In the fixed format the structure of the questionnaire is well defined and planned. The
respondents need to answer from the provided solution.
Benefits of Questionnaires: The method saves time and the respondent answers freely
without any fear. The method requires less expense and the users feels free to state their view as
there is no need to provide any personal data. The results are calculated at a much faster rate.
Drawbacks of Questionnaires: The response obtained sometimes are not complete. The
body postures and language of the respondents cannot be noticed by the analyst. There is no
scope for the analyst to explain themselves and it is difficult to prepare good sets of questions for
the questionnaire method.
Interviews

8SYSTEM ANALYSIS AND DESIGN
The interview is considered to the most used fact finding technique of all the mentioned
methods. The interview is done face-to-face between the participant and the interviewer. The
interviewer is generally the system analyst. The purpose of the interview is collect and rectify
facts as well as motivating the participant to provide better and insight data about working
processes, constraints and requirements. The interviewer crates a set of questions before the
interview process starts. In order to conduct the interview process, the interviewer must have
great communication skills. Only the experiences and skilled analysts are capable of connecting
an interview properly.
Structured Interviews: The structured interview is done when the analyst has predefined
set of questions to ask the interviewee.
Unstructured Interview: The questions are not defined in the unstructured interview. The
analysts starts the interview with aim of finding some fact about the system. The whole
conversation is driven the answers and intuition of the analyst.
Advantages of Interview: The interview process is used for motivating the participant
which in return provide confidence to the participant to freely answer the questions. The analyst
can collect quality feedback from the participant as there is possibility of rectifying the collected.
The cross examination allows loop holes in the provided information.
Disadvantages of Interview: The interview process is extremely time consuming. The
cost of conducting interview is also very high. The skills of the interviewer has great impact on
the outcome.
Development Tools and Methods:
Development Tools:

9SYSTEM ANALYSIS AND DESIGN
AWS cloud 9: It is a known to be cloud based IDE (integrated development environment)
which is needed for writing, debugging and overall running of code. It is mainly inclusive of
code editor, terminal and lastly debugger (Choi et al. 2018). Cloud9 comes up with pre-packed
with certain number of tools for some of well-known programming language like Python,
JavaScript and many other. User does not need to install required files or overall configuration of
development of machine. As Cloud9 is known to be cloud based so the user can easily work on
the projects right from home and any other location by the help of internet. It mainly aims to
provide seamless experience needed for developing a server less application. It mainly allows the
user to easily define all the required resources.
Microsoft Azure: Microsoft Azure can be stated as the platform of cloud services that
requires open-source and standard based technologies. It can be considered to be as one of the
best solution from Microsoft and other related organization. It is mainly hosted and managed
version of Microsoft technologies (Persico et al. 2015). The overall billing structure of Azure is
completely based on resource information and not on the reserved capacity. The overall price
tends to vary in between various kind of services and storage that are away from physical
location. Azure tends to lack any kind of upfront cost and overall delay in time in providing
resources. It mainly tends to ensure that capacity is completely available on required demand.
Development Methods:
Waterfall model: It can be considered to sequential model which defence the overall
software development in various phases. Each of the required phase is divided for performing the
activity in the whole SDLC model (Kuhrman et al., 2017). This particular model is considered to
be very much easy to use. In this model, each particular phase needs to be completed right before
the beginning of the next phase. It can be easily achieved if and only if there are no kind of

10SYSTEM ANALYSIS AND DESIGN
overlapping in each and every phase. This particular model is known to be easiest one among all
the software development. It is known to be first SDLC model can be easily widely used in the
whole domain of software for ensuring the overall success of the project. It comprises of list of
phases like collecting requirement and analysis, design of system, implementation, integration
and testing, system development and lastly maintenance.
Scrum: It is a well-known framework by which people can easily address various kind of
complex issues. It is mainly needed for production and delivery of products for its highest value.
Scrum is known to be a simple framework which is needed for effective collaboration of
complex products (Seppä 2018). Scrum methodology is very much simple in nature. Scrum
comes up with huge number of features like lightweight, simple and lastly difficult for mastering.
Scrum methodology completely depends on self-organization and cross-functional team
members.
Conclusion
From the above study it can be concluded that the system to be developed for Sydney
Medical Centre will be highly effective if all the system requirements are implemented properly.
The system needs to be developed in such way that stakeholders are part of the project all the
time. The diagrams are created very well and represents the scenario accurately. The diagrams
shows that reports will be provided to the authorized personnel.

11SYSTEM ANALYSIS AND DESIGN
Modelling Exercise
Fig 1: USE Case Diagram for SMC
(Source: Created by Author)

12SYSTEM ANALYSIS AND DESIGN
Fig 2: Context diagram for SMC information system
(Source: Created by Author)
Fig 3: level 0 DFD for SMC
(Source: Created by Author)

13SYSTEM ANALYSIS AND DESIGN
Fig 4: ERD for the new system that contains at least four entities
(Source: Created by Author)

14SYSTEM ANALYSIS AND DESIGN
References
Abrahamsson, P., Salo, O., Ronkainen, J. and Warsta, J., 2017. Agile software development
methods: Review and analysis. arXiv preprint arXiv:1709.08439.
Brace, I., 2018. Questionnaire design: How to plan, structure and write survey material for
effective market research. Kogan Page Publishers.
Celesti, A., Fazio, M., Romano, A. and Villari, M., 2016, May. A hospital cloud-based archival
information system for the efficient management of HL7 big data. In 2016 39th International
Convention on Information and Communication Technology, Electronics and Microelectronics
(MIPRO) (pp. 406-411). IEEE.
Choi, J., Lian, R., Li, Z., Canis, A. and Anderson, J., 2018, June. Accelerating Memcached on
AWS Cloud FPGAs. In Proceedings of the 9th International Symposium on Highly-Efficient
Accelerators and Reconfigurable Technologies (p. 2). ACM.
Groene, O., Arah, O.A., Klazinga, N.S., Wagner, C., Bartels, P.D., Kristensen, S., Saillour, F.,
Thompson, A., Thompson, C.A., Pfaff, H. and DerSarkissian, M., 2015. Patient experience
shows little relationship with hospital quality management strategies. PloS one, 10(7),
p.e0131805.
Hashim, N.M.Z. and Mohamed, S.N.K.S., 2013. Development of student information
system. International Journal of Science and Research (IJSR), 2(8), pp.256-260.
Khan¹, S., Dulloo, A.B. and Verma, M., 2014. Systematic review of requirement elicitation
techniques.
Kuhrmann, M., Diebold, P., Münch, J., Tell, P., Garousi, V., Felderer, M., Trektere, K.,
McCaffery, F., Linssen, O., Hanser, E. and Prause, C.R., 2017, July. Hybrid software and system

15SYSTEM ANALYSIS AND DESIGN
development in practice: waterfall, scrum, and beyond. In Proceedings of the 2017 International
Conference on Software and System Process (pp. 30-39). ACM.
Persico, V., Marchetta, P., Botta, A. and Pescapé, A., 2015, December. On network throughput
variability in microsoft azure cloud. In 2015 IEEE Global Communications Conference
(GLOBECOM) (pp. 1-6). IEEE.
Seppä, T., 2018. Transition to Agile: monitoring the transition from Waterfall to Agile Scrum at
Neste Engineering Solutions NAPCON unit.
Villacara, A.A., Lazar, E.J. and Regan, B.K., 2018. Refining the Hospital Incident Command
System to improve Hospital Command Center management of survey activity. Journal of
Emergency Management, 10(6), pp.449-458.
Zadeh, S.E., Haussmann, R. and Barton, C.D., 2019. Health care risk managers' consensus on the
management of inappropriate behaviors among hospital staff. Journal of Healthcare Risk
Management, 38(4), pp.32-42.