I am sure that there are people who use Scenarios and Use Cases while managing their requirements in DOORS. Is it useful to store Scenarios and Use Cases in DOORS? If so, what suggestions do you have for managing them in DOORS?
gregsittler - Sat Jan 21 16:44:28 EST 2012 |
|
Re: Use cases in DOORS
llandale - Sat Jan 21 17:58:02 EST 2012
It may be useful to manage those things outside of DOORS, and every week update a suragate DOORS module with the associated ID and some summary attributes. Other DOORS things like Requirements can then link to the "Use Case" and see enough information about it to be useful.
In order to update them you'd need to make sure your Scenarios and Use Cases all had their own unique expternal ID.
-Louie
|
|
Re: Use cases in DOORS
sammyc - Mon Jan 23 08:52:41 EST 2012
There are a couple of ways to do this in DOORS depending on your needs and style that will provide the right level of requirements capture for text based use cases or scenarios which are just another "type" of requirement.
You can define use cases with each requirement being a step or you can assign a requirement to an entire use case. There are other ways I've seen as well = if you want some examples of how they would look, send me a private msg and I'll send you some.
If you are trying to attach to use case diagrams to requirements, there are integrations to other modeling products or you can look at the DOORS Analyst modeling tool.
|
|
Re: Use cases in DOORS
SystemAdmin - Tue Feb 07 13:05:15 EST 2012 sammyc - Mon Jan 23 08:52:41 EST 2012
There are a couple of ways to do this in DOORS depending on your needs and style that will provide the right level of requirements capture for text based use cases or scenarios which are just another "type" of requirement.
You can define use cases with each requirement being a step or you can assign a requirement to an entire use case. There are other ways I've seen as well = if you want some examples of how they would look, send me a private msg and I'll send you some.
If you are trying to attach to use case diagrams to requirements, there are integrations to other modeling products or you can look at the DOORS Analyst modeling tool.
|
|
Re: Use cases in DOORS
Yanina - Tue Feb 21 09:49:54 EST 2012 sammyc - Mon Jan 23 08:52:41 EST 2012
There are a couple of ways to do this in DOORS depending on your needs and style that will provide the right level of requirements capture for text based use cases or scenarios which are just another "type" of requirement.
You can define use cases with each requirement being a step or you can assign a requirement to an entire use case. There are other ways I've seen as well = if you want some examples of how they would look, send me a private msg and I'll send you some.
If you are trying to attach to use case diagrams to requirements, there are integrations to other modeling products or you can look at the DOORS Analyst modeling tool.
Thanks,
Yanina Beyder
|
|
Re: Use cases in DOORS
adevicq - Tue Feb 21 11:09:14 EST 2012 Yanina - Tue Feb 21 09:49:54 EST 2012
Plese advide what is the best way for managing Use Cases in DOORS. If you have examples of Use Cases in DOORS - please share them with me. I really appreciate it.
Thanks,
Yanina Beyder
We use DOORS to document use cases. I have created a module template with specific DXL attributes. The module allows to:
-
describe all the standard information for a use case (objective, actors, pre condition, main course, alternate paths, post condition, miscellaneus rules)
-
auto number the steps in the main course
-
auto number the alternate paths depending on the step it is related to
-
...
We can easily link an element to a high level requirement.
We have views to display alternate paths as well as specific rules in front of the corresponding step.
I have built an export module to export use cases to MS Word.
Everything works pretty well (in some cases the developers use DOORS to read the requirements) although it has needed a lot of customization.
For the use case diagrams we import images from "star UML" or "modelio". Of cours diagrams and textual use cases are not really linked together...
Alain
|
|
Re: Use cases in DOORS
Yanina - Tue Feb 21 14:09:35 EST 2012 adevicq - Tue Feb 21 11:09:14 EST 2012
Hi,
We use DOORS to document use cases. I have created a module template with specific DXL attributes. The module allows to:
-
describe all the standard information for a use case (objective, actors, pre condition, main course, alternate paths, post condition, miscellaneus rules)
-
auto number the steps in the main course
-
auto number the alternate paths depending on the step it is related to
-
...
We can easily link an element to a high level requirement.
We have views to display alternate paths as well as specific rules in front of the corresponding step.
I have built an export module to export use cases to MS Word.
Everything works pretty well (in some cases the developers use DOORS to read the requirements) although it has needed a lot of customization.
For the use case diagrams we import images from "star UML" or "modelio". Of cours diagrams and textual use cases are not really linked together...
Alain
Thank you so much for the info. Seems that it works very well for you - but with heavy customization. We are looking now for a simple solution to avoid customization because we are in the process of transitioning from DOORS to Serena RM. I am looking for a temporary simple solution without any customization.
Regards,
Yanina
|
|
Re: Use cases in DOORS
sammyc - Tue Feb 21 14:20:53 EST 2012 Yanina - Tue Feb 21 09:49:54 EST 2012
Plese advide what is the best way for managing Use Cases in DOORS. If you have examples of Use Cases in DOORS - please share them with me. I really appreciate it.
Thanks,
Yanina Beyder
Sam
|
|