How to tap into MDE: Conditions for Success

287 views

Published on

Published in: Technology, Business
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
287
On SlideShare
0
From Embeds
0
Number of Embeds
2
Actions
Shares
0
Downloads
4
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

How to tap into MDE: Conditions for Success

  1. 1. FOCUS 2
  2. 2. 3
  3. 3. 2 1 3 4 ORGANIZATION & MDE 4
  4. 4. 2 1 3 4 ORGANIZATION & MDE ERP CRM XML Java PHP Product artifact Order Material HRM ‘Product’ Product artifactProduct artifact Product artifact Product artifact 5
  5. 5. ORGANIZATION & MDE OTS DSM PIM PSM DSM CIM 2 1 3 4 DSM PIM PSM 6 CASE
  6. 6. 2 1 3 4 ORGANIZATION & MDE E <10X E < 0.5X Q: code Q: Product, Product Type, planning, customer satisfaction… E <10X E > 0.5X 7 Q: customer satisfaction…
  7. 7. 2 1 3 4 ORGANIZATION & MDE MetaEdit MetaEdit Mendix Platform OutSystems Agile Platform OAW OAW Proprietary Code Generators Code Generators SAP MatLab 8
  8. 8. 2 1 3 4 ORGANIZATION & MDE Philips Thales ASML SAP MetaCase Mendix OutSystems ICT company ICT company ICT company 9
  9. 9. 10
  10. 10. 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
  11. 11. Business & MDE Processes Business Process MDE Process 11
  12. 12. Business & MDE Processes Business Process MDE Process BUSINESS & MDE PROCESSES 11
  13. 13. 12
  14. 14. ¨  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
  15. 15. Business & MDE Processes Business Process MDE Process 13
  16. 16. 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
  17. 17. 14
  18. 18. 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
  19. 19. 15
  20. 20. PROJECT ¨  Continuous BC justification ¨  Progress in controlled steps 15
  21. 21. 16
  22. 22. ¨  Continuous BC justification ¨  Progress in controlled steps ¨  Agile collaboration with users ¨  Direct communication with experts PROJECT 16
  23. 23. 17
  24. 24. ¨  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
  25. 25. 18
  26. 26. 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
  27. 27. 19
  28. 28. Doing the job efficiently Doing the job SPECIALIZATION 20
  29. 29. 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
  30. 30. 21
  31. 31. CHANGE-FRIENDLY CASE TOOLS ¨  Expressiveness for problem domain ¨  Support for application architecture ¨  Extension points (Service-oriented organizations) 21
  32. 32. 22
  33. 33. 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
  34. 34. 23
  35. 35. 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
  36. 36. 24
  37. 37. 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
  38. 38. 25
  39. 39. QUALIFICATIONS & TOOLS ¨  Analysis ¤  ORM ¤  BPM ¤  DEMO ¨  Project operation ¤  PRINCE2, DSDM Atern ¤  Agile SCRUM ¨  Build for change ¤  DDD ¤  TOGAF ¤  DSM ¤  MDA ¨  Technology ¤  OutSystems ¤  Mendix ¤  MetaEdit+ 25 These are examples!
  40. 40. Tony Sloos www.architecit.nl tony@architecit.nl tony.sloos.com Andriy Levytskyy www.zest-ap.nl www.conceptworks.eu Andriylevytskyy twitter.com/levytsky 26

×