Release Management Configuration management. Release Management Goal Coordinate the processes through the project development life cycle Ensure the.

Slides:



Advertisements
Similar presentations
Structured development process Wednesday 20 September 2006 Brett Coster Business Analyst uniqueworld
Advertisements

Configuration Management
© 2007 AT&T Knowledge Ventures. All rights reserved. AT&T and the AT&T logo are trademarks of AT&T Knowledge Ventures. Interactive Solutions & Design Group.
Validata Automated Build & Configuration (ABC)
Validata Release Coordinator Accelerated application delivery through automated end-to-end release management.
Chapter 14 Maintaining Information Systems Modern Systems Analysis and Design Seventh Edition Jeffrey A. Hoffer Joey F. George Joseph S. Valacich.
Mentor Update 2007 – Content includes: B71 / B73 SPL Supporting Practice Learning Module, Continuity of Practice Assessment Record, Sign-off Mentor.
Copyright © 2001 Bolton Institute Faculty of Technology Multimedia Integration and Applications Lecture 9: Production Management Damien Markey.
APPLICATION DEVELOPMENT BY SYED ADNAN ALI.
Interface Programming 1 Week 15. Interface Programming 1 CALENDAR.
Maintaining Information Systems Class 27. SDLC Project Identification & Selection Project Initiation & Planning Analysis Logical Design Physical Design.
Chapter 16 Maintaining Information Systems
Copyright 2002 Prentice-Hall, Inc. Modern Systems Analysis and Design Third Edition Jeffrey A. Hoffer Joey F. George Joseph S. Valacich Chapter 18 Maintaining.
Configuration Management Avoiding Costly Confusion mostly stolen from Chapter 27 of Pressman.
Release & Deployment ITIL Version 3
Sys Prog & Scripting - HW Univ1 Systems Programming & Scripting Lecture 15: PHP Introduction.
CSCI ClearQuest 1 Rational ClearQuest Michel Izygon - Jim Helm.
Web Development Process Description
Software Engineering Modern Approaches
Maintaining Information Systems Modern Systems Analysis and Design.
Module CC3002 Post Implementation Issues Lecture for Week 6 AY 2013 Spring.
OSF/ISD Project Portfolio Management Framework January 17, 2011.
EPA Web Procedures and Standards October 26, 2010.
Date: 07/20/2011 HCSIS, Independent Monitoring for Quality (IM4Q) - Considerations.
COMP-14: Automating your deployments using ANT Gary S Clink Business Consultant.
Project Management : Techniques and Tools (60-499) Fall 2014 / Winter 2015.
MODULE B: Case Report Forms Jane Fendl & Denise Thwing April 7, Version: Final 07-Apr-2010.
Copyright 2009  Describe the five project management (PM) process groups, the typical level of activity for each, and the interactions among them  Understand.
MACIASZEK, L.A. (2001): Requirements Analysis and System Design. Developing Information Systems with UML, Addison Wesley Chapter 6 - Tutorial Guided Tutorial.
Bring Your Own Device in HCPSS. What is BYOD? BYOD stands for Bring Your Own Device Students and staff are welcome to bring their personal devices such.
Florida Department of Community Affairs - Codes and Standards Overview: Code Modification Process.
Project Methodology May 2, System Development Life Cycle Overview.
CSSE 375 Software Construction and Evolution: More SCM, and a loop back to Feathers! Shawn and Steve Left – On big systems, SCM is a well-defined process.
Develop Project Charter
Requirements Traceability Matrix
Configuration Management and Change Control Change is inevitable! So it has to be planned for and managed.
Software Configuration Management (SCM). Product Developer Disciplines One view of the world is that there are three types of activities are required.
Project management Topic 1 Project management principles.
Software Configuration Management n Art of coordinating SW development to minimize confusion n Software quality assurance (umbrella) activity n Set of.
State of Georgia Release Management Training
Waterfall Model Software project Management. Waterfall Model  The Waterfall Model was first Process Model to be introduced. It is also referred to as.
1 of 5 This document is for informational purposes only. MICROSOFT MAKES NO WARRANTIES, EXPRESS OR IMPLIED, IN THIS DOCUMENT. © 2007 Microsoft Corporation.
Project management Topic 8 Configuration Management.
WEEK 6 Introduction to Project Management. Agenda Phase 4: Controlling.
Chapter 16 Maintaining Information Systems. Objectives:  Explain and contrast four types of system maintenance.  Describe factors affecting maintenance.
1 Presented by: Val Pennell, Test Tool Manager Date: March 9, 2004 Software Testing Tools – Load Testing.
Adaptive Software Development Process Framework. Version / 21 / 2001Page Project Initiation 2.0 Adaptive Cycle Planning 5.0 Final Q/A and.
QA process for Business Catalyst projects.. Starting a project What QA needs to start testing::  Specifications – A detailed description of the product,
Overview: Code Modification Process Summary. PROPONENT Step 1 - Proponent has a code change in mind MODIFICATION (Mod) Step 2 - Proponent enters the mod.
Chapter 14 Maintaining Information Systems
Configuration Management
Chapter 18 Maintaining Information Systems
5.5 Control Scope The process of monitoring the status of both the project and product scope Focuses on managing any changes to the scope baseline and.
From delivery to acceptance
Using E-Business Suite Attachments
Brian McCallum UWS, Web Services Unit 15 November 2011
Configuration Management and Prince2
Description of Revision
Application name OPERATIONAL READINESS Stage Gate Review Version 1.0
OSOR - new opportunities for sharing statistical software
Maintaining Information Systems (SAD- 18)
South Carolina Alternate Assessment
WordPress Unit Web Coordinators
Configuration Management
WordPress Unit Web Coordinators
{Project Name} Organizational Chart, Roles and Responsibilities
Port Back Data Collection & Transition
Chapter 18 Maintaining Information Systems
Presentation transcript:

Release Management Configuration management

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

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

Supporting processes Configuration management Change management Content management Version control

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

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

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

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