Data Analysis

1. Ensure analysis is accurate and complete Part 2

2. Prioritising requirements

11. The table below provides an example of relative and absolute rating, where the higher the number the more important the requirement is. 5 1 The system must enable customers to check delivery and production status. n Requirements 15 - 2 10 16 The system must display products on screen. Relative (5-10) Absolute (1-16) Importance Rating Business Requirement (Functional Requirement)

16. An example of applying capability to business requirements 27.5 5.5 5 1 The system must enable customers to check delivery and production status n x n n n Requirements 15 - 2 80 8 10 16 The system must display products on screen Relative 5-10 Relative 5-10 Absolute 1-16 Final Rating Ease of Realisation Importance Rating Business Requirement (Functional Requirement)

19. Screen shot of EasyWinWin.

21. Frequent Software Development Win-Lose Patterns (That Usually Turn into Lose-Lose Situations) Winner Loser Winner Proposed solution Developer Customer and user Driver too hard a bargain Customer Developer and user Add lots of "bells and whistles" User Developer and customer Quickly build a cheap, sloppy product