[INF43] Lecture 15 Pr
@ZYX 写于2020年06月02日
Process
Process are rememdies
- Process can help but not silver bullet
What is model
- an ideal version of process: an ideal simplified representation
What is model for
- see ppt
Software Life Cycle Models
Models
Build-and-Fix
- Simple
- Strength
- Good for small programs that do not require much maintenance or many developers
- Weaknesses
- Not rigorous enough for non-trivial projects
Waterfall
- Very linear and very sequential
- Very ideal: all the requirements are written at the beginning, nothing will change
- Can create a lot of documentation
- for the programs that are highly regulated like Space
- Strength
- Promotes understanding of requirements first
- Disciplined, rigorous, formal
- Lots of documentation
- Good for projects with well-understood requirements that are unlikely to change
- Provided a starting point for other software process models
- Weakness
- Rigid, not amenable to change
- Limited user input
- Bad for projects with any ambiguity in requirements or technology
- Often run out of time for testing
- “The waterfall model amounts to a pledge by all parties not to learn anything while doing the actual work.”
Rapid Prototyping
- “People don’t know what they want until they see what they don’t want.” – Humphrey’s Law
- “People don’t know what they want until you show it to them.” – Steve Jobs
Incremental
- Software becomes more complex as the time going
⇧