Use-Case 2.0 Mini-Seminar 19 Maart Copyright Ivar Jacobson International SA. All rights reserved

Transcription

1 Use-Case 2.0 Mini-Seminar 19 Maart 2013

2 Agenda Introductie Use-Case Slices Pauze Workshop Use-Case Slicing Evaluatie & Discussie Lunch 2

3 DiVetro wie wat waar het realiseren van verandertrajecten waarin informatieoplossingen een belangrijke rol spelen Analyse informatieanalyse, requirements, specificaties, pve s, functionele ontwerpen, solution design, architectuur Sourcing sourcingsstrategie, sourcingskalender, selectie, transitie, aanbestedingen, regie, vraagsturing, pdc s, business cases, samenwerkmodellen DiVetro 2013 Management 3 Accountmanagement, programmamanagement, projectmanagement, informatiemanagement interim-management, lean six sigma Copyright 2013 Divetro All rights reserved

5 Ivar Jacobson International: Wie, Wat, Waar The Smarter Way Vanuit het geloof dat er altijd slimmere manieren zijn, kennis verzamelen, bundelen, verspreiden en overdragen Workshops Training Certificering Project Rescue / Recovery Enterprise Agile Transformatie 5

6 6

7 7

8 Enkele klanten Financial & Insurance Telecom Operators Government, Services & Other Products 8

9 Introductie Use-Case Slices Use-Case 2.0 Mini-Seminar 19 Maart 2013 Eric Lopes Cardozo Dennis Geluk

10 Agenda Terugblik Use-Case 2.0 Use-Case Slices Tips 10

11 Wat is Use-Case 2.0 Set algemene principes Schaalbare techniek Inwinnen, communceren, vastleggen en onderhouden van requirements Besturing software-ontwikkeling Geschikt voor vele soorten systemen en aanpakken Practice / Procesbouwsteen Controle-elementen, Werkproducten, Taken, Competenties E-book Opleidingen & Certificering 11

12 Waarom Use-Case 2.0? 1. Corrigeren van misvattingen 2. Terug naar de essentie 3. Geschikt maken voor Agile: Scrum, Kanban Use Cases zijn Alleen voor requirements Functies Complex Alleen voor nieuwbouw Use Cases zijn Voor requirements en het besturen van de realisatie Verhalen Eenvoudig Voor alle soorten ontwikkeling 12

14 Van Use Case tot Werkende Software 14

15 Van Use Case tot Use-Case Slices Use Case Beschrijving Browse and Shop Brief Description This use case describes how the actor Customer uses the system to view and purchase products on sale. Products can be found by various methods, including browsing by product category or keyword searches. Basic Flow 1) Browse Products 2) Select Products 3) Provide Payment Details 4) Provide Delivery Details 5) Confirm Purchase Use Case Alternative Flows A1 - Keyword Search for Products A2 - No Products Selected A4 - Invalid Payment Details A5 - Invalid Delivery Details A6 - Obtain Delivery and Payment Details A7 - Product Out of Stock 15

16 Van Use Case tot Use-Case Slices Use Case Beschrijving Browse and Shop Brief Description This use case describes how the actor Customer uses the system to view and purchase products on sale. Products can be found by various methods, including browsing by product category or keyword searches. Basic Flow 1) Browse Products 2) Select Products 3) Provide Payment Details 4) Provide Delivery Details 5) Confirm Purchase Use Case Alternative Flows A1 - Keyword Search for Products A2 - No Products Selected A4 - Invalid Payment Details A5 - Invalid Delivery Details A6 - Obtain Delivery and Payment Details A7 - Product Out of Stock 18

17 Van Use Case tot Use-Case Slices Use Case Beschrijving Browse and Shop Brief Description This use case describes how the actor Customer uses the system to view and purchase products on sale. Products can be found by various methods, including browsing by product category or keyword searches. Use Case Basic Flow 1) Browse Products 2) Select Products 3) Provide Payment Details 4) Provide Delivery Details 5) Confirm Purchase Alternative Flows A1 - Keyword Search for Products A2 - No Products Selected A4 - Invalid Payment Details A5 - Invalid Delivery Details A6 - Obtain Delivery and Payment Details A7 - Product Out of Stock 2.1 Select and Buy 1 Product Flows: BF Test: 1 product, default payment, valid details 2.2 Select 100 Products & Buy Them Flows: BF Test: 100 products, default payment, valid details Use Case Slices 19

18 De rol van de Use-Case Slice Schatten Scoping Prioriteren Plannen Tracking 21

19 Use-Case Slices en Werkproducten Doel Taak Aanpak Werkproduct Detailniveau 22

