0% found this document useful (0 votes)
33 views

Chapter 9 System Development Life Cycle

Uploaded by

cabalidalyn08
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
33 views

Chapter 9 System Development Life Cycle

Uploaded by

cabalidalyn08
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 38

systems development life cycle:

nursing informatics and


organizational decision-making
C H A P T E R 9

GROUP 1- ORLANDO

CATUDIO , ENCILA, GUTIERREZ, KATIGBAK, LAGOS, LOPEZ, MARQUEZ, MENDIGORIN, MERCADER, NERO, ROMERA
I_f__m_t___
System
Information
System
INTRODUCTION

WHAT IS SYSTEMS DEVELOPMENT LIFE CYCLE?

The Systems Development Life Cycle (SDLC) is a way to


deliver efficient and effective information systems that fit
with a strategic business plan, which stems from the
mission of the organization.

By using SDLC in healthcare, healthcare organizations can


develop secure and effective software systems that
improve patient care and outcomes.
STAGES of system
development life cycle

PLANNING
The planning stage involves identifying the needs and requirements
of healthcare professionals and patients

ANALYSIS
The analysis stage involves analyzing the requirements identified in
the planning stage.

DESIGNING
The design stage involves designing the software system based on
the requirements specified in the planning and analysis stages.

IMPLEMENTATION
The implementation stage consists in developing the software
system based on the design created in the previous step.

MAINTENANCE/DEPLOYMENT
The maintenance stage consists in maintaining and updating the
software system after it has been released to users.
APPROACHES
TO SDLC

01 WATERFALL MODEL

RAPID PROTOTYPING OR RAPID


02
APPLICATION DEVELOPMENT (RAD)

OBJECT-ORIENTED SYSTEM
03
DEVELOPMENT (OOSD)

DYNAMIC SYSTEM DEVELPMENT


04
METHOD (DSDM)

05 AGILE METHOD
W____ f___
M___l
Waterfall
Model
APPROACHES TO THE SDLC

waterfall
model

One of the oldest methods that depicts waterfall


Waterfall Phases
of facts—the output from each previous phase
flows into or becomes the initial input for next
phase.

03
waterfall phases

Feasibility Analysis Design


Determines whether the Requirements for the system Focuses on high- and low-level
project should be initiated and are teased out design and interface and data
supported Workflows and business design
Generate a project plan and practices are examined Great care is taken during this
estimated budget Consider options for changing phase
Follows TELOS strategy the business process
> High-level phase - establish needed
programs
> Technology - technological capabilities
> Low-level phase - how will the programs
> Economic - cost-benefit analysis
work
> Legal - legal ramifications
> Interface design - what the interfaces will
> Operational - determine the effectiveness
look like
> Schedule feasibility - viability of the time
> Data design - which data are required or
frame
essential
waterfall phases

Implementation Test Maintain


Testing process includes five layers:
Waterfall model requires
Designs translated into
1. The individual programming modules completing each stage before
programming code.
2. Integration moving to the next.
C++, Pascal, and Java
3. Volume Disadvantage: difficulty in handling
4. The system as a whole changes in requirements.
5. Beta testing. Best for simple projects with stable
requirements.
Rapid
P__t_t__ i_g
Rapid
Prototyping
Build

Rapid
Analysis
Implemen
and quick Demon- Testing
-tation
design strate

prototyping Refine

A.K.A. RAPID APPLICATION DEVELOPMENT (RAD)


A rapid requirements-gathering phase relies on
Provides a fast way to add functionality through workshops and focus groups to build a prototype
prototyping and user testing application using real data. This prototype is then
Easier for users to examine an actual prototype beta tested with users, and their feedback is used to
than documentation perfect or add functionality and capabilities to the
RAD proposes that products can be developed system.
faster and of higher quality (Alexandrou) 1. Requirement Gathering & Concept Development
2. Building the Prototype
3. User Evaluation
4. Iteration
Rapid prototyping

The RAD approach uses: Major advantage of RAD Also the biggest
Informal communication The speed with which the disadvantage
Repurposes components system can be deployed (If a person is in a tight
Typically follows a fast- development schedule)
At times, the system may be
paced schedule The process may be too
deemed acceptable if it meets
Object-oriented fast for adequate testing
a predefined minimum set of
programming requirements, rather than all to be put in place and
Using languages (C++ and of the identified requirements. completed.
Java) This rapid deployment also The most dangerous lack
Promotes software limits the project's exposure to of testing is in the realm
repurposing and reuse change elements. of security.

The RAD approach is chosen because it builds systems quickly through user-driven prototyping and
adherence to quick, strict delivery milestones.
Object oriented

The object-oriented systems development (OOSD) model blends SDLC logic


with object-oriented modeling and programming power, Object-oriented
modeling represents real-world objects by modeling the real-world Sties or
things (clinic, patient, account, or nursing or healthcare professional) into
abstract computer software objects. The objects are derived from classes,
and each object comprises data and the actions that can be cracted on that
data.
Object oriented

Class hierarchy - allows objects to inherit attributes from par-int classes, which
fosters object reuse and results in less coding. Therefore, the class hierarchy must
be clearly and appropriately designed to deep the benefits of this SLC approach,

The processing begins by investige ing where object-oriented solutions can address
Business problems or needs,
Determining user requirements,
Designing the system,
Programming or modifying object modeling (class hierarchy and objects),
Implementing, testing, and modifying and reimplementing the system and ends with the
new system
The Dynamic Systems
Development Method (DSDM)

The Dynamic Systems Development Method (DSDM) is an iterative and


incremental approach to project management and software
development. It involves high levels of user input and collaboration
throughout the development process.

