SOA and Business Process Management Byungwook Cho K. 2006-06-01
Agenda
Introduction to BPM
BPM versus BPMS
When to choose BPM
Overview of BPM system
Vision and caveat
BPM and process enabled SOA
Design implication for SOA architects
Conclusion
Introduction to BPM
Business Process Reengineering (BPR)
Emerged in the early 1990 – Michel Hammer & James Champy.
Many of projects resulted in complete failure
Resistance to change
Lack of understanding of business model and underlying process
Failure of nerve on the part of the client companies.
Business Process Management (BPM)
After 10 years from BPR.
BPR start from scratch
BPM build on and transform that which already exist [ incremental change and evolutionary optimization ]
BPM versus BPMS
BPM
ISO9000, Six sigma
BPMS
Technical platform for realizing BPM management initiatives.
not limited the automatic execution of digital process model, but “encompasses the discover, design, and deployment of business processes as well as the executive,administrative, and supervisory control over them to ensure that they remain compliant with business object”
When to choose a BPMS
Complexity and cost of BPM should be considered
When to choose? 고려사항
IT and business must work hand-in-hand
Business management in enterprise should be prepared together with IT organization to apply BPMS . [IT:BPMS, Business:6Sigma]
Utilize process template
Incremental process change from Business process template from BPM vendor can reduce risk
Match the right technology to your problem
Two key characteristic of business process is “complexity” and “frequency of change”
Adopt the development model
Overview of BPM System
Modeling language
Graphical modeling language – BPMN (Business Process Modeling Notation)
Process modeling Language
Define business process
Enable the exchange of process definitions between different vendors
BPEL4WS (Business Process Execution Language) Developed by IBM & Microsoft
BPML (Business Process Modeling Language) Developed by BPMI.org and supported by SAP,SeeBeyond,Sun etc.
BPMN
Overview of BPM System
Architecture of BPM System
Processes are modeled graphically – BPMN
Process are stored in a blocked model BPEL4WS,BPML
Processes are executed by process engine
Vision and caveat
Vision
Instead of application hard coding, BPM facilitates the modification,reconfiguration, and optimization of process definitions with graphical tools that can be used by less technology-oriented business analysis
Caveat
??
Topology of Hub&Spoke and BPM The scope of BPM is limited to a single business unit Crossing the border of the organization requires distributed process control and largely heterogeneous standards
BPM and the Process-Enabled SOA
PAST
Data & Function OOP Distributed Object
Limitation
Fine grained
Performance problem : Coarse grained (SOA) require less frequent interaction between client and server
Reuse problem : Fine grained granularity has complex dependency. It reduce reusability.
BPM and the Process-Enabled SOA
Future (SOA)
Past : Data and functionality
Future : Core business logic & Process control logic increasing agility
Core business logic
Comprise basic data access service,c o mplex caculation, and complex business rule.
0 comments
Post a comment