Use Case Description Supplementary material to support Bennett

Use Case Description Supplementary material to support Bennett, Mc. Robb and Farmer: Object Oriented Systems Analysis and Design Using UML, (4 th Edition), Mc. Graw Hill, 2010. © 2010 Bennett, Mc. Robb and Farmer

In This Presentation You Will Learn: • What is a Use Case Description • The difference between essential and real use cases • How to describe Use Cases informally as a step-by-step sequence of actions • How to apply Cockburn’s template formal Use Case Descriptions 2 © 2010 Bennett, Mc. Robb and Farmer

What is a Use Case Description? • A Use Case Diagram gives an overall view: – Of a system’s functionality (use cases) – How functions relate to each other at run-time ( «extends» and «includes» relationships) – How user roles (actors) interact with functions • Use Case Diagrams do not show: – Sequence or iteration of inputs and outputs while a use case executes – Alternative courses of action dependent on conditions – Pre-conditions for a use case to commence execution – Other meta-data about the use case 3 © 2010 Bennett, Mc. Robb and Farmer

What is a Use Case Description? • A Use Case Description addresses these limitations of the diagram • There are several ways to document a Use Case Description, ranging from very informal to very formal • Most organizations will have their own style and standard, often based on Cockburn’s (2001) template 4 © 2010 Bennett, Mc. Robb and Farmer

Essential and Real Use Cases • Some authors distinguish between essential and real use cases • An essential use case is quite abstract, and makes no reference to design or technology aspects • A real use case is implementationoriented, referring to specific technologies (e. g. interface widgets, hardware devices, etc) • For this presentation, we will focus mainly on essential use case descriptions 5 © 2010 Bennett, Mc. Robb and Farmer

Informal Step by Step Descriptions • It is often useful to describe a use case simply as a sequence of I/O: – User inputs something – System outputs something – User inputs something else – System outputs something else • Very easy to confirm with users • Also gives developers lots of clues about data, processing and screen content 6 © 2010 Bennett, Mc. Robb and Farmer

Example #1: ‘Buy product’ Buy product online Customer (this example is adapted from Fowler,

Imagine the Scenario • If you buy something from a website, you probably: – Browse through several products – Choose one – Go to the checkout – Fill in some information – Get confirmation of the sale 8 © 2010 Bennett, Mc. Robb and Farmer

Main Scenario: ‘Buy product’ • Informal description: Buy product online 1. Customer browses catalogue 2. System displays product details 3. Customer selects item to buy, goes to check-out 4. System displays shopping cart page 5. Customer fills in delivery information 6. System shows full pricing, including shipping 7. Customer fills in credit card details 8. System authorizes card, confirms sale on screen and sends email to customer (Note that ‘Shopping cart’ and ‘email’ are real aspects of this use case, while the rest of the description is essential) 9 © 2010 Bennett, Mc. Robb and Farmer

Optional Steps • Description also covers any alternative courses, and the triggers that initiate their execution: Alternative course: Card fails to authorize • At step 8, system fails to authorize credit purchase. • Return to step 7, allow customer to re-enter credit card information, retry authorization. 10 © 2010 Bennett, Mc. Robb and Farmer

What the Description tells us: • Even an informal description gives a lot of information that is useful to the developer: – Sequence and any iteration of steps – what order things should happen – I/O – fields, text boxes, buttons, etc needed on the screen – Data – what must be stored or retrieved – Process – calculations, other steps that will need coding – Alternatives – branch points in the sequence 11 © 2010 Bennett, Mc. Robb and Farmer

Example #2: Training Administration System Book course place Admin clerk (this example is adapted

Main scenario: ‘Book course place’ Book course place 1. Admin clerk retrieves scheduled course details 2. System displays number of places free 3. Admin clerk chooses ‘add delegate to a course’ 4. System requests delegate details 5. Admin clerk enters delegate details 6. System stores details and confirms 13 © 2010 Bennett, Mc. Robb and Farmer

Alternate course: no free places 1. Admin clerk retrieves scheduled course details 2 a. System displays ‘no places free’ 2 a 1. Admin clerk selects ‘search for dates with free places’ 2 a 2. Systems displays dates with free places 2 a 3. Admin clerk selects date (back to main course, step 4) 14 © 2010 Bennett, Mc. Robb and Farmer

Alternate course: details missing 4. System requests delegate details 5 a. Admin clerk enters details that are known 5 a 1. Systems displays ‘reservation is conditional on full details – OK? ’ 5 a 2. Admin clerk clicks OK (back to main course, step 6) 15 © 2010 Bennett, Mc. Robb and Farmer

Formal Descriptions: Cockburn’s Template • The usual basis formal use case descriptions, this is divided into five main sections: – Characteristic Information: a summary of the purpose and context of the use case – Description: Main Success Scenario, Extensions and ‘Technology and Data Variations List’ – (Optional) Related Information: non-functional aspects, links to other use cases, etc. – (Optional) Open Issues: unresolved issues still to be addressed – Schedule (for development) 16 © 2010 Bennett, Mc. Robb and Farmer

Characteristic Information in detail • Goal in Context: what is this use case for? • Scope: the system (or systems) within which this use case applies • Level: is this use case primary - called directly by the actor? • Preconditions: what should be true for the use case to execute? • Success End Condition: what should have changed after it has executed? • Minimal Guarantee: what should minimally occur even if the use case fails to achieve its main goal • Primary Actor: self explanatory • Trigger: what event causes execution to begin? 17 © 2010 Bennett, Mc. Robb and Farmer

Description in detail • Main Success Scenario: the steps of the scenario from trigger to success, including any final closing down (e. g. interfaces or database connections) • Extensions: alternate courses are described here, also any calls to other «includes» or «extends» use cases • Technology and Data Variations List: describes alternative ways that the use case might be implemented, e. g. to allow for different UI devices (say, touch screen vs keyboard and mouse interface) 18 © 2010 Bennett, Mc. Robb and Farmer

Related Information (optional) • Priority: how important is this use case to the project? • Performance Target: how quickly must the system respond to input or complete execution? • Frequency: how often will it need to execute? • Subordinate Use Cases: other use cases on which this one depends for its success • Channel to primary actor: how will the actor communicate with the use case? • Secondary Actors: other actors who can initiate and execute the use case • Channel to Secondary Actors: as above 19 © 2010 Bennett, Mc. Robb and Farmer

Open Issues and Schedule • Any unresolved questions should be described in enough detail for another developer to work on them later • If the development schedule for this use case has been decided, it should be documented 20 © 2010 Bennett, Mc. Robb and Farmer

Summary In this presentation you have learned : • What a Use Case Description is • What is the difference between essential and real use cases • How to describe Use Cases informally as a step-by-step sequence of actions • How to apply Cockburn’s template formal Use Case Descriptions 21 © 2010 Bennett, Mc. Robb and Farmer