Systems Development Case Study – Health Care System Report

This report presents a comprehensive case study on the development of an automated patient management system for a healthcare system. It begins with a feasibility study, analyzing operational, technical, and economical aspects, and identifies the intended audience and purpose of the system. The report then explores specific requirements, including patient access to medical history and online appointment booking. It details the software architecture, outlining responsibilities and functionalities. The importance of the SDLC methodology is discussed, comparing agile and waterfall approaches and addressing problems solved by agile methods. The scope is enhanced through functional and non-functional requirements. Challenges in healthcare and the product backlog are presented. Furthermore, the report covers the use of various tools, use case diagrams, and activity diagrams. It evaluates user requirements and the role of quality assurance throughout the system development life cycle. The report concludes with a summary of findings and references.

Systems Development Case Study –
Health Care System

TABLE OF CONTENTS
INTRODUCTION...........................................................................................................................1
TASK 1............................................................................................................................................1
1. Feasibility study report including all essential components ..............................................1
Operational ............................................................................................................................2
Technical ...............................................................................................................................2
Economical.............................................................................................................................2
2. Specific perspectives related to the requirements..............................................................3
3. Software architecture for the system featuring the responsibilities....................................3
TASK 2............................................................................................................................................4
1. Importance of SDLC methodology in system development..............................................4
Need for SDLC.......................................................................................................................4
Problems that can be solved by the agile methodologies ......................................................5
2. Enhanced statement of the scope........................................................................................6
3a) Challenges for the health care.........................................................................................6
3b) Listing the product backlog..............................................................................................7
c. Sprint backlog for two items of the product backlog.........................................................7
TASK 3............................................................................................................................................7
1. Tools and their use..............................................................................................................7
2. Use case diagram for the whole scenario and activity diagrams........................................8
TASK 4..........................................................................................................................................12
1. Evaluation of the user requirement in this system development......................................12
2. Role of quality assurance in all stages of the system development..................................13
CONCLUSION..............................................................................................................................14
REFERENCES..............................................................................................................................15

INTRODUCTION
Involvement of automated management system can help in involving the improvised or
modified features to a system that has already been made. The health care system has been
facing issues because they are using an outdated system which is unable to keep records of
patients as it records a very limited amount and rest of it is being done manually. So, to avoid the
issues, local group has decided to develop an automated patient management system that can
help in recording sufficient amount of information and also keep updating the data on a regular
basis. The report is about representing a particular feasibility report for new system along with
proper architecture of same.
TASK 1
1. Feasibility study report including all essential components
A feasibility study report can be considered as a sample or document which helps in
making an assessment of all the possible solutions for various opportunities as well as for the
issues. Also, after analysing, it helps in determining the best one solution for continuing the
analysis further. As the GP group is using a system for uploading the records of the patients but
it is quite outdated and because of which, the system is not able to record the sufficient details.
Instead, it records a very minimum number of details, so the group has to manually note down all
the remaining details. So, they are focusing on the development of a new automated patient
management system in which they can involve all the necessary features such as various
integrated services, data analysis etc. There are some components of a feasibility report and the
same will be included in the feasibility report for the new database system which will be
included in the health care. A feasibility report for the same is discussed as under:
Purpose
The purpose of a database system is that the health care system and the local GP groups
are having limited access to the system as it records a very limited information and data about
the medical history of the patient. So, a database management system can stay helpful for the
healthcare management system so that they can include all the details of the patients and update
it as well every easily on a continuous basis as a database system is considered as an organised
and systematic collection of data and information.
Intended audience
1

