Review and select a process

Non-DCM-initialized database, by default, use a default process named Standard. This process includes built-in generic process rules that do not treat tasks from other databases any differently from tasks completed locally. For example, for Integration Testing, all completed tasks are collected, including both local and non-local tasks.

When a database is DCM initialized, an additional process named Distributed is created. This process differs from the Standard process because it supports a two tier form of development and testing:

With this two tier approach, changes that break the build affect the local build only and do not directly affect developers on remote sites. This process is more controllable especially when there is a significant time zone difference between sites. The disadvantage is that developers possibly have to wait until a Master Integration Baseline has been created before their projects can be updated with non-local changes.

In a DCM-initialized database, you can use the default Standard or Distributed process, modify either process, or create a custom process of your own design.

Existing release definitions and process rules are not modified during the DCM initialization. If the database that was DCM initialized has already been used for development, review the process used for current releases. Check to see whether the current process is still appropriate for those releases. You can modify the process rules used for the release. You can also copy an alternative generic process rule to a release-specific process rule to implement a revised process for that release.

If the database that you have DCM initialized has not yet been set up with release definitions, review the two default processes. If neither are appropriate for a release, you can modify either one. You can also create a custom process. When you create a release, you can select which process to use.


Feedback