Daniel Selman, Product Architect – IBM WebSphere ILOG BRMSParis Java User Group, November 2010Enabling Agile Businessand I...
Things change.                 © 2010 IBM Corporation
Expect it. Design for it.                            © 2010 IBM Corporation
Change Oriented Architecture.                                © 2010 IBM Corporation
Externalize your data from your code.                                        © 2010 IBM Corporation
Create reusable services.(if you can afford to)                            © 2010 IBM Corporation
Externalize your volatile business policy from your code.                                                        © 2010 IB...
How many change processes do you need?  1. Code  2. Configuration  3. GUI  4. Rules  5. Processes  6. Data  7. Models  8. ...
What metadata do you need to govern your changes?                                                    © 2010 IBM Corporation
Who initiates a change? – How do they know that change is required?Performs the change?Validates the change?              ...
Do you need side-by-side execution of configurations?(Can you afford it?)                                                 ...
How will you audit what changes were made?(for how long?)                                             © 2010 IBM Corporation
How do you ensure that the pre-conditions for a change are in- place or planned?                                          ...
Is the change comprehensible to a human being?                                                 © 2010 IBM Corporation
Your job as an architect/developer:  Build a “container for change”                                      © 2010 IBM Corpor...
Cross-disciplinary work, requiring: A solid knowledge of the business An appreciation of human behavior Deep (and broad...
BRMS cannot solve all these problems(but it can help with many)                                       © 2010 IBM Corporation
Short demo of a change cycle with ILOG BRMS                                              © 2010 IBM Corporation
Upcoming SlideShare
Loading in...5
×

Paris Java User Group : Enabling Agile Business and IT Collaboration

159

Published on

Introducing the concept of Change Oriented Architecture.

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

  • Be the first to like this

No Downloads
Views
Total Views
159
On Slideshare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
0
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

Transcript of "Paris Java User Group : Enabling Agile Business and IT Collaboration"

  1. 1. Daniel Selman, Product Architect – IBM WebSphere ILOG BRMSParis Java User Group, November 2010Enabling Agile Businessand IT Collaboration © 2009 IBM Corporation
  2. 2. Things change. © 2010 IBM Corporation
  3. 3. Expect it. Design for it. © 2010 IBM Corporation
  4. 4. Change Oriented Architecture. © 2010 IBM Corporation
  5. 5. Externalize your data from your code. © 2010 IBM Corporation
  6. 6. Create reusable services.(if you can afford to) © 2010 IBM Corporation
  7. 7. Externalize your volatile business policy from your code. © 2010 IBM Corporation
  8. 8. How many change processes do you need? 1. Code 2. Configuration 3. GUI 4. Rules 5. Processes 6. Data 7. Models 8. Transformations 9. Topology 10.Etc. © 2010 IBM Corporation
  9. 9. What metadata do you need to govern your changes? © 2010 IBM Corporation
  10. 10. Who initiates a change? – How do they know that change is required?Performs the change?Validates the change? © 2010 IBM Corporation
  11. 11. Do you need side-by-side execution of configurations?(Can you afford it?) © 2010 IBM Corporation
  12. 12. How will you audit what changes were made?(for how long?) © 2010 IBM Corporation
  13. 13. How do you ensure that the pre-conditions for a change are in- place or planned? © 2010 IBM Corporation
  14. 14. Is the change comprehensible to a human being? © 2010 IBM Corporation
  15. 15. Your job as an architect/developer: Build a “container for change” © 2010 IBM Corporation
  16. 16. Cross-disciplinary work, requiring: A solid knowledge of the business An appreciation of human behavior Deep (and broad) technical skills to choose the right technologies An understanding of governance concerns Top-down management support for funding Abhorrence of over-engineering… – Design for expected changes © 2010 IBM Corporation
  17. 17. BRMS cannot solve all these problems(but it can help with many) © 2010 IBM Corporation
  18. 18. Short demo of a change cycle with ILOG BRMS © 2010 IBM Corporation

×