A Prototyping Lifecycle. The Waterefall Model and Prototyping 4 As early as the 1980’s the classic “Waterfall model” of software development was criticised.

Slides:



Advertisements
Similar presentations
Prescriptive Process models
Advertisements

SYSC System Analysis and Design
Agile
Dynamic Systems Development Method (DSDM)
 RAD is a complete methodology covering systems development from business requirements through to ongoing development ( often incorectly called maintenance)
Left overs. Agenda 9. Sept Leftovers PM –Methodologies –Models in system development XPM Project Group establishment (45 min) Introduction to requirement.
NJIT From Inception to Elaboration Chapter 8 Applying UML and Patterns Craig Larman.
1 SOFTWARE LIFE-CYCLES Beyond the Waterfall. 2 Requirements System Design Detailed Design Implementation Installation & Testing Maintenance The WATERFALL.
1 CS 691z/791z Topics on Software Engineering CS 691z/791z Topics on Software Engineering Software Processes Based on Chapter 4 of the book [SE-8] Ian.
03/12/2001 © Bennett, McRobb and Farmer Managing Object-Oriented Projects—DSDM and XP Based on Chapter 21 of Bennett, McRobb and Farmer: Object.
University of Sunderland CSEM04 ROSCO Unit 13 Unit 13: Risk Methods CSEM04: Risk and Opportunities of Systems Change in Organisations Dr Lynne Humphries.
Software Engineering: A Practitioner’s Approach, 6/e Chapter 4 Agile Development copyright © 1996, 2001, 2005 R.S. Pressman & Associates, Inc. For University.
Coming up: The Manifesto for Agile Software Development 1 Software Engineering: A Practitioner’s Approach, 7/e Chapter 3 Agile Development Software Engineering:
Keith Richards Keith Richards Consulting DSDM + PRINCE2 + Facilitation
CHAPTER 19 Building Software.
Agile Process: Overview n Agile software engineering represents a reasonable compromise to conventional software engineering for certain classes of software.
Software Engineering Lecture No:12. Lecture # 7
CSI315 Web Technology and Applications
Introduction to RUP Spring Sharif Univ. of Tech.2 Outlines What is RUP? RUP Phases –Inception –Elaboration –Construction –Transition.
THE PROTOTYPING MODEL The prototyping model begins with requirements gathering. Developer and customer meet and define the overall objectives for the software.
 Since in 1994, DSDM, the Dinamic Systems Development Method, has gradually become the number one framework for rapid application development (RAD) in.
These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 6/e and are provided with permission by.
Chapter 4 An Agile View of Process
Chapter 4 Agile Development 1. The Manifesto for Agile Software Development 2 “We are uncovering better ways of developing software by doing it and helping.
DSDM
CS 360 Lecture 3.  The software process is a structured set of activities required to develop a software system.  Fundamental Assumption:  Good software.
Industrial Software Project Management Some views on project managing industrial and business software projects.
May 11, 2007Mohamad Eid Interaction Design Process Chapter 4.
Interaction Design Process COMPSCI 345 S1 C and SoftEng 350 S1 C Lecture 5 Chapter 3 (Heim)
[ §3 : 1 ] 2. Life-Cycle Perspective Overview 2.1 Motivation 2.2 Waterfall Model 2.3 Requirements in Context.
These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 6/e and are provided with permission by.
University of Palestine software engineering department Testing of Software Systems Testing throughout the software life cycle instructor: Tasneem Darwish.
Agile
IS Methodologies. Systems Development Life Cycle - SDLC Planning Planning define the system to be developed define the system to be developed Set the.
Coming up: The Manifesto for Agile Software Development 1 Software Engineering: A Practitioner’s Approach, 7/e Chapter 3 Agile Development Software Engineering:
Fifth Lecture Hour 9:30 – 10:20 am, September 9, 2001 Framework for a Software Management Process – Life Cycle Phases (Part II, Chapter 5 of Royce’ book)
Gary MarsdenSlide 1University of Cape Town Human-Computer Interaction - 4 User Centred Design Gary Marsden ( ) July 2002.
University of Toronto at Scarborough © Kersti Wain-Bantin CSCC40 other methodologies 1 Method/Process = step-by-step description of the steps involved.
1 The Manifesto for Agile Software Development “We are uncovering better ways of developing software by doing it and helping others do it. Through this.
CS 3610: Software Engineering – Fall 2009 Dr. Hisham Haddad – CSIS Dept. Chapter 4 Agile Development Discussion of Agile Development and Agile Process.
© 2007 BigVisible Solutions, Inc. All Rights Reserved Training Solutions Agile Training Game v
Chapter 3 Agile Development
Overview of RUP Lunch and Learn. Overview of RUP © 2008 Cardinal Solutions Group 2 Welcome  Introductions  What is your experience with RUP  What is.
Agile. Processes Waterfall Traditional With prototyping Sprial Agile Dynamic Systems Development Method (DSDM) Scrum Crystal eXtreme Programming (XP)
Interaction Design Process COMPSCI 345 S1 C and SOFTENG 350 S1 C Lecture 19 Lecturer: Jim Warren Based on Heim Chapter 3.
DSDM Dynamic Systems Development Method. DSDM Methodology Goals On time Within budget Of desired quality.
Software Development Process CS 360 Lecture 3. Software Process The software process is a structured set of activities required to develop a software.
44222: Information Systems Development
Some Rapid Application Development (RAD) Principles Dr. Ernest Cachia.
Software Engineering: A Practitioner’s Approach, 6/e Chapter 4 Agile Development copyright © 1996, 2001, 2005 R.S. Pressman & Associates, Inc. For University.
Unit 6 Application Design KLB Assignment.
Software Engineering: A Practitioner’s Approach, 6/e Chapter 4 Agile Development copyright © 1996, 2001, 2005 R.S. Pressman & Associates, Inc. For University.
Ernest Cachia Department of Computer Information Systems
Software Engineering: A Practitioner’s Approach, 7/e Chapter 3 Agile Development copyright © 1996, 2001, 2005 R.S. Pressman & Associates, Inc. For University.
Software Engineering: A Practitioner’s Approach, 6/e Chapter 4 Agile Development copyright © 1996, 2001, 2005 R.S. Pressman & Associates, Inc. For University.
V-Shaped SDLC Model Lecture-6.
UNIFIED PROCESS.
How to Successfully Implement an Agile Project
Lecture # 5 Software Development Project Management
Atern v2 – Summary of changes from v1
Agile Process: Overview
Software Engineering: A Practitioner’s Approach, 6/e Chapter 4 Agile Development copyright © 1996, 2001, 2005 R.S. Pressman & Associates, Inc. For University.
Gathering Systems Requirements
Project organisation and work to be done
Software Engineering: A Practitioner’s Approach, 6/e Chapter 4 Agile Development copyright © 1996, 2001, 2005 R.S. Pressman & Associates, Inc. For University.
Gathering Systems Requirements
Information Systems Development (ISD) Systems Development Life Cycle
Presentation transcript:

