02.05.2013 Views

MKS Implementer 2006 Administration Guide

MKS Implementer 2006 Administration Guide

MKS Implementer 2006 Administration Guide

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

deployer<br />

tester<br />

development manager/project leader<br />

Multi-Platform Development and Deployment Scenarios<br />

Additional roles may be added at each point in the process; however, adding roles changes<br />

the process, but it does not alter the change management activities.<br />

Managing Change Requests<br />

Software systems require change. Change is identified by a change request. A change goes<br />

through the appropriate software development lifecycle based on the technology and the<br />

platform. By using change requests, two classes of management information must be<br />

available at all times. These can be represented by the following questions:<br />

Where in the software development lifecycle and deployment is the change request?<br />

What change requests are resolved in this new version of an object?<br />

In addition to tracking by change request, it is also important to be able to work based on<br />

change requests. This allows work to be done on a change request and at the same time to<br />

affect all of the related objects.<br />

The General Process<br />

Typically, change requests flow through the following stages:<br />

Does an issue<br />

exist?<br />

Customer<br />

Deliver<br />

Analyze<br />

Change<br />

Requests<br />

Design<br />

Implement<br />

Test<br />

53

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!