How to insert requirement into a use case?

[linhndt]

Hi All,

I'm a new bie with EA. Is there anybody help me?

A use case definition includes:

- Scenario
- Business rule specification
- Others ...

When I draw use case diagram with EA, I can right-click on a use case to open its properties. Then click Scenario tab. At there, I think I can insert use case scenario. But there're three type of scenario: Alternative, Basic Path, and Simple.

1. I don't know what simple is. Reflect it with a use case's information, what is it?

2. How can I manage version for a use case with EA?

3. Where could I specify business rule in a use case's properties?

4. Does EA support to generate a use case specification into .doc document, or other file types...?  

Thanks,

[Jan ´Bary´ Glas]

1. I don't know what simple is. Reflect it with a use case's information, what is it?

EA has a lot of features that are supposed for a specific use. Don't get annoyed and just ignore them. If your methodology specifies Basic and Alternate flows only, you may delete it in Settings > General Types > Scenarios for your project.

2. How can I manage version for a use case with EA?

Investigate on version control here in forum and in EA help.

3. Where could I specify business rule in a use case's properties?

EA use a specific Requirement element. You may set a type "Business Rule". You see this in Require tab of a UC properties.

You may add such a business rule to an UC also just by dragging it from Project Browser and dropping it onto the element.

4. Does EA support to generate a use case specification into .doc document, or other file types...?  

Is RTF enough? MS Words supports this format. I recommend using a .doc document with links into .rtf documents.

[bioform]

Lot of questions there...

I will give you some advice on the first...

First in EA requirements can be modeled two ways... as internal responsibilites of the UML object (thus the requirements tab), or as an external requirement object (NOT really a UML object, just an EA construct that is VERY helpful.)

If a requirement is "internal" to the UML object, then it would inherit the phase/version value of the UML object and have the same status as the UML object too. While an external requirement would have it's OWN status and phase/version value.

So which way do you want to go?

I define internal requirements for the UC when I KNOW that they will be included in the release of that's UC functionality (e.g., Version number), When I know that the requirement is for a future release (or one that is TBD) and is specific to this UC. I define it within the UC, then use the "Move External" feature to have EA create it as a separate requirement, that is automatically linked to the UC (saves ME some steps that way!)

If a requirement will apply more than one UML object, then I define it as an external requirement, and create the necessary associations to the objects (usually realizations or traces for a requirement)

Another thing to examine is the "Change" object which I make use of for our "Change Control Board" activities. I document the proposed/requested change in it, then associate the impacted objects (UC, Classes, External requirements, UIs, etc.) VERY powerful approach to managing "Changes" in the model that affect the baseline(s)