Siklus Pengembangan

Sistem Informasi
Proses Bisnis
FAM601 Teknologi dan Layanan Informasi Kefarmasian
Semester Genap 2021/2022

S2 Ilmu Farmasi, Fakultas Farmasi

Universitas Airlangga

Ira Puspitasari, Ph.D.

Healthcare 4.0

Sumber: Aceto, G., Persico, V., & Pescapé,

A. (2020). Industry 4.0 and health:
Internet of things, big data, and cloud
computing for healthcare 4.0. Journal of
Industrial Information Integration, 18,
100129.

2
System Development Life Cycle

3
System Development Lifecycle
Source:
https://www.innovativearchitects.com/KnowledgeCenter/basic-IT-
systems/system-development-life-cycle.aspx

4
 • Identifies whether or not there is the need for a new
system to achieve a business’s strategic objectives.
• a preliminary plan (feasibility study) for a company’s
business initiative to acquire the resources to build on an
infrastructure to modify or improve a service
• Operational feasibility: how a project plan meets the
criteria specified during the system development
requirements analysis phase.
• Technical feasibility: assists companies in determining
whether technical resources are enough and whether the
technical team is capable of translating ideas into workable
SDLC: •
systems.
Schedule feasibility: determines whether or not the project
Planning can be completed within the timeframe provided.
• Economic feasibility: includes a cost/benefit analysis of the
project, which assists businesses in determining the
viability, cost, and advantages of a project before allocating
financial resources. 5
 • Analysis of problem to be solved by new system
• Defining the problem and identifying causes
• Specifying solutions
• Identifying information requirements

• Establishing information requirements

• Who needs what information, where, when, and how

• Define objectives of new/modified system

SDLC: • Detail the functions new system must perform

• Faulty requirements analysis is leading cause

Analysis and of systems failure and high systems
Requirements development cost.

6
 Business Process Analysis
Business Process
Analysis and Modeling

Problem Discovery and

Analysis
SDLC:
Analysis &
Requirements
Require- Identification

ments Requirements Analysis

and Documentation
System Requirements Analysis
7
 • Describes system specifications that will deliver
functions identified during systems analysis.
• Should address all managerial, organizational,
and technological components of system
solution.
• High-level design details include the desired
functionality of software and system modules.
• Low-level design details can include the functional
logic, interface details, dependency issues, and errors.

SDLC: System Requirements (SRS)

Design
Data design Functional User interface /
(database) design, modules, User experience
(UI/UX) 8
 • Programming: system specifications from
design stage are translated into software
program code.
• Individual developers will build their own
codebase within the development
environment, then merge it with the
collaborating teams in a common build
environment.
• Deliverables:
SDLC: • Application / information systems

Development • Data schema

• Documentation

9
 • Investigate the performance of the software
• Discover and identify potential issues to fix or
address.

System
Testing

SDLC: Integration System

User
Unit Testing Acceptance
Integration and Testing Testing
Testing

Testing Error
Functional Performance
handling
testing Testing
testing
10
SDLC:
Integration
and Testing
11
 • Process of changing from old system to new
system.
• Transferring ownership and licensing,
• Deploying and installing the product on customer
systems.

• Four main strategies

• Direct changeover
• Parallel conversion
• Gradual conversion
SDLC: • Modular prototype conversion

Implementation • Requires end-user training

• Finalization of detailed documentation

showing how system works from technical and
end-user standpoint. 12
 • System reviewed to determine if revisions needed
• May include post-implementation audit
document
• Maintenance: changes in hardware, software,
documentation, or procedures to a production system
to correct errors, meet new requirements, or improve
processing efficiency

SDLC: • 20% debugging, emergency work

• 20% changes to hardware, software, data, reporting

Operations and • 60% of work: User enhancements, improving

documentation, recoding for greater processing
Maintenance efficiency

13
Business Process

14
 • “A series of tasks or activities to achieve a given purpose or
