when move from UML to DSL and what about use case
Hi
I have been using RUP for 4 years, and one thing that I am used to, is the diagrams, especially use case, secuence and class diagrams, I want to keep this diagrams because I found they very useful, use case diagrams allow me to see the scope, and the design diagrams allow me to see what developers want to do before they write some code, so, I have questions about how I could still use them in MSF and VSTS tools
1. Why use scenarios if I have use case that is composed for all the scenarios?
2. Scenarios going to be allways the standar or this going to change in the future? 3. How I keep traceability between my use case and the work items?
4. when i should leave UML and move to DSL ?
5. Should I give maintenance to design diagrams in UML ?
Victor Hugo Pozo
MCAD .Net
MCP SQL Server 2000
Guayaquil - Ecuador
Hi Hugo,
In an agile world, scenarios are a better fit for short iterations because they are smaller chunks of functionality and easier to manage. Shorter releases are better because they allow for more frequent customer feedback. However, use cases and scenarios are closely related (as I am sure that you are aware). Scenarios are a single path through a use case. A use case collects multiple paths. The way to obtain traceability is by attaching your use case descriptions to the scenario work item.
By the way, you could create a use case work item. Check out the DSL work going on. Move from UML to DSLs when you feel comfortable that they meet your needs. Your code and models should stay synchronized through tooling. Our class diagrams reflect the code.
Randy
I've been trying to reconcile UML use cases with Team System scenarios and it seems like these points are relevant:
(1) Use cases represent a piece of functionality with many paths through them and TS scenarios are clearly stated to be a single unique path, so for a use case you have many TS scenarios,
(2) Use case diagrams allow "include" and "extend" relationships which allow you to show decomposition of requirements nicely (which you don't have with TS scenarios), then when you define the scenarios for the lowest level use cases, they become TS scenario work items.
(3) How do you tie your scenarios in Team System to your Visio UML use cases? You could attach the Visio files of course, but I reckon it's a good idea to use part of your project structure (Area path) to represent your use case functional breakdown tree, then you can set the area path in your scenario to link to your use case in this way.
What do people think of this?
