1 / 16

Lecture 4: Where to start

Lecture 4: Where to start. Requirements Scenarios DSDM. Scenario-based design 1. In 1994 a European project entitled UNOM (users, network operators and manufactures) aimed to make the most of broadband telecoms Broadband (ATM, 100Mbit per second)

max
Download Presentation

Lecture 4: Where to start

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. Lecture 4: Where to start Requirements Scenarios DSDM

  2. Scenario-based design 1 • In 1994 a European project entitled UNOM (users, network operators and manufactures) aimed to make the most of broadband telecoms • Broadband (ATM, 100Mbit per second) • Project made up from network providers and two banks (1 in Madrid, the other in Milan)

  3. The Madrid Bank • Banco del Commercio was like any UK bank • Central bank in Madrid, lots of small branches across the major cities in Spain and even smaller branches in small towns and villages • And the management want to save money

  4. Their bright idea • If they could close the smaller branches and centralise their business they could save money • Replace smaller branches with a state-of-the-art automatic teller • but … • how does one apply for a mortgage or a loan via an automatic teller?

  5. The multi-service terminal • We need to define the requirements on the MST • Where to begin? • Interviews with stakeholders • Scenario-based design • What is a scenario ...

  6. Scenarios • stories about using the envisaged system • realistic whos, whats, whens and hows (task and co-occurences) • can directly use input from ethnography • should illustrate a particular point or points • used to develop a sense of ‘user space’

  7. Step 1: lets be bank staff • We now will brainstorm (i.e. suggest without criticism)what the MST might do… • (15 minutes)

  8. Step 2: scenario-based design (a) • Let’s consider a person applying for a loan • The scenario begins … • Jose decides that he needs to buy a new car • The car cost 200 000 pesetas • He walks up to the MST and … • What does he do?

  9. Step 3: Scenario-based design (b) • It is a Sunday afternoon, Jose and Maria are getting married and have seen an apartment they would like to buy • They spot an MST and decide to see how much the bank will lend them (i.e. a mortgage) • What next … (15 minutes)

  10. Next ... • There is a need to work through multiple scenarios to explore the problem space (cf UML) • Consider the need to stop and resume a transaction • The question of identity • Special needs access • and so on …

  11. What next? • Analyse scenarios for requirements • Reflect back the statement of requirements to the stakeholders • Prioritise requirements • Storyboarding • For the next step write down at least 15 requirements on the MST

  12. DSDM - dynamic systems development method • DSDM - a structured means of prototyping developed by major companies in the UK • One of the techniques is MoSCoW as a means of prioritising requirements • M - must have (minimum usable set of requirements • S - should have • C - could have • W - would like (but not this time)

  13. Sketches & storyboards • Sketching • users interpret system images to form model of system • highlighting, relating and animating key aspects of the design model • Storyboards • series of sketches to produce a visual equivalent of a scenario • the ‘Wizard of Oz’ technique

  14. Now storyboard applying for a loan at the MST • Sketch screens with annotations • The screens should show main dialogues between applicant and bank • Make this clear enough to use next week

  15. Requirements elicitation User-designer communication Design rationale Envisionment Software design Implementation Documentation and training Evaluation Abstraction Team building Uses of scenarios in summary -Carroll, 1995

  16. In summary • Brainstorm • Interviewing stakeholders • Use of scenarios • The analysis of scenarios for requirements • Prioritisation of scenarios & the use of MoSCoW • Storyboarding

More Related