L19 - life cycle and process models

L19 - life cycle and process models - Engineering Design...

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

View Full Document Right Arrow Icon
Engineering Design and the Software Life Cycle • Over the next week or so, we will consider: – Software Life Cycle • Several life cycle models exist, we’ll touch on some – Engineering Design • general engineering design process – Software Engineering Design • the Rational Unified Process – Object Oriented Design and the First Design Project
Background image of page 1

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

View Full DocumentRight Arrow Icon
How Programs Are Usually Written … This is how the program is described by marketing department The requirements specification was defined like this The developers understood it in that way This is how the problem was solved before. This is how the problem is solved now That is the program after debugging This, in fact, is what the customer wanted … :-) Images due to I. Potopov
Background image of page 2
The Software Life Cycle A software product usually starts as a vague concept – wouldn’t it be nice if the computer could do … – this leads to need determination and a refinement of the concept One software life cycle model: – build and fix – may work on short exercises (100 to 200 lines of code) – really bad if the product is of any realistic size the cost of detecting and correcting a fault in a program rises very quickly after implementation begins build first version modify until client is satisfied maintenance phase product retirement
Background image of page 3

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

View Full DocumentRight Arrow Icon
Phases of the “Traditional” Software Life Cycle requirements phase – concept explored and refined; the customer’s requirements are elicited specification (or analysis) phase – client’s requirements are analyzed and a specification document is produced – what the product is supposed to do is documented in the spec doc – a software project management plan is developed design phase – architectural design break the product down into components called modules – detailed design design each module – the resulting design documents describe how the product does what it is supposed to do
Background image of page 4
Phases of the “Traditional” Software Life Cycle (cont) implementation phase – code and test the various components integration phase – components are combined and tested as a whole – acceptance testing by the client and deployment in the client’s environment ends this phase maintenance phase – all changes to the product once the client has agreed that it meets the spec doc – kinds of maintenance: corrective maintenance (software repair – fix it while leaving the specifications unchanged) enhancement (software update – changes to the specs and implementation of these changes): perfective maintenance (changes the client thinks will improve the product) adaptive maintenance (changes made in response to changed operating environment)
Background image of page 5

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

View Full DocumentRight Arrow Icon
Software Process Models • What’s a software process? – A structured set of activities required to develop a
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.

Page1 / 28

L19 - life cycle and process models - Engineering Design...

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