20 Doe wat het team nodig heeft! 23

21 Definition of Done: Sprint goals 24

22 User Stories of Use-Case Slices? User Stories / Use-Case Slices 25

23 User Stories of Use-Case Slices? User Stories / Use-Case Slices Story board 26

24 User Stories of Use-Case Slices? User Stories / Use-Case Slices Use Case Model 27

25 Daarom nog steeds use cases! Use Cases bieden: Een eenvoudig overzicht op systeem-functionaliteit Een kapstok voor een initiële planning Een context voor ieder requirement Een mechanisme voor het identificeren van alle gebruiksscenario s 2. Browse and Shop ACE Loyalty System Stock Control System Shopper Browse and Shop Payment System Order Management System 2.1 Brief Description This use case describes how the actor Customer uses the system to view and purchase products on sale. Products can be found by various methods, including browsing by product category or keyword searches. 2.2 Basic Flow 1) Browse Products 2) Select Products 3) Provide Payment Details 4) Provide Delivery Details 5) Confirm Purchase 2.3 Alternative Flows A1 - Keyword Search for Products A2 - No Products Selected A4 - Invalid Payment Details A5 - Invalid Delivery Details A6 - Obtain Delivery and Payment Details A7 - Product Out of Stock A8 - No Purchase Confirmation A9 - Bank System Unavailable A10 - Loyalty System Unavailable A11 - Stock Control System Unavailable A12 - Order Control System Unavailable A13 - Product Explicitly Identified A14 - Quit shopping 28

27 Tip - Vormgeven Use-Case Slice Naamgeving Vervat het doel of eindresultaat in de naam van de use-case slice Geheugensteun / Denkrichting: Ik wil <activiteit> Als een <actor> kan ik <activiteit> zodat <toegevoegde waarde> Testcondities Maak duidelijk met welke logische test-inputs een story moet worden uitgevoerd Geheugensteun / Denkrichting: Doe het met <test input> 30

28 Manieren om stories te splitsen 1. Workflow Stappen Workflow incrementeel implementeren 2. Business Rule Variatie Verschillende manieren om hetzelfde te doen 3. Het moeilijkste eerst Eerst basis infrastructuur, daarna functionaliteit toevoegen 4. Eenvoudig/Complex Start eenvoudig, daarna variaties toevoegen 5. Operaties Splitsen op basis van CRUD 5. Variatie in Data Start met eenvoudigste story, daarna data variatie en alternatieve databronnen 6. Invoer/Uitvoer-methoden Start met eenvoudige UI, daarna aanvullen 7. Uitstellen Kwaliteitseisen Maak stories voor iedere ility 8. Spike afsplitsen Aparte stories voor technische risico s Adapted from Scalable Agile Framework 31

29 Stories splitsen en Use-Case Slices Combinaties van flows Basic Flow Basic Flow, Alternative Flows 2. Browse and Shop Browse and Shop Shopper 2.1 Brief Description This use case describes how the actor Customer uses the system to view and purchase products on sale. Products can be found by various methods, including browsing by product category or keyword searches. 2.2 Basic Flow 1) Browse Products 2) Select Products 3) Provide Payment Details 4) Provide Delivery Details ACE Loyalty System Stock Control System Payment System Order Management System 5) Confirm Purchase 2.3 Alternative Flows Combinatie flows en Special Requirements ilities die tot een specifieke use case behoren A1 - Keyword Search for Products A2 - No Products Selected A4 - Invalid Payment Details A5 - Invalid Delivery Details A6 - Obtain Delivery and Payment Details A7 - Product Out of Stock A8 - No Purchase Confirmation A9 - Bank System Unavailable A10 - Loyalty System Unavailable A11 - Stock Control System Unavailable A12 - Order Control System Unavailable A13 - Product Explicitly Identified A14 - Quit shopping Uitstellen Test Cases Wijs specifieke test cases toe aan specifieke sprints 32

30 33

31 Bronnen en Hulpmiddelen Use-Case 2.0 ebooks English Nederlands Use-Case 2.0 Practice Content EssWork Practice Workbench authoring Use-Case 2.0 Opleidingen Basiscursus Conversiecursus 34

32 Heb je vragen, neem dan contact op met Eric Lopes Cardozo of Dennis Geluk Download white papers en andere kennisdragers via 35

33 Agenda Introductie Use-Case Slices Pauze Workshop Use-Case Slicing Evaluatie & Discussie Lunch 36

34 Workshop Use-Case Slicing Use-Case 2.0 Mini-Seminar 19 Maart 2013 Eric Lopes Cardozo Dennis Geluk

