![\"Paul](\"http:\/\/www.katiachumakova.com\/wp-content\/uploads\/2016\/09\/development-process.png\")
Development process<\/figcaption><\/figure>\n
Here are some of the main approaches:<\/p>\n
WATERFALL ( read a bit more\u2026 <\/a>) This was the first approach invented, it is very straight forward and easy to understand. This process works best for projects that do not change requirements in late stages of development because it is very hard to make changes and implement new features after early stages. <\/p>\n PROTOTYPING Some types of prototyping methodologies are: Although it is better for user involvement it can also lead to confusion over the protoypes and the final product. <\/p>\n SPIRAL This model is good for budget estimating and issue discovery at early stages of development, but it also involves a lot of time and high costs and has quite limited re-usability. <\/p>\n AGILE or EXTREME PROGRAMMING (read a bit more\u2026 <\/a>)<\/p>\n OTHERS<\/p>\n -Lightweight Methodologies Sources:<\/p>\n Software Development Life Cycle Models and Methodologies<\/a><\/p>\n","protected":false},"excerpt":{"rendered":" Software Development Processes are the basic models that give us a rough guideline on how to organize all of the work involving the creation of a software product. All of the methodologies are based on the Software Development Life Cycle. Paul DowneyDevelopment process Here are some of the main approaches: WATERFALL ( read a bit … Continue reading The Software Development Process<\/span><\/a><\/p>\n","protected":false},"author":10,"featured_media":37389,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[5,4],"tags":[173,158,162,134,255,54,256,25,202],"class_list":["post-37388","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-blogs","category-syndicated","tag-process","tag-agile","tag-development","tag-mastery-topics","tag-prototyping","tag-software","tag-spiral","tag-tc1019","tag-waterfall"],"_links":{"self":[{"href":"https:\/\/kenscourses.com\/tc1019fall2016\/wp-json\/wp\/v2\/posts\/37388","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/kenscourses.com\/tc1019fall2016\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/kenscourses.com\/tc1019fall2016\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/kenscourses.com\/tc1019fall2016\/wp-json\/wp\/v2\/users\/10"}],"replies":[{"embeddable":true,"href":"https:\/\/kenscourses.com\/tc1019fall2016\/wp-json\/wp\/v2\/comments?post=37388"}],"version-history":[{"count":1,"href":"https:\/\/kenscourses.com\/tc1019fall2016\/wp-json\/wp\/v2\/posts\/37388\/revisions"}],"predecessor-version":[{"id":37390,"href":"https:\/\/kenscourses.com\/tc1019fall2016\/wp-json\/wp\/v2\/posts\/37388\/revisions\/37390"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/kenscourses.com\/tc1019fall2016\/wp-json\/wp\/v2\/media\/37389"}],"wp:attachment":[{"href":"https:\/\/kenscourses.com\/tc1019fall2016\/wp-json\/wp\/v2\/media?parent=37388"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/kenscourses.com\/tc1019fall2016\/wp-json\/wp\/v2\/categories?post=37388"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/kenscourses.com\/tc1019fall2016\/wp-json\/wp\/v2\/tags?post=37388"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}
\nA linear model that follows a sequential flow, work is split into many phases and development happens first in one phase, gets completed and then moves to the next phase, the phases don\u2019t overlap. <\/p>\n
\nThis model focuses on creating protoypes for the client so he\/she gets a better idea of how the requirements they gave are being implemented. This is a good model for testing and reduces the misunderstanding gap between developer and client. <\/p>\n
\n-Throwaway Prototyping
\n-Evolutionary Prototyping
\n-Incremental Prototyping<\/p>\n
\nThis method involves combining design and prototyping. This model is used mostly for expensive and complex projects, these project is composed mostly of small waterfall models, the phases go in the same order, and then prototypes are built and simulated. <\/p>\n
\n-Rapid Application Development
\n-Code Fix
\n-Chaos Model
\n-Incremental Funding
\n-V-Model
\n-Unified Process<\/p>\n