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]
31. August 2009
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]
30. August 2009
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 = 'http://www.clemensreijnen.nl/post/Soma-on-Architecture-Toolse280a6.aspx'; var dzone_title = 'Soma on Architecture Tools…'; var dzone_blurb = 'Soma on Architecture Tools…'; var dzone_style = '2';
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]
26. August 2009
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 = 'http://www.clemensreijnen.nl/post/MSDN-VSTS2010-doce28099s-Modeling-User-Requirements.aspx'; var dzone_title = 'MSDN VSTS2010 doc’s - Modeling User Requirements'; var dzone_blurb = 'MSD... [More]
25. August 2009
ALM , TMap
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 timevar dzone_url = 'http://www.clemensreijnen.nl/post/TMap-Process-Template-for-VSTS2010-e28093-Short-Version.aspx'; var dzone_title = 'TMap Process Template for VSTS2010 – S... [More]
This is an update of the work we have been doing regarding TMap [a widely adopted test approach] and VSTS2010. With the release of Beta1 of VSTS2010 we’ve started to build a TMap test process template. This 38 minutes video recording [silverlight] is an overview of this work in progress. Feel free to give us any kind of feedback, by using the comment form or by sending a mail directly at Clemens dot Reijnen at Sogeti dot nl and introduction story can be found here.
WMV [127 Mb]
Zune [66 Mb]
IPod [59 Mb]
just for fun… This is an architecture diagram from the TeamArchitect.Modelstore.Interfaces… impressive vsts2010 can render such a diagram. But, also useless for analyzing, although…. It looks like a swarm and there are some theories how these swarms behave… for example this article “The Genius of Swarms” or wiki’s explanation of the swarm theory… Swarm intelligence (SI) is a type of artificial intelligence based on the collective behavior of decentralized, self-organized systems. So, the TeamArchitect.Modelstore.Interfaces has some kind of intelligence, a collective behavior. The Swarm Theory is also connected with Chaos Theory and that one with The Lorenz attractor, ... [More]
3. July 2009
ALM , TMap , VS2010
As probably everybody already know, Microsoft is going to deliver a toolset for the tester with Visual Studio Team System 2010. If you didn’t know this, you can start by reading several previous posts on this blog, on Rob’s blog or on Bing. It’s not only going to support development testing or system testing but the whole stack of the testing practice including acceptance testing [manual testing].
This support for all the different test tasks by VSTS 2010, combined with the power of TFS 2010 to guide processes and Sogeti’s method for structured software testing ‘TMap’ is a major win to the application lifecycle. To get this structured software... [More]
Nice article by Gartner and fits partly in the presentation Edward and I gave yesterday for SDN; having guidance in VSTS2010 for you design and architecture process as I call it “Collaborative Knowledge Sharing and Decision Making”… These are the Key Findings of the report, its interesting to read them with software architecture process in mind: CDM is a category of decision support system for nonroutine, complex decisions that require iterative human interactions. Social software extends the collaborative decision-making process by allowing decision makers to discuss an issue, "brainstorm" options, evaluate their pros and cons, and agree on a course of act... [More]