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.

Chapter 2: Understanding <strong>Implementer</strong><br />

54<br />

Identifying an Issue<br />

A user submits a change request to report a bug, enhance functionality, or add new<br />

features.<br />

Analyze<br />

Once you decide to accept the change request, you analyze the problem and identify<br />

what needs to be created or changed to provide a suitable solution. This may include<br />

things other than software, such as technical publications or training materials.<br />

Design<br />

You define the solution, establish a schedule for completion, and assign the tasks to<br />

individuals.<br />

Implement<br />

You develop each solution component, which may include coding or documenting the<br />

changes to the product, system, or application.<br />

Test<br />

You test the solution to ensure it performs as designed and meets the customer’s original<br />

need.<br />

Deliver<br />

The cycle is completed once you deliver the requested change back to the customer,<br />

ensuring their satisfaction. This corresponds to delivering a new release of a product or<br />

releasing the changes to the production systems.<br />

“Identifying an issue” and “Analyze” represent the Decision Phase, which addresses the<br />

assessment and negotiation steps that are required to ensure that changes are prioritized<br />

and scheduled for a timely resolution. “Design” and “Implement” are referred to as the<br />

Development Phase. “Test” is referred to as the Verification Phase, and “Deliver” as the<br />

Deployment Phase.<br />

Sometimes, for small changes, a person may quickly go through the thought process for<br />

the first four steps in one step (for example, correcting a typographical error). For more<br />

complicated cases, these steps may be handled by different roles such as a review board,<br />

developer, or QA manager. It is important, therefore, to structure your process to<br />

incorporate the ability to hand off the issue to the responsible parties. Whatever process<br />

you enforce, you want to verify that it supports these four basic phases.<br />

Managing the Physical Movement of Objects<br />

The purpose of a change management system is to manage the movement of software objects.<br />

Yo must accomplish this in an appropriate way for the platform containing the objects. This<br />

includes, for example, honoring and enforcing the security and integrity of the platform.<br />

<strong>MKS</strong> Integrity provides an effective means of dealing with the problems and issues<br />

surrounding multi-platform development and deployment.

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

Saved successfully!

Ooh no, something went wrong!