Pemodelan Proses Bisnis
K Candra Brata
[email protected]
Business Process
Management Architectures
Workflow Management
Architectures
Build Time &
Run Time
During the build time of a workflow, a workflow model
is specified completely, typically using a graphical
workflow modelling tool.
Workflow models are the blueprint for implemented
business processes in workflow management systems.
Workflow models need to be in line with business process
models that capture the operational business processes
Build Time &
Run Time
Build Time VS Run Time Workflow
Workflow Management
System Architecture
• Workflow management systems architectures organize the subsystems that
are involved in the design and enactment of both system workflows and
human interaction workflows.
• The architecture contains the following subsystems and roles, whose
responsibilities are described as follows:
– The Workflow Modelling provides means to model the technical aspects of
implemented business processes. For each activity in the operational business
process model realized by software, a detailed specification of the execution
environment of the software needs to be provided.
– The workflow models are stored in a Workflow Model Repository. This repository
contains the set of workflow models of the company and is therefore an important
asset.
– The Workflow Engine is responsible for enacting workflow processes. If an event
occurs during the daily business of the company for which a workflow model is
defined, the workflow engine creates a new workflow instance based on the defined
workflow model.
Workflow Management
System Architecture
Workflow Management
System Architecture
• If a system workflow is created, the workflow engine uses the workflow
model to call the invoked applications defined for the system workflow.
The workflow engine is also responsible for transferring data between
calls to different applications.
• Since human interactions are not available in system workflows, the
workflow engine can be regarded as an interpreter of workflow models.
• In the case of human interaction workflows, the workflow instance
contains both automatically invoked applications and human
interactions. These human interactions are performed using the
Graphical User Interface.
WfMC Reference
Architecture
• To provide a common view on workflow management systems
architectures, the Workflow Management Coalition—an interest group
in which vendors and users of workflow management systems are
organized—developed the WfMC Workflow Reference Architecture.
WfMC Reference
Architecture
Workflow reference architecture, proposed by the Workflow Management Coalition
WfMC Reference
Architecture
• The workflow enactment service—the WfMC term for workflow
engine—is the central component of the architecture. Interfaces
describe how the other subsystems connect to the workflow enactment
service.
• Process definition tools are used for workflow modelling; they are
attached to the central component by Interface 1.
• Interface 1 is specified in the XML language XML Process Definition
Language, or XPDL
• The XPDL package metamodel can be used to represent business
process diagrams expressed in the BPMN.
• The metamodel includes classes for pools, lanes, processes, participants,
and message flow.
WfMC Reference
Architecture
• During the enactment of human interaction workflows, the persons
involved receive work items that inform them about activities due for
execution.
• This functionality is realized by workflow client applications, attached to
the enactment service by Interface 2. The goal of standardizing Interface
2 is to allow workflow client applications of different vendors to talk to a
given workflow enactment service.
• Interface 3 provides the technical information to invoke applications
that realize specific workflow activities.
• Interface 4 is used for interoperability between different workflow
enactment services.
• The administration and the monitoring of workflows are handled by a
dedicated component, accessed by Interface 5.
Flexible Workflow Management
Flexible Workflow
Management
• traditional workflow management systems are based on a separation of
build time and run time of a workflow, so that after process instances
have started, there is no well-specified link to the process model.
– This approach is well suited to supporting business processes with static
control structures, i.e., processes that are modelled once and that are
executed in a routine fashion.
• In business process scenarios in highly dynamic environments,
however, it turns out that while some business processes have a static
structure, others do not. The need to respond to new market
requirements, not anticipated during build time, leads to new
requirements regarding the flexibility of workflow management
systems.
Conceptual
Design
• Object modelling techniques are used to develop a metamodel, in
which relevant entities are represented by objects in the software
system, encapsulat- ing their structure and behaviour.
• Workflow model objects, workflow instance objects, and objects
describing the organizational and technical execution environments of
workflows are at the centre of attention..
Conceptual
Design
Conceptual
Design
• The workflow class is the central class; it contains workflow objects that
are either workflow models or workflow instances, represented by the
recursive InstanceOf relationship relating workflow objects.
• The hierarchical structure of workflows is modelled by the Nesting
relationship class, which defines a relationship between a complex
workflow and a workflow, which can be complex or atomic.
• Workflow models and workflow instances are identified by different
states of workflow objects.
Dynamic Adaptations
by Example
• Workflow models are formal representations of
the automated parts of business processes that
are designed to meet the business goals.
– A workflow instance is therefore correct if it
satisfies the constraints imposed by the workflow
model.
Dynamic Adaptations
by Example
Dynamic Adaptations
by Example
A workflow instance i is adaptable to a workflow model s’ if and
only if there is a continuation of i such that i complies with s’.
Dynamic Adaptations
by Example
Web Services
Technology
• Web services are self-contained, self-describing,
modular applications that can be published, located,
and invoked across the Web.
• Web services perform functions, which can be
anything from simple requests to complicated
business processes.
• Once a Web service is deployed, other applications
(and other Web services) can discover and invoke the
deployed service.
Web Services
Technology
Web Services
Technology
Web Services
Technology
• Simple Object Access Protocol (SOAP) defines an XML messaging
protocol for communicating services. SOAP takes advantage of
standards to translate a SOAP message to an actual service invocation
and to translate the return values of a service invocation back to a
SOAP message.
• Web Services Description Language (WSDL) introduces a format to
specify Web services. WSDL serves the same purpose as interface
definition languages in standard middleware environments. However,
WSDL features a set of extensions to account for the missing
centralized knowledge on transport and addressing, such as service
endpoints, required to invoke Web services.
• Universal Description, Discovery, and Integration (UDDI) provides an
infrastructure to publish information about services and their
providers. The UDDI application programming interface provides
access information to the registry, for instance, to register a service or
to search for appropriate services or service providers.
Web Services
Technology
Web Services
Technology
• The provider of a Web service is responsible for preparing the WSDL file
of the service. In order to invoke a Web service, service requestors need
access to the WSDL specification, typically by using a service registry.
• The service requestor creates a SOAP message, using the information in
the logical contract of the WSDL specification. The information in the
physical contract is used to determine the appropriate message
encoding and the transport protocol.
• The message is sent to the service endpoint, which is specified in the
physical contract of the WSDL file. The service provider receives the
message and invokes the software that implements the service. If a
response message is defined for the invoked Web service, a SOAP
message holding the return values is sent to the service requestor,
completing the Web service execution.
Web Services
Composition
• Service compositions describe how a set of individual services are
related to each other, i.e., they describe process structures. As a
result, a service composition contains a set of services, each of
which realizes a process activity.
• Web services composition is a concrete realization of
workflow concept.
• Service composition is a recursive concept: each service
composition can be specified as a Web service, using the Web
Services Description Language
Web Services
Composition
• The standard in Web services composition is the Business Process
Execution Language for Web Services, WS-BPEL, or BPEL. It is the
outcome of a merger of the Web Services Flow Language by IBM
and XLANG by Microsoft.
• Web Services Flow Language can be considered an XML
serialization of Flow Definition Language, the script language that
was used in IBM’s work- flow product, enhanced by concepts to
access Web services
Web Services
Composition
• Data dependencies are specified by data flow between
activities. Process behaviour is specified by transition
conditions attached to control flow links.
• XLANG is a block structured language that was used in
BizTalk, Microsoft’s enterprise application integration
software, focusing on the integration of heterogeneous
back-end systems using processes
Web Services
Composition
• BPEL can be used to characterize both abstract
processes and concrete processes.
– Abstract processes describe the externally visible
behaviour of a business process. They mainly serve
communication purposes, so operational details are
disregarded.
– Concrete processes contain information required to
execute the Web services of the service composition.
The following types of
activities are available in
BPEL.
Invoke: Invoke an operation offered by a Web service; this invocation
may or may not have a response
Receive: Wait for a message to arrive
Reply: Send a reply in response to a receive message
Wait: Wait for a specified time period
Assign: Assign data values, for instance, from received messages to
process variables
Throw: Indicate that an error has occurred; used for exception handling
Terminate: Complete the process
Activities in BPEL can be
related to each other using the
following control flow
structures.
Sequence: Define a block consisting of an ordered
sequence of activities
Switch: Based on an expression, select a particular
activity from a set of possible alternatives
Pick: Wait for a suitable message to arrive or for a time-
out event. On receipt of the message (or the time-out
event), start a defined activity
While: Execute a set of activities as long as a condition
is evaluated to true
Flow: Concurrently execute a set of activities
Link : Execution constraint between activities
Sample Case
Behavioral Compatibility
• The sample service composition is activated once a purchase
order is received. the initial price is calculated, production
scheduling is started, and a shipper is selected that will be
used to ship the ordered products to the customer.
• the complete price calculation can only be done after the
shipper has been determined.
• Once the shipper has been determined, the logistics can be
arranged. The arrangement of the logistics has implications on
the production scheduling, so that the final production
scheduling can only be done once the logistics has been
arranged.
BPEL
Explanation
• The process consists of a sequence consisting of three blocks,
two of which are process activities (Receive Purchase Order and
Invoice Processing) and one of which is a flow block with an
internal structure. The flow consists of sequences, each of
which hosts two activities.
• directed arrows are drawn between activities: from the Decide
on Shipper activity to the Complete Price Calculation activity
and from the Arrange Logistics activity to the Complete
Production Scheduling activity.
• the business logic can be represented: be- cause shippers
provide shipping services at different costs, the complete price
calculation can only be done when the shipper is determined,
and production scheduling can only be started when the
logistics have been arranged.
a high-level view on the
purchase order Web
services composition
Explanation
• The purchase order process is invoked by receiving a
purchase order message sent by a business partner,
identified by the term purchasing.
• The purchase order process uses three Web services:
invoicing, shipping, and scheduling.
Service Composition in
Enterprise Application
Integration
Explanation
• The Analyze Order Service uses these services to realize a
composed service. The term composed service refers to a
service that is realized by a service composition.
• The Analyze Order Service not only uses Web services provided
by the enterprise application integration middleware, but also a
Web service S3 that is directly available from the Order 324
system.
• The composed Analyze Order Service can be realized in
different ways. Either a traditional programming language like
Java or C# can be used to realize the application logic, or a
service composition language can be employed.
Service Composition in
Enterprise Application
Integration
Explanation
• There are Web services S1, S2, and S3 available whose WSDL specifications
are stored in a registry. The designer of the composed service uses a BPEL
editor to assemble Web services
• (1) the BPEL editor retrieves this information from the registry. Once the
designer has finalized the service composition, the resulting BPEL file is
generated
• (2a) The composed service can now be made available by storing in the
registry the respective WSDL file that describes how this new service can be
used (2b).
• When the composed service is executed, a BPEL engine reads the respective
BPEL specification (3).
• During the enactment of the composed service, the services are invoked in
sequence, as specified in the sample BPEL excerpt, as indicated by messages
4a through 6b.
Thanks..
We are
moving..
http://j.gs/18164083/ppb
Evaluation:
Process Mining
Info PROJECT AKHIR Business Activity Monitoring
M. Weske: Business Process Management,
© Springer-Verlag Berlin Heidelberg 2007
Evaluation
Tugas kelompok. Enactment:
Operation Enactment
Administration
and Design &
Design:
Business Process
Identification and
Modeling
Monitoring Stakeholders Analysis
Maintenance Analysis:
Validation
Simulation
Configuration Verification
Kelompok terdiri dari 4 orang.
Configuration:
System Selection
Analisis sebuah perusahaan,
Implementation
Test and Deployment
Fig 1.5. Business process lifecycle
syarat min punya CV.
Amati proses bisnis yang terjadi.
Buat Pemodelan terkait sebuah proses
utama. (as-is)
Re-engnineering Proses yang ada jika
menurut kalian kurang efisien. (to-be)
Lakukan simulasi dan analisis hasilnya.
