Simulation of Market-Driven Requirements Engineering Processes Björn Regnell, Martin Höst, Johan Natt och Dag, Josef Nedstam, Lena Karlsson.

Slides:



Advertisements
Similar presentations
Proposal / Request For Proposal Proposal / Request For Proposal Initiation Control Planning Close-down Execution.
Advertisements

Developing a communications and engagement commissioning support service A new locally delivered, nationwide service for the NHS January 2012.
© Colin Potts, 1996 C3-1 Feasibility and Desirability analysis Colin Potts Georgia Tech.
1 Requirements and the Software Lifecycle The traditional software process models Waterfall model Spiral model The iterative approach Chapter 3.
RAMIRI2 Prague 2012 Project management and the RI Life Cycle.
Stoimen Stoimenov QA Engineer SitefinityLeads, SitefinityTeam6 Telerik QA Academy Telerik QA Academy.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 17 Slide 1 Rapid software development.
Copyright 2000, Stephan Kelley1 Estimating User Interface Effort Using A Formal Method By Stephan Kelley 16 November 2000.
SWE Introduction to Software Engineering
Iterative development and The Unified process
CSE Senior Design II Staged Delivery Instructor: Mike O’Dell.
D. Pandey, A. K. Ramani and U. Suman.  D. Pandey  assistant professor at the Department of Information Technology of the BBA University in India. 
Chapter 2- Software Process Lecture 4. Software Engineering We have specified the problem domain – industrial strength software – Besides delivering the.
Software Test Plan Why do you need a test plan? –Provides a road map –Provides a feasibility check of: Resources/Cost Schedule Goal What is a test plan?
CMSC 345, Version 1/03 An Overview of Software Processes Reference: Software Engineering, by Ian Sommerville, 6 th edition, Chapter 3.
Pre-Project Planning Lessons from the Construction Industry Institute Construction Industry Institute Michael Davis, P. Eng, PMP Ontario Power Generation.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 7 Slide 1 Requirements Engineering Processes 1.
13 April 2004 Experiences from Architectural Evolution Josef Nedstam Even-André Karlsson.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 17 Slide 1 Extreme Programming.
© AMALTHEA - All rights reserved, also regarding any disposal, exploitation, reproduction, editing, distribution, as well as in the event of applications.
© Copyright 2010 Hewlett-Packard Development Company, L.P. 1 1 Risk Assessment and Decision Support for Security Policies IEEE Policy 2011 Symposium Marco.
S/W Project Management Software Process Models. Objectives To understand  Software process and process models, including the main characteristics of.
Introduction to RUP Spring Sharif Univ. of Tech.2 Outlines What is RUP? RUP Phases –Inception –Elaboration –Construction –Transition.
Paper 484 Penny F. Dakhil 1 Session 484 Managing a Portfolio of Projects Penny Dakhil Program Manager HP Corporaate IT Planning and Execution Roseville.
BSBPMG508A Manage Project Risk 11.4 Perform Quantitative Risk Analysis Adapted from PMBOK 4 th Edition InitiationPlanning ExecutionClose Monitor Control.
Chapter 5: Requirement Engineering Process Omar Meqdadi SE 2730 Lecture 5 Department of Computer Science and Software Engineering University of Wisconsin-Platteville.
©Ian Sommerville 2000, Mejia-Alvarez 2009 Slide 1 Software Processes l Coherent sets of activities for specifying, designing, implementing and testing.
Topic (1)Software Engineering (601321)1 Introduction Complex and large SW. SW crises Expensive HW. Custom SW. Batch execution.
Agile Release Planning Steven Jol. Overview (1) Release planning: release planning deals with selecting a set of requirements for a certain release (Karlsson,
New Tools in an Old Company PMI Honolulu Chapter Meeting June 20, 2007.
Requirements Engineering Requirements Elicitation Requirements Analysis Requirements Validation Requirements Management.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 7 Slide 1 Requirements Engineering Processes.
Extreme/Agile Programming Prabhaker Mateti. ACK These slides are collected from many authors along with a few of mine. Many thanks to all these authors.
Lecture 3 Software Engineering Models (Cont.)
Object-oriented Analysis and Design Stages in a Software Project Requirements Writing Analysis Design Implementation System Integration and Testing Maintenance.
CHECKPOINTS OF THE PROCESS Three sequences of project checkpoints are used to synchronize stakeholder expectations throughout the lifecycle: 1)Major milestones,
Rapid software development 1. Topics covered Agile methods Extreme programming Rapid application development Software prototyping 2.
Company LOGO Team assignment 03 Team 04 K15T02. Members… 1.Hoàng Thị Kim Dâng 2.Thái Thanh Nhã 3.Trần Thị Mộng Hà 4.Trần Tiễn Hưng 5.Chu Thị Thu Hương.
NCAR’s Societal Impacts Program: WIST-Related Research Efforts Julie Demuth NCAR Societal Impacts Program 3 rd National Surface Transportation Weather.
Review of Software Process Models Review Class 1 Software Process Models CEN 4021 Class 2 – 01/12.
An Introduction to Software Engineering
LSST Scheduler construction plan Francisco Delgado Sr. Software Engineer Telescope & Site.
Experiences from the Architectural Change Process Josef Nedstam Even-André Karlsson Martin Höst Dept of Telecom, Lund University, Sweden
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 7 Slide 1 Requirements Engineering Processes.
Requirements Engineering. Requirements engineering processes The processes used for RE vary widely depending on the application domain, the people involved.
Software Project Management (SEWPZG622) BITS-WIPRO Collaborative Programme: MS in Software Engineering SECOND SEMESTER /1/ "The content of this.
Overview of Building Information Modeling What does it mean for Civil Engineering?
Requirements Engineering Processes. Syllabus l Definition of Requirement engineering process (REP) l Phases of Requirements Engineering Process: Requirements.
CS223: Software Engineering Lecture 4: Software Development Models.
Chapter 2 – Software Processes Lecture 2 1Chapter 2 Software Processes.
CSE Senior Design II Staged Delivery Instructor: Manfred Huber Partially adapted from Mike O’Dell.
Requirements engineering The process of establishing the services that the customer requires from a system and the constraints under which it operates.
Advanced Project Management Project Planning Phase Ghazala Amin.
Design Visualization Visualize building early in the process to support and accelerate the decision making process. Schedule Visualization Visualize construction.
RUP RATIONAL UNIFIED PROCESS Behnam Akbari 06 Oct
Requirements Engineering Processes, York EngD Programme, 2009Slide 1 Requirements engineering processes Prof Ian Sommerville.
Advanced Requirement Engineering SYSM 6309 Mairon Toçi 02/11/2012.
 The processes used for RE vary widely depending on the application domain, the people involved and the organisation developing the requirements.  However,