The DSDM consists of three main phases:


1. Preproject
2. Project life cycle
3. Postproject
PREPROJECT
PHASE

In the preproject phase, the focus is on


establishing buy-in and securing funding for the
project. This phase helps identify stakeholders
and gain their support. The project life cycle
includes feasibility and business studies,
functional model iteration, design and build
iteration, and implementation.

FIRST PHASE
PROJECT Life
Cycle

This phase includes five steps :


1. Feasibility
2. Business Studies
3. Functional Model Iteration
4. Design and Build Iteration
5. Implementation

SECOND PHASE
PROJECT Life Cycle
1 . F e a s i b i l i t y
The phase where it identifies the potential risk during the study. It covers feasibility reports, project plan and risk
log

2 . B u s i n e s s S t u d i e s
This part extended the feasibility report by examining the process and the stockholders needs . It is important to
align the stakeholders and secure in buy-in because is is necessary to o input and involvement throughout the
DSDM process.
MoSCoW - Must have ( requirement needed ) , Should have ( requirements are those that would be great to have ),
Could have (requirement that is nice to have ) and Would have ( requirements that can be put up to after )
Approach in setting priorities to meet the business needs

3 . F u n t i o n a l I t e r a t i o n M o d e l
The phase where deliverables are functional model and prototype ready for user testing,
examination of quality of products , revisions and risk logs.
PROJECT Life Cycle

4 . D e s i g n a n d B u i l d I t e r a t i o n
It integrates the functional components and the identifying the non functional requirment needed to be in tested
system

5 . I m p l e m e n t a t i o n

Deliverables are the system ready to use, documentation, and trained users. It should be satisfied along the users
need.
The first and final part of this phase consist of the full review and training of users , implementing the approved
system of the project.
POSTPROJECT
PHASE

The postproject phase involves verifying


that the system is functioning properly and
beginning the maintenance schedule.
Because DSDM is iterative, postproject
activities are ongoing, allowing for
refinements to be made to deliverables.

THIRD PHASE
Agile methodology prioritizes the
01
collaboration and effectiveness of teams over
rigid processes.

Agile development involves iterative and


02 incremental builds, typically in 2- to 4-week
intervals, fostering quick adaptability and
customer satisfaction.

Failure is viewed positively within Agile if it


03
leads to learning and progress toward goals.
The Scrum master is responsible for
07
removing barriers, fostering a positive
environment, and shielding the team from
distractions to maximize productivity.

The Scrum master guides, coaches, and


08
develops the team to produce high-quality
deliverables.
Scrum, a popular Agile framework,
04
emphasizes collaboration, team autonomy,
and flexibility to adapt to changing business
needs.
Scrum organizes developers into self-
05
managing teams, with the Scrum master
serving as a servant-leader to facilitate team
success.
Key concepts in Scrum include adaptation,
06
transparency, and inspection, ensuring
efficient product delivery.
COMPUTER AIDED SOFTWARE
ENGINEERING TOOLS
CASE - is the scientific application of a set of tools and methods
to a software system.
promotes adherence to the SDLC process by automating
several required tasks
reduce cost and development time while enriching the
quality of the product
contains repository with information about systems like
models, data definitions and references linking models
together
COMPUTER AIDED SOFTWARE
ENGINEERING TOOLS
TYPES OF TOOLS
upper-CASE , supports the analysis and design phases
lower-CASE , supports implementation

EXAMPLES OF CASE TOOLS


According to Andoh-Baidoo et al. (2009)
Visible Analyst - supports structured and object-oriented
design
Rational Rose- supports solely object-oriented design
COMPUTER AIDED SOFTWARE
ENGINEERING TOOLS
Both builds and reverses database schemas for SQL and Oracle
and supports code generation for pre-.NET versions of Visual
Basic.
VISUAL ANALYST CAN SUPPORT SHELL CODE GENERATION FOR
PRE-.NET VERSIONS OF C AND COBOL
RATIONAL ROSE CAN SUPPORT COMPLETE CODE FOR C++ AND
JAVA.

CASE have many advantages however they can be difficult to


customize and use with existing systems.
O___ S_____
S___w___
Open Source
Software
Open source software and
Free/open source software

It enables users to implement, modify, apply, reconstruct, and restructure the rich
libraries of source codes available from proven, well-tested products.

Early attempts at OSS ventures in the healthcare realm failed because of a lack of
support for sustained effort, technological lags, lack of authority and credibility and other
such issues.

North America is the home of many mature, stable and widely disseminated FLOSS
(Free/Libre Open Source Software) applications. It has the longest tradition in applying
FLOSS-HC (healthcare) delivery.
Examples of OSS and FOSS OTHER BENEFITS OF
FLOSS

LOW COST

FLEXIBILITY

OPPORTUNITIES TO INNOVATE

INDEPENDENCE FROM VENDORS


I____o____b___t_
Interoperability
INTEROPERABILITY

The ability to share information across


organizations, will remain paramount under the
HITECH Act.
Refers to the standards, protocols, technologies,
and mechanisms that allow data to flow between
diverse systems with minimal human
intervention.
It allows diverse systems to talk to each other and
share information in real time
INTEROPERABILITY
IN HEALTHCARE Health information
agencies
Laboratories

DATA
Hospitals INTEROPERABILITY State agencies
PLATFORM

Registries Practices
BENEFITS OF
INTEROPERABILITY

01 STREAMLINE DATA
MANAGEMENT

02 IMPROVE PRODUCTIVITY

55+
Our Facilities 03 PROMOTE SCALABILITY

04 REDUCED COST
Thank You

You might also like