\nIn software development, a process model may also be referred to as a software development life cycle model. It generally refers to the steps of the development process itself.<\/p>\n
\nWith the waterfall model, the development activities are separated, and one is completed before the next is begun. It’s somewhat similar to how physical tasks are performed, such as baking a cake, wherein the steps are sequential: one decides on the recipe, preheats the oven, assembles the ingredients, mixes the dry ones together, mixes the wet ones together, combines the dry and wet mixes together, greases the pan, pours the combined mixture into the pan, places the pan in the oven, lets the cake bake, then removes it.<\/p>\n
\nIn a similar way to producing a cake, the waterfall model starts with defining the requirements. Once those are fully defined, the next step, system design, is undertaken. Having been designed, the system is coded. Next, it’s tested. After that, it’s implemented, and so on.<\/p>\n
\nMost new software projects are not produced along the waterfall model. However, likely because it aligns with how physical things are built, the waterfall model is often referenced. Moreover, for critical systems, the waterfall model is still used.<\/p>\n
\nSource:<\/p>\n
Sommerville, Ian (2016). Software Engineering,<\/em> tenth edition. Pearson.<\/p>\nJack of Oracle Tutoring by Jack and Diane,<\/a> Campbell River, BC.\n\n","protected":false},"excerpt":{"rendered":" Self-tutoring about software development models: the tutor mentions the waterfall model. In software development, a process model may also be referred to as a software development life cycle model. It generally refers to the steps of the development process itself. …<\/p>\n