{"status":"ok","message-type":"work","message-version":"1.0.0","message":{"indexed":{"date-parts":[[2026,3,20]],"date-time":"2026-03-20T20:45:53Z","timestamp":1774039553327,"version":"3.50.1"},"reference-count":7,"publisher":"Association for Computing Machinery (ACM)","issue":"3","license":[{"start":{"date-parts":[[1985,7,1]],"date-time":"1985-07-01T00:00:00Z","timestamp":489024000000},"content-version":"vor","delay-in-days":0,"URL":"https:\/\/www.acm.org\/publications\/policies\/copyright_policy#Background"}],"content-domain":{"domain":["dl.acm.org"],"crossmark-restriction":true},"short-container-title":["SIGSOFT Softw. Eng. Notes"],"published-print":{"date-parts":[[1985,7]]},"abstract":"<jats:p>The conventional wisdom of planning software engineering projects, using the widely cited \"waterfall model\" is not the only useful software development process model. In fact, the \"waterfall model\" may be unrealistic, and dangerous to the primary objectives of any software project.The alternative model, which I choose to call \"evolutionary delivery\" is not widely taught or practiced yet. But there is already more than a decade of practical experience in using it. In various forms. It is quite clear from these experiences that evolutionary delivery is a powerful general tool for both software development and associated systems development.Almost all experienced software developers do make use of some of the ideas in evolutionary development at one time or another. But, this is often unplanned, informal and it is an incomplete exploitation of this powerful method. This paper will try to expose the theoretical and practical aspects of the method in a fuller perspective. We need to learn the theory fully, so that we can apply and learn it completely.<\/jats:p>","DOI":"10.1145\/1012483.1012490","type":"journal-article","created":{"date-parts":[[2004,10,7]],"date-time":"2004-10-07T17:39:09Z","timestamp":1097170749000},"page":"49-61","update-policy":"https:\/\/doi.org\/10.1145\/crossmark-policy","source":"Crossref","is-referenced-by-count":27,"title":["Evolutionary Delivery versus the \"waterfall model\""],"prefix":"10.1145","volume":"10","author":[{"given":"Tom","family":"Gilb","sequence":"first","affiliation":[{"name":"Independent Consultant, Kolbotn, Norway"}]}],"member":"320","published-online":{"date-parts":[[1985,7]]},"reference":[{"key":"e_1_2_1_1_1","doi-asserted-by":"publisher","DOI":"10.1145\/1010925.1010932"},{"key":"e_1_2_1_2_1","unstructured":"Gilb-SET-83: \"Software Engineering Templates\" about 40 pages unpublished manuscript. Course documentation. Freely copiable. It defines a number of fundamental software metrics in hierarchical measurable form.  Gilb-SET-83: \"Software Engineering Templates\" about 40 pages unpublished manuscript. Course documentation. Freely copiable. It defines a number of fundamental software metrics in hierarchical measurable form."},{"key":"e_1_2_1_3_1","unstructured":"Gilb-SSD-79: Gilb T. \"Structured Design Methods for Maintainability\" in Infotech State of the Art Report on Structured Software Development 1979. See also Data Processing (UK) \"Maintaining Software System \" June 1984. Also extracts of it in Gilbert-83 pp 186--192.  Gilb-SSD-79: Gilb T. \"Structured Design Methods for Maintainability\" in Infotech State of the Art Report on Structured Software Development 1979. See also Data Processing (UK) \"Maintaining Software System \" June 1984. Also extracts of it in Gilbert-83 pp 186--192."},{"key":"e_1_2_1_4_1","unstructured":"Gilb-SM-76: \"Software Metrio\" Winthrop USA (now out of print) and Studentlitterature AB Lund Sweden (in print). Three pages (187 214 217) directly treat evolutionary development concepts. It is interesting as an early reference. Fagan's Inspection method is also treated extensively in the book (see Fagan-1976 reference here).  Gilb-SM-76: \"Software Metrio\" Winthrop USA (now out of print) and Studentlitterature AB Lund Sweden (in print). Three pages (187 214 217) directly treat evolutionary development concepts. It is interesting as an early reference. Fagan's Inspection method is also treated extensively in the book (see Fagan-1976 reference here)."},{"key":"e_1_2_1_5_1","volume-title":"SRA Publishers","year":"1983"},{"key":"e_1_2_1_6_1","volume":"4","author":"Mills Harlan","journal-title":"IBM Systems Journal"},{"key":"e_1_2_1_7_1","doi-asserted-by":"crossref","unstructured":"Wong. Carolyn \"A Successful Software Development\" IEEE Trans on Software Engineering Nov. 1984. The SDC experience with evolutionary delivery is stated in the context of a number of other successful methods used with it. Wong . Carolyn \"A Successful Software Development\" IEEE Trans on Software Engineering Nov. 1984. The SDC experience with evolutionary delivery is stated in the context of a number of other successful methods used with it.","DOI":"10.1109\/TSE.1984.5010300"}],"container-title":["ACM SIGSOFT Software Engineering Notes"],"original-title":[],"language":"en","link":[{"URL":"https:\/\/dl.acm.org\/doi\/10.1145\/1012483.1012490","content-type":"unspecified","content-version":"vor","intended-application":"text-mining"},{"URL":"https:\/\/dl.acm.org\/doi\/pdf\/10.1145\/1012483.1012490","content-type":"unspecified","content-version":"vor","intended-application":"similarity-checking"}],"deposited":{"date-parts":[[2025,6,18]],"date-time":"2025-06-18T16:31:42Z","timestamp":1750264302000},"score":1,"resource":{"primary":{"URL":"https:\/\/dl.acm.org\/doi\/10.1145\/1012483.1012490"}},"subtitle":[],"short-title":[],"issued":{"date-parts":[[1985,7]]},"references-count":7,"journal-issue":{"issue":"3","published-print":{"date-parts":[[1985,7]]}},"alternative-id":["10.1145\/1012483.1012490"],"URL":"https:\/\/doi.org\/10.1145\/1012483.1012490","relation":{},"ISSN":["0163-5948"],"issn-type":[{"value":"0163-5948","type":"print"}],"subject":[],"published":{"date-parts":[[1985,7]]},"assertion":[{"value":"1985-07-01","order":2,"name":"published","label":"Published","group":{"name":"publication_history","label":"Publication History"}}]}}