model driven applications using visual studio code name rosario

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

Upload: clint-edmonson

Post on 09-May-2015

2.847 views

Category:

Technology


2 download

DESCRIPTION

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

TRANSCRIPT

Page 1: Model Driven Applications Using Visual Studio Code Name Rosario

Model Driven Applications using Visual Studio Code Name "Rosario Clint EdmonsonArchitect EvangelistMicrosofthttp://www.notsotrivial.net

Page 2: Model Driven Applications Using Visual Studio Code Name Rosario

Topics

• Why should we model?

• What should we model?

• How will we model using Rosario?

• Why is Microsoft investing in modeling?

Page 3: Model Driven Applications Using Visual Studio Code Name Rosario

Quick show of hands

Anyone using…• Visio• Together• Altova• Rational• Sparx• Others???

Page 4: Model Driven Applications Using Visual Studio Code Name Rosario

Why should we model?

Page 5: Model Driven Applications Using Visual Studio Code Name Rosario

Customer Problems

Page 6: Model Driven Applications Using Visual Studio Code Name Rosario

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?

Page 7: Model Driven Applications Using Visual Studio Code Name Rosario

Demo

Architecture Explorer

Page 8: Model Driven Applications Using Visual Studio Code Name Rosario

What should we model?

Page 9: Model Driven Applications Using Visual Studio Code Name Rosario

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

Page 10: Model Driven Applications Using Visual Studio Code Name Rosario

Architectural Frameworks

• Krutchen’s 4+1 Views of Architecture• The Open Group Architecture Framework

(TOGAF)• Zachman Framework

Page 11: Model Driven Applications Using Visual Studio Code Name Rosario

Architectural Frameworks

Krutchen’s 4+1 Views

Page 12: Model Driven Applications Using Visual Studio Code Name Rosario

Architectural Frameworks

TOGAF

Page 13: Model Driven Applications Using Visual Studio Code Name Rosario

Architectural FrameworksZachman Framework

Page 14: Model Driven Applications Using Visual Studio Code Name Rosario

Architectural Views

• As a minimum (think Agile): – Use Case Diagram (Logical)– Logical Class Diagram (Logical)– Component Diagram (physical)– Deployment Diagram (physical)

Page 15: Model Driven Applications Using Visual Studio Code Name Rosario

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

Page 16: Model Driven Applications Using Visual Studio Code Name Rosario

How will we model with Rosario?

Page 17: Model Driven Applications Using Visual Studio Code Name Rosario

UML & other DSLs

Page 18: Model Driven Applications Using Visual Studio Code Name Rosario

Our Approach

Page 19: Model Driven Applications Using Visual Studio Code Name Rosario

Demo

Use Case Diagram

Page 20: Model Driven Applications Using Visual Studio Code Name Rosario

Demo

Sequence Diagram

Page 21: Model Driven Applications Using Visual Studio Code Name Rosario

Architecture Edition April CTP

• Architecture Explorer• UML Diagrams

– Use Case Diagram– Class Diagram– Sequence Diagram– Component Diagram– Activity Diagram

Page 22: Model Driven Applications Using Visual Studio Code Name Rosario

XMI Interchange Support

• Rational• Sparx Systems Enterprise Architect• Togethersoft• Altova• Visio

Page 23: Model Driven Applications Using Visual Studio Code Name Rosario

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

Page 24: Model Driven Applications Using Visual Studio Code Name Rosario

Why is Microsoft investing in modeling?

Page 25: Model Driven Applications Using Visual Studio Code Name Rosario

Our GoalsBroadening the Reach of Modeling

Page 26: Model Driven Applications Using Visual Studio Code Name Rosario

Next Steps• Download the September CTP

• Available later this month

• Team blog:• http://blogs.msdn.com/vsarch

• Contact the team lead – Peter Provost• [email protected]

• Stayed tuned to my blog for more…• http://www.notsotrivial.net

Page 27: Model Driven Applications Using Visual Studio Code Name Rosario

Q & A

Page 28: Model Driven Applications Using Visual Studio Code Name Rosario

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