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 +