35 Storytelling ACE Loyalty System Stock Control System Payment System Order Management System Shopper Locate Store Browse and Shop ACE Loyalty System ACE Stock Control System Use-Case Beschrijvingen geven mogelijk manieren om een use case uit te voeren. Track Orders 1. Locate Store Locate Store Shopper 1.1 Brief Description This use case describes how the actor Customer uses the system to locate and obtain directions to the nearest ACE DIY high street store using either a postcode or a place name. 1.2 Basic Flow 1) Provide User Postcode 2) Submit Store Location Request 3) Display list of nearest three stores 4) Select store 5) Display map and directions 1.3 Alternative Flows A1 Invalid Postcode A2 Search Using Place Name A3 Browse for Store A4 Abandon Store Location A5 Print Map and Directions A6 - Locally Store Map and Directions A7 Send Map and Directions to a Friend 2. Browse and Shop Shopper 2.1 Brief Description This use case describes how the actor Customer uses the system to view and purchase products on sale. Products can be found by various methods, including browsing by product category or keyword searches. 2.2 Basic Flow 1) Browse Products 2) Select Products 3) Provide Payment Details 4) Provide Delivery Details 5) Confirm Purchase 2.3 Alternative Flows A1 - Keyword Search for Products A2 - No Products Selected A4 - Invalid Payment Details A5 - Invalid Delivery Details A6 - Obtain Delivery and Payment Details A7 - Product Out of Stock A8 - No Purchase Confirmation A9 - Bank System Unavailable A10 - Loyalty System Unavailable A11 - Stock Control System Unavailable A12 - Order Control System Unavailable A13 - Product Explicitly Identified A14 - Quit shopping Browse and Shop 3. Track Orders Track Orders Shopper 3.1 Brief Description This use case describes how the actor Customer uses the system to track the progress of previously made product orders. 3.2 Basic Flow 1) Provide Order Details 2) Submit Tracking Request 3) Display Tracking Progress 3.3 Alternative Flows A1 Invalid Order Details A2 Order Control System Unavailable A3 Print Tracking Progress A4 - Locally Store Tracking Progress ACE Order Control System Bank System Order Management System Minimale inhoud: Beknopte omschrijving; doel en inhoud. De basic flow d.m.v. bullet points. Geïdentificeerde alternative flows. Dit niveau noemen we Bulleted Outline. 38

36 Opdracht: Identificeer Product Backlog Items Identificeer voor de gegeven use cases de Use-Case Slices. Aandachtspunten 1. Verdeel in slices (paden, flows). Eet de olifant in plakjes 2. Iedere slice heeft tenminste één flow. 3. Geef iedere slice een volgnummer. <uc nr.>.<slices nr.> 4. De basic flow moet worden geïmplementeerd met slice nummer één. <uc x>.1 5. Iedere slice heeft minstens één testconditie waarmee de succesvolle implementatie kan worden geverifieerd 6. Neem indien van toepassing ook niet-functionele eisen / kwaliteitseisen mee. 39

37 Voorbeeld 2. Browse and Shop ACE Loyalty System Product Backlog Item 2.3 Try to buy out of stock product Flows : BF, A7 Stock Control System Test : 1 out-of-stock product, Shopper 2.1 Brief Description This use case describes how the actor Customer uses the system to view and purchase products on sale. Products can be found by various methods, including browsing by product category or keyword searches. 2.2 Basic Flow 1) Browse Products 2) Select Products 3) Provide Payment Details 4) Provide Delivery Details 5) Confirm Purchase 2.3 Alternative Flows A1 - Keyword Search for Products A2 - No Products Selected A4 - Invalid Payment Details A5 - Invalid Delivery Details A6 - Obtain Delivery and Payment Details A7 - Product Out of Stock A8 - No Purchase Confirmation A9 - Bank System Unavailable A10 - Loyalty System Unavailable A11 - Stock Control System Unavailable A12 - Order Control System Unavailable A13 - Product Explicitly Identified A14 - Quit shopping Browse and Shop Payment System Order Management System Points: Product Backlog Item 2.2 Select and Buy 100 Products Flows : BF Test : 100 products, Default payment card, Valid details and amount. Points: Product Backlog Item 2.1 Select and Buy 1 product Flows : BF Test : One product, Default payment card, Valid details and amount. Points: 40

38 GO! Werk in groepen (max 6 personen) Houdt rekening met presenteren van oplossing 41

39 Evaluatie & Discussie 42

40 Heb je vragen, neem dan contact op met Eric Lopes Cardozo of Dennis Geluk Download white papers en andere kennisdragers via 43