Description - Mks.com

and updates file revisions as required to create the desired change. If merging is required, you can
use the Resync CP command. Resync CP allows you to either merge in desired changes or merge
around unwanted changes.
Apply CP and Resync CP are most useful for code and other text files where differencing can be
performed.
The Change Package Methodology
When used across a development project, Apply CP and Resync CP are powerful tools for
managing changes and new content. However, the effectiveness of the functionality ultimately
relies on the following factors:
● accurate and consistent logging of issues into the Integrity Manager database
● associating related changes into a single change package that ultimately addresses the
issue in question
Because issues, and their associated change packages, follow a workflow progression, it is critical
that each member of the development team record and track all changes as they are made, from
the initial phase to the completion phase in which the associated problem is addressed. All
changes relating to a given issue must then be associated with the correct change package. Once
the problem is addressed, or the feature added, that change package can be closed.
It is equally important that issues are clearly delineated so that each change package addresses
only one problem area or feature. Certainly, one problem area or feature may require many files to
address it, but if you create a change package that is too wide in scope, it becomes difficult to
extract specific changes later on.
With accurate and consistent logging, Source Integrity can clearly identify the specific member
revisions (or files) that address the identified problem or complete the required feature. Without this
type of tracking, applying a change package may not have the desired results and manual reviews
may become necessary.
The Commands
Consider the following scenario at abcBusiness--a major customer purchased version 2.0 of
abcBusiness' Aurora software. The customer now wants a new feature--data compression--that
they can use with Aurora 2.0 The development team at abcBusiness has already completed work
on a data compression feature, bu the feature has been engineered only as part of the upcoming
Aurora 3.0 release.
To address the customer's needs, abcBusiness would normally have to assign a separate
development team to create the new feature for Aurora 2.0 But how can abcBusiness take
advantage of the work already completed on the data compression feature and provide it to the
48 of 457