Scenario 1 - Adding a new project to Team Coherence

MCN produces an install builder application called GP-Install. GP-Install was originally developed for internal use, but has now been released as freeware to gain the company more exposure. Ewan, the developer of Team Coherence has not had to maintain previous versions of GP-Install, and has done all the development himself. It has been decided to split the workload for GP-Install amongst all developers so it now has to be added to Team Coherence.

MCN has a Product repository used for the maintenance of internal tools and products and Ewan has been asked to use that repository for GP-Install. As GP-Install was written in Delphi, Ewan decides that the easiest way to archive it is to use the Delphi interface.

He starts up Delphi in the usual way and opens the GP-Install project in the IDE.

He is now ready to add GP-Install to Team Coherence. Since this project has not yet been archived, most of the IDE interface menu options and buttons are disabled. He selects Workgroups/Add Project to Version Control from the main menu.

He is presented with the check in dialog box, and enters some comments to indicate the status of the files. As he needs to make some changes to the files he elects to check the Leave it Locked radio button on the Options page of this dialog. Once he has reviewed his settings, he presses the OK button to add the files.

Team Coherence processes all the files and presents the Status Dialog so that Ewan can correct any problems that might have occurred. There were no problems, so he presses the OK button to return to Delphi. As a check to make sure all the files were checked in, he starts up Version Manager by selecting Workgroups / Team Coherence from the IDE menu and checks that the project is archived and that he still has a lock on the files he just added.