I'm looking for a way to add traceability to a model that I'm currently working on and would like to get your advice on the best approach. In essence, I want to be able to be able to associate individual requirements to pieces of code that will satisfy that requirement. Here are a couple of approaches that I came up with, but I'm curious about what other people do.
1. Create a "Traceable" stereotype and tagged values for "requirement-id" and "requirement-href" and associate it with anything that is traceable. The requirement id would be a static human-readable id, and the requirement-href would be the id that ArgoUML automatically assigns to model elements. 2. Use the "see" field in the Documentation tab to link to specific use-case objects in the xmi document. Something like " myproject.xmi#requirement.id=1234". Currently my use cases have a special tagged value called "requirement id" and this is just a reference to that id. I haven't figured out any way to create arbitrary associations between use cases and classes or methods, but I've seen this capability in other tools. Is there a way to do this in ArgoUML? Are there any other ways of adding traceability? Regards, Mark Fortner
