The need for the IT to be fast enough to supply Business demand, is a false problem and can even probably be dangerous, leading to disastrous solutions often creating more and more inertia to IT itself that will be less and less capable of keeping pace with the Business. In addition an IT innovation will boost the business even more leaving IT in the dust. The approach to be fulfill is to make the Business "ride" the IT and create a virtuous circle. The speech will describe the risks in insisting in Business-IT alignment and investigate how to leverage MDA as a way to successfully have the Business to "ride" IT.

1. Business and IT alignment, how to escape from the sand-trap Pierfranco Ferronato Chief Archiect and Founder, Soluta.Net

3. We perceive that IT needs to support business "better"

4. We see that Business runs faster then IT

5. We see that Business is bound to IT and makes things slow

6. We understand that IT is struggling to support Business

9. Design for change is more complex

13. It's not as simple

16. IT can give the Business new horizons

17. Assuming that there is a gap to close, gives the false perception that IT is "behind" the Business, chasing it

18. IT has not simply the goal to align with the business because it can pull the Business

19. The IT is running the Business

20. No Business can reasonably be conducted without the support of IT.

22. Consultant: „Cool, what does this means to you?“

25. But this Virtual Business Machine need to have nothing inside about Business

26. You describe the business and give it to IT for execution

28. Business is buried in the code

30. Shall look for an architectural style that GETS THE BUSINESS OUT OF THE IT!

34. It's already a legacy perception of IT

35. It's more complex than that

36. Get rid of the gap

37. Because there has not to be a gap

38. Business and IT need to be UNRELATED

42. Ok„ Whats the way to go then? “

43. As a solution architect you are thinking " Cool motto, but how's this going to affect my current strategies and decisions? "

45. DSL are the isolation level between IT and the Business

46. Use architecture modelling techniques that allow application be described as models using DSLs to be then executed by the IT

50. Business Rules: RuleML

54. A Modelling Environment

56. Load them in a BEE

59. New semantics in the DSLs

63. No need to align!

65. Graphical contributions from Sue Maurizio, healingdream, jscreationzs, M. Bartosch, Felixco Inc. e Michelle Meiklejohn Pierfranco Ferronato Soluta.Net mobile: +39.348.071.4898 skype: pferronatosn