Hi,
For my current project, I will need a Versionable stereotype. I want to
discuss with you guys the need, requirements and implementation of this
stereotype before we start designing and implementing it.
The need would be to keep a history of the modifications that are made
to an entity. For example, if I have a Product class that is
stereotyped with "Versionable". If someone (Bob) creates a Product
instance named Orange, an entry should be entered in the ProductVersions
stating:
- Type of modification (in this case creation)
- Who made the modification (Bob)
- Time of modification (timestamp)
- ?? What was modified: for now this seems a little complicated to
implement but we can add it later on
For the implementation, it would be the equivalent to having an
aggregation between the Product and ProductVersions classes. Now do we
want to modify the XMI before the compilation of the UML or do we want
to add it in the generation process, that we need to discuss.
Obviously we will also need to add logic in the web and business tier to
automatically update the ProductVersions table. Furthermore, in my
opinion, the history should not be in the editable forms but should
appear in the views.
Lets have a discussion on this before we start implementing,
François
-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid0944&bid$1720&dat1642
_______________________________________________
Mdarad-toolbox-devs mailing list
Mdarad-toolbox-devs@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mdarad-toolbox-devs
