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 5: <strong>MKS</strong> Integrity Integration<br />

The iSeries Component<br />

198<br />

The <strong>Implementer</strong> and <strong>MKS</strong> Integrity integration manages software applications across your<br />

enterprise with a streamlined process for the creation and approval of mission-critical<br />

business applications. Based on a unique, open, application server architecture, the solution<br />

includes:<br />

workflow (<strong>MKS</strong> Integrity) for collaboration, approval, and change management<br />

host based version control (<strong>Implementer</strong>) and configuration for software management<br />

client/server and Java version control (<strong>MKS</strong> Source, formerly Source Integrity®<br />

Enterprise) and configuration for software management<br />

promotion and deployment (<strong>Implementer</strong>) for the movement of software changes to QA<br />

and production<br />

Process and Workflow<br />

Managers have a window into the development process, allowing them to monitor the<br />

progress of issues and changes. Resolving issues is accomplished through an integrated<br />

change management process facilitated by a common software architecture between<br />

<strong>MKS</strong> products.<br />

Issues<br />

<strong>MKS</strong> Integrity uses issues to track changes during the software development cycle. Problems,<br />

solutions, and tasks are all examples of issues. Issues can be related to each other for<br />

reference, easy tracking, and monitoring. For example, a solution may be associated with a<br />

problem and the relationship allows you to capture the data on the problem resolution<br />

during different stages of the development process. Each issue has an audit trail, which may<br />

be used to evaluate internal processes for the effectiveness of the problem resolution process.<br />

Types<br />

Issue types describe different categories of issues, such as a change request, problem, solution,<br />

or task. For example, you can use one type for issues that record deficiencies in design. You<br />

can use another type for issues that request design changes to fix problems, or to propose<br />

enhancements or new functionality for your component. Similarly, you can use a type for<br />

issues that assign work tasks to address problems or to suggest and implement solutions.<br />

<strong>MKS</strong> Integrity is an extremely flexible issue management system. <strong>MKS</strong> Integrity allows any<br />

number of types. Each type can have its own defined workflow of allowed state transitions<br />

and its own user defined set of fields.

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

Saved successfully!

Ooh no, something went wrong!