Commit cfa2b624 authored by Bernhard Rumpe's avatar Bernhard Rumpe
Browse files

BR

parent 35dbfae0
Checklist
=========
Creation time: 07.11.2013, 14:53
Old model: core, revision 213
New model: core, revision 276
Found model differences:
------------------------
- Added class de.test.ECU
- Deleted class de.OtherTest
- Deleted class de.YetOtherTest
- For class de.test.Script:
- Added association (0:*) childScripts to class de.test.Script
- Renamed attribute de.FurtherTest#filePath to path
Used impact rules:
- XML migration analysis
- ORM file analysis
- Property file analysis
- Changelog analysis
XML migration analysis:
======================
This rule checks whether it is necessary to implement XML migration classes.
This activity is necessary if ...
- Implement XML migration class for class 'de.Test':
- Reason: Deleted class 'de.OtherTest'
- Reason: Deleted class 'de.YetOtherTest'
Proposed XML migration class:
public class ConvertTest implements IConverter {
public void convert(Document pDocument) {
//Implementation not shown here
}
}
ORM file analysis:
==================
This rule checks whether it is necessary to change a ORM file due to model changes.
The change operations on the ORM file consider the ORM file located at ... in this case.
- Add entry to mapping file for new class. (Reason: Added class 'de.test.ECU')
- Rename entry in mapping file. Excerpt from file:
<package name="de">
<!-- other entries for de -->
<class name="FurtherTest" ...>
<field name="filePath" .../>
<!-- further fields -->
</class>
</package>
(Reason: Renamed attribute de.FurtherTest#filePath to path)
//The simplified impact rule shown in the paper does not create these further hints:
- Add entry to mapping file for new association. (Reason: Added association (0:*)
childScripts to class de.test.Script).
- Delete entry from mapping file for deleted class. (Reason: Deleted class 'de.OtherTest')
- Delete entry from mapping file for deleted class. (Reason: Deleted class 'de.YetOtherTest')
Property file analysis:
=======================
This rule checks whether new entries have to be added to properties files,
have to be deleted from properties files or have to be updated in properties files...
- Add these entries to the property file core.properties:
- ECU (Reason: Added class ’de.test.ECU’)
- ECUS (Reason: Added class ’de.test.ECU’)
- SCRIPT_CHILDSCRIPTS (Reason: Added association (0:*) childScripts to class de.test.Script)
- ...
- Delete these entries from the properties file core.properties:
- OTHERTEST (Reason: Deleted class ’de.OtherTest’)
- OTHERTEST (Reason: Deleted class ’de.OtherTest’)
- ...
It was detected that elements were renamed. If elements are renamed, then the property file
might already contain values for the keys that belong to the original element:
- Add entry for key FURTHERTEST_PATH. Check whether entry FURTHERTEST_FILEPATH already
exists. You might take the associated value for FURTHERTEST_PATH.
//The following impact rule was not introduced in the paper.
//In Authoring, so-called changelog files exist for all UML
//class diagrams used for generation purposes. These capture in
//which way the UML class diagrams were changed in the past
//and they provide a simple means to comprehend the model evolution.
//This impact rule simply suggests that the changelog has to be
//modified due to identified model differences. Furthermore, it
//proposes a textual representation of the entries that
//should be added to the changelog.
Changelog analysis:
======================
This rule checks whether new entries have to be added to the changelog file.
- Take the following textual description of the identified model differences and copy
it to the changelog file.
- Added class de.test.ECU
- Deleted class de.OtherTest
- Deleted class de.YetOtherTest
- For class de.test.Script:
- Added association (0:*) childScripts to class de.test.Script
- Renamed attribute de.FurtherTest#filePath to path
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment