ReviewEssays.com - Term Papers, Book Reports, Research Papers and College Essays
Search

Software Control and Maintenance

Essay by   •  December 27, 2010  •  Essay  •  932 Words (4 Pages)  •  1,327 Views

Essay Preview: Software Control and Maintenance

Report this essay
Page 1 of 4

Software Control and Maintenance

The importance of managing change in information technology (IT) environments has grown significantly in the last few years. This shift is having a major impact on mid-sized businesses, which needs to increase their focus on compliance and initiatives centered on control, security and documentation. The challenge for change management today focuses on organizational and technological maturity. Most IT shops have been busy building out their technology infrastructure while fighting fires. Today, more IT organizations are realizing the reasons why change management warrants the time and investment required to meet accountability needs.

Software Change Management (SCM) is the process of handling changes correctly and efficiently, with minimum impact while following the organization's business objectives and priorities. Correctly managing the change process is defined as; documenting the request, analyzing technical and business impacts and risks, gaining approval from stakeholders, scheduling and managing the change workflow, and reviewing the change tasks. The change management process in and of itself must also be tuned for operational efficiency assessing the types of changes that are being requested across the organization, the speed with which changes are made, or the number of changes that must be reversed.

The costs of inadequate SCM are significant; Enterprise Management Associates estimates that 70% or more of all performance and availability errors alone are due to accidental configuration errors, caused by individuals within the organization. The true cost of not managing change is the impact it has on IT service quality. Impacts include:

* Inefficient and lengthy approval processing

* Lack of appropriate assessment and review, resulting in change failures

* Catastrophic lack of back-out plans

* Uninformed and angry end users and business managers

* Incomplete tracking of costs, changes, and time spent implementing changes

Investing in SCM is a necessary step for any business that relies on development in an IT environment. For the McBride Financial Services environment it is recommended that two software packages are considered to control their SCM.

IBM Rational ClearCase provides management and control of software development assets, allows integration into the Software Development Life Cycle (SDLC) at design, development, build, test and deployment phases of a projects. Productivity can be gained through version control allowing automated workspace management, branching and parallel development support, software baseline management, and build and release management.

IBM Rational ClearQuest automates and enforces the development processes during the SDLC by providing traceability from requirements to production, managing defect and requirement change tracking and integrating communications between all teams including design, development, testing, deployment and stakeholders.

Both IBM Rational ClearQuest, ClearCase have local, remote and Web interfaces enabling secure access to either product virtually anytime or anywhere. These products support development and work on Microsoft Windows, Linux, Unix or OS/2. Figure 1 outlines the IBM pricing of each product, including support.

IBM Rational ClearCase with 12 month SW Maintenance $4125

IBM Rational ClearQuest with 12 month SW Maintenance $1620

Figure 1.

Installing IBM Rational ClearQuest, ClearCase SCM tools the IT department and the stakeholders will receive the following benefits:

* Task orientation keeps developers focused on functionality, not files.

Requirements and defects are defined as change requests; these change requests are broken down into tasks and assigned to developers for implementation. User activities are then managed in terms of these tasks rather than in terms of changes to software artifacts.

* Traceability provides the business with better visibility into IT.

In addition to defining changes in terms of tasks,

...

...

Download as:   txt (6.5 Kb)   pdf (92.9 Kb)   docx (11.4 Kb)  
Continue for 3 more pages »
Only available on ReviewEssays.com