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. Related:  vsts - visual studio team foundation

software factories and VSTS Marcel de Vries Info Support Jack Greenfield Microsoft Corporation November 2006 Applies to: Microsoft Visual Studio Team System Microsoft SQL Server 2005 Reporting Services Software Factories Summary: This white paper discusses how software factories and Microsoft Visual Studio Team System can be used together to improve quality, predictability, and productivity. This white paper concludes that greater quality, predictability, and productivity can be achieved with a software-factory approach, rather than with traditional one-off development. Contents IntroductionChanging the Way We Build SoftwareMeasuring Quality and ProductivityApplying Visual Studio Team SystemUsing Measurement Constructs (ISO 15939)Putting It All TogetherConclusionReferences Introduction Building software today is hard. Changing the Way We Build Software For several decades, the software industry has created software systems to support the needs of its customers. How Software Is Built Today But let's be honest. Figure 1.

patterns & practices: Project Silk vsts - coach Enregistrement conseillé L'enregistrement est un processus rapide et il permet à Microsoft de vous fournir les dernières ressources pertinentes par rapport à vos intérêts, en ce compris des Service Packs, des notifications de sécurité et des formations. Cliquez sur le bouton Continuer. <a id="547e66ef-fe0d-cfc0-6bc3-0c8524b0afbc" target="_self" class="mscom-link download-button cont" href="registration-suggested.aspx? Formez-vous avec le Coach VSTS !! DétailsIntroductionTeamSystem-COACH-VSTS.zip Développez des applications fiables et performantes, en respectant les délais, tout en acceptant les changements, tel est le challenge quotidien des équipes projets !

patterns & practices: App Arch Guide 2.0 Knowledge Base vsts - documentation Mise à jour : novembre 2007 Team Foundation est une collection de technologies de collaboration qui soutiennent le travail en équipe pour fournir un produit. Si les technologies de Team Foundation sont généralement employées par des équipes de développement pour générer des produits logiciels, elles peuvent également être utilisées sur d'autres types de projets. La partie restante est divisée en trois zones en fonction du rôle joué par une équipe : administrateurs de projet, coordinateurs de projet et membres du projet. Fournit des liens vers les rubriques traitant des concepteurs visuels qui permettent aux architectes, aux responsables des opérations et aux développeurs de concevoir des solutions orientées service qui peuvent être validées par rapport à leurs environnements opérationnels. Fournit des liens vers les rubriques traitant des outils de développement avancés qui permettent aux équipes de générer des services et des applications fiables et stratégiques.

ploeh blog team development with VSTS J.D. Meier, Jason Taylor, Prashant Bansode, Alex Mackman, and Kevin Jones Microsoft Corporation September 2007 This guide shows you how to make the most of Team Foundation Server. Download the Guide Final release is available! Download the Team Development with Visual Studio Team Foundation Server Guide Abstract There are many elements, processes, and roles that combine to enable successful team-based software development projects. The development process The build process The project management process The following diagram illustrates the relationship between typical software development processes relating to team development and how Team Foundation Server can be leveraged to provide horizontal foundational support for these initiatives. Parts Forewards Chapters Introduction Part I, Fundamentals Part II, Source Control Part III, Builds Part IV, Large Project Considerations Ch 10 – Large Project Considerations Part V, Project Management Part VI, Process Templates Part VII, Reporting Guidelines Practices

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!

MSF for CMMI process improvement for VSTS ALM Using the work item types (WITs), reports, and dashboards shown in the illustration, teams can plan projects and then track, view, and report their progress. These artifacts, which are based on the Capability Maturity Model Integration (CMMI) requirements, are created when you create a team project using the Microsoft Solutions Framework (MSF) for CMMI process template. The latest version of the CMMI process template is automatically uploaded to Team Foundation Server (TFS) when you install or upgrade to the latest version of TFS. Use the Process Template Manager to download and upload process templates. In addition to the work item types, reports, and dashboards, teams have access to a set of shared work item queries to track information, analyze progress, and make decisions. Teams plan their project by capturing features and requirements. A work item is a TFS database record that contains the definition, assignment, priority, and state of work.

Visual Studio ALM - Requirements Overview Report (CMMI) The Requirements Overview report lists all requirements, filtered by area and iteration and in order of importance. For information about how to open this report, refresh the data, or manage reports, see Reports (SQL Server Reporting Services). Required Permissions To view the report, you must be assigned or belong to a group that has been assigned the Browser role in Reporting Services. The Requirements Overview report presents a snapshot of the work that has been performed for the filtered set of requirements to the current date, as the following illustration shows: This report displays the following information for each user story that it lists: Work Progress % Hours Completed: A numeric value and visual representation that shows the percentage of completed work based on the rollup of baseline and completed hours for all tasks that are linked to the requirement or its child requirements. Test Status Requirements appear in order of their importance, based on their assigned ranking.

Visual Studio ALM - Plan Manual Tests using Team Web Access Create test plans to track manual testing for sprints or milestones. That way you can see when the testing for a specific sprint or milestone is complete. With TFS 2013 Update 3, you can customize test plans and suites. For example, add an extra field to identify the reviewer for a test plan, or change the default values for the state field to fit your process better. For additional changes introduced with TFS 2013.3, review the Q & A section. If you haven't already, create your team project and create your backlog. Now you've created a requirement-based test suite for each backlog item. A: If you are using on-premises TFS with TFS 2013 Update 3, you can edit the properties of test plans and test suites from Team Web Access or Microsoft Test Manager (MTM). From the Test hub in Team Web Access, select a test plan or test suite and then open it. With Update 3 for MTM and TFS 2013 Update 3 installed: You can edit the properties of the work item from MTM too. A: Yes. A: Yes. A: Yes. A: Yes.

Related: