Track changes in requirements

[Zatak]

I have a Use case [User Login] which has some activity diagrams like [Database Login] and [Windows Authorisation].

Now after some months the business wants changes to the [Database Login] activity diagram.
How do I track this change in activity diagram.

This change can be in an activity diagram or a requirement etc. How can this be tracked?

Any suggestions welcome.

[thomaskilian]

Depends on what purpose this change shall be tracked. So I can only guess some answers:
- Make a note and place it inside the diagram. Write in plain words: Change - blabla. Color the note to make it obvious. This is recommended to make people aware of a recent change. The note would normally vanish after some time.
- Use souce code control to track changes over time. You will be able to go back to a former version at any time.
- Keep a "History" package. You can make use of version numbers or dates. The disadvantage would be that you have many instances of the same thing and might get confused.

Maybe you could indicate what's the real purpose of this tracking.

[jaimeglz]

Hi Zatak,

Here is another possible solution.

Under the package that contains your use cases, or even as a high-level package in your model, you can create a package called "Model evolution", or whatever seems appropriate. In that package, you can create a diagram for your particular package or use case, where you will relate the old package (or the old use case, activity, or whatever...) with the new one. UML has the <<trace>> dependency relationship stereotype, which is defined by Rumbaugh as "a dependency that indicates a historical relationship between two elements...".

Keep the old elements in the "Model evolution" package, and place the new behaviour elements in your use case (or whatever) model. You can now create a matrix with the dependencies between the old and the new, and keep a very neat history of your model evolution.

Hope this helps,

Jaime