1. IBM WODM Development
Process Overview

2. Term Relationships
Business processes Applications
call / invoke
1..
Decision services 1.. Decision signature
1..* 0..*
1..*
1..* Vocabulary
Decisions
Situation 1..*
1..* 1..* 1..*
1.. 1..*
Events Rules 1..* 1..*
Contextual
1..* 1..*
Actions trigger
Situational

3. Decision development lifecycles
 Gather requirements  Discover
 Decision evaluation  Validate rule
 Model & Simulate  Construct & test
 Simulate & test  Deploy rules
 Design  Compose
 Business
 Business Analysts Analysts
 Business Users  Business
 Architect Users
 IT/Software  Architects
developers
 Integrate people
 Manage apps & services  Improve
 Integrate processes  Observe KPIs
 Manage identity & compliance performance
 Manage and integrate
 Monitor business metrics
information
Most fundamental decision works Business users leverages decision
(analysis, decision point, decision artifacts to establish business rules and
signature, decision services, rule decides responses to situations.
harvesting, situation, vocabulary, and etc)
are done in Service Lifecycle

4. IBM WODM Decision Development Process
∗ Start from business process development to identify
the decision requirements.
∗ Decision points development
∗ Identify key decision points across the solution
∗ Identify information in the decisions.
∗ Situation identification and response development
∗ Identify situations and find out the ways to response to them
∗ Decision information models and vocabulary
∗ identify concepts, object types, business terms(naming,
verbalization , decision characteristics, situations, actions)
∗ Align business object types across rules, events and
processes.
∗ Business object definitions
∗ Business object filed primitives
∗ Domains or enumerations
∗ Variables

5. Any questions ?