Kent Institute: Systems Analysis and Design Report for SMC System

Verified

Added on  2022/11/15

|19
|2749
|129
Report
AI Summary
This report presents a comprehensive systems analysis and design for Sydney Medical Centre (SMC). It begins with an introduction to the healthcare industry's evolving landscape and the need for an efficient system at SMC. The report details both functional and non-functional requirements for the proposed system, encompassing modules for patients, doctors, staff, and administrators. It explores fact-finding methods like brainstorming, surveys, and prototyping, along with their pros and cons. The report also discusses system development tools, including CASE and modeling tools, and proposes development methodologies such as Agile and JAD. Furthermore, it includes essential system diagrams like use case, context, DFD, and ERD, to illustrate the system's design and structure. The analysis also reviews the relationships between different components of the system. The report concludes with a summary of the key findings and recommendations for the successful implementation of the proposed system.
tabler-icon-diamond-filled.svg

Contribute Materials

Your contribution can guide someone’s learning journey. Share your documents today.
Document Page
Running head: SYSTEMS ANALYSIS AND DESIGN FOR SMC
Systems Analysis and Design for SMC
Name of the Student
Name of the University
Authors note
tabler-icon-diamond-filled.svg

Secure Best Marks with AI Grader

Need help grading? Try our AI Grader for instant feedback on your assignments.
Document Page
1SYSTEMS ANALYSIS AND DESIGN FOR SMC
Executive Summary
The following report contributes to the discussion about the development of a
information system for Sydney Medical Centre. Different sections of this reports consist of
discussion on different methodologies and tools that can be used as well as different
functional requirements for the proposed system.
Document Page
2SYSTEMS ANALYSIS AND DESIGN FOR SMC
Table of Contents
Introduction................................................................................................................................3
System requirements for the proposed system...........................................................................3
Functional requirement..............................................................................................3
Non-functional requirement.......................................................................................5
Fact finding methods for collection of information...................................................................6
Pros and cons of three methods..................................................................................7
Systems development tools........................................................................................................9
Development methods for the system......................................................................................10
Use case diagram......................................................................................................................12
Context diagram for the system...............................................................................................13
Level 0 DFD.............................................................................................................................14
ERD for SMCs.........................................................................................................................15
Analysis of relationship............................................................................................................17
Conclusion................................................................................................................................17
References................................................................................................................................18
Document Page
3SYSTEMS ANALYSIS AND DESIGN FOR SMC
Introduction
The Health care industry is growing is rapidly changing as well as growing rapidly
throughout the world. Similarly, for Sydney Medical Centre the scenario is changing in terms
of providing health care services, management of the appointments, record keeping of the
patients. Usually all these tasks are competed in a manual way which lead to increased
complexity and lack of availability of information to different stakeholders in the complete
industry. In addition to that this manual process required involvement of specific individuals
and time consumption to maintain the non-overlapping appointments to avoid any conflicts
for a given day and availability of the doctors to get the diagnosis and results of any tests
prescribed by the doctors or physicians.
System requirements for the proposed system
As day by day the population in the region is increasing therefore the SMC (Sydney
Medical Centre) requires efficient way so that they can have enhanced access to the medical
services. Through the proposed system the users or the patients will be able to book an
appointment without being present at the clinic, users can access the system in order to
upload their medical history as well as additional medical history in advance. In this way, the
doctor or the physician will have adequate time to diagnose the scenario of the patient before
the patient is physically present at the clinic. Following are the functional and non-functional
requirement for the proposed system.
Functional requirement
As the proposed system will be used by the patients, doctors, staffs and management
of the SMC thus, for different users there will be modules that will address the different
segments of the users.
tabler-icon-diamond-filled.svg

Secure Best Marks with AI Grader