The intended audience here can include the patients, their family members, doctors, other
practitioners, staff members and the other employees (Kushniruk and Borycki, 2015). This
audience has been selected because in a health care system, the related members will be patients,
doctors, nurses and family members only. These are the only associated members as relevant
according to the study, so this is the reason why this audience has been selected. It is because
the database system can help them all in different manners.
Feasibility considerations
Feasibility considerations are the means that needs to be considered while preparing the
feasibility study report. The essential components involve the time scale, technical factors etc.
The time scale that the health management centre has about 6 months and the budget is about
£75,000.
There are various types of feasibility criteria's such as operational, time scale, technical and
economical and these are discussed as following :
Operational
This is considered as that aspect of the feasibility criteria which helps in defining the
urgency of the issues. When the automated system will be developed in order to record all the
requirements of the GP group, it has to be used properly. Various sub factors are involved in the
same as social issues along with people oriented. Various internal issues are also included in the
same. It checks the fact that if the practices might able to support the new factors and systems or
not.
Technical
It ensures the fact that whether the feasibility of the project comes under the limit or not.
Also, it is being checked that the development of the automated system for recording all the
necessary details, it is available in the specified budget or not. The automated system considers
the input devices, output devices and the choice of the processing unit as well. In this, the choice
of the processing unit is quite dependent on the specific method of the processing that is required
in the work place. s
Economical
In case of various projects, the bottom line has been observed as the economic feasibility
only. Initially, the economic feasibility usually stays efficiently but as soon as the specifications
2

are being identified, all the benefits and costs of the new automated system are being calculated
by the specified analyst. This process is also termed as the cost benefit analysis.
Outcomes
The results or outcomes of the feasibility report can result in demonstrating an
understanding of the whole scope of knowledge about all the facts and figures of the new
database system which can further help the health care system in replacing their manual system
with the new database system by the help of which they can be able to make the whole processes
faster and also, they can be able to store the whole information regarding the medical history of
the patients. It can be considered a better option to go ahead with this project because it covers
all the important aspects and its respected factors that can actually help in further researches as
well.
2. Specific perspectives related to the requirements
The fact is clear enough that the GP group has to maintain the manual recording of the
medical history of patient just because their current system records very limited amount of data.
So, they have proposed some new requirements that they want in their new system. These
requirements are that there must be some system so that the patients can be able to see their own
medical history whenever they want to, they can book appointments according to their own wish,
alerting the staff to maintain regular check-ups, analysis of data etc. (Wilcox, Narus and
Vawdrey, 2014). In that case, they can also involve a feature of popping up a notification about
health check-ups so that even if the patient does not check the portal and database, they must be
aware of the check-up.
A list of some specific questions is being given as under :
Q1. Are there some systems the patients can use to check their own medical history?
Q2. How can they book appointments online ?
Q3. How they can alert their staff to manage regular check ups?
Q4. How can the GP group analyse the whole data?
3. Software architecture for the system featuring the responsibilities
A software architecture is considered as an appropriate process of determining an
efficient solution or a way that can be able to comply with all the basic needs and requirements
3

whether technically or regarding the processes. Along with this, it will help the health care
system in including all the necessary and important structural elements that will be helpful for
the system in recording all the details of the patient and keeps updating the system properly. The
software architecture for the system and its requirement is represented as following:
The structure represents that the automated system which is to be developed would be
able to fulfil all these requirements. It is because the company was using a system that was
outdated and wants to go for a new one so that these new features can be involved in it such as
various integrated services, data analysis and various services that can be available to the users.
TASK 2
1. Importance of SDLC methodology in system development
System development life cycle (SDLC) is considered as a conceptual model which helps
in controlling the environment of development which further helps the developers in developing
a standard quality system which can be sufficient and capable of meeting the expectations of the
patients.
4

Need for SDLC
The system development life cycle (SDLC) is considered as a very efficient application
of the development life cycle. There is a huge need of SDLC technology in various platforms
such as in information systems, systems engineering, software engineering etc. There is the
requirement of SDLC because it helps in a better planning, creation, testing and in positioning
the whole system. The software development life cycle can help the company in achieving all the
basic needs and requirements of the organisation as well as of the customers. There are some
factors as well that can be achieved by the use of software development life cycle and these can
be classified as a better analysis, designing, testing and implementation of the operations more
efficiently and appropriately. Also, it helps in managing and controlling the resources more
efficiently. Along with this, it ensures about the quality as well. So, can be considered as a better
option for the organisation.
The comparison between the traditional waterfall type and agile software development is
described as under:
Trait/Factor Agile Waterfall
Availability of the patients This method gives priority to
the availability of the
customers than considering the
other factors (Kushniruk and
Borycki, 2015).
This model requires the
involvement of patients at
some specific paths.
Scope Changes and modifications are
welcomed but can be
expensive as well. Agile
method acts more effective
before the scope is known.
Waterfall method works better
after the scope is known.
5

