Additional slides to accompany Chapter 3 : Process Model.

Slides:



Advertisements
Similar presentations
kareRCIserIsviFIsaRsþGnuvtþKMerag
Advertisements

Software Processes.
Prescriptive Process models
Lecture # 2 : Process Models
1COM6030 Systems Analysis and Design © University of Sheffield 2005 COM 6030 Software Analysis and Design Lecture 2- Software Process Models and Project.
Multimedia Specification Design and Production 2013 / Semester 1 / week 7 Lecturer: Dr. Nikos Gazepidis
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 1 Slide 1 المحاضرة الثانية.
Software Engineering Saeed Akhtar The University of Lahore Lecture 4 Originally shared for: mashhoood.webs.com.
CS487 Software Engineering Omar Aldawud
1 Chapter 4 - Part 1 Software Processes. 2 Software Processes is: Coherent (logically connected) sets of activities for specifying, designing, implementing,
Chapter 3 Process Models
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 4 Slide 1 Software Processes.
Sharif University of Technology Session # 3.  Contents  Systems Analysis and Design Sharif University of Technology MIS (Management Information System),
1 CS 425/625 Software Engineering CS 425/625 Software Engineering Software Processes Based on Chapter 4 of the textbook [SE-7] Ian Sommerville, Software.
CS 425/625 Software Engineering Software Processes
Project phases and the life cycle
Software Life Cycle Model
3.3.1 apid pplication evelopment. What Rapid Application Design is including: – Joint Development Application Workshops (JAD). – Timeboxing The benefits.
CSI315 Web Technology and Applications
1COM6030 Systems Analysis and Design © University of Sheffield 2005 COM 6030 Software Analysis and Design Lecture 2- Software Process Models and Project.
1 CMPT 275 Software Engineering Software life cycle.
Chapter 2 The process Process, Methods, and Tools
THE PROTOTYPING MODEL The prototyping model begins with requirements gathering. Developer and customer meet and define the overall objectives for the software.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 4 Slide 1 Software Processes.
CS 360 Lecture 3.  The software process is a structured set of activities required to develop a software system.  Fundamental Assumption:  Good software.
Teaching material for a course in Software Project Management & Software Engineering – part II.
Software Engineering Environment  A quality focus: constant incremental improvement  Process: framework to organize development activities  Methods:
Prescriptive Process Models
Software Processes n What is a process?  Sequence of steps required to develop or maintain software n Characteristics  prescribes major activities 
Prescriptive Process Models Jon Walker. Prescription? What does prescriptive mean?
Rapid software development 1. Topics covered Agile methods Extreme programming Rapid application development Software prototyping 2.
Software Development Cycle What is Software? Instructions (computer programs) that when executed provide desired function and performance Data structures.
1 SWE Introduction to Software Engineering Lecture 4.
Software Engineering MCS-2 Lecture # 6
Software Process Model
Chapter 13: Software Life Cycle Models Omar Meqdadi SE 273 Lecture 13 Department of Computer Science and Software Engineering University of Wisconsin-Platteville.
Software Development Life Cycle (SDLC)
Software Project Management Iterative Model & Spiral Model.
©Ian Sommerville 2006Software Engineering, 8th edition. Chapter 4 Slide 1 Software Processes.
Software Model Process
Software Engineering Process Models Models for Guiding the Development of Software.
Chapter 1: Introduction Omar Meqdadi SE 3860 Lecture 1 Department of Computer Science and Software Engineering University of Wisconsin-Platteville.
Software Development Process CS 360 Lecture 3. Software Process The software process is a structured set of activities required to develop a software.
Software Engineering CE 501 Prepared by : Jay Dave.
Teaching slides Chapter 2. Chapter 2 Software Engineering Methodologies Introduction Why a methodology? Agile methodologies Waterfall model Rational Unified.
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.
3 - Software Process Models. Based on slides of: Ian Sommerville :
Systems Development Life Cycle
1 Chapter 2 SW Process Models. 2 Objectives  Understand various process models  Understand the pros and cons of each model  Evaluate the applicability.
Systems Development Process and Methodologies Dr. T. Ravichandran.
Chapter 2: The Process. What is Process? Software Engineering Process is the glue that holds the technology layers together and enables rational and timely.
Methodologies/Life Cycle Models
Software Development - Methodologies
Teaching slides Chapter 2
Unit 6 Application Design KLB Assignment.
The Software Development Cycle
SOFTWARE LIFE-CYCLES Beyond the Waterfall.
CS 425/625 Software Engineering Software Processes
Rapid Application Development Model
Chapter 2 SW Process Models
Software Life Cycle Models
Prescriptive Process Models
Lecture 2 Revision of Models of a Software Process
Software life cycle models
SE-2-Session-4 Software Process and Process Models
SOFTWARE LIFE-CYCLES Beyond the Waterfall.
Software Processes Process should be
The Waterfall Model Also known as: classic life cycle, the waterfall model, the linear model Rarely projects are sequential (allows iteration indirectly)
The Software Development Cycle
Presentation transcript:

Additional slides to accompany Chapter 3 : Process Model

Software Process Models Irrespective of which level of CMM the organization has, the software engineer has 5 choices for selection of software process models. The models are:  Linear Sequential Model(LSM)  The Prototype Model(PRM)  The Rapid Application Development Model(RAD)  The Incremental Model(INM)  The Boehm Spiral Model(BSM) In all models, core activities, namely Analysis- Design-Code-Test are common. However, their execution differs from model to model.

Linear Sequential Model(LSM)  Also called classic life cycle model similar to Waterfall Model The Prototype Model(PRM)  This model is proposed when users, customers or stakeholders are not sure about the requirements  Also sometimes software engineer is not sure what kind of design solution would be the most appropriate

The Rapid Application Development Model(RAD)  RAD is proposed when requirements and solutions can be modularized as independent system or software components; each of which can be developed by different teams The Incremental Model(INM)  Use this model when the requirement is complex and visualizing it in precise terms is difficult  In each increment, additional functions and features are added after confirming the utility of earlier increments

The difference between RAD and INM is that :  RAD – the requirement of software systems is well defined and agreed to all i.e users, customers and stakeholders  INM – requirement need to evolved incrementally to ensure its correctness and to ensure quality

The Boehm Spiral Model(BSM)  Combines INM, RAD and LSM with the use of prototyping  Recommended where requirements and solutions is for developing full-fledge, large, complex system with a lot of features and facilities from scratch  Used when experimenting on technology, trying out new skill and when the user is not able to offer requirement in clear terms