Diane Pozefsky. Interactions  There is no “right answer”  Typically people and product are fixed  … can adapt process  (which is where we will start)

Slides:



Advertisements
Similar presentations
Software Processes.
Advertisements

Prescriptive Process models
SDLC – Beyond the Waterfall
The System and Software Development Process Instructor: Dr. Hany H. Ammar Dept. of Computer Science and Electrical Engineering, WVU.
Software Development Life-Cycle Models
PROC-1 3. Software Process. PROC-2 What’s a process? Set of activities in creating software It involves creativity –hard to automate –Requires human judgment.
Chapter 2 Modeling the Process and Life Cycle Shari L. Pfleeger
Systems Analysis and Design in a Changing World, 6th Edition
CHAPTER 1 SOFTWARE DEVELOPMENT. 2 Goals of software development Aspects of software quality Development life cycle models Basic concepts of algorithm.
29 September Interactions  There is no “right answer”  Typically people and product are fixed  … can adapt process  (which is where we will.
 © Ian Sommerville A software process model is an abstract representation of a process. It presents a description of a process from some particular perspective.
Copyright © Texas Education Agency, Computer Programming Software Life Cycle.
SYSC System Analysis and Design
6 December ’s  60’s “Cowboys” wrote software anyway that they could Difference between best programmers and worst as high as 28:1 (many sources)
20 September Importance of People Most important factor in the quality of software is the quality of the programmers If your life depended on.
22 September Fundamental Steps STEPS  Requirements  Design  Implementation  Integration  Test  Deployment  Maintenance MODELS Waterfall.
Software Development. Sub Processes Analysis - Environment, Requirements, Use cases Design - Program, Module, Function Implementation Validation - Test,
Software Development Overview CPSC 315 – Programming Studio Spring 2009.
Software Development Overview CPSC 315 – Programming Studio Spring 2008.
CMSC 345, Version 1/03 An Overview of Software Processes Reference: Software Engineering, by Ian Sommerville, 6 th edition, Chapter 3.
Diane Pozefsky. 1960’s  60’s “Cowboys” wrote software anyway that they could Difference between best programmers and worst as high as 28:1 (many sources)
1 CMPT 275 Software Engineering Software life cycle.
Dr. Tom WayCSC Software Processes CSC 4700 Software Engineering.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 4 Slide 1 Software Processes.
©Ian Sommerville 2000 Software Engineering, 6th edition. Chapter 1 Slide 1 Software Processes (Chapter 3)
Software Processes lecture 8. Topics covered Software process models Process iteration Process activities The Rational Unified Process Computer-aided.
Prescriptive Process Models
Engineering  Turning ideas into reality  Creating something useful from other things using science and math.
1/23 Prescriptive Process Models. 2/23 Prescriptive Models Prescriptive process models advocate an orderly approach to software engineering Prescriptive.
1 Software Development Software Engineering is the study of the techniques and theory that support the development of high-quality software The focus is.
CSE 403 Lecture 2 Software Lifecycle Models Reading: Rapid Development Ch. 7, 25 (further reading: Ch. 21, 35, 36, 20) slides created by Marty Stepp
Solar Tech Chuck Hess, CEO Jamie Tofte, CFO Christina Cruz, CTO.
WATERFALL DEVELOPMENT MODEL. Waterfall model is LINEAR development lifecycle. This means each phase must be completed before moving onto the next!!! WHAT.
24 January Software Engineering Processes Risk Management.
Ch7: Software Production Process. 1 Waterfall models  Invented in the late 1950s for large air defense systems, popularized in the 1970s  Main characteristics:
©Ian Sommerville 2006Software Engineering, 8th edition. Chapter 4 Slide 1 Software Processes.
CS223: Software Engineering Lecture 5: Software Development Models.
Software Engineering Process Models Models for Guiding the Development of Software.
Waterfall Model Software project Management. Waterfall Model  The Waterfall Model was first Process Model to be introduced. It is also referred to as.
Introduction Requirements and the Software Lifecycle (3)
Teaching slides Chapter 2. Chapter 2 Software Engineering Methodologies Introduction Why a methodology? Agile methodologies Waterfall model Rational Unified.
Software Engineering Overview 23 January. Software Engineering Overview What is engineering? Why is software engineering different than other engineering.
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...
CS 4500: Software Development Software Process. Materials Sommmerville Chapters 1, 2 and 3 Software Cycle and Models:
10 September Interactions  There is no “right answer”  Typically people and product are fixed  … can adapt process  (which is where we will.
Industrial Software Development Process Bashar Ahmad RISC Software GmbH.
Software Development. The Software Life Cycle Encompasses all activities from initial analysis until obsolescence Analysis of problem or request Analysis.
Laurea Triennale in Informatica – Corso di Ingegneria del Software I – A.A. 2006/2007 Andrea Polini II. Software Life Cycle.
Project Management Software development models & methodologies
Software Development.
Teaching slides Chapter 2
Software Development Overview
Methodologies and Algorithms
CSC 355 – Newer Approaches to System Development Life Cycles & Processes, Spring 2017 March 2017 Dr. Dale Parson.
Appendix B Agile Methodologies
Software Engineering Processes
Software Processes (a)
V-Shaped SDLC Model Lecture-6.
Systems Analysis and Design in a Changing World, 6th Edition
Software Process Models
Software Processes.
Computer Science Life Cycle Models.
Lecture 2 Revision of Models of a Software Process
Chapt 2 Iterative Evolutionary Agile.
Basic SDLC Models SDLC  System Development Life Cycle.
Software Process Models
Software Engineering: A Practitioner’s Approach, 6/e Chapter 3 Prescriptive Process Models copyright © 1996, 2001, 2005 R.S. Pressman & Associates, Inc.
SDLC (Software Development Life Cycle)
Software Engineering: A Practitioner’s Approach, 6/e Chapter 3 Prescriptive Process Models copyright © 1996, 2001, 2005 R.S. Pressman & Associates, Inc.
Software Development Overview
Presentation transcript:

Diane Pozefsky

Interactions  There is no “right answer”  Typically people and product are fixed  … can adapt process  (which is where we will start)

Fundamental Steps  Requirements  Design  Implementation  Test  Deployment  Maintenance

Processes  Differ by how often you do the steps Focus and emphasis  Points on the spectrum  Differences in overhead  Three fundamental processes Waterfall Spiral Iterative

Waterfall  Do it once  Traditional model  Used for large next version releases,  especially when  well understood product  tightly coupled changes

Waterfall  1970s  Built on 1950’s stage-wise process  Recognized the need for feedback Limited Heavy process

Waterfall  Pros Simple documentation management Clean design phase  Cons Least flexibility No early feedback

Iterative (a.k.a. Agile)  Many iterations  Each iteration is on a fixed cycle Typically biweekly  Used for projects with  lots of small independent, but well understood, changes  small development team  strong client involvement

Iterative  Reaction to waterfall  Derived from “evolutionary” process Requirements and specs evolve over time  Two well-known models Extreme programming SCRUM

Iterative (a.k.a. Agile)  Pros Fast feedback on problems Very adaptable to any changes Lots of versions to work with Heavy user involvement  Cons Document maintenance Code maintenance Requires good automation

Spiral  Few iterations  Each iteration adds new requirements  Used often for projects with less well defined requirements

Spiral  Risk based  Barry Boehm 1988  “A Spiral Model of Software Development and Enhancement”

Spiral  Pros Adaptation to changes based on risks Good customer interaction Early version Limited iterations provide phase structure  Cons Document maintenance

Historical Perspective  Waterfall: 1970, built on 1950’s stage- wise processes Recognized need for feedback  Iterative (agile): late 70s,modeled on evolutionary model Didn’t work well for large products  Spiral: 1988, risk-based

Unified Process  Variant of Spiral  Identifies that iterations differ  Also known as Rational Unified Process (Rational products) Rational Unified Process Phases Core Processes