Application Lifecycle Management Across Multiple Environments
timhahn 100000F0AC Visits (2134)
There was a time, not so long ago, when the tools that you used for software development were specific to the platform on which your application was going to run. But just as automobiles, airplanes, buildings, and computer systems evolve over time, so do the tools which are used to create and maintain software which runs on those systems.
It is now possible to have all of an organization's software development teams using a common set of tools to manage their development projects, maintain their source code, and collaborate on project plans, work items, source code control, and build processing. Why is this important? Well, in today's competitive environment and into the future, software development teams are going to be asked more and more to work on projects across a wide spectrum of environments and systems. One day, the team may be working on some Java code running in an application server. The next day, the same team may have to update some C/C++ code running in a AIX system hosted on a PureFlex environment. And on Wednesday, just to keep the team on their toes, they might have to update a COBOL or PL/I program running on a z/OS system.
If this team is to be flexible enough to work in all these environments, they can't be burdened with having to learn (or re-learn) a different set of tools when working in each of these spaces. If they can use the same tools, with the same terminology, and the same usage characteristics across all of those systems, then the team can move quickly from project to project and task to task.
A unique aspect of working on z/OS systems is that it contains multiple file system implementations, each of which have valuable usage characteristics for programs running on z/OS. To address this, the Rational Team Concert product offers special processing for handling application source code meant to run in these environments. Furthermore, for application developers who are focused on writing COBOL, PL/I, or Assembler language programs for the z/OS platform, accessing source code in Rational Team Concert which is targeted to be built on and run on z/OS requires that these file systems be supported. These teams are often most familiar with using a text-based user interface through a terminal-based connection to the z/OS system. For these teams, having a text-based user interface for loading, changing, and checking in source code to the change control system of Rational Team Concert streamlines the task of application development on z/OS systems.
With Rational Team Concert 4.0, enhancements have been made to the ISPF-based user interface to Rational Team Concert. These enhancements include more granular file loading options, support for handling merge of file changes delivered by colleagues, and improvements in sharing files into the Rational Team Concert source code management system. You can learn more about these enhancements from this video.
Commercial software development requires teams of people to collaborate on the planning, tasks, source code changes, build, and testing of applications built for the business. Rational Team Concert enables all of these important tasks for software development teams, and enables this across the widest set of platforms in the industry. By having a common set of tools in place, application development teams are more nimble and able to move from project to project and platform to platform more quickly and will less start-up and re-education time.