A Prototyping Lifecycle

The Waterefall Model and Prototyping 4 As early as the 1980’s the classic “Waterfall model” of software development was criticised –as a “fake” –as failing to address the fundamental issue of the software crisis incomplete, inaccurate, changed requirements –for pushing user evaluation to the end of the lifecycle 4 A “prototyping” RAD lifecycle proposed instead –rejected as “unmanageable” –prototyping restricted to requirements gathering 4 RAD has re-emerged in the last two years

DSDM2- a RAD Process 4 The Dynamic Systems Development Method (DSDM2) is a public domain standard specification for a Rapid Application Development (RAD) or evolutionary delivery process –supported by more than 200 companies in the UK –worthy as an example of a modern, industrial strength, lifecycle for prototyping

DSDM Overview 4 “Three pizzas and a cheese”: the five phases of DSDM are: 1. Feasibility study 2. Business study 3. Functional model iteration 4. System design and build iteration 5. Implementation

“Three Pizzas and a Cheese”

DSDM Feasibility Study 4 An assessment of whether or not DSDM is appropriate to the project. –Has serious impact on user community; worth it in trade-off to deliver in sharp time-scales? –Feasibility study should be short, sharp –Deliverables include Feasibility Report; Outline Development Plan and a fast prototype

DSDM Business Study 4 Aim is to gain understanding of the business processes of the client organisation 4 The activity is strongly collaborative –involves facilitated workshops 4 First deliverable is a Business Area Definition –high-level, prioritised, view of processes to be automated –identifies business processes, user classes, user representatives for development 4 Other deliverables are System Architecture Definition and Outline Prototyping Plan

DSDM Functional Model Iteration 4 Shares with the Design and Build Iteration the following cycles of four activities : 1. Identify what you are doing in the cycle 2. Agree how you will go about doing it 3. Do it 4. Check that you did it right by reviewing documents, demonstrating a prototype or software testing 4 Delivers Analysis model(s) and major software components

DSDM Functional Iteration (contin.) 4 Other products include –Prioritised functions core functions are guaranteed delivery –Functional prototyping review documents maintains history of user feedback –Non-functional requirements –Risk analysis of future development

DSDM Design and Build Iteration 4 Product is the Tested System –tests are iterative –tested system will not necessarily deliver ALL requirements, but will deliver the core “minimum usable subset”) –early deliverables are design prototypes and design prototyping review documents.

DSDM Implementation 4 Covers cutover from development environment to operational environment 4 Products include –delivered system and documentation –User Manual –trained user population –Project Review Document

Principles of DSDM 4 Active user involvement is imperative 4 DSDM teams must be empowered to make decisions 4 Focus is on frequent delivery of products 4 Fitness for purpose is the essential criterion for acceptance of deliverables 4 Iterative and incremental development is necessary to converge on an accurate business solution 4 All changes during development are reversible

Principles of DSDM (contin.) 4 Requirements are base-lined at a high level 4 Testing is integrated throughout the lifecycle 4 A collaborative and co-operative approach between all stakeholders is essential