background preloader

UML Modeling and Code Generation in Visual Studio 2010

UML Modeling and Code Generation in Visual Studio 2010
This article provides an overview of UML modeling in Visual Studio 2010. Assuming that reader is already familiar with UML, it focuses on custom UML profiles - an extensibility mechanism that can be used to tailor UML models to a particular problem domain. Readers will see an example of such a profile, which extends UML Class Diagrams for database modeling. Finally, the article shows how code can be generated from UML models using T4 text templates. This article is based on Beta 2 of Visual Studio 2010 Ultimate Edition. To follow the code example you may also want to install T4 Editor which provides color syntax highlighting and IntelliSense for text templates in Visual Studio. UML Modeling in Visual Studio In order to start using UML diagrams in Visual Studio 2010, you first need to create a Modeling Project. Once you have the project created, you can add new diagrams to it. Here is an example of class diagram you can create. UML Profiles Custom UML Profiles Sample Database Profile <? UML vs.

patterns & practices: Project Silk create UML modeling and diagrams UML models help you understand, discuss, and design software systems. Visual Studio Ultimate provides templates for five of the most frequently used UML diagrams: activity, class, component, sequence, and use case. In addition, you can create layer diagrams, which help you define the structure of your system. You need Visual Studio Ultimate to create UML models. UML modeling diagrams and layer diagrams can exist only inside a modeling project. You need Visual Studio Ultimate to create modeling projects. To create a diagram and add it to a project On the Architecture menu, choose New Diagram. If your solution is open, the new project is added to the solution. If you already have a modeling project, you can also use the following procedure. To add a diagram to an existing modeling project In Solution Explorer, click the modeling project node. To create a blank modeling project On the File menu, point to New, and then click Project. To permanently delete a diagram from a project

The UML Model Explorer - Skinner's Blog In the VSTS 2010 Architecture product, we've added another toolwindow to VS designed to help you understand and manipulate the UML models that you will be building. The UML Model Explorer ( that's what we're currently calling it, but that can certainly change :) ) is a WPF component that represents the UML Package hierarchy of your models. "Models" in this context refer to the contents of the Modeling projects you have created and added to the current solution. The root node or nodes of the UML Model Explorer are UML packages representing those Modeling Projects. For example, in the image below, I have created two Modeling Projects, "My First Modeling Project" and "My Second Modeling Project". You'll notice that the UML Model Explorer has two corresponding nodes in the tree. You might immediately be asking yourself "What's up here? As I mentioned earlier, every time you create a Modeling Project, a new node will be displayed in the UML Model Explorer. Adding Elements Summary

patterns & practices: App Arch Guide 2.0 Knowledge Base wiki - UML (fr) Un article de Wikipédia, l'encyclopédie libre. Pour les articles homonymes, voir UML. En informatique UML (de l'anglais Unified Modeling Language), ou Langage de modélisation unifié, est un langage de modélisation graphique à base de pictogrammes. Il est utilisé en développement logiciel, et en conception orientée objet. UML est l'accomplissement de la fusion de précédents langages de modélisation objet : Booch, OMT, OOSE. UML est utilisé pour spécifier, visualiser, modifier et construire les documents nécessaires au bon développement d'un logiciel orienté objet. Activité d'un objet/logicielActeursProcessusSchéma de base de donnéesComposants logicielsRéutilisation de composants Les méthodes objets ont commencé à émerger au début des années 80, ces méthodes avaient pour but de remplacer les méthodes structurée et fonctionnelles, trop liés à la machine. En janvier 1997, UML est devenu un standard OMG. Les standards UML 1.x restent largement influencés par la notation OMT.

How to: Create UML Modeling Projects and Diagrams UML models help you understand, discuss, and design software systems. Visual Studio provides templates for five of the most frequently used UML diagrams: activity, class, component, sequence, and use case. In addition, you can create layer diagrams, which help you define the structure of your system. UML modeling diagrams and layer diagrams can exist only inside a modeling project. Each modeling project contains a shared UML model and several UML diagrams. Each diagram is a partial view of the model. To see which versions of Visual Studio support this feature, see Version support for architecture and modeling tools. To create a diagram and add it to a project On the Architecture menu, choose New UML or Layer Diagram.In the Add New Diagram dialog box, click the type of modeling diagram that you want. If your solution is open, the new project is added to the solution. If you already have a modeling project, you can also use the following procedure. To create a blank modeling project

ploeh blog enterprise architect - UML modeling tool visual studio - Reverse Engineering Code into a UML Class Diagram in VS 2010 Domain Driven Design: A Step by Step Guide - Part 2 This is the second part in a series on Domain Driven Design. You can read the first part here. This article was created and edited (with permission) from a series of posts on Casey's blog. Entities and Value Objects Entities and Value Objects (VO) form the core building blocks of Domain Driven applications. Why has it taken this long to get to something so fundamental? DDD has refined this concept a little, by splitting the idea of these business objects into two distinct types, Entities and Value Objects Entities “this is my Entity, there are many like it, but this one is mine” The key defining characteristic of an Entity is that it has an Identity – it is unique within the system, and no other Entity, no matter how similar is the same Entity unless it has the same Identity. Examples of common Entities are: Customer, Product, Container, Vehicle Whichever way you choose to represent it, an Entity is defined by having an Identity. Value Objects Hey, I’ve Heard of These, We Have Them in .Net!

argouml.tigris.org

Related: