11. NO SIZE FITS ALL
● Diverse approaches, results and experiences (old
and new) from different environments
● 4 quarters with different MDE parameters
● 2 types of organizations:
● Service-oriented: odd quarters 1, 3
● Production-oriented: even quarters 2, 4
● An organization may operate in multiple quarters
● Caution when adopting somebody’s success formula
10
12. Business & MDE Processes
Business Process MDE Process
11
13. Business & MDE Processes
Business Process MDE Process
BUSINESS & MDE PROCESSES
11
15. ¨ Where (Organization structure)
¨ What (Artifact development)
¨ How (Incidental “want”)
¨ MDE development process
¨ Context confusion lead to sub-optimal
DN/UP strategy
Q: UP? DOWN?
12
16. Business & MDE Processes
Business Process MDE Process
13
17. ARTIFACT: A CLOSER LOOK
¨ Artifact may be a multi- stage outcome
¤ Complexity
¤ Variation points (design, technology,
optimizations)
¨ Different benefit models:
¤ DN: 1pr. x 1art. x (big) ROI x TP
¤ UP: M pr. x N stages x (little) ROI x TP
13
19. A: IT DEPENDS…
¨ Where and What depends on Business Case
¨ DN/UP in artifact development:
n Different Outcomes
n Different Benefit Plans
n Top-down projects benefit from domain analysis
n Bottom-up projects need to plan for broad
reuse of outcomes
n Generic knowledge
¨ DN is preferable in MDE development
14
25. ¨ Continuous BC justification
¨ Progress in controlled steps
¨ Agile collaboration with users
¨ Direct communication with experts
¨ Plan post-project activities to realize benefits
(training, etc.)
¤ Organizations are often not not prepared for any form
of success
PROJECT
17
27. ANALYSIS
Benefits
¨ Why, need vs. want
¨ Includes non-technical
solutions
¨ Improves requirements,
user stories
¨ Drives building for
change
¨ Helps define MDE
approach (UML/DSM…)
What & Where
¨ Domain/ontology and
process analysis in:
¤ MDE Development in:
n Production
n Service
¨ Not the same as in
MDE-powered
processes.
18
29. Doing the job efficiently
Doing the job
SPECIALIZATION
20
30. Doing the job efficiently
Doing the job
Now it has 5 nuts
instead of 6....
You need to change!
• People skills
• Proper MDE tools
SPECIALIZATION
20
32. CHANGE-FRIENDLY CASE TOOLS
¨ Expressiveness for problem domain
¨ Support for application architecture
¨ Extension points
(Service-oriented organizations)
21
34. CHANGE-FRIENDLY DSM TOOLS
¨ Support for application architecting
n Customizable code generation
n Architecture must be in place
¨ Fit-for-purpose DSL-development tools
n Up to 10 times more efficient than
otherwise
(Production-oriented organizations)
22
36. ALWAYS EVALUATE TECHNOLOGY
¨ Established vendor name is not guarantee of
fit-for-purpose
¨ No standard evaluation benchmarks
¨ No all-round perfect MDE tool
¨ There are more aspects to consider…
23
38. CONDITIONS FOR SUCCESS
① Know yourself:
¤ Service/Production
¤ Business Case
¤ Business Product
Variation
② Choose right DN/UP
strategy for max.
benefit
③ Progress in agile and
controlled steps
④ Do not save on
analysis
⑤ Build-for-change with
right:
¤ Qualified team
¤ MDE technology
24
