由NordriDesign™提供
www.nordridesign.comDoan Trieu Duong
Nov 2014
Business Process &
System Integration
in a context
of legacy systems
Page 2
LOGO Agenda
1. Traditional Applications
2. Integration Strategy
3. Business Process & System Integration
4. Applying Business Process Orientation
5. BPMS in the market
6. References
Page 3
LOGO 1. Traditional Applications
� Helpful for 2 past decades
� Remaining in business and important parts of business
� Getting more pressure on business to be more agile
� Inadaptable the pace of market changes
Page 4
LOGO 2. Integration Strategy
� Traditional Integration Overview
� Connects data across applications directly.
� Same data exists in two or more siloed applications
� Traditional integration blocks
� Duplicated data in separated siloed applications.
� Multi integration technology for siloed applications.
� Traditional integration focuses on technology of integration and isolated data
flows.
Page 5
LOGO 2. Integration Strategy
� SOA
� Better model for traditional
application integration
� Provide a solution to unify
across siloed applications
� Make the integration between
siloed applications smoother
and more flexible
SOA & Slide App
Page 6
LOGO 3. Business Process & System Integration
� Stronger agility of business with process centric
A approach of integration to unify the transactions in a business service, streamline
business processes and mitigate duplicated data in order to strengthen business
agility.
� 6 focal points for applications in business nowadays
1. Business processes
2. User roles
3. Business transactions and queries
4. Capability-centric information views
5. Business control, insight, and flexibility
6. Business capability connectors
Page 7
LOGO 3. Business Process & System Integration
� Six focal point in a sample architecture diagram
Six focal points of Digital Business Design
Page 8
LOGO 3. Business Process & System Integration
� Necessary features
� SOA support
� Modularization
� Mobility
� Certain wide-supportable integration
� Collaboration
� Sociality
� Cloud-base and on-premised support
Page 9
LOGO 3. Business Process & System Integration
� Technology concerns
� Process flow decision points based on business rules or embedded
analytics
� Complex event processing that encompasses activity flowing through
digital business services
� SOA processing policies that are informed by embedded analytics
Page 10
LOGO 4. Applying Business Process Orientation
� Objectives
� Design first for business outcome
� Revenue Generation & Cost Saving.
� Business Agility & Time to Market.
� Customer Retention and Loyalty.
� Reusability
� Mitigating investment in rewriting or purchasing software.
� Leverage existing applications effectively rather than creating other
redundant applications.
� Openness of Architecture
� Ability of applications to adopt open standard and technology in a flexibility
and agility platform.
� Agility
� Scalability of technology and infrastructure
� Adoptability of technology and infrastructure
� Flexibility of technology and infrastructure
Page 11
LOGO 4. Applying Business Process Orientation
� Reusability
� Solutions for vintage and monolithic applications to achieve your
best business design
� Subsume vintage UIs
� Subsume vintage business logic
� Subsume vintage data
� Extract business events
� Continue to directly access monolithic application Uis
� Off-the-self application conversion
� Configurable, model-based processes and workflow
� Built-in digital business services
� Flexible UI tooling that supports role-based workspaces
Page 12
LOGO 4. Applying Business Process Orientation
� Conversion for Off-the-Self Applications
Off-the-shelf App
Page 13
LOGO 4. Applying Business Process Orientation
� The architecture diagram with the new integration orientation
Page 14
LOGO 4. Applying Business Process Orientation
� Openness of Architecture
� Adopting open standards and technology to reduce dependency in
vendors and provide a flexible and agility platform.
� Standardizing in-house software to adopt open standards.
Open system standards is an interface specification that describes
services provided by software. The most common one nowadays is the
SOA standard.
Page 15
LOGO
� Agility
� Building an architecture to adapt business process oriented. Which
includes separated layers, persistent layer, business logic layer, control
layer, process management layer and user interface layer.
� Deploying EBS.
� Standardizing connections.
� Modifying current in-house systems to adopt SOA standard.
� Upgrading off-the-self applications to adopt SOA standard.
� Applying a reliable business process management suite to assure
performance between layers of the architecture.
4. Applying Business Process Orientation
Page 16
LOGO 5. BPMS in the market
� BonitaSoft
� Capable to apply the architecture mentioned above
� BPM and embedded analytics
� Provides a variety of system integration
� SOA
� Rapid process building tool - GUI for process design
� Reduce coding/developing cost
� Process simulator
� Mobility, clouding support.
� Capable to work with Red Hat Jboss, Sun Glassfish, IBM WebSphere
Application Server 8, Oracle WebLogic Server 11gR1, Apache Tomcat
6/7.
Page 18
LOGO 5. BPMS in the market
� K2
� Almost capable to apply the architecture mentioned above
� Provides a variety of system integration
� SOA
� Rapid process building tool - GUI for process design
� Reduce coding/developing cost
� Process simulator
� Mobility, clouding support
� Base on MS SharePoint
Page 20
LOGO 5. BPMS in the market
� AuraPortal
� Focuses on solution for workflow application only. Can functionalize as
UI layer and workflow engine layer of the architecture mentioned above
� Provides a variety of system integration
� Rapid process building tool - GUI for process design
� Reduce coding/developing cost
� Process simulator
� Mobility, clouding support
� Base on MS SharePoint
Page 22
LOGO 5. BPMS in the market
� Activiti
� Focuses on building a core process management module
� Capable to apply the architecture mentioned above as a process
management layer.
� Have to integrate with other software to build other layers to get an
entire architecture.
� Provides a variety of system integration
� SOA
� Mobility, clouding support
� Capable to work with Red Hat Jboss, Apache Tomcat 6/7.
Page 24
LOGO 5. BPMS in the market
� JBoss JBPM
� Focus on building a core process management module. Only can take
functionalities of process management layer.
� Have to integrate with other software to build other layers to get an
entire architecture.
� Provides a variety of system integration
� SOA
� Mobility, clouding support
� Capable to work with Red Hat JBoss, Apache Tomcat 6/7.
Page 26
LOGO 5. BPMS in the market
� TIBCO
� Capability to apply the architecture mentioned above
� BPM and embedded analytics
� Provides a variety of system integration
� SOA
� Rapid process building tool - GUI for process design
� Reduce coding/developing cost
� Process simulator
� Mobility, clouding support
Page 28
LOGO 5. BPMS in the market
� IBM BPMS
� Capability to apply the architecture mentioned above
� BPM and embedded analytics
� Provides a variety of system integration
� SOA
� Rapid process building tool - GUI for process design
� Reduce coding/developing cost
� Process simulator
� Mobility, clouding support
Page 30
LOGO 6. References
- Forester reports.
- Website & other referent sources from BonitaSoft.
- Website & other referent sources from K2.
- Website & other referent sources from AuraPortal.
- IBM’s website.
- TIPCO’s website.
- Activiti’s website.