Predefined Lifecycle Templates › Production

Production

Production software development takes a different approach than release software. The emphasis in the Production lifecycle is to keep an application operational; the concept of a release does not exist. In a production project, you do not need to track previous versions of the software, but you do need to be able to look at changes between production versions. Because of this difference, the Production lifecycle relies heavily on views and the software that is available in a view at a specific time. Financial institutions, insurance companies, assembly lines, and other commercial organizations are typical production projects.

In the Production lifecycle the Development, Emergency, and Production states share the same view. This helps ensure that when an item is checked out in Development, the latest version is also in Production. If a version is checked out for Update in the Development view and then checked back in, the version is available in Production automatically. Therefore, the only mode of check-out allowed for update is concurrent update; when a version is checked out in Development, it is placed on a branch. This lets users change versions in Development without affecting Production.

Note: When a new file is added to the system, it must be checked in to the Merge state. If you attempt to check in the new file to the Development state, it is automatically seen in Production, which is not wanted. A separate view must be used when you check in the file. A notification process in the Development state sends a mail message notifying the merge engineer that the package has been promoted, and that the new file needs to be checked in.