The Change-Management Challenge


The Complications of Integrating mainframe code with new applications


Email    print   
January 15, 2003 —  (Page 1 of 6)
Integrating new applications with legacy code-the type of software found on mainframes as well as other older platforms-adds new layers of complication to the job of change management and version control.

Developers building new applications must ensure the applications continue to interoperate with those older systems, across barriers of different platforms, languages, tools and corporate cultures. Often, that means attempting to make change-management and version-control tools interoperate between modern application servers and bell-bottom-era mainframe environments.

The most common method of integrating legacy applications and new code is putting application-server middleware and Web interfaces on host applications. In fact, Meta Group Inc. recently predicted that more than 90 percent of large enterprises will use host-access products that connect to legacy applications via Web services by 2007. Indeed, enterprises have found many different solutions to this problem.

APPLICATIONS COEXIST
For the foreseeable future, new applications will coexist with legacy applications. Verizon Communications, a large telecommunications firm based in Reston, Va., is building a billing system integrating mainframe applications with app servers. The application has 65,000 software items, including CICS assets on the mainframe, and distributed applications running Java and COBOL. The application is distributed on sites spread out nationwide, with about 120 developers working on the project.

The team, according to Jim Winder, Verizon's change-control management/version-control administrator, starts with detailing requirements, then formulates a design, codes, tests, completes the code, performs system tests and moves the code into production. Developers at different stages of the cycle remain in communication with one another. "We do not do waterfall methodology; they all talk to each other," Winder said.

The company (www.verizon.com) uses MKS' Integrity Manager for change management. Developers take change requests, also known as "issues," and Integrity Manager guides them through the phases of the change process, which increases quality control and reduces the need to go back and fix bugs later. "A project that doesn't have to be fixed is a project that causes positive things for business, and not negative ones," Winder said. "It's about giving the business what they need, and making sure that what they give the business works."




Pages 1 2 3 4 5 6 


Share this link: http://sdt.bz/26975
 
Most Read Latest News Blog Resources

Add comment


Name*
Email*  
Country     


  • Comment
Loading




close
NEXT ARTICLE
Cloud Computing Interoperability Presents a Greater Challenge to Adoption Than Security, Say IEEE Cloud Experts
Improved tools for IT control over security and may reassure IT managers and support continued cloud adoption Read More...
 
 
 
 
News on Monday
more>>
SharePoint Tech Report
more>>


   

 
 

Download Current Issue
FEBRUARY 2012 PDF ISSUE

Need Back Issues?
DOWNLOAD HERE

Want to subscribe?


 
blogs tab
Are you at risk for burnout?
Burnout is a severe problem and it can strike at any time. Here's how to tell if you are nearing the edge.
02/09/2012 02:16 PM EST

Agility, mom, and apple pie
If we're to evaluate the state-of-the-art in software development, we should start with the values espoused in the Agile Manifesto.
02/07/2012 11:57 AM EST

RIM woos developers with free tablet
How do you get more apps ported to the BlackBerry PlayBook? By giving every developer a free tablet, of course!
02/04/2012 01:57 PM EST

GitHire: Use Headhunters to Find Your Perfect Programmer
Are you a hiring manager tired of scouring the job boards? Check out this new service that will find 5 people interested in your jobs.
02/03/2012 12:17 PM EST

Facebook claims hacker cred
Facebook's SEC S-1 filing form includes a short essay on the Hacker Way by Mark Zuckerberg himself.
02/02/2012 08:26 AM EST

Ryan Dahl steps down
Ryan Dahl, creator of Node.js, steps back from his position as gatekeeper for the project.
02/01/2012 04:58 PM EST

 
Events calendar tab
2/13/2012 to 2/16/2012
Santa Clara
TechWeb

2/26/2012 to 2/29/2012
San Francisco
BZ Media

2/27/2012 to 3/2/2012
San Francisco
RSA

3/4/2012 to 3/7/2012
Las Vegas
IBM Tivoli

3/5/2012 to 3/9/2012
San Francisco
TechWeb