Model Driven Applications Using Visual Studio Code Name Rosario

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

Topics

Why should we model?

What should we model?

How will we model using Rosario?

Why is Microsoft investing in modeling?

Quick show of hands

Anyone using…

Visio

Together

Altova

Rational

Sparx

Others???

Why should we model?

Customer Problems

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?

Demo Architecture Explorer

What should we model?

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

Architectural Frameworks

Krutchen’s 4+1 Views of Architecture

The Open Group Architecture Framework (TOGAF)

Zachman Framework

Architectural Frameworks Krutchen’s 4+1 Views

Architectural Frameworks TOGAF

Architectural Frameworks Zachman Framework

Architectural Views

As a minimum (think Agile):

Use Case Diagram (Logical)

Logical Class Diagram (Logical)

Component Diagram (physical)

Deployment Diagram (physical)

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

How will we model with Rosario?

UML & other DSLs

Our Approach

Demo Use Case Diagram

Demo Sequence Diagram

Architecture Edition April CTP

Architecture Explorer

UML Diagrams

Use Case Diagram

Class Diagram

Sequence Diagram

Component Diagram

Activity Diagram

XMI Interchange Support

Rational

Sparx Systems Enterprise Architect

Togethersoft

Altova

Visio

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

Why is Microsoft investing in modeling?

Our Goals Broadening the Reach of Modeling

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

Q & A

© 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.