REQUIREMENTS ENGINEERING PROCESSES Chapter 6. Activities in Requirements Engineering processes  Requirements elicitation;  Requirements analysis; 
سياسات التوزيع الفصل السادس عشر.
Chapter 2 – Software Processes
Fundamental Test Process
(from Chapter 14 of Royce’ book)
Group Truck Technology, Powetrain Engineering, Control Systems dept.
Requirements Engineering Introduction
BPM in E-Gov Vienna Prof. Dr. Friedrich Roithmayr & Dr. René Riedl Johannes Kepler University.
Construction Projects
Extreme Programming.
Process Wind Tunnel for Improving Business Processes
Presentation transcript:

Simulation of Market-Driven Requirements Engineering Processes Björn Regnell, Martin Höst, Johan Natt och Dag, Josef Nedstam, Lena Karlsson

What is Market-Driven Requirements Engineering? “Traditional RE” (Bespoke development):  A single, well-defined customer  A customised system  A contract: the customer decides Market-driven RE (Product development):  A large market with many potential customers  A generic system  No contract: the development organisation decides Stakeholding Risks Scheduling

Simulation model: Discrete event simulation queue-server Previous Release Current Release Next Release Incoming requirements Urgency 1 Urgency 3 Not Selected Completed Not R e l e a s e ElicitSelectConstruct ElicitSelectConstruct ElicitSelectConstruct

Parameters of model elicited through interviews Arrival intensity Service times Number of employees in each phase Distribution of priorities Estimation error General experience of process

Simulation results Case 1: based on interviews Case 2: more resources or increased productivity Case 3: fewer req’s or early prioritisation Overload

Simulation as Research Methodology Empirical Studies Model Construction Model Execution Experiments Model Validation Increased Understanding

Further work RE Process Efficiency Explore Cause-Effect and Trade-off Effort Spent on Requirements Engineering + Product Quality - Effort Spent on Construction +