Your SlideShare is downloading. ×
Ch03
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×

Saving this for later?

Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime - even offline.

Text the download link to your phone

Standard text messaging rates apply

Ch03

620
views

Published on

Published in: Business, Technology

0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total Views
620
On Slideshare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
34
Comments
0
Likes
0
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide

Transcript

  • 1. Software Engineering: A Practitioner’s Approach, 6/e Chapter 3 Prescriptive Process Models copyright © 1996, 2001, 2005 R.S. Pressman & Associates, Inc.
  • 2. Prescriptive Models
    • Prescriptive process models advocate an orderly approach to software engineering
    • That leads to a few questions …
    • If prescriptive process models strive for structure and order, are they inappropriate for a software world that thrives on change?
    • Yet, if we reject traditional process models (and the order they imply) and replace them with something less structured, do we make it impossible to achieve coordination and coherence in software work?
  • 3. The Waterfall Model
  • 4. The Incremental Model
  • 5. The RAD Model
  • 6. Evolutionary Models: Prototyping communication Quick plan Modeling Quick design Construction of prototype Deployment delivery & feedback
  • 7. Evolutionary Models: The Spiral
  • 8. Evolutionary Models: Concurrent
  • 9. Still Other 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
    • Unified Process —a “use-case driven, architecture-centric, iterative and incremental” software process closely aligned with the Unified Modeling Language (UML)
  • 10. The Unified Process (UP) inception inception elaboration
  • 11. UP Phases
  • 12.  
  • 13. UP Work Products