
Be the first to like this
Slideshare uses cookies to improve functionality and performance, and to provide you with relevant advertising. If you continue browsing the site, you agree to the use of cookies on this website. See our User Agreement and Privacy Policy.
Slideshare uses cookies to improve functionality and performance, and to provide you with relevant advertising. If you continue browsing the site, you agree to the use of cookies on this website. See our Privacy Policy and User Agreement for details.
Published on
There are “waterfall”, “iterative”, “unified”, “agile” and “spiral” software development life cycles (SDLCs), so why not a triangular SDLC?
This paper describes how the triangular life cycle model grew out of a growing frustration with the waterfall life cycle and a search for better ways to integrate quality concerns into the SDLC.
The starting point for the triangular life cycle model was the article “What Does Product Quality Really Mean?” by David Garvin. The article identifies five different views of product quality. The triangular life cycle model was created by placing three of the views – user, manufacturer and product – at the corners of the triangle.
The sides of the triangle are formed by the inevitable “gaps” that exist between the three views of quality. When the SDLC activities are superimposed on the triangle, the underlying reason behind the quality gaps becomes clear.
With the basic elements in place, the focus of the triangular life cycle model shifts to how the gaps can be closed.
Presented in Singapore at The Software Process Engineering Conference 2008  voted best paper and in Bangkok at The 3rd International Conference on Advances in Information Technology (IAIT2009).
Be the first to like this