1 / 9

Is There a Silver Bullet for Adding Value to Requirements Selection?

Is There a Silver Bullet for Adding Value to Requirements Selection?. Ayb ü ke Aurum School of Information Systems, Technology and Management University of New South Wales. Value Based Requirements Engineering.

nguyet
Download Presentation

Is There a Silver Bullet for Adding Value to Requirements Selection?

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Is There a Silver Bullet for Adding Value to Requirements Selection? Aybüke Aurum School of Information Systems, Technology and Management University of New South Wales

  2. Value Based Requirements Engineering • Value-based Requirements Engineering (VBRE) aims to maximise the value of software releases for all stakeholders through the selection and prioritisation of requirements. • The creation of product value through requirements selection and prioritisation is a new area of study, however little is known about industry perceptions of creating product value through Requirements Engineering (RE) and release planning. • This talk is concerned with the decision making process in the selection of requirements for software products. A.Aurum, ISERN'05

  3. Aligning RE Decisions Software applications need to be well aligned with business strategies of organizations Business decision  Product Decisions Product decisions  Project Decisions Ideally, this is where we would like to be in software development A.Aurum, ISERN'05

  4. RE Decisions Framework A.Aurum, ISERN'05

  5. Impact of the Requirements Selection Process • Business • Making good decisions leads to making good business? • People • Satisfaction with the decision, the outcome of the decision and the decision making process. • Project • Cost effectiveness -- within budget and on time • Product • An important decision in software product development has two distinct components: • Technical judgments • Value judgments A.Aurum, ISERN'05

  6. Research Questions • How is value-based requirements engineering perceived by the software development industry? • How does the software industry conduct release planning in order to create product value? • What values are applied to the decision making process to select and prioritise requirements for a software project or release? • How does this differ to industry perceptions of the optimal application of the criteria? • To what degree to the do the perspectives of the major stakeholders influence the requirements selection and prioritisation process? • How does this differ to industry perceptions of the optimal application of the criteria? A.Aurum, ISERN'05

  7. Shortages in the Decision Making Process • Adding value to a decision is not well defined! Many decisions are ad hoc • The decision-making process is not well identified – in many cases it is unstructured and open-ended. There are no specific decision making criteria. • Lack of communication between business, product and project level stakeholders • Uninformed stakeholders • Decision Hijackers • Lack of understanding of the business strategy • Decision leaders and decision executors are not necessarily the same people • Time pressure • Geographically dispersed stakeholders A.Aurum, ISERN'05

  8. References • Biffl S, Aurum A, Boehm B, Erdogan H, Grunbacher P (Eds) (2005). Value-Based Software Engineering. Springer, Heidelberg, Germany ISBN 2-540-25993-7 • Aurum A, Wohlin C (Eds) (2005). Engineering and Managing Software Requirements. Springer, Heidelberg, ISBN 3-540-25043-3 • Wohlin C, Aurum A (2005). Bundling Software Requirements to Create Product Value. In Value-based Software Engineering by Biffl S, Aurum A, Boehm B, Erdogmus H, Grünbacher P (Eds) Springer, Heidelberg, Germany • Wohlin C, Aurum A (2005). What is Important when Deciding to Include a Software Requirement in a Project or a Release? 4th International Symposium on Empirical Software Engineering, Noosa Heads, Australia, 17-18 Nov 2005 • Aurum A, Wohlin C (2005). Aligning Requirements with Business Objectives: A Framework for Requirements Engineering Decisions. Workshop on Requirements Engineering Decision Support, Paris, France 29 Aug-2nd Sept, 2005 • Barney, S, Aurum A, Wohlin C (2005). Quest for a Silver Bullet: Creating Software Product Value through RequirementsSelection.Submitted to Australian Software Engineering Conference, ASWEC’06, Sydney, Australia, 18-21 April, 2006 A.Aurum, ISERN'05

  9. Discussion • Is there a Silver Bullet for adding value to requirements selection? • What are the main challenges in empirical research when investigating the value-based approach? • How do we include the 3 perspectives -- business, project, product -- in our empirical research? • How do we combine studies across the different levels? • What do value-based requirements help increase cost effectiveness in the subsequent processes? A.Aurum, ISERN'05

More Related