1. Mohammad Amin Kuhail M.Sc. (York, UK) University of Palestine Faculty of Engineering and Urban planning Software Engineering department Requirements Engineering Sunday, 14 December 2008 Lecture 12 of Requirements Prioritization

2. Why Prioritization is needed Basic Trade-offs Cost-Value Approach Sorting Requirements by cost/value Estimating Relative Costs/Values using AHP What if stakeholders disagree? Visualizing differences in priority Resolving Disagreements Outline

3. Requirements Prioritization Due to time and budget constraints, it is often difficult to implement all the requirements that have been elicited for a system. It may also be the case that requirements are implemented in stages, and prioritization can help to determine which ones should be implemented first. Why?

4. Requirements Prioritization

7. Put all requirements in one pile. Take one requirement and put it as root node. Take another requirement and compare it to the root node. If the requirement is less important than the root node, compare it to the left child node. If the requirement is more important than the root node, compare it to the right child node. If the node does not have any appropriate child nodes, insert the new requirement as the new child node to the right or left, depending on if the requirement is more or less important. Binary Search Tree

8. Requirements Prioritization Binary Search Tree

11. Requirements Prioritization The Numeral Assignment Technique provides a scale for each requirement. Brackett proposed dividing the requirements into three groups: mandatory, desirable, and inessential [Brackett 90]. According to Joachim Karlsson's method, adapted from Saaty's approach, participants assign each requirement a number on a scale of 1 to 5 to indicate the importance of those requirements [Karlsson 95]. The numbers carry the following meaning:[Brackett 90][Karlsson 95] does not matter (the customer does not need it) not important (the customer would accept its absence) rather important (the customer would appreciate it) very important (the customer does not want to be without it) mandatory (the customer cannot do without it) The final ranking is the average of all participants' rankings for each requirement. Numeral Assignment Technique

12. Requirements Prioritization The planning game is a feature of extreme programming [Beck 01] and is used with customers to prioritize features, based on stories. This is basically a variation of the Numeral Assignment Technique, where the customer distributes the requirements into three groups, "those without which the system will not function", "those that are less essential but provide significant business value," and "those that would be nice to have." [Beck 01] Planning Game

15. ROI: Return Of Investment

16. Stakeholders Conflict Resolve