703_sec2a - Software Life-Cycle and Process Models Used...

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

View Full Document Right Arrow Icon
1 Software Life-Cycle and Process Models Used with permission of: Krzysztof Czarnecki
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 • Some of these slides are based on: – Lecture slides by Ian Summerville accompanying his classic textbook software engineering, see http://www.comp.lancs.ac.uk/ computing/resources/ser/
Background image of page 2
3 Overview • Build-and-fix model • Waterfall model • Rapid prototyping model • Incremental model • Evolutionary • Spiral model
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 Software Life-Cycle and Process Models • Life-cycle models – Phases in the life of artifacts • Process models – The software development and operation activities and their dependencies • Requirements elicitation • Specification • Design • Implementation • Integration • Testing • …
Background image of page 4
5 Build-and-Fix Model Properties – No planning or analysis – The working program is the only workproduct Advantage – Appropriate for small programs written by one person Disadvantage – Understandability and maintainability decrease rapidly with increasing program size – Totally unsatisfactory – Need a life-cycle model • “Game plan” • Phases • Milestones
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 Waterfall Model Characterized by Sequential steps (phases) Feedback loops (between two phases in development) Documentation-driven Advantages Documentation and clearly defined phases Maintenance easier (assuming up-to-date docs available) Disadvantages Complete and frozen specification document up-front often not feasible in practice Customer involvement in the first phase only Sequential and complete execution of phases often not desirable Process difficult to control The product becomes available very late in
Background image of page 6
Image of page 7
This is the end of the preview. Sign up to access the rest of the document.

This note was uploaded on 02/15/2010 for the course CAS 703 taught by Professor Tom during the Winter '10 term at McMaster University.

Page1 / 20

703_sec2a - Software Life-Cycle and Process Models Used...

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

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