1. www.ddss.arch.tue.nl 7M822 Software Requirements A Use Case Approach 14 September 2010

2. www.ddss.arch.tue.nl 7M822 Software Requirements The Rock Problem ?! [Ed Yourdon] 2

3. www.ddss.arch.tue.nl 7M822 Software systems nature Software systems by their nature are –intangible –abstract –complex –infinitely changeable 3

4. www.ddss.arch.tue.nl 7M822 Requirements engineering Get a complete description of the problem –feasibility study 4

5. www.ddss.arch.tue.nl 7M822 Software development Goal –to develop quality software that meets customers’ needs What is this software supposed to do? How, exactly, will we know when the software does exactly that and nothing else? 5

6. www.ddss.arch.tue.nl 7M822 Software requirement A software requirement is a capability needed by the user to solve a problem to achieve an objective, and is imposed on the system 6

7. www.ddss.arch.tue.nl 7M822 Problem domain The problem domain is the home of those people (real users, other stakeholders) whose needs must be addressed in order to build the perfect system. 7

8. www.ddss.arch.tue.nl 7M822 Needs Features Software requirements problem domain solution domain 8

9. www.ddss.arch.tue.nl 7M822 Stage Relative cost to repair a defect Derived from: Alan Davis, Software Requirements: objects,functions and states; Prentice-Hall, 1993 Requirements time Design Coding Unit test Acceptance test Maintenance.1-.2.5 1 2 5 20 9

10. www.ddss.arch.tue.nl 7M822 Functional requirements Find the solution for the user needs by proposing objectives for the system that involves –problem definition –identifying the users –defining the solution system boundary –identifying the constraints 10

11. www.ddss.arch.tue.nl 7M822 Defining solutions system boundary System InputsOutputs inputs / system / outputs relationship Of concern: 1.Our system 2.Things that interact with our system actor 11

12. www.ddss.arch.tue.nl 7M822 System boundary Our Solution Users Other Systems System Boundary I/O 12

13. www.ddss.arch.tue.nl 7M822 System perspective New Solution Users Catalog system System Boundary Library system 13

14. www.ddss.arch.tue.nl 7M822 Use case approach Lending services User administration Books database Library user Library staff library system 14

15. www.ddss.arch.tue.nl 7M822 NS Ticket machine – a use case approach Traveler Purchase Ticket Maintenance basic data NS Take ticket Destination 15

16. www.ddss.arch.tue.nl 7M822 Example Use Cases A simple word processor is required to create new and edit existing documents. Also the ability to print is required. Question? Find the system boundary, actors and use cases 16

17. www.ddss.arch.tue.nl 7M822 Study matter Ian Sommerville Software Engineering, 6 th edition – Ch.6 Addison Wesley Dean Leffingwell & Don Widrig Managing Software Requirements, 2 nd edition Addison Wesley 17