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 number is added because they also get shown in the model explorer, two shapes with the same name isn’t possible]
If you want these shapes to be the same, and not a copy, you need to drag and drop the shape from the model explorer on design surface of the new diagram.
The benefit of this is that now these model shapes are connected, changing the name of one [on the diagrams or the model explorer ] will automatically synchronize the other elements.
Another thing to pay attention to is the copy-past behavior between different model projects…. actually you can see it immediately when pasting in the diagram of the other modeling project, no number added. So you could think that the behavior is the same as drag and drop from the model explorer. But that isn’t the case, while adding an other modeling project also a new root is created in the model explorer. So, those two model elements are two different things. Drag and drop isn’t possible between model projects.
If you do want to re-use mode elements in a different modeling project, you can us the copy past functionality, which works really nice. But, you also can copy past the content of the modeldefinition file to the other project. Don’t think that is the way to go… but it works, it also reminds the relationships between the elements. You could create a default package every project needs to us…
Soma on Architecture Tools…
Nice overview post on the Architecture Tools by Somarsegar. He uses some new bits for the images of the diagrams.
![y1pOvtjHPmcumaRA19YyvZNqNMPEGS3pYwfHuGvpDSmLZD0qqaJMpSF-VGysgRU-WIfWuR45LcB29n3I0V8bNJxAg[1]](http://www.clemensreijnen.nl/image.axd?picture=WindowsLiveWriter/SomaonArchitectureToolsandthelittledevil/66F49082/y1pOvtjHPmcumaRA19YyvZNqNMPEGS3pYwfHuGvpDSmLZD0qqaJMpSFVGysgRUWIfWuR45LcB29n3I0V8bNJxAg1_thumb.png "y1pOvtjHPmcumaRA19YyvZNqNMPEGS3pYwfHuGvpDSmLZD0qqaJMpSF-VGysgRU-WIfWuR45LcB29n3I0V8bNJxAg[1]")
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 :-)
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 exploratory testing.
- Focus on automation.
- Repeatability is a key success factor, frequent testing.
- Pair testing.
Tool and processes support should focus on these characteristics. At this moment the tool support with VSTS 2010 for the tester is getting really mature [see this post]. So, beside the agile support for the developer like TDD, refactoring, continuous builds, guidance and many other things [see this post and image below].
Also the tester wants / needs this kind of support, beside an easy connection with all the capabilities developers have he needs the capabilities to execute his work in an agile team…
So, what practices needs to be in place for the tester within a VSTS 2010 agile project? just randomly start using the offered tools isn’t the right direction. In the coming posts I will capture some thoughts, practices and lessons learned from around the world…
As a start some useful agile testing links:
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]
TMap Process Template for VSTS2010 – Short Version
Got way too much comments on the length of the TMap process template ‘overview’ video, I know 38 minutes is long for listing to me, my wife even can hold it for 38 seconds, wen I start talking about my work ;-). So, I made a ‘community cut’, a shorter version with only the highlights of the extended version…
I’ll keep the YouTube constrains for other video’s, max 10 minutes. [post a comment if that's even too long]
just saw that the end is a bit strange/ abrupt, don’t know what went wrong, will change it on a latter time