1. Update and Version Management1 Klaus Bothe 3rd Workshop Software Engineering Education and Reverse Engineering, Ohrid, Macedonia, 2003 Institute of Informatics, Humboldt University – Berlin, Germany, bothe@informatik.hu-berlin.de Joint Course on Software Engineering

2. Update and Version Management2 Joint Course on Software Engineering Update management Version: 14 July 2003-07-14 Author: Klaus Bothe 1.Unique current topic files: For each topic, there is only one current ppt slide file which is located at the SE education website of HU. 2.Only one modifier of a topic file at one moment: At one moment, only one party is allowed to modify the current topic file. 3.Technical modification procedure: Agreement of a topic modification between the modifier and the project manager. The current topic file has to be marked by “in update by ‘modifier’ s name’” (done by the website administrator). After the modification, the website administrator physically exchanges the old current topic file by the modified current topic file. Joint Course on Software Engineering Update management Version: 14 July 2003-07-14 Author: Klaus Bothe 1.Unique current topic files: For each topic, there is only one current ppt slide file which is located at the SE education website of HU. 2.Only one modifier of a topic file at one moment: At one moment, only one party is allowed to modify the current topic file. 3.Technical modification procedure: Agreement of a topic modification between the modifier and the project manager. The current topic file has to be marked by “in update by ‘modifier’ s name’” (done by the website administrator). After the modification, the website administrator physically exchanges the old current topic file by the modified current topic file.

3. Update and Version Management3 4. Save old topic versions: Two old topic versions should be saved by the website administrator (Should they also be accessable from the SE website by a link?). 5.Version identification: A version has to be be uniquely identified by its date (on the title slide of the topic). 6.Documentation of modifications: The lecture notes of the title slide have to capture all (important) modifications with respect to the previous version. Reference to a modified slide should be done by its slide number and its slide title (slide numbers can change, slide titles should be unique). 7. Release intervals: To have a common basis of discussion, versions should not be released so often (each some months, half a year). 4. Save old topic versions: Two old topic versions should be saved by the website administrator (Should they also be accessable from the SE website by a link?). 5.Version identification: A version has to be be uniquely identified by its date (on the title slide of the topic). 6.Documentation of modifications: The lecture notes of the title slide have to capture all (important) modifications with respect to the previous version. Reference to a modified slide should be done by its slide number and its slide title (slide numbers can change, slide titles should be unique). 7. Release intervals: To have a common basis of discussion, versions should not be released so often (each some months, half a year).

4. Update and Version Management4 1.Unique current topic files Joint Course Website Topic 5 Topic 5c Topic 5b Topic 5a personal copy current topic file ^_^ updates

5. Update and Version Management5 2. Only one modifier of a topic file at one moment Joint Course Website Topic 5 Topic 5c Topic 5b Topic 5a personal copy current topic file ^_^ current topic file in modification ^_^ modifier A

6. Update and Version Management6 3. Technical modification procedure Joint Course Website Topic 5 Topic 5a current topic file ^_^ modifier A current topic file in modification ^_^ website administrator project manager step 1: agreement in update by A step 2b: mark topic step 2a: request step 3a: modification finished step 3b: exchange Topic 5 by Topic 5a

7. Update and Version Management7 4. Save old topic versions: Two old topic versions should be saved by the website administrator (Should they also be accessable from the SE website by a link?). 5.Version identification: A version has to be be uniquely identified by its date (on the title slide of the topic). 6.Documentation of modifications: The lecture notes of the title slide have to capture all (important) modifications with respect to the previous version. Reference to a modified slide should be done by its slide number and its slide title (slide numbers can change, slide titles should be unique). 7. Release intervals: To have a common basis of discussion, versions should not be released so often (each some months, half a year). 4. Save old topic versions: Two old topic versions should be saved by the website administrator (Should they also be accessable from the SE website by a link?). 5.Version identification: A version has to be be uniquely identified by its date (on the title slide of the topic). 6.Documentation of modifications: The lecture notes of the title slide have to capture all (important) modifications with respect to the previous version. Reference to a modified slide should be done by its slide number and its slide title (slide numbers can change, slide titles should be unique). 7. Release intervals: To have a common basis of discussion, versions should not be released so often (each some months, half a year).

8. Update and Version Management8 Flexibility: the current topic file in modification can move Joint Course Website Topic 5 Topic 5c Topic 5b Topic 5a personal copy current topic file ^_^ modifier current topic file in modification new modifier current topic file in modification 5a

9. Update and Version Management9 Update management: dependence on the topic maturity and topic usage (1) Development phase: a lot of errors and shortages of the material only a few lectures based on the material recommendations for improvements will come only from a few parties  the update process is easy to coordinate

10. Update and Version Management10 Update management: dependence on the topic maturity and topic usage (2) Consolidation phase: more stable versions several parallel lectures recommendations for improvements will come from different parties  the update process has to be coordinated more carefully Review reports: collect remarks and suggestions There is no full-time job person that can immediatly modify the topic according to the remarks and suggestions.

11. Update and Version Management11 Use of review reports for the update management Joint Course Website Topic 5 Topic 5c Topic 5b Topic 5a ^_^ Review report Modifications of topic 5 have to be agreed between the review report authors and the project manager Proposals for new slides