Ch3 - Chapter 3 Requirements and the Software Lifecycle The...

Info iconThis preview shows pages 1–8. Sign up to view the full content.

View Full Document Right Arrow Icon
1 Requirements and the Software Lifecycle The traditional software process models Waterfall model Spiral model The iterative approach Chapter 3
Background image of page 1

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
2 Any Good Software Development Process should have Collect + Analysis: Identify what the system should do Design: Determine what is the best way to do it Implementation + Test: Build the system correctly
Background image of page 2
3 Traditional Software Process Models Effective requirements management can occur only within the context of a reasonably well- defined software process that defines the full set of activities your team must execute to deliver the final software product. In order for your team to reach its goal, your team's software development process should define who is doing what , when and how.
Background image of page 3

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
4 The Waterfall Model The waterfall model is sequential: Software activities proceed logically through a sequence of steps . Each step bases its work on the activities of the previous step. The waterfall model was widely followed in the 1970s and '80s and served successfully as a process model for a variety of medium- to large-scale projects.
Background image of page 4
5 The Waterfall Model (Royce 1970)
Background image of page 5

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
6 The Waterfall Model 1. Collect major requirements (hardware, software & human parts), define clearly, and document them. 2. 3. Code the system and test units, 4. Link all parts, install and test as a whole 5. Corrective, adaptive & perfective maintenance
Background image of page 6
7 Waterfall Model Problems Inflexible partitioning of the project into distinct stages makes it difficult to respond to changes in customer requirements. Therefore, this model is only appropriate when the requirements are well-understood and changes will be fairly limited during the design process.
Background image of page 7

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
Image of page 8
This is the end of the preview. Sign up to access the rest of the document.

Page1 / 25

Ch3 - Chapter 3 Requirements and the Software Lifecycle The...

This preview shows document pages 1 - 8. Sign up to view the full document.

View Full Document Right Arrow Icon
Ask a homework question - tutors are online