Need help grading? Try our AI Grader for instant feedback on your assignments.
Document Page
4SYSTEMS ANALYSIS AND DESIGN FOR SMC
Functional requirements for the staff module
Patients must be able to register and login to the accounts created in the
proposed system.
For a non-registered patient, there will be a guest booking option.
Patients will be able to search doctors using some criterions.
The registered patients will be able make appointment through the web based
proposed system for a doctors that has been searched by the patient using
some criterions.
View all the appointments
The patients will be able to see the results of diagnosis of the past
appointments.
Cancel booked appointments
Modify their own profile on the system.
Upload documents related to the patients’ medical history.
The staff should be able to send emails and SMS to the patients in order to
remind their appointments.
Functional requirement from the perspective of Doctors
This user also needs to be registered users and contrary to the patient users would not
have any kind of guest functionality. Furthermore, following are list of functional
requirements;
They will be able to view the list of booked appointments for a given date or
time period as per their convenience.
Send results of the diagnostic session with a patient to their accounts in the
system.
Document Page
5SYSTEMS ANALYSIS AND DESIGN FOR SMC
View the medical history (if any) uploaded by the patient.
All the details of the sessions for a specific patient in order measure the impact
of treatment throughout all their appointments.
Mark a day in the calendar as their holiday so that the system would not
allow any booking for that day.
Functional requirement from the perspective of Admin
Admin of the system should be able to schedule the vacations as well as their shihft
timing for every day.
Generate reports for their payments, appointments attended by the health service
providers.
Generation of the insurance company reports.
Non-functional requirement
As the proposed system will be used by a health care clinic which is considered as one
of the most important health service providers therefore there are certain aspects related to the
proposed system that needs to maintained. For this it is important to ensure the following
non-functional requirements;
Performance
As it is possible that in certain scenarios there is huge number of patients are trying to
book their appointments during any kind of epidemic then the proposed should be able to
maintain the workload and does not get crashed in the working hours.
Usability
The proposed system must be easy to use by all the potential users without any
technical knowledge about the system. Every proposed module as well as functions in the
Document Page
6SYSTEMS ANALYSIS AND DESIGN FOR SMC
system should be usable by the intended users. It is most important that all the function are
meaningful to the connected module inside the system.
Responsiveness
The proposed system should be capable of responding against the user requests in
very minimal time span so that the waiting time at the client/user end can be reduced and
the intended task can be completed whether the user is patient or a doctor. Therefore, for
this proposed system the responsiveness should be considered as one of the main concerns in
the implementation process.
Reliability
Proposed system must be reliable and for any query of the user the system should
generate accurate output for the user.
Security of the data
As the proposed system will be storing the personal as well as medical history of the
individual that are considered as confidential thus there needs to be security measure (such as
storing data in an encrypted way) in place to secure the confidentiality of the data.
Fact finding methods for collection of information
As there are multiple stakeholders for the proposed system, therefore it is important to
gather the requirements that needs to be included in the system as functionalities in order to
automate and ease the manual processes. For this project, following three fact finding
methodologies will be considered.
Brainstorming: This technique is one of the most popular fact finding methods in case of
the environment of the group of people as available in this scenario. This technique is used in
tabler-icon-diamond-filled.svg

Paraphrase This Document

