Requirements Diagram

[edusem]

I'm trying to use requirements captured using Volere's Snow Card into an EA requirements diagram.  
A typical requirement in Volere has  the following fields (in bold in this example):

Requirement Name: UI20
Requirement type: X:1
Use-case #: 1, 2, 3, 4, 5, and 6
Description: The user interface should use
pastel colors.
Rationale: This will be soothing to the eyes and
will look formal.
Source: Ivan Banks, accounting manager
Daisy Brown, HR director
Fit criterion: The colors used in the user
interface must use a combination of pastel
shades provided in the Microsoft Windows
environment.
Customer satisfaction: 5
Customer dissatisfaction: 4
Dependencies: All the requirements referring to
the user interface.
Conflicts: None
Supporting materials: None
History: Created July 3, 2007

In EA, for e/a requirement I can easily define the requirement Name, Type,  Description: (under notes), History (with date created and/or versioning) and Supporting materials (from the file tab).

Any ideas how to handle the other fields?

Use-case #  -  how can I reference (link) these for the requirement?
Rationale
Source
Fit criterion
Customer satisfaction/dissatisfaction:
Dependencies
Conflicts
[/list]

Any suggestions would be greatly appreciated,

Ed.

[thomas.kilian]

Simply use Tagged Values. That's exactly what they are designed for. You can use Depedency (optional <<trace>>) links where applicable.

[Torsten Binias]

Hi Ed,

I would use Dependencies for dependencies and use cases (if you have modelled your use cases).

SysML suggests a comment with stereotype "Rationale" but i've never used it and don't feel too comfortable with it.

Concerning the other attributes I can theoretically define your own properties:

A standard requirement includes properties to specify its unique identifier and text requirement. Additional properties such as verification status, can be specified by the user.

Source: OMG SysML, Version 1.0 (formal/07-09-01), page 141

Unfortunately I have no idea how to do this with EA.

Best regards,
Torsten

[thomas.kilian]

SysML suggests a comment with stereotype "Rationale" but i've never used it and don't feel too comfortable with it.

How would you stereotype a comment (note) with EA? I haven't looked through Superstructures but is this mentioned there at any place?

[jfzouain]

Why don't you look at RaQuest, is an add-on for EA.
I think this will let you do what you want.

[Torsten Binias]

Hello abcde,

How would you stereotype a comment (note) with EA?

You can start your note with "<<rationale>>".
Alternatively you can try the AddIn for SysML (http://www.sparxsystems.com/products/mdg_sysml.html) but I don't know if it supports the stereotype.

I haven't looked through Superstructures but is this mentioned there at any place?

I guess it is as much mentioned as the possibility to set a sterotype for classes and relationships. ;-)

Best regards,
Torsten

[thomas.kilian]

Ooops. EAUI hit again.  Of course there is the properties pane where you can set the sterotype. Dbl-click only shows the notes text. Sometimes that really sucks...