IN4MATX 43 Chapter Notes - Chapter 4.1-4.2: Software Projects, Waterfall Model, Unit Testing
Document Summary
W/o software processes, projects take a longer time with poor end products and, in worse situations, total project failure. Goal of software process model is to provide guidance for systematically coordinating and controlling the tasks that must be performed in order to achieve the end product and the product objectives. A set of tasks that need to performed. The input to and output from each task. The preconditions and postconditions for each task. The sequence and flow of these tasks. The simplest process model: code-compile-unit test cycle/code-and-fix model. This simple process model served many early projects, but now as software projects are much more complex, it doesn"t help much. There is no one process model that will fit all software projects. Waterfall model: tasks occur sequentially one after another. Provided many advantages in the early 1970s. Requirements must be specified in the first step.
