ad010236 1 - PowerPoint PPT Presentation
1 / 17
Title: ad010236 1
1
UML Profile for EDOCDSTC and IBM Revised
Submission(ad/01-01-01)
- Keith Duddy
- dud_at_dstc.edu.au
2
Presentation Overview
- Overview of this Submission
- Motivating Example
- Business Process
- Business Events
- Non-Normative Mapping
- Key Benefits of our Submission
3
Overview of this Submission
- Covers EDOC RFP-1 requirements
- Modeling of Business Processes, Entity, Rule and
Event Objects - Proof of Concept of Mapping
- MOF Alignment
- Does not directly cover
- Component Modeling
- Specification of Relationships
4
Procurement Example
5
Business Process Model
- Provides the ability to express
- Complex dependencies between activities, pre- and
post-conditions all in a single diagramming
notation - Ability to express and relate detail at different
levels of abstraction - Associations between business tasks and business
roles - Support for unexpected occurrences exceptions
- Initiation of tasks in response to business
events - Exposure of actions as business events
- Various time expressions eg. duration and
deadlines - Representation of iteration in business tasks
6
Business Process Model - detail
- Compound Tasks contain
- Input Output Groups
- Activities
- Flows
- BPRoles
- Activities are
- performed by BPRoles
- OR
- defined by other Compound Tasks
- Flows connect
- Inputs and Outputs
7
Activities
- Activity - models a specific piece of work
- Input Groups (sync or async) with typed Inputs
- Output Groups (sync or async) with typed Outputs
- Exception Output Groups
Activity Name
Data Map
Evaluate
Input
Output
Synch Input Group
Output Group
Exception Output Group
Asynch Input Group
8
Compound Task
- Contains
- DataGroups with DataElements (Input Groups and
Output Groups) - Activities
- Data Flows connecting the CompoundTask Data Elts
Activity Data Elts - BPRoles
- Unit of reusability
- Termination well defined
- in terms of its contained Activities
- Unconstrained concurrency
DataFlow
CompoundTask
TaskA
ControlPoint (degenerate DataElement)
9
Business Process Roles
- BPRole defines a placeholder for a behaviour in a
context (of a Compound Task) - BPRole - specifies type and manner of selection
of entities performing or being used by
Activities - BPRoles are owned by Compound Tasks
- BPRoles are in performedBy or uses relations with
Activities
Order/
Purchasing
Authorising
Contract
Officer
Officer
RU
Evaluated
Award
Source(s)
Evaluation
Error
RU
Accounting
10
Business Process Metamodel
11
Business Events
- Notification of actions or state changes in
business model - driven by rules for emission and consumption
- Business Event Source
- emits events based on the actions and properties
of some model element - e.g. Order Release Activity completes
- Business Event Sink
- consumes events for use by some model element
- e.g. Order Repository Entity subscribes to Order
Release completion
12
Event Metamodel
13
Business Event Rules Mapping
- Rules
- specify when events are emitted or consumed
- Mappings
- allow modellers to populate or use Events payload
14
Model Extensions via Patterns
- Loops
- patterns using tail recursion
- Multiple Activity spawning to process collections
- pattern using head recursion
- Kill and Timeout Activities
- patterns using async flows and exception
semantics - Guards and Postconditions
- patterns of predicate evaluation Activities
15
Non-Normative Mapping
- The mapping to CORBA and Services should be
flexible - else abstraction level suffers
- don't want EDOC to be an IDL macro language
- Alternatives should exist for
- different legacy integration
- different infrastructure
- For example
- CORBA2 vs CCM
- RPC based vs Event based
16
Mapping our Model
- Business Process
- Workflow Mgmt Facility
- OR event types/notifications
- OR interfaces/operations
- OR EAI Profile
- Filling of Business Roles
- Trader service type/query
- OR Structured Naming Contexts
- Business Events
- Notification Service usage
- OR Event Service usage
- OR Messaging Service
17
Conclusion
- Small but Powerful set of modelling concepts
- Process/Role duality
- Rule-based Events for loose coupling
- Basis for automatic CORBA Code Generation
- our flexible mapping allows the use of
- various CORBA technology alternatives
- MOM Products
- EAI Profile and its mappings to technologies
Recommended
CrystalGraphics Presentations
