1 / 18

Modelling Standards in Visual Studio 2010

Modelling Standards in Visual Studio 2010. Steve Cook Software Architect, Microsoft Visual Studio Architecture Board and Board of Directors, Object Management Group. The Application Architect’s Job. Designing how to move from requirements to code Handling complexity

mayda
Download Presentation

Modelling Standards in Visual Studio 2010

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Modelling Standards in Visual Studio 2010 Steve Cook Software Architect, Microsoft Visual Studio Architecture Board and Board of Directors, Object Management Group

  2. The Application Architect’s Job • Designing how to move from requirements to code • Handling complexity • Platforms, libraries, technology evolution, languages, testing, methodologies, requirements, organization, work, people, … • Using tools • Abstraction & Views • Visualization • Verification • Generation • Communication

  3. The Modelling Dilemma: Two Masters • The “Model Centric” Master • Sometimes referred to as “Top Down” • The “Code Centric” Master • Sometimes referred to as “Code Up” • The value is in the integration between the two approaches…

  4. Models and Code Code artefacts Models Libraries Discover Visualize As-Is Reference RefactorGenerate Code Analyze Validate To-Be What-If Tests Debug Traces Abstract Concrete

  5. VS2010 Architecture and Visualization Tools

  6. What is the Unified Modeling Language (UML)?

  7. UML 2.1 diagrams in VS2010

  8. How UML is defined Diagram Model Visualizes and edits Defined informally Defined using concepts from UML MetaModel UML Constructs (class, property, association, etc) Defined using concepts from MOF Model Defined using concepts from

  9. XMI: how UML is interchanged Model <?xml version="1.0" encoding="UTF-8" ?> <uml:Modelxmi:version="2.1" xmlns:xmi=… … … </uml:Model> http://www.omg.org/spec/UML/20090901/Superstructure.cmof <?xml version="1.0" encoding="UTF-8" ?> <cmof:Packagexmi:version="2.1" xmlns:xmi=… … … </cmof:Package> UML.xsd UML MetaModel <?xml version="1.0" encoding="UTF-8" ?> <cmof:Packagexmi:version="2.1" xmlns:xmi=… … … </cmof:Package> MOF Model

  10. Diagram Definition • Currently there is no standard for interchanging UML diagrams effectively, or for defining precisely what legal UML diagrams are • The Diagram Definition RFP is developing a new “meta-standard” for defining and interchanging diagrams, led by IBM • There will (eventually) be a standard for UML diagrams, based on DD

  11. UML history • V2.3 early 2010 • V2.2 February 2009 • V2.1.2 November 2007 • V2.1.1 August 2007 • V2.0 July 2005 • V1.5 March 2003 • V1.4 September 2001 • V1.1 November 1997

  12. UML history • V2.3 early 2010 <- Microsoft • V2.2 February 2009 • V2.1.2 November 2007 • V2.1.1 August 2007 • V2.0 July 2005 • V1.5 March 2003 • V1.4 September 2001 • V1.1 November 1997 <- Microsoft

  13. “Future of UML” Request for Information • Issued December 12, 2008 (chaired by S Cook) • Response deadline August 17, 2009 • Responses: • 01Communications • ARTISAN Software Tools • SOFTEAM • Microsoft • SAP AG • Oose Innovative InformatikGmbh • Systems Engineering DSIG • No Magic Inc • IBM • Model Driven Solutions • HL7/OMG Working Group • Oracle • BAE Systems, CSC, Mega International, NIST, oose • 88Solutions • AdaCore, CoFluent, EADS, INRIA, THALES • Sparx Systems Pty Ltd

  14. Plan for future • Step 1: UML 2.4 - a short-term revision doing metamodel/XMI cleanups on formal issues that inhibit implementation generation and interchange • Completed July 2010 • Step 2: UML Specification Simplification RFP. Keep the UML definition the same, but reorganize the specification so that it is consumable and manageable • Completed December 2010 • Step 3: UML cleanup RFPs • Refactor and simplify • “Unbundle” and reduce dependencies • Eliminate unintended inheritance • Correct conceptual errors • Reorganize OMG modeling architecture • Eventually leading to UML 3.0

  15. UML is a Family of Languages UML UPDM SoaML SysML C# java Testing Real-time & Embedded

  16. Microsoft engagement • Member of OMG Board of Directors • Elected to OMG Architecture Board • Instigator of Future of UML RFI • Co-chair of UML 2.4 RTF • Submitter to SMOF • Future submitters to UML specification simplification and UML cleanup RFPs • Planned interception of revised standards in our evolving modelling products

  17. Keep in touch steve.cook@microsoft.com http://blogs.msdn.com/stevecook Visual Studio http://msdn.microsoft.com/en-us/vstudio Visual Studio Visualization and Modeling SDK http://code.msdn.microsoft.com/vsvmsdk

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

More Related