Better Software - January 2009 - (Page 20) HP Software application lifecycle: a better fit for a new breed of applications The most recent wave in application modernization is gaining in both speed and strength. This modernization touches almost all aspects of the IT enterprise, turning local and dedicated teams into virtual and distributed ones, re-shaping applications from stove-pipe to composite entities, enriching user experience via Web 2.0 technologies, and drawing release management away from singular launches toward comprehensive “release trains.” How should IT organizations manage – and maximize – these modernization trends? HP’s approach to Application Lifecycle Management (ALM) helps to ensure modernization initiatives remain framed by the business’s goals. Jonathan Rende, Vice President of Product Marketing, explains how. “The most significant application refresh the industry has seen in 20 years is underway right now,” says Rende. “The trick is to align modernization initiatives with business objectives. The complete application lifecycle is actually much broader than the traditional software development lifecycle [SDLC]. HP recognizes this and places more emphasis on ’upstream‘ activities, such as business strategy and planning, as well as ’downstream‘ efforts such as upgrades, patches and maintenance. “The traditional view of the application lifecycle was developer-centric and focused on the launch date,” continues Rende. “But when you look comprehensively at the work to build and manage an application, only about 20 percent of the time and effort goes into the development and delivery phase; the majority of the effort is spent on maintaining applications running in production. The true application lifecycle not only supports, but integrates, these key activities—everything from the strategic value of the application, to the actual development and testing processes, to change management and other operational issues. The HP approach supports all of these activities.”
For optimal viewing of this digital publication, please enable JavaScript and then refresh the page. If you would like to try to load the digital publication without using Flash Player detection, please click here.