Groups/ Teams Smaller groups or practitioners
are preferred in the health care
system but coordination is
required.
The coordination between the
groups and other teams of the
practitioners is limited (Yen
and Bakken, 2011).
Output Agile methodology is better
and feasible as well to adopt.
Plan driven can help in
minimizing the risk factors.
Problems that can be solved by the agile methodologies
Agile methodologies are considered as a framework for the project management that can
help in managing and controlling the imperativeness of all the operations and processes going in
an organisation. It is also classified as a software development way that orients individual
focused interactions and the flexibility that is required to continue the processes that have been
stopped by some factors which act as barriers and challenges in the going path. These
methodologies have a drastic percentage of change in various environments. It helps in making a
sort of compromise where there is a case of no or some process. It is being done in order to get a
reasonable pay off.
2. Enhanced statement of the scope
There are two general ways by which the statement of the scope can be enhanced and it
involves functional and non-functional requirement documents. Functional requirement
documents (FRD) is considered as a formal statement which must be involving all the functional
requirements of an application. It is quite similar to a contract. FRD is considered as a central
document as well in case of development of a system. In a system software, where it does not
represent what the software will function is termed as the non-functional requirement documents.
Functional Requirements Non functional Requirements
 Rules of the business
 Tracking of the audit
 External interfaces
 Legal regulations
 Corrections in the transactions
 Capacity
 Reliability
 Manageability
 Data integrity
6

3a) Challenges for the health care
As the health care is not following the agile framework while implementing the system
development, it may have to face various challenges which are discussed as under:
 Identification of the epics in the beginning
 Investigating about value streams
 Execution of a planning scene for release (Wilcox, Narus and Vawdrey, 2014).
 Ensuring about the quality of the code.
3b) Listing the product backlog
Product backlogs are considers as a smaller or may be larger list of things that needs to be
included in the project. As a product owner, there are some backlogs always present in the
system development and these are discussed as under:
 Integrated services.
 Patient self-services
 Data analysis
 Exclusion of all manual processes
Backlog item Size
Integrated services 5
Patient self-services 6
Data analysis 9
Exclusion of all manual processes 7
c. Sprint backlog for two items of the product backlog
Task Monday Tuesday Wednesday Thursday Friday
Patient self-
services
4 5 7 8 3
Data analysis 2 5 7 4 9
7

This is the sample of a sprint backlog in which the two tasks, analysis of the data and
patient self-services are been taken from the product backlog.
TASK 3
1. Tools and their use
Use case diagrams
Use case diagrams are also referred as the behavioural diagrams that helps in representing
a set of use cases. In short, it represents the interaction between a user and a system ( Rajoo and
Noor, 2017). The system and the user along with the activities are represented by the specific use
cases of their own.
Activity diagrams
Activity diagrams are considered as a graphical representation of the work flow of all the
actions and activities along with the support of choice, concurrency and iteration. It helps in
representing the series of actions. Usually, they are being used in the modelling of a business
project. These are very much similar to the data flow diagrams and flow charts.
Both these diagrams can help in providing all the requirement for the software that can
accommodate all the changes that the health care and group wants to include in their new system
such as the integrated services, patient facing services, home care and data analysis etc. Both
these diagrams will help in representing various different aspects of the new updated system such
as the actors which can be considered as the local group or the authorities of the health care,
interface between them, package and the system boundary which means including all the
requirements that the local GP group wants to include in the new system. At the time of
representing all the requirements that the local groups wants to involve in their new system, at
that stage, utilizing these diagrams would help the whole process.
2. Use case diagram for the whole scenario and activity diagrams
The use case diagram for the new system that can involve all the necessary features such
as the integrated services, data analysis and which can also help in excluding all the manual
process of the health care (Wandersman, Chien and Katz, 2012). So, the use case diagram for
the same is represented as following:
8

9
Illustration 1: Use case diagram for automated patient system

The activity diagrams for the same are represented as under:
10
Illustration 2: Activity diagram for automated patient system