1 / 9

Integrated Release and Configuration Management System

Streamline release and configuration processes, manage project artifacts, ensure production quality, and coordinate deployment activities. Oversee version control, change management, and content management effectively.

maxineb
Télécharger la présentation

Integrated Release and Configuration Management System

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Release Management Configuration management

  2. Release Management Goal • Coordinate the processes through the project development life cycle • Ensure the quality of production version • Manage the project artifacts

  3. Release Management Processes • Release Design • Monitor and Verify the progress of Release • Obtain sign-off • Approve Production Implementation • Coordinate Release Deployment Activity • Implement Release • Post Implementation Review

  4. Supporting processes • Configuration management • Change management • Content management • Version control

  5. Configuration Management • Manage • Project artifacts • Builds • Source code • Start Up Procedure • Documentation

  6. Build • Is identified uniquely by number and date • Contains modules of different versions • After compiling may go to QA • After compiling remains unchanged • Is to be signed off to QA by Build Manager

  7. Change Management • Build in QA or in production can be changed only with Change Request • Change Requests are registered and approved • Developers change a working build • Old source code remains in the storage • After changes done new build goes to QA

  8. Content Management • Developed to manage particularly web site content • Control over the processes of web site updates • Design approval process • Store updated versions of web pages

More Related