3.1 Prescriptive Models Prescriptive process models advocate an orderly approach to software engineering If prescriptive process models strive for structure and order, are they inappropriate for a software world that thrives on change? If we reject traditional prescriptive process models and replace them with something less structured do we make it impossible to achieve coordination and coherence in software work?

3.2 The Waterfall Model Is the waterfall model obsolete?

3.3 The Incremental Model What is an “increment”? When is it appropriate to apply the incremental model?

3.3 The RAD Model When is it appropriate/inappropriate to apply the RAD model?

3.4 Evolutionary Models: Prototyping How are evolutionary models different from incremental models? Quick plan communication Modeling Quick design Deployment delivery & feedback Construction of prototype

3.4 Evolutionary Models: The Spiral How does the spiral model differ from prototyping? What is the role of risk analysis in the spiral model?

3.4 Evolutionary Models: Concurrent I don’t like this one so don’t spend too much time reading about it.

3.5 Specialized Process Models Component based development—the process to apply when reuse is a development objective Formal methods—emphasizes the mathematical specification of requirements AOSD—provides a process and methodological approach for defining, specifying, designing, and constructing aspects What are the primary advantages of the component-based process model?

3.6 The Unified Process (UP) inception elaboration inception What is a use-case?

3.6 UP Work Products