If you Google "uml traceability" (without the quotes), you'll come up
with some hits for how others like IBM and Sparx's Enterprise
Architect do this stuff.  One of the things that will be immediately
obvious is that they have much higher levels of support for this type
of stuff.  We've got all the basic building blocks that you'd need to
do this, but you have to roll your own conventions and process instead
of having something that you can use off the shelf.

In addition to the Trace relationship that I mentioned before, you can
also Derived and Refine relationships as well as a number of other UML
elements to do traceability.

BTW, the UML Standard Elements profile exists in ArgoUML 0.24 as well,
it's just merged in with the Java profile and the ArgoUML specific
profile into one big profile that's not easily changeable.  What's new
in 0.26 is more sophisticated management facilities which allow you to
do things like easily select C++ or Java profiles or just use the
standard UML profile, as well as to add your own profiles to the mix.

Tom

On Fri, Sep 19, 2008 at 1:15 PM, Mark Fortner <[EMAIL PROTECTED]> wrote:
> I was playing around with the Profiles in the latest beta release, and
> wanted to be able to apply a "requirement" stereotype to a use case, but it
> seems as though this is only possible with comments.  How is this supposed
> to work?  Are you supposed to comment use cases, and then assign the
> stereotype to the comment? Can you then associate the same "requirement"
> comment to any node (class, state, etc) to capture traceability?
>
> Also, there doesn't seem to be any tags associated with requirements to
> allow you to capture the requirement ID.  Is there some other way of
> capturing the requirement ID?
>
> Regards,
>
> Mark Fortner
>

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to