Need a fresh take? Get an instant paraphrase of this document with our AI Paraphraser
Document Page
7SYSTEMS ANALYSIS AND DESIGN FOR SMC
the beginning of the project. Using this technique it is possible to collect and address the
requirements of multiple stakeholders initial ideas for the proposed system (Seeber et al.
2017). Everyone in the organization or group is encouraged in order to contribute their ideas
for the proposed system.
Survey questionnaire: It is the method used to extricate data from number of individuals
similar to this situation. This technique can be embraced and utilized just by an expert
investigator. The Questionnaire comprises of set of queries confined together in coherent
way. The inquiries are basic, clear and to the point (Steinke, Al-Deen and LaBrie 2018).
Prototype: A prototype for a proposed system is a partially completed application, and are
constructed from the get-go in the improvement lifecycle. They are regularly used to provide
a partially completed system to the client to look for input and have understanding that will
decide the improvement of the system meeting some of the business needs.
Pros and cons of three methods
Pros of brainstorming
Use of the brainstorming process is helpful in getting large amount of information
with in the short amount of time.
It is possible to uncover insights that may not be available with other methods.
Brainstorming technique can be motivating while working in large group of
stakeholders as well as engages the stakeholders.
Cons of brainstorming
It is important to have right format along with the good facilitator for the process so
that ideas can be documented for future use (Sittig and Singh 2015).
Document Page
8SYSTEMS ANALYSIS AND DESIGN FOR SMC
In this process it is possible to get overloaded with ideas or information’s for the
functionality of the system.
No idea in the process is rectified or elicited thus may lead to unnecessary
complication in the next stages.
Pros of Prototype
Through this technique it is possible to get in-depth, real-time user feedback for the
proposed system.
This technique is helpful to test the way potential users will use the proposed systems.
Only Works in agile environment.
Cons of Prototype
This technique is considered as expensive as well as time-consuming.
Not suitable for waterfall-based projects.
Pros of questionnaire
This technique is quick and is possible get it large number of queries and ideas from
a group.
Questions can be tailored for different stakeholders in the group of potential users to
address different objectives (Steinke, Al-Deen and LaBrie 2018).
This technique helps in saving time that are required for arranging meetings and
recording the information.
Cons of questionnaire
Document Page
9SYSTEMS ANALYSIS AND DESIGN FOR SMC
For a complex project this process can be very time-consuming in order to write a
good set of good survey questionnaire.
In of this method participation can be limited depending on the project type.
This technique is one way. Thus it is not possible to clarify any blind spot in the
received response.
Systems development tools
Two system development tools are CASE and Modelling tool.
Modelling
Modelling tool is helpful in produces a graphical depiction of an idea or procedure
that developers can break down, test, and modify. An analyst can depict and improve a data
framework by utilizing a lot of business, information, and procedure models.
A requirements model, depicts the data that a system must provide. An information
model portrays information structure and plan (Sittig and Singh 2015).
CASE tool
CASE Tools are helpful to the developers in order create and keep up data
frameworks. CASE tools give an overall structure to the system improvement and support a
wide assortment of plan techniques, including organized examination and article arranged
investigation (Freire, Oliveira and de Sousa Gomes 2018).
Since CASE apparatuses make it simpler to fabricate a data framework, they support
it profitability and improved the nature of the completed item.
Notwithstanding conventional CASE tools system designers frequently use project
management tools.
tabler-icon-diamond-filled.svg

Secure Best Marks with AI Grader

Need help grading? Try our AI Grader for instant feedback on your assignments.
Document Page
10SYSTEMS ANALYSIS AND DESIGN FOR SMC
Development methods for the system
Agile methodology
The agile methodology is one of the most suitable methodology that is helpful in
responding to the change in the requirements for the proposed information system. Using this
methodology, it is possible to handle the development in turbulent and uncertain
environments.
This software development methodology is also helpful in minimizing the risk in the
system development project by developing the proposed system in short time spans which are
denoted as iterations with the finite number of functionalities. This iteration typically had the
time from one week to four weeks.
Each iteration generates a miniature software for the project. This iteration includes
every tasks that is required for releasing a miniature with the newer functionalities. This
includes planning, analysis of the new functionalities, design phase, coding and testing of the
system as well as documentation for the partially developed system. At the end of every
iteration of agile methodology project team re-assesses project priorities for the next iteration.
JAD methodology
This methodology is helpful in faster delivery of the system with relatively low
investment compared to other methods. The complete project is divided into different smaller
segments so that the inherent risk at each phase can be reduced. In this way, the key
concentration is to fulfil all the business requirements for a proposed information system
(Sittig and Singh 2015). Active user engagement is very important in this development
technique. In this way, it is possible to rapidly change the design according to the user
requirements. Consequently, this leads to the system development with the reduced human
effort, cost as well as time.
Document Page
11SYSTEMS ANALYSIS AND DESIGN FOR SMC
Use case diagram
Document Page
12SYSTEMS ANALYSIS AND DESIGN FOR SMC
Context diagram for the system
tabler-icon-diamond-filled.svg

