Once you have a correct set of components, BPM can allow you to recompose them at will into new processes, and SOA can allow you to deploy and execute them on an enterprise (or even inter-enterprise) service bus. But, neither BPM nor SOA can, together or singly, tell you how to define the correct components you'll need at either level, much less how to synch these up. With MDA, we can paint a much clearer and more compelling picture of the BPM-to-SOA approach. We start by defining a formal BPM-based business viewpoint, a formal SOA-based services viewpoint, and a formal transformation between them. Until we can do all this, we really can’t guarantee that any particular set of business components – or any business process built from those components – can map down to SOA.
Read »MDA, SOA and BPM: The Enterprise Model-Driven Solutions Set
http://mda-soa.blogspot.com –

Category: Business Process Management Tags:
Search
Login
Who's new
- NorikoCapilla
- stephanie
- lolamiller
- benjaminhiatt
- hasenchat
Who's online
There are currently 0 users and 1 guest online.
You are logged in as
Anonymous
Categories
- All
- Business Rules in Enterprise Architecture
- Business Rules in Business Process Management
- Business Rules in Workflow Management
- Business Rules Conferences & Symposiums
- Business Process Management
- Event Driven Architecture
- Business Rules Standards
- Rule Engine
- Business Rules News
- SBVR
- Business Rules Design & Architecture
- Business Rules Design Patterns
- Business Rules General
- Business Rules Performance
- BRMS
- Business Rules Whitepapers
- Rule Markup Languages
- Model Driven Architecture & Engineering
- Business Intelligence
- Model Transformations
- Rule Based Frameworks
- Knowledge Engineering
- Semantic Web
- Business Rule Validation
- Business Rule Verification
- Business IT Gap