Software development process: Difference between revisions

Content deleted Content added
m Restored revision 1284585450 by Apparition11 (talk): WP:COPYVIO
OAbot (talk | contribs)
m Open access bot: url-access updated in citation with #oabot.
Line 175:
 
* Focus is on risk assessment and on minimizing project risk by breaking a project into smaller segments and providing more ease-of-change during the development process, as well as providing the opportunity to evaluate risks and weigh consideration of project continuation throughout the life cycle.
* "Each cycle involves a progression through the same sequence of steps, for each part of the product and for each of its levels of elaboration, from an overall concept-of-operation document down to the coding of each individual program."<ref name="BB86">{{cite journal |author=Barry Boehm |author-link=Barry Boehm |url=http://doi.acm.org/10.1145/12944.12948 |title=A Spiral Model of Software Development and Enhancement |journal=ACM SIGSOFT Software Engineering Notes |publisher=[[Association for Computing Machinery]] |volume=11 |issue=4 |pages=14–24 |date=August 1986|doi=10.1145/12944.12948 |s2cid=1781829 |url-access=subscription }}</ref>
* Each trip around the spiral traverses four basic quadrants: (1) determine objectives, alternatives, and constraints of the iteration, and (2) evaluate alternatives; Identify and resolve risks; (3) develop and verify deliverables from the iteration; and (4) plan the next iteration.<ref name="RT-BB86">{{cite book |author1=Richard H. Thayer |author2=Barry W. Boehm |author2-link=Barry Boehm |date=1986 |title=Tutorial: software engineering project management |publisher=Computer Society Press of the IEEE |page=130}}</ref>
* Begin each cycle with an identification of stakeholders and their "win conditions", and end each cycle with review and commitment.<ref>{{cite book |author=Barry W. Boehm |author-link=Barry Boehm |date=2000 |title=Software cost estimation with Cocomo II: Volume 1}}</ref>