1 / 10

3.1 Prescriptive Models

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?

nevin
Télécharger la présentation

3.1 Prescriptive Models

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. 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?

  2. 3.2 The Waterfall Model • Is the waterfall model obsolete?

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

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

  5. 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

  6. 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?

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

  8. 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?

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

  10. 3.6 UP Work Products

More Related