Hi,
For my current project, I will need a Versionable stereotype. I want=
to=20
discuss with you guys the need, requirements and implementation of th=
is=20
stereotype before we start designing and implementing it.
The need would be to keep a history of the modifications that are mad=
e=20
to an entity. For example, if I have a Product class that is=20
stereotyped with "Versionable". If someone (Bob) creates a Product=
=20
instance named Orange, an entry should be entered in the ProductVersi=
ons=20
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=
=20
implement but we can add it later on
For the implementation, it would be the equivalent to having an=20
aggregation between the Product and ProductVersions classes. Now do =
we=20
want to modify the XMI before the compilation of the UML or do we wan=
t=20
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=20
automatically update the ProductVersions table. Furthermore, in my=
=20
opinion, the history should not be in the editable forms but should=
=20
appear in the views.
Lets have a discussion on this before we start implementing,
Fran=E7ois
|
