Relating features to requirements

[Glassboy]

I've been reading the help and looking at the example models but there doesn't seem to be an example that shows the relationships generally used to join a feature to a requirement.  (Not to mention issues and risks).

http://www.sparxsystems.com/enterprise_architect_user_guide/13.5/model_domains/feature.html

What's the optimal?  And does it work well with the relationship matrix?

[qwerty]

I usually use <<trace>> relations from features to requirements. Though I have not used it with the RM there should not be any issue (but that could be <<trace>>d in another dimension).

q.

[Helmut Ortmann]

Hello,

from my experience traceability and relationship-matrix works well. You may use the <<trace>> stereotype as qwerty mentioned. But any other or self-defined stereotype works as well.

With EA you can link almost everything together. The only limits are your imagination.

If you work a lot or with a team in this area it would be a good idea to standardize your method and use a MDG to support your types (stereotypes and tagged values) like features or so. You have to define the stereotypes as meta-types to use them in a Relationship Matrix.

There are two other features worth looking after:
- Charts (for metrics, versatile)
- ModelViews to visualize as free definable table (arbitrary complex, also for metrics)

Best regards,

Helmut

[Glassboy]

With EA you can link almost everything together. The only limits are your imagination.

Well obviously but I've been watching the toolbox grow on the requirements diagram and it looks there is a "method to the madness" that isn't being reflected in the help pages or in the sample models.  There was always a chance someone here had more of a clue than I do.