1. Figure 3.1 Basic version control. © 2003 Crnkovic, Asklund, Persson Dahlqvist, ”Implementing and Integrating Product Data Management and Software Configuration Management” 1.41.51.62.0 2.1 1.5.1.1 1.5.2.1 1.5.2.2 1.4.1.1 1.4.1.2 1.4.1.3 Branch name: Main Bug-fix 1 Bug-fix 2 Macintosh-branch Release 2.3 Release 2.4 Label Temporary branches Permanent branch Revisions

2. Figure 3.2 A bound configuration can be defined by tagging all files with the same label. © 2003 Crnkovic, Asklund, Persson Dahlqvist, ”Implementing and Integrating Product Data Management and Software Configuration Management” Version Release 1.92.02.12.2 Item A Item B Item C Product 2.22.3 2.7 2.8 2.03.1 2.1 2.2 2.3 2.2 2.3 Build/Make 3.0 2.2

3. Figure 3.3 Developers use different configurations concurrently. © 2003 Crnkovic, Asklund, Persson Dahlqvist, ”Implementing and Integrating Product Data Management and Software Configuration Management” Time now 2.6 2.7 3.0 3.1 4.0 2.7.1.1 2.7.2.1 2.7.2.2 2.6.1.1 2.6.1.2 2.6.1.3 Branch Product -Bug-fix 1 -Bug-fix 2 -External release 2.3 Item A Item B Item C -Bugfix 1 Item D -Bugfix 2 -Maintenance Rel 2.3 Stable Rel. 2.3.0 Rel. 2.3.1 1.2 1.3 2.0 Rel. 2.3 1.1 1.2 5.0 1.1 Stable 1.1.1.1 4.2.1.2 4.2 4.3 4.2.1.1 Rel. 2.3Stable Rel. 2.3Stable Rel. 2.3 Stable 4.2.2.1 4.2.2.2 4.2.2.3 Version Planned Label Version Label Established Item\VersionRelese 2.3.0 StableLatest Product2.6.1.13.03.1 Item A1.2 1.3 Item B1.1 Item C1.11.1.1.11.2 Item D4.2.2.14.3

4. Figure 3.4 Replication of repositories. © 2003 Crnkovic, Asklund, Persson Dahlqvist, ”Implementing and Integrating Product Data Management and Software Configuration Management” Site A Main branch owned by site A Bug-fix branch owned by site B 1.0 Main 1.1 1.2 2.0 1.1.1.1 1.1.1.2 1.1.1.3 Bug-fix Main Bug-fix Site B Updates automati- cally sent between replicas to keep them synchronized Version 2 not yet sent to the other replicas 1.0 1.1 1.2 2.0 1.1.1.1 1.1.1.2

5. Figure 3.5 An example of a CR process. © 2003 Crnkovic, Asklund, Persson Dahlqvist, ”Implementing and Integrating Product Data Management and Software Configuration Management” Change proposal Document EvaluateDisapproveApprove Implement Verify

6. Figure 3.6 From a CR, it is easy to see which files have been changed (what version has been created) due to the CR. For a specific version of an item, it is also easy to see why this version was created, due to which CR. © 2003 Crnkovic, Asklund, Persson Dahlqvist, ”Implementing and Integrating Product Data Management and Software Configuration Management”

7. Figure 3.7 As part of the release notes, all CRs implemented between the last and the new release are listed. From these CRs, the actual changes made can be traced as depicted in Figure 3.6. © 2003 Crnkovic, Asklund, Persson Dahlqvist, ”Implementing and Integrating Product Data Management and Software Configuration Management” Release Notes JavaTM 2 SDK, Standard Edition Version 1.2.2 FileDialog always shows English word "All Files (*.*) in all countries. 4152317 Drag Enter/Exit events not reported correctly on Solaris 4017222 Dialog.setResizable(false) does not work. 4115213 Deadlock between modal dialog and Container.add() 4119383 DEFAULT_CURSOR has different semantic on Solaris and Win32 4111379 CustomCursor only shows black and white colors 4106384 Cursor setting still not works properly 4160474 Container.trackMouseEnterExit leaks memory 4193022 Component.printAll() passes invalid Graphics object 4212564 Color float constructor should round (?) 4139978 Can't set cursor in JPanel or JComponent 41t1t4073 Button background color inheriting from frame 4148334 AltGr keys are not working in Components (Swing, JBCL, AWT) 4122687 AWT ScrollPane Paint Problem 4160721 Synopsis CR_ID Change Requests Fixed