Tutorial 8: Establishing requirements

1. Tutorial 8: Establishing requirements IMD07101: Introduction to Human Computer Interaction Brian Davison 2011/12

2. Agenda • Establishing requirements • Functional and non-functional requirements • Use cases • Sketch design • (Storyboarding) • Critique 0.05 – 0.06

3. Use cases 1 • Who are the actors (roles)? • What functions do they require? Personal agenda Store appointment Alter appointment Delete appointment Owner Deliver reminder Synchronise System 0.06 – 0.07

4. Use cases 2 • Describe the detail Personal agenda • UC1: Store appointment • Actor: Owner • Choose day • Choose time • Enter detail • Enter duration • Save Store appointment Alter appointment Delete appointment Owner Deliver reminder Synchronise System 0.08 – 0.10

5. Process • Work in groups of about 5-6 • Groups will be paired • Group 1 will produce use cases and NFR list • Group 2 will critique • Group 2 will produce Home Page sketch and storyboard • Group 1 will critique • Note any changes to the requirements as you go through • At what stage did the changes occur? • Why were they needed? • Why were they not identified earlier? 0.10 – 0.11

6. Schedule • 15 min: Use cases • 4 min: Comments from group 2 • 20 min: Non-functional requirements • 5 min: Comments from group 2 --- SWAP specifications --- • 15 min: Sketch Home Page • 5 min: Comments from group 1 • 15 min: Home page V2 / Storyboard • 5 min: Final comments from group 1 0.11 – 0.12

7. Use cases (15 min) • Identify all possible actors (roles) • WHO needs to interact with the system? • For each actor, identify their requirements • WHAT functions does each actor need? • Some may be shared • Add to diagram 0.12 – 0.27

8. Comments (4 min per group) • Has the other group correctly identified all actors? • Have they identified all use cases? • Are there any use cases obviously missing from the brief? 0.27 – 0.35

9. Non-functional requirements (20 min) • P • What kind of people will use the system? • How can you reflect their needs in the design? • A • What kind of activities are involved – work/leisure, urgent/relaxed, etc? • What implications are there for the interface? • C • In what context will the system be used – work, home, public place, mobile, etc? • Implications? • T • What technologies are available? • Which technology choice would be appropriate? 0.35 – 0.55

10. Comments (5 min per group) • Has the other group correctly identified all NFRs? • Are their interface suggestions accurate? • Are there better ways of accommodating the NFRs? 0.55 – 1.05

11. Sketch the home page (15 min) • Users must be able to access all functions from the home page • The home page may use some conventions (why?) • The home page design should reflect the NFRs • You are delivering the other group’s system: • Use their specification • Try to get as close as possible to their requirements • Make notes of any changes you are obliged to make 1.05 – 1.20

12. Comments (5 min per group) • Does the other group’s design reflect your requirements? • Have they correctly interpreted your specification? • Have they made any obvious errors? 1.20 – 1.30

13. Home page V2 / storyboard (15 min) • Users must be able to access all functions from the home page • The home page may use some conventions (why?) • The home page design should reflect the NFRs • You are delivering the other group’s system: • Use their specification • Try to get as close as possible to their requirements • Make notes of any changes you are obliged to make 1.30 – 1.45

14. Comments (5 min per group) • How has the other group improved on version 1? • Have they used your feedback from version 1? 1.45 – 1.55