Almost as soon as software development entered the business mainstream, it evolved from being the work of a small handful of programmers to the product of a team operating within a recognizable lifecycle, incorporating identifiable activities of requirements definition, design, coding and test. Just as rapidly, practitioners and project managers alike recognized two essential truths: coordination between team members and across the lifecycle is both essential to delivering business value and extremely hard to achieve. Today, software delivery is both more complex and more business critical than ever.
In the first part of this IBM® Redguide™ publication, we talk about the business value of lifecycle integration in software development. We then discuss the major architectural approaches that organizations have tried in the past to achieve that business value. We explain why these approaches, which may seem attractive on paper, fall short in the real world of business.
In the second part of this IBM Redguide publication, we introduce the innovative IBM Jazz™approach. We explain both how it is both a new technical architecture that draws heavily on the extraordinarily successful architecture of the Web to overcome the shortcomings of previous architectures, and also a new approach to the relationships between competing vendors and between vendors and customers that emphasizes the creation of a value network.
Table of contents