Model Driven Applications using  Visual Studio Code Name "Rosario  Clint Edmonson Architect Evangelist Microsoft http...
Topics <ul><li>Why should we model? </li></ul><ul><li>What should we model? </li></ul><ul><li>How will we model using Rosa...
Quick show of hands <ul><li>Anyone using… </li></ul><ul><li>Visio </li></ul><ul><li>Together </li></ul><ul><li>Altova </li...
Why should we model?
Customer Problems
Lower Fidelity + Higher Abstraction <ul><li>Design before code – lower fidelity , saves time, money , and avoids mistakes ...
Demo Architecture Explorer
What should we model?
Logical & Physical Designs <ul><li>Logical design refers to the class and algorithmic structure of a program </li></ul><ul...
Architectural Frameworks <ul><li>Krutchen’s 4+1 Views of Architecture </li></ul><ul><li>The Open Group Architecture Framew...
Architectural Frameworks Krutchen’s 4+1 Views
Architectural Frameworks TOGAF
Architectural Frameworks Zachman Framework
Architectural Views <ul><li>As a minimum (think Agile):  </li></ul><ul><ul><li>Use Case Diagram (Logical) </li></ul></ul><...
Design vs. Realization <ul><li>Should designs be tightly coupled to code?  </li></ul><ul><ul><li>To the VS project or solu...
How will we model with Rosario?
UML & other DSLs
Our Approach
Demo Use Case Diagram
Demo Sequence Diagram
Architecture Edition April CTP <ul><li>Architecture Explorer </li></ul><ul><li>UML Diagrams </li></ul><ul><ul><li>Use Case...
XMI Interchange Support <ul><li>Rational </li></ul><ul><li>Sparx Systems Enterprise Architect </li></ul><ul><li>Togetherso...
Progress Since April 2008 CTP <ul><li>Architectural Explorer  UX enhancements and lots more </li></ul><ul><li>Layer Diagra...
Why is Microsoft investing in modeling?
Our Goals Broadening the Reach of Modeling
Next Steps <ul><li>Download the September CTP </li></ul><ul><ul><ul><li>Available later this month </li></ul></ul></ul><ul...
Q & A
© 2008 Microsoft Corporation. All rights reserved. Microsoft, Windows, Windows Vista and other product names are or may be...
Upcoming SlideShare
Loading in …5
×

Model Driven Applications Using Visual Studio Code Name Rosario

3,081 views
2,964 views

Published on

Overview of new UML features coming in Visual Studio Rosario and why they are important to Architects.

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

No Downloads
Views
Total views
3,081
On SlideShare
0
From Embeds
0
Number of Embeds
210
Actions
Shares
0
Downloads
78
Comments
0
Likes
1
Embeds 0
No embeds

No notes for slide
  • Model Driven Applications Using Visual Studio Code Name Rosario

    1. 1. Model Driven Applications using Visual Studio Code Name &quot;Rosario Clint Edmonson Architect Evangelist Microsoft http://www.notsotrivial.net
    2. 2. Topics <ul><li>Why should we model? </li></ul><ul><li>What should we model? </li></ul><ul><li>How will we model using Rosario? </li></ul><ul><li>Why is Microsoft investing in modeling? </li></ul>
    3. 3. Quick show of hands <ul><li>Anyone using… </li></ul><ul><li>Visio </li></ul><ul><li>Together </li></ul><ul><li>Altova </li></ul><ul><li>Rational </li></ul><ul><li>Sparx </li></ul><ul><li>Others??? </li></ul>
    4. 4. Why should we model?
    5. 5. Customer Problems
    6. 6. Lower Fidelity + Higher Abstraction <ul><li>Design before code – lower fidelity , saves time, money , and avoids mistakes </li></ul><ul><li>Abstraction level above code </li></ul><ul><li>Determine difficult decisions before we start building anything </li></ul><ul><li>Communicate our thoughts to others without making them read the code </li></ul><ul><li>Why is Microsoft adding UML support now? </li></ul>
    7. 7. Demo Architecture Explorer
    8. 8. What should we model?
    9. 9. Logical & Physical Designs <ul><li>Logical design refers to the class and algorithmic structure of a program </li></ul><ul><li>Physical design refers to how these classes are packaged into assemblies and deployed </li></ul>
    10. 10. Architectural Frameworks <ul><li>Krutchen’s 4+1 Views of Architecture </li></ul><ul><li>The Open Group Architecture Framework (TOGAF) </li></ul><ul><li>Zachman Framework </li></ul>
    11. 11. Architectural Frameworks Krutchen’s 4+1 Views
    12. 12. Architectural Frameworks TOGAF
    13. 13. Architectural Frameworks Zachman Framework
    14. 14. Architectural Views <ul><li>As a minimum (think Agile): </li></ul><ul><ul><li>Use Case Diagram (Logical) </li></ul></ul><ul><ul><li>Logical Class Diagram (Logical) </li></ul></ul><ul><ul><li>Component Diagram (physical) </li></ul></ul><ul><ul><li>Deployment Diagram (physical) </li></ul></ul>
    15. 15. Design vs. Realization <ul><li>Should designs be tightly coupled to code? </li></ul><ul><ul><li>To the VS project or solution? </li></ul></ul><ul><li>Our approach is to use explicit designer initiated transformations </li></ul>
    16. 16. How will we model with Rosario?
    17. 17. UML & other DSLs
    18. 18. Our Approach
    19. 19. Demo Use Case Diagram
    20. 20. Demo Sequence Diagram
    21. 21. Architecture Edition April CTP <ul><li>Architecture Explorer </li></ul><ul><li>UML Diagrams </li></ul><ul><ul><li>Use Case Diagram </li></ul></ul><ul><ul><li>Class Diagram </li></ul></ul><ul><ul><li>Sequence Diagram </li></ul></ul><ul><ul><li>Component Diagram </li></ul></ul><ul><ul><li>Activity Diagram </li></ul></ul>
    22. 22. XMI Interchange Support <ul><li>Rational </li></ul><ul><li>Sparx Systems Enterprise Architect </li></ul><ul><li>Togethersoft </li></ul><ul><li>Altova </li></ul><ul><li>Visio </li></ul>
    23. 23. Progress Since April 2008 CTP <ul><li>Architectural Explorer UX enhancements and lots more </li></ul><ul><li>Layer Diagram </li></ul><ul><li>UML Class Diagram Pushing and pulling from .NET Class Diagram </li></ul><ul><li>Use Case Diagram supports sub-system and doc references </li></ul><ul><li>Implemented common UML meta-model that all diagrams will use </li></ul>
    24. 24. Why is Microsoft investing in modeling?
    25. 25. Our Goals Broadening the Reach of Modeling
    26. 26. Next Steps <ul><li>Download the September CTP </li></ul><ul><ul><ul><li>Available later this month </li></ul></ul></ul><ul><li>Team blog: </li></ul><ul><ul><ul><li>http://blogs.msdn.com/vsarch </li></ul></ul></ul><ul><li>Contact the team lead – Peter Provost </li></ul><ul><ul><ul><li>[email_address] </li></ul></ul></ul><ul><li>Stayed tuned to my blog for more… </li></ul><ul><ul><ul><li>http://www.notsotrivial.net </li></ul></ul></ul>
    27. 27. Q & A
    28. 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.

    ×