goal, which can be completed either in sequence or in
parallel, by people or systems, either inside or outside an
organization.” [Butler Group]
• “a collection of related, structured activities or tasks that
produce a specific service or product (serve a particular goal)
for a particular customer or customers.” [Paul Harmon, 2007]

Business
Process

15
Source: https://www.allaboutrequirements.com/business-process/
 • Scope: Starting and end point for the series of steps.

• Purpose: Overall objective or reason why the process

is performed.
• Steps: Specific actions performed by team members.

• Sequence: Order in which steps are performed.

• Team members: Individuals that perform the steps.

Business • Outcome: The specific product, service or result that

comes from executing the process.
Process • Customer: Next process, requestor, or end-user of the
Characteristics outcome.

16
 • The analytical representation or put simply
an illustration of an organization’s business processes.
• Modeling processes is a critical component for
effective business process management.
• A business process model is a graphical representation
of a business process or workflow and its related sub-
processes.
Business • Events and activities that occur within a workflow
• Who owns or initiates those events and activities
Process • Decision points and the different paths workflows can take

Modeling based on their outcomes

• Devices involved in the process
• Timelines of the overall process and each step in the process

17
 • A flow chart method that models the steps of a
planned business process from end to end.
• Visually depicts a detailed sequence of business
activities and information flows needed to
Business complete a process.

Process • High level: BPMN is targeted at participants and

other stakeholders in a business process to gain
Modeling understanding through an easy-to-understand
Notation visual representation of the steps.

(BPMN) • Detailed level: it’s targeted at the people who will

implement the process, giving sufficient detail to
enable precise implementation.
18
 Events
• A trigger that starts, modifies or completes a process.

• Includes message, timer, error, compensation, signal, cancel,

escalation, link and others.
• They are shown by circles containing other symbols based on
event type.

BPMN: Activities
Flow Objects • A particular activity or task performed by a person or system.

19
 Gateways: Decision point that can adjust the path based on
conditions or events.

Exclusive Decision / Merge

• Indicates locations within a business process where the sequence
flow can take two or more alternative paths.
• Only one of the paths can be taken.

BPMN: • Depicted by a diamond shape that may contain a marker that is

shaped like an “X”.

Flow Objects Parallel Fork / Join

• Provide a mechanism to synchronize parallel flow and to create
parallel flow.
• Depicted by a diamond shape that must contain a marker that is
shaped like a plus sign.
20
BPMN: Case 1 Order Management Process

Reject order

Check stock
Send invoice
availability

Confirm order

Ship goods

21
BPMN: Case 2 Order Management Process

22
 Sequence Flow
• Shows the order of activities to be performed. It is shown as a
straight line with an arrow.

Message Flow
• Depicts messages that flow across “pools,” or organization
boundaries such as departments.

Association
BPMN: • Shown with a dotted line, it associates an artifact or text to an
Connecting event, activity or gateway.

Objects

23
 Pool: major participants in a process, a different pool may be in a
different company or department but still involved in the process.

Swimlanes: Show the activities and flow for a certain role or

participant, defining who is accountable for what parts of the process.

BPMN:
Pool and
Swimlane

24
BPMN: Case 3 Order Management Process

Customer
Place
Make
purchase
payment
order

Invoice

Order Rejection Notification Shipment notification

Purchase Order confirmation

order notification Send invoice

Confirm order
Supplier

Check stock
Ship goods
availability

Reject order

25
BPMN:
Case 4
Order Management
Process

26
 • Data object shows what data is necessary for an activity.

• Group shows a logical grouping of activities but doesn’t

change the diagram’s flow.
• Annotation provides further explanation to a part of the
diagram.

BPMN:
Artefacts

27
BPMN: Case 5
Order Management Process

Send invoice
Purchase
Order
Confirm order

Check stock Set PO to approved

Ship goods
availability
Set PO to rejected

Reject order

28