How to keep you fingers on the keyboard within VSTS 2010 Architecture Edition

Keyboard junkies have a hard time with all that dragging and dropping of shapes and connectors around within VSTS 2010. So here are some tips for these junkies how to keep you fingers on the keyboard. New default DSL Tools behavior… Adding shapes to the design surface allows you to directly start typing, for example after adding a class shape to the design surface lets you start typing the class name. Hitting 'Enter’ will confirm the value and F2 lets you edit it again. More interesting, in the compartments of the class shape hitting Enter twice adds an attribute or operation.  So, type a name for an attribute, hit Enter to confirm the value and hit Enter again for adding a new att... [More]

SDL ‘Merged’ Process Template White Paper.

The SDL group just released a paper which describes the steps [seven easy steps] you need to take to merge the SDL specific process items with your existing process template. Two New Security Tools for your SDL tool belt (Bonus: a “7-easy-steps” whitepaper) Very nice work… Hopeful we get in the future the possibilities to merge process templates in a less manual way, but this works. The steps described in this paper are based on unfold process template so you have to take this steps for every new project you create. An other way to merge template is by providing the XML and manually merge it with your existing template. A possibility described in this post “VSTS 2010 TMap Process Temp... [More]

03: Agile Testing Business Whitepaper.

My colleague's in Ireland wrote a great paper about Agile Testing practices… ‘ At its heart, agile is all about quality and focusing on the customer. Testing therefore has a significant role to play within an agile development environment and can actually strengthen the output of the process.’   Part 00: Agile Testing with VSTS 2010 and TMap Part 01: User Stories 02: Management, preserving and organization of manual test cases within VSTS 2010. 03: … this post 04: … [probably] 2.1 test case management practicesvar dzone_url = ''; var dzone_title = '03: Agile Testing Business Whitepaper.'; ... [More]

02: Management, preserving and organization of manual test cases within VSTS 2010.

Part 00: Agile Testing with VSTS 2010 and TMap Part 01: User Stories [current post, removed the Agile Testing blablabla and part pre-fix] This post belongs to the series of “Agile Testing with VSTS 2010 and TMap” although this topic has a wider scope, in used software delivery methodology you have to think about test case management. A small introduction. First a small introduction to give some direction on the needs of test case management. The drawing below I made during a discussion with several TMap experts and explains how test cases are created and executed in a simple situation. From top to bottom and left to right. Teams start brainstorm o... [More]

Enrich VSTA 2010 Use case diagram with SketchFlow Screens

A use case diagram visualizes the interaction of an external user with your system. So, you can say that in many situations [cases] that there is a need for an user interface, a screen. Not that strange that RUP connects the user interface designer to use cases. [see image below at the bottom]   UML Type: Artifact Something every diagram has in VSTS 2010 is the UML type ‘Artifact’. With this type we can attach physical pieces of information to or diagrams. For example in this diagram below, I defined an artifact which points to a class file. [don’t think it very useful to associate C# class files with use cases.. but as an example] Some nice functionality of this ‘artifact’ sh... [More]

Agile Testing with VSTS 2010 and TMap: Part 01-User stories

Previous post: Part 00: Agile Testing with VSTS 2010 and TMap … [current post] User stories breakdown... This post is about the work breakdown of user stories during the planning phase of an iteration. [image from the documentation about VSTS 2010 on MSDN, this page] During the planning phase of the project, also called iteration 0 [first blue piece], user stories are collected / brainstormed / defined /… in VSTS this information is collected in the new work item type ‘user story’ [image below].   During the planning of the iteration developers the team start to breakdown the user stories [which are selected for that iteration] in implementation tasks. With... [More]

Copy-Past Modeling Diagrams and Modeling Elements within VSTS 2010

This is completely new for me… CTRL-A // CTRL-C ALT-TAB // CTRL-V It also works in other applications, even Outlook. This kind of functionality [copy past between models] was already written down in the DSL Tools Book [page 437]. Copy past between models is also possible, but than you have to look very careful what and how you do it. For example copy past within the same model create a model element with the same name with a number at the end. It’s interesting to look at the Model Explorer, also in that one there are shapes added with the same name. Now, copy pasting from one diagram to another diagram has the same behavior, modelelements are created with a number. [the numb... [More]

Soma on Architecture Tools…

Nice overview post on the Architecture Tools by Somarsegar. He uses some new bits for the images of the diagrams.   The layer diagram has two more menu item groupings [I like the custom items] and strange numbers in the shapes, curious what that is. Finally we have a nice overview how the Petshop application works :-)var dzone_url = ''; var dzone_title = 'Soma on Architecture Tools…'; var dzone_blurb = 'Soma on Architecture Tools…'; var dzone_style = '2';

Agile Testing with VSTS 2010 and TMap: Part 00

Part, because I’m planning several posts around this topic. 00, because this is the ‘setting the stage’ post… While in the Agile manifesto is written: “Individuals and interactions over processes and tools” I will cover in the coming posts information how individuals and there interactions are supported by tools and processes. Several characteristics of agile testing [in random order]. Lightweight implementation of tools and processes. Find bugs as early as possible. Don’t do things twice, just enough testing. Short feedback loops to the team. Customer involvement in writing tests. An iteration is ready when the tests succeed. There needs to be space for ... [More]

MSDN VSTS2010 doc’s - Modeling User Requirements

Have been reading all the MSDN documentation about VSTS2010 last few days and I’m amazed by the quality of this. So if you don’t have the bits installed, just take a look at MSDN to get a deep dive in the new functionalities of VSTS2010. This is a screenshot from the Team Architect doc’s about “Modeling User Requirements“…   and when you do have the bits installed, hit F1 sometimes… [I often forget that functionality] var dzone_url = ''; var dzone_title = 'MSDN VSTS2010 doc’s - Modeling User Requirements'; var dzone_blurb = 'MSD... [More]

Şarkı Sozleri