Life Cycles Birth to death! i.e what happens to a piece of software from the first appearance of the need for it to the time when it is finally retired.

Slides:



Advertisements
Similar presentations
Software Processes.
Advertisements

Prescriptive Process models
Computer Science Department
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 4 Slide 1 Software Processes.
CS 501: Software Engineering Fall 2000 Lecture 2 The Software Process.
Unit 2. Software Lifecycle
©Ian Sommerville 2006Software Engineering, 8th edition. Chapter 4 Slide 1 Software Processes.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 1 Slide 1 المحاضرة الثانية.
Software Project Management
CSE 470 : Software Engineering The Software Process.
Soft. Eng. II, Spring 2002Dr Driss Kettani, from I. Sommerville1 CSC-3325: Chapter II Chap1: Software Engineering Models (Review) Mandatory reading: chapter.
The software process A software process is a set of activities and associated results which lead to the production of a software product. This may involve.
Software Engineering COMP 201 1COMP201 - Software Engineering Lecturer: Sebastian Coope Ashton Building, Room G.18 COMP.
CS3773 Software Engineering Lecture 01 Introduction.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 4 Slide 1 Software Processes.
1 CS 501 Spring 2003 CS 501: Software Engineering Lecture 2 Software Processes.
Requirements - Why What and How? Sriram Mohan. Outline Why ? What ? How ?
CS 501: Software Engineering
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 4 Slide 1 Software Process Models.
©Ian Sommerville 2000 Software Engineering, 6th edition Slide 1 Software Processes l Coherent sets of activities for specifying, designing, implementing.
CS 501: Software Engineering
Software Engineering Incorporating Interface Design Into Software Engineering.
IMS1805 Systems Analysis Topic 6: Analysis as a process within a process.
Software Engineering: A Practitioner’s Approach, 6/e Chapter 3 Prescriptive Process Models copyright © 1996, 2001, 2005 R.S. Pressman & Associates, Inc.
Objectives By the end of today’s class you will be able to… –Describe the major steps in the interaction design process –Explain the importance of iterative.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 4 Slide 1 Software Processes.
CMSC 345, Version 1/03 An Overview of Software Processes Reference: Software Engineering, by Ian Sommerville, 6 th edition, Chapter 3.
Software Life Cycle Model
Chapter 3 Software Processes.
CSI315 Web Technology and Applications
1 CSE 403 Software Lifecycle Models Reading: Rapid Development Ch. 7, 25 (further reading: Ch. 21, 35, 36, 20) These lecture slides are copyright (C) Marty.
Software Processes.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 4 Slide 1 Software Processes.
©Ian Sommerville 2000, Mejia-Alvarez 2009 Slide 1 Software Processes l Coherent sets of activities for specifying, designing, implementing and testing.
Introduction to Software Development 1. Outline The code-compile-debug process for writing a program The software development process 2.
Software Processes lecture 8. Topics covered Software process models Process iteration Process activities The Rational Unified Process Computer-aided.
SOFTWARE ENGINEERING MCS-2 LECTURE # 3. SOFTWARE PROCESS  A software development process, also known as a software development life- cycle (SDLC), is.
13-January-2003cse LifeCycle © 2003 University of Washington1 Lifecycle CSE 403, Winter 2003 Software Engineering
1 SWE Introduction to Software Engineering Lecture 4.
Software Engineering - Abdul Majeed. What is software? Definition of Software Engineering Software Process Generic view of Software Engineering Software.
1 CS 501 Spring 2004 CS 501: Software Engineering Lecture 2 Software Processes.
Introduction to Software Development (Software Engineering - I)
Chapter 13: Software Life Cycle Models Omar Meqdadi SE 273 Lecture 13 Department of Computer Science and Software Engineering University of Wisconsin-Platteville.
Intro. to Software Engineering 1CSCI 3333 Data Structures.
WATERFALL DEVELOPMENT MODEL. Waterfall model is LINEAR development lifecycle. This means each phase must be completed before moving onto the next!!! WHAT.
KUFA UNIVERSITY Department of Computer Science. Fundamentals of Software Engineering Presented By Neamah Hassan Presented By Neamah Hassan.
Prototyping life cycle Important steps 1. Does prototyping suit the system 2. Abbreviated representation of requirements 3. Abbreviated design specification.
Process Asad Ur Rehman Chief Technology Officer Feditec Enterprise.
Modelling the Process and Life Cycle. The Meaning of Process A process: a series of steps involving activities, constrains, and resources that produce.
CC20O7N Software Engineering 1 CC2007N Software Engineering 1 Part 1 Introduction to Software Engineering.
1 These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 5/e and are provided with permission by.
Chapter 1: Introduction Omar Meqdadi SE 3860 Lecture 1 Department of Computer Science and Software Engineering University of Wisconsin-Platteville.
Lectures 2 & 3: Software Process Models Neelam Gupta.
CSE 403, Spring 2008, Alverson Software Development Lifecycle The Power of Process.
Topic:- At the end we will be able to explain:- Why it is called Meta Model ?? Spiral Model Its Advantages & Disadvantages… Phases of Spiral Model...
1 Chapter 2 SW Process Models. 2 Objectives  Understand various process models  Understand the pros and cons of each model  Evaluate the applicability.
Chapter3:Software Processes
Software Life Cycle “What happens in the ‘life’ of software”
CS 5150 Software Engineering
SOFTWARE LIFE-CYCLES Beyond the Waterfall.
Software Processes (a)
Chapter :Software Process Model
CS 425/625 Software Engineering Software Processes
Chapter 2 SW Process Models
Software Engineering: A Practitioner’s Approach, 7/e Chapter 2 Prescriptive Process Models copyright © 1996, 2001, 2005 R.S. Pressman & Associates, Inc.
Software Engineering: A Practitioner’s Approach, 7/e Chapter 2 Prescriptive Process Models copyright © 1996, 2001, 2005 R.S. Pressman & Associates, Inc.
Process Models Coming up: Prescriptive Models.
An Overview of Software Processes
Software Processes.
SOFTWARE ENGINEERING LECTURE 2
Presentation transcript:

Life Cycles Birth to death! i.e what happens to a piece of software from the first appearance of the need for it to the time when it is finally retired from use. An attempt to address S/W problems by understanding the processes involved in each part of the software lifecycle. –classic text - “The mythical man-month” by Brooks, Addison Wesley Still the subject of research –Software Engineering journals the best source of modern information Shows the need for active management of the process Different lifecycle models have been used to help study software lifecycles –Waterfall model –Prototyping –Boehm’s spiral –Formal models

The Waterfall model Requirements definition System & software design Implementation & unit testing Integration & system testing Operation & maintenance

Difficulties with the waterfall model Real projects are rarely so sequential – there is always some iteration or backtracking, which is not ‘part of the plan’ and so causes management problems. It assumes the customers knows all the requirements exactly at the very start. This will often not be the case, particularly in a fast moving world where different techniques (especially in the area of user interfaces) are evolving all the time. It doesn’t produce anything visible for the customer until almost the end of the cycle, by which time, especially if there are any delays, the customer, or more likely the financial backer may be pulling their hair (and maybe their money) out! This, despite the fact that the project may be very healthy indeed.

Prototyping Mainly to validate user requirements, which may be unclear Throw away? or transform to final design Advantages –Can clear up misunderstandings (use of language) user/developer –Can identify missing user services –Developer can identify inconsistencies in requirements –Can provide a working model for managers/sponsors/accountants Disadvantages –Hard to manage –Temptation to use as real system –Features may be omitted –Not a good basis for any contract Outline specspecify system Develop prototype Evaluate prototype design & implement validate components