meeting_the_challenges_of_software_208156 - White Paper...

Info iconThis preview shows pages 1–3. Sign up to view the full content.

View Full Document Right Arrow Icon
White Paper www.butlergroup.com Analysis without compromise M M e e e e t t i i n n g g t t h h e e C C h h a a l l l l e e n n g g e e s s o o f f S S o o f f t t w w a a r r e e C C h h a a n n g g e e M M a a n n a a g g e e m m e e n n t t CA Endevor ® Software Change Manager (SCM) and How to Do Lifecycle Management Right
Background image of page 1

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
White Paper www.butlergroup.com 2 CA – Meeting the Challenges of Software Change Management © Butler Direct Limited Written by: Michael Azoff and Stephen Mann Published May 2009 © Butler Direct Limited All rights reserved. This publication, or any part of it, may not be reproduced or adapted, by any method whatsoever, without prior written Butler Direct Limited consent. EXECUTIVE SUMMARY Meeting the Challenges of Software Change Management There are a number of challenges facing organisations with significant IBM z/OS mainframe operations. In all these organisations, it is safe to say, the mainframe is used to support mission-critical applications, and the majority of these are run on COBOL code. These enterprise and business applications can run to thousands of components, and migrating this legacy code is the least attractive option on grounds of cost. However, the task of continued development and maintenance of this code base is becoming more difficult. Regulatory requirements and compliance policies mean that the management of this code needs to be tighter: it needs to be audited and safeguards need to be in place to mitigate risks. For custom applications, and many of these mainframe applications are either in-house built or customised brought-in applications, the challenges are even greater: managing the software lifecycle is a challenge in itself. Development in concurrent work styles and across parallel deployments means that sources of error are high – the complexity factor can lead to synchronisation errors, as wrong libraries are used, code goes missing, or dependencies are missed, causing applications to break. The aging mainframe workforce is another factor to consider: the new generation of developers is trained on distributed systems and the difficulty of replacing mainframe and COBOL developers puts more pressure on the remaining staff. The SCM name tag is an understatement in Butler Group’s opinion: in addition CA Endevor SCM does Configuration Management, Build Management, Release Management, and Deployment Management. CA Endevor Software Change Management (SCM) is designed to meet these challenges for mainframe systems running IBM z/OS. The SCM name tag is an understatement in Butler Group’s opinion: CA Endevor SCM does SCM and Configuration Management, Build Management, Release Management, and Deployment Management, and it has an Integrated Development Environment (IDE) named Quick Edit (a separate module). From a lifecycle management view point, CA Endevor SCM encapsulates so many of the lifecycle practices in an integrated manner that it offers advantages beyond the separate management activities. Thus a build is performed with CA Endevor SCM knowing which files are up to
Background image of page 2
Image of page 3
This is the end of the preview. Sign up to access the rest of the document.

This note was uploaded on 11/19/2009 for the course NCKU Informatio taught by Professor Hero during the Spring '09 term at Accreditation Commission for Acupuncture and Oriental Medicine.

Page1 / 12

meeting_the_challenges_of_software_208156 - White Paper...

This preview shows document pages 1 - 3. Sign up to view the full document.

View Full Document Right Arrow Icon
Ask a homework question - tutors are online