Paraphrase This Document

Need a fresh take? Get an instant paraphrase of this document with our AI Paraphraser
Document Page
13SYSTEMS ANALYSIS AND DESIGN FOR SMC
Level 0 DFD
Document Page
14SYSTEMS ANALYSIS AND DESIGN FOR SMC
ERD for SMCs
Document Page
15SYSTEMS ANALYSIS AND DESIGN FOR SMC
tabler-icon-diamond-filled.svg

Secure Best Marks with AI Grader

Need help grading? Try our AI Grader for instant feedback on your assignments.
Document Page
16SYSTEMS ANALYSIS AND DESIGN FOR SMC
Analysis of relationship
In the above ERD, there will be 1:M relation among the tables patient and
appointment tables as a patient can book more than one appointment for multiple sessions.
There will be 1:1 relation among the patient and doctor tables as an patient will be able to get
service from a single doctor. Similarly, for the staff and report table there will be 1:1 relation.
Conclusion
In the manual system it is difficult to get the availability of appointments/schedulers
in order to book further appointment booing for a specific doctor. The proposed system will
be very helpful in the real time availability of the information for the patients, doctors as well
as other staffs at the clinic. There are numerous development methodologies as well as tools
that can useful in the development of the project. Thus, it is important for the project team in
order to choose a suitable methodology in order to develop the system while reducing the
risk, cost and time for the project.
Document Page
17SYSTEMS ANALYSIS AND DESIGN FOR SMC
References
Abrahamsson, P., Salo, O., Ronkainen, J. and Warsta, J., 2017. Agile software development
methods: Review and analysis. arXiv preprint arXiv:1709.08439.
Bonner, N.A., Kulangara, N., Nerur, S. and Teng, J.T., 2016. An empirical investigation of
the perceived benefits of agile methodologies using an innovation-theoretical model. Journal
of Database Management (JDM), 27(3), pp.38-63.
Catarinucci, L., De Donno, D., Mainetti, L., Palano, L., Patrono, L., Stefanizzi, M.L. and
Tarricone, L., 2015. An IoT-aware architecture for smart healthcare systems. IEEE Internet
of Things Journal, 2(6), pp.515-526.
Dwivedi, Y.K., Wastell, D., Laumer, S., Henriksen, H.Z., Myers, M.D., Bunker, D., Elbanna,
A., Ravishankar, M.N. and Srivastava, S.C., 2015. Research on information systems failures
and successes: Status update and future directions. Information Systems Frontiers, 17(1),
pp.143-157.
Freire, E.S.S., Oliveira, G.C. and de Sousa Gomes, M.E., 2018, October. Analysis of Open-
Source CASE Tools for Supporting Software Modeling Process with UML. In Proceedings of
the 17th Brazilian Symposium on Software Quality (pp. 51-60). ACM.
Seeber, I., De Vreede, G.J., Maier, R. and Weber, B., 2017. Beyond brainstorming: Exploring
convergence in teams. Journal of Management Information Systems, 34(4), pp.939-969.
Sittig, D.F. and Singh, H., 2015. A new socio-technical model for studying health
information technology in complex adaptive healthcare systems. In Cognitive Informatics for
Biomedicine(pp. 59-80). Springer, Cham.
Document Page
18SYSTEMS ANALYSIS AND DESIGN FOR SMC
Steinke, G.H., Al-Deen, M.S. and LaBrie, R.C., 2018, September. Innovating Information
System Development Methodologies with Design Thinking. In Titel: Proceedings of the 5th
Conference in Innovations in IT, Volume Nr. 5. Bibliothek, Hochschule Anhalt.
Wager, K.A., Lee, F.W. and Glaser, J.P., 2017. Health care information systems: a practical
approach for health care management. John Wiley & Sons.
chevron_up_icon
1 out of 19
circle_padding
hide_on_mobile
zoom_out_icon
logo.png

Your All-in-One AI-Powered Toolkit for Academic Success.

Available 24*7 on WhatsApp / Email

[object Object]