The document discusses model-driven applications utilizing Microsoft Visual Studio, emphasizing the importance of modeling in software development for better design and communication. It outlines the types of designs to model, including logical and physical designs, and introduces architectural frameworks such as Krutchen’s 4+1 views and TOGAF. Microsoft’s investment in modeling is highlighted, including the introduction of UML support and enhancements in their architecture exploration tools.

1. Model Driven Applications using Visual Studio Code Name "Rosario Clint Edmonson Architect Evangelist Microsoft http://www.notsotrivial.net

2. Topics Why should we model? What should we model? How will we model using Rosario? Why is Microsoft investing in modeling?

3. Quick show of hands Anyone using… Visio Together Altova Rational Sparx Others???

4. Why should we model?

5. Customer Problems

6. Lower Fidelity + Higher Abstraction Design before code – lower fidelity , saves time, money , and avoids mistakes Abstraction level above code Determine difficult decisions before we start building anything Communicate our thoughts to others without making them read the code Why is Microsoft adding UML support now?

7. Demo Architecture Explorer

8. What should we model?

9. Logical & Physical Designs Logical design refers to the class and algorithmic structure of a program Physical design refers to how these classes are packaged into assemblies and deployed

10. Architectural Frameworks Krutchen’s 4+1 Views of Architecture The Open Group Architecture Framework (TOGAF) Zachman Framework

11. Architectural Frameworks Krutchen’s 4+1 Views

12. Architectural Frameworks TOGAF

13. Architectural Frameworks Zachman Framework

14. Architectural Views As a minimum (think Agile): Use Case Diagram (Logical) Logical Class Diagram (Logical) Component Diagram (physical) Deployment Diagram (physical)

15. Design vs. Realization Should designs be tightly coupled to code? To the VS project or solution? Our approach is to use explicit designer initiated transformations

16. How will we model with Rosario?

17. UML & other DSLs

18. Our Approach

19. Demo Use Case Diagram

20. Demo Sequence Diagram

21. Architecture Edition April CTP Architecture Explorer UML Diagrams Use Case Diagram Class Diagram Sequence Diagram Component Diagram Activity Diagram

22. XMI Interchange Support Rational Sparx Systems Enterprise Architect Togethersoft Altova Visio

23. Progress Since April 2008 CTP Architectural Explorer UX enhancements and lots more Layer Diagram UML Class Diagram Pushing and pulling from .NET Class Diagram Use Case Diagram supports sub-system and doc references Implemented common UML meta-model that all diagrams will use

24. Why is Microsoft investing in modeling?

25. Our Goals Broadening the Reach of Modeling

26. Next Steps Download the September CTP Available later this month Team blog: http://blogs.msdn.com/vsarch Contact the team lead – Peter Provost [email_address] Stayed tuned to my blog for more… http://www.notsotrivial.net

27. Q & A

28. © 2008 Microsoft Corporation. All rights reserved. Microsoft, Windows, Windows Vista and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries. The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.