Chapter 5 Evolutionary requirements

Slides:



Advertisements
Similar presentations
Chapter 05: Evolutionary Requirements Definition : Requirements  “Requirements are capabilities and conditions to which the system, and more broadly.
Advertisements

©Ian Sommerville 2006Software Engineering, 8th edition. Chapter 4 Slide 1 Software Processes.
Adaptive Processes Software Processes Adaptive Processes.
Chapter 5 Evolutionary requirements –Expect change! –Learn as you go –Validate as you build Why – 25% requirements change on an average software project.
Software Processes Coherent sets of activities for specifying, designing, implementing and testing software systems.
Chapter 7 Other Requirements Good Fast Cheap Pick any two. 1CS John Cole.
Object-Oriented Analysis and Design
Requirements Analysis CMPT 371 Fall 2004 J.W. Benham.
©Ian Sommerville 2000 Software Engineering, 6th edition. Chapter 8 Slide 1 Software Prototyping l Rapid software development.
Software Engineering Incorporating Interface Design Into Software Engineering.
Dr. Kivanc DincerCS319 Week 1 - Sept.12,20051 Chapter 4 INCEPTION IS NOT THE REQUIREMENTS PHASE Objectives Define the inception step. Motivate the following.
NJIT Evolutionary Requirements Chapter 5 Applying UML and Patterns Craig Larman.
Figure 1.1 The observer in the truck sees the ball move in a vertical path when thrown upward. (b) The Earth observer views the path of the ball as a parabola.
©Ian Sommerville 2000 Software Engineering, 6th edition. Chapter 8 Slide 1 Software Prototyping l Rapid software development to validate requirements l.
Copyright © Craig Larman All Rights Reserved Requirements.
CompSci 230 Software Design and Construction
Supplementary Specifications (Chapters 20,22 - Requirements Text) 1.
Case Study :. Introduction The ATM network will consist of a large number of ATM machines distributed over a wide geographical area. The network must.
Chapter 11: Software Prototyping Omar Meqdadi SE 273 Lecture 11 Department of Computer Science and Software Engineering University of Wisconsin-Platteville.
©Ian Sommerville 2000 Software Engineering, 6th edition. Chapter 8 Slide 1 Software Prototyping l Rapid software development to validate requirements.
Chapter 6 Use Case –The interaction between an actor and the system.
Chapter 7 Applying UML and Patterns -Craig Larman
Chapter 7 Applying UML and Patterns Craig Larman
Jan 7, A UP project organizes the work and iterations across four major phases: – Inception -- approximate vision, business case, scope, vague estimates.
 Dr. Syed Noman Hasany.  Review of known methodologies  Analysis of software requirements  Real-time software  Software cost, quality, testing and.
Chapter 13: Software Life Cycle Models Omar Meqdadi SE 273 Lecture 13 Department of Computer Science and Software Engineering University of Wisconsin-Platteville.
Chapter 5 Evolutionary Requirements. Introduction 5.1 Definition: Requirements 5.2 Evolutionary vs. Waterfall Requirements 5.3 What are Skillful Means.
Software Engineering 1 Object-oriented Analysis and Design Applying UML and Patterns An Introduction to Object-oriented Analysis and Design and Iterative.
Understanding Requirements Chapter 5 Applying UML and Patterns -Craig Larman.
Software Development Life Cycle (SDLC)
©Ian Sommerville 2006Software Engineering, 8th edition. Chapter 4 Slide 1 Software Processes.
Software Process Models The slides and the material of this chapter is adopted from: 1. “Software Engineering”, by I. Somerville, 7th Ed., “Software.
Larman chapter 41 Inception Larman chapter 4 and 7.
©Ian Sommerville 2000Software Engineering, 6th edition. Chapter 1 Slide 1 Chapter 1 Introduction As modified by Randy Smith.
CS 310 Ch 4: Software Processes Software process: a set of activities that lead to a software system specification design and implementation validation.
CS 501: Software Engineering Fall 1999 Lecture 23 Design for Usability I.
CSC 480 Software Engineering
Prototyping in the software process
MISY 301 Mr.Mohammed Rafeeque.
UML Diagrams By Daniel Damaris Novarianto S..
SOFTWARE ENGINEERING - SOFTWARE LIFECYCLE MODELS
Exam 0 review CS 360 Lecture 8.
Environment. Waterfall.
Software Engineering Experimentation
Evolutionary requirements
School of Business Administration
Transforming Organizations
System Development Process
WXGE6103 Software Engineering Process and Practice
Prototype Model Lecture-4.
Systems Analysis and Design
UML Diagrams Jung Woo.
Unified Process(UP) popo.
HCI in the software process
The design process Software engineering and the design process for interactive systems Standards and guidelines as design rules Usability engineering.
The design process Software engineering and the design process for interactive systems Standards and guidelines as design rules Usability engineering.
Software Prototyping Animating and demonstrating system requirements.
Documentation in Continuous Delivery Model and DevOps
Week 2.
Software Engineering Experimentation
Chapter 6 Use Case The interaction between an actor and the system.
Evolutionary Requirements
Bachelor’s Thesis Process
HCI in the software process
Other Requirement Artifacts
HCI in the software process
10TH STANDARAD TEXT BOOK-1
Styling Individual Tags
Chapter 3 Discussion Pages
Other System Requirements
Presentation transcript:

Chapter 5 Evolutionary requirements Expect change! Learn as you go Validate as you build Why – 25% requirements change on an average software project

The case against waterfall On average 25% of requirements change during a project Inflexible Fig 5.1 in text - 45 % of requirements actually not used! A word of caution - waterfall is sometime still the best way! (why?)

Finding The text emphasizes finding requirements This requires skill!

FRUPS + Functional Usability Reliability Performance Supportability

+ Implementation Interface Operations Packaging Legal

UP defines: Use-Case Model Supplementary specs – non-functional Glossary Vision Business rules

Resources Text offers several suggestions Also, refer to any text on UP or software engineering as well