16.AuthoringUseCases

16.AuthoringUseCases - AuthoringUseCases(Filled andFocused)

Info iconThis preview shows pages 1–9. Sign up to view the full content.

View Full Document Right Arrow Icon
  1 Authoring Use Cases  (Filled  and Focused) from Use Case Modeling , by Bittner and  Spence, Chapters 4, 6, and 7
Background image of page 1

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
  2 Introduction We: Know that Use Cases represent / can capture  the functional requirements of an application. Know that there are ‘levels of maturity’ of Use  Cases. Know about Façade Use Cases and Know about the use of a template. Know different organizations will likely require  different formats, attributes…
Background image of page 2
  3 Use Case Number: Use Case Name: Actor (s): Maturity: (Façade/Focused/… Summary: Basic Course of Events: Actor Action System Response Alternative Paths: Exception Paths: Recall the format  we will use:
Background image of page 3

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
  4 Extension Points: Triggers: Assumptions: Preconditions: Post Conditions: Reference: Business Rules: Reference: Risks Author(s): Date:
Background image of page 4
  5 Façade Use Cases Also recall facts about Façade Use Cases: Identify the Use Cases Placeholders Help to establish a framework for further maturity  development Help to establish application boundary Contain a number of attributes, but no basic course  of events is included. Often features may map one to one to a use case if  feature is general (abstract) enough.
Background image of page 5

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
  6 Outline the Use Case Use Cases can be:  a short as half a page to  as long as a number of pages  Whatever is required to capture both the basic  and alternative flows in a form that satisfies  ALL of the stakeholders. If at all possible, abstract out some of the  details (glossary;  domain model;  subflows,  include and extend use-cases). KISS.
Background image of page 6
  7 Start off with an Outline of Use Case Start off with the Use Case name, a brief description  of the use case and identify actors (persons,  systems, …) Identify the basic flow of events as steps. Walk through these!   This is an art! Enumerate  the alternate flows as A1, A2, etc.   just an outline here.   Will undertake the real use case authoring shortly. Example:
Background image of page 7

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
  8 Sample Outline – Withdraw Money Basic Flow  (Outline format) Insert Card Validate Card Validate Bank Customer Select Withdraw Select Amount from List of Standard Amounts Confirm Transaction with Banking System Dispense Money Eject Card List of Alternate Flows A1.  Card cannot be identified A2.  Customer cannot be identified A3.  Withdraw not required A4.  Non-standard amount required A5.  No money in the account A6.  Attempt to withdraw more than daily amount A7.  No connection to the banking system A8.  Link goes down A9.  Card stolen – the card is on the hot-card list A10.  The ATM is out of money
Background image of page 8
Image of page 9
This is the end of the preview. Sign up to access the rest of the document.

This note was uploaded on 07/26/2011 for the course CEN 6016 taught by Professor Sanchez,a during the Spring '08 term at UNF.

Page1 / 36

16.AuthoringUseCases - AuthoringUseCases(Filled andFocused)

This preview shows document pages 1 - 9. Sign up to view the full document.

View Full Document Right Arrow Icon
Ask a homework question - tutors are online