1. Common Usage Model Using ClearCase and a change process

2. Workspace (View) Displays Associate Project Work Profile (View Profile) Contains Uses Baselines (Label) Selects Has Structural Overview System Subsystem (VOB) Contains Configuration Item (Element) Version Contains Has

3. Role map  Project Manager  Architect  Configuration Manager  Any designer  System Integrator  (Build maestro, Release Manager)  Test (Test Manager, Designer)  Project Manager  Architect  Configuration Manager  Any designer  System Integrator  (Build maestro, Release Manager)  Test (Test Manager, Designer)

4. Project Manager

5. Architect

6. Configuration Manager IEEE SEI Rational Unified Process

7. CM - Plan  SCM  SCM Activities  Configuration Identification  Configuration Control  Configuration Status Accounting  Configuration Auditing  Milstones  Training  SCM  SCM Activities  Configuration Identification  Configuration Control  Configuration Status Accounting  Configuration Auditing  Milstones  Training

8. Any Designer

9. System Integrator

10. (Release Manager, Build maestro) Release Manager Build Maestro

11. Test (Manager and designer)

12. Overview Tester

13. How to organize? Release 1.1 Patch 1.2_1Patch 1.2_1US Patch 1.0_1 Patch 1.1_1 Patch 1.2_2 Patch 1.0_2 Patch 1.1_2 Patch 1.1_3 Patch 1.2_3 Patch 1.2_4 Patch 1.2_2US Patch 1.2_3US Patch 1.0_3 Patch 1.0_4 Patch 1.0_5 Patch 1.1_4 Patch 1.1_5 Patch 1.1_6 Release 1 Release 1.2Release 1.2_JPRelease 1.2_US Release 3 Release 2 Release 2 UNIX_JP Patch 1.2_7US Patch 1.2_4US Patch 1.2_5US Patch 1.1_4 Patch 1.2_5 Patch 1.1_5 Patch 1.2_8 BUG

14. How to organize? C1 C2C4 C2 C5C4 Release VOB Productstructure Source Structure Common Make USA Japan Make

15. How to organize? 1 MAIN 2 3 REL_1 REL_2 REL_3 0 DP 1 2 3 4 5 Feat xxx 1 1 2 1 2 Efeat xxx 1 23 2 CR xxx Feat 4 1 2 1 2 1 2 E_CRxxx 1 2 1 3 0 BP 1 2 3 4 5 PR_xxx 1 1 2 1 2 MA_PRxxx 1 23 2 33 4 IT1 IT4 IT2 INC_2.1 IT3 INC_2.2 ALFA BETA RM IMDEV

16. Promotion The process for a new feature DP 0 1. The DP exists or will be created automatic. Feat 1 2. The branch will be created automatic for the view. 1 2 3. The developer will add whats specified. 4. When the task is tested (FT=“OK”) and complete, the developer will promote this change to the DP- branch by setting an attribute PRO=“INT”. FT=“OK” PRO=“INT” 1 5. When IM recieves the FT=“OK” and PRO= “INT”, the merge to the DP will be initiated. PRO=“IT1 TEST” 6. When IM have completed the merge and compiled all elements, a promotion of next state change will be performed. PRO will initiate TM for different test cases. IT1 7. When TM have performed all testcases defined for the integrationmodel and approved the tests, a baseline for IT model will be executed. State=“Submit, assigned, open, integrate, test,close”

17. Change Request Flow SubmitAssign Complete Request Spec PR Open Review Postpone Cancel CCB ClearQuest IntegrateVerify

18. ClearCase-ClearQuest Integration main bugfix 4 5 6 2 1 3 2 0 0 1 ClearCase

19. Integration with Clearcase file version Reason for change foo.c2.3.1.2fixed bug bar.c2.7. frams.c4.3added doc frap.c3.7.2.2fixed Ralph’s problem blarg.c7.2 main.c3.7Bill will like this file version Change ID Reason for change foo.c2.3.1.2QTCth03173 SegVs when user directory is 700 permissions bar.c2.7QTCth03520 delete children core dumps xxigt(1) on dec frams.c4.3QTKqa00018 reports of mailfile(1) hanging forever frap.c3.7.2.2QTKqa00656 Need an example of read access control blarg.c7.2QTKqa00775 mailfile(1) produces garbage in the Defaults field main.c3.7QTKqa00958 atoi(1) fails if there are more than 9 integers Meaningful Release Notes Meaningless Release Notes

20. Implementation 025 Part 1 Part 2 Part 3 CM-PlanCCB Model and CR-process Effort

21. Thank You!