1 / 11

Structured Use Case Descriptions for Effective ECE 621 Authoring

Understand the benefits of Structured Use Case Descriptions in ECE 621 Authoring Styles, aiding clarity, consistency, and error avoidance. Learn about headers, actions, flow structures, alternative and extension points.

jerryyoung
Download Presentation

Structured Use Case Descriptions for Effective ECE 621 Authoring

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. Using SUCD to Describe Use Cases ECE 621

  2. Authoring Styles • Many authoring styles exist • Tailored for specific domains • Real-Time systems • Safety critical systems • Most authoring styles use templates • Overwhelming majority only use unstructured natural language • Very little structure

  3. SUCD • Provides rigor • Helps clarify the flow of use cases • Helps avoid common mistakes • Can be used to automatically generate the corresponding use case diagrams, hence ensures consistency

  4. Headers an actions Actions The Actor • {BEGIN enter member information} • Librarian enters member’s name • Librarian enters member’s address • Librarian enters member’s phone number • {END enter member information} The Same A Header

  5. Basic Flow {BEGIN Use Case} … Headers and Actions …. {END Use Case} Reserved only for the Basic Flow

  6. Alternative Flow The Header in the Basic Flow AT {enter ticket order information} • PERFORM search tickets IF tickets not available … Headers and Actions … The action in that header from the Basic Flow The condition

  7. Subflows Subflow name SUBFLOW print receipt {BEGIN print transaction information} • SYSTEM prints Customer information • SYSTEM prints team hockey card information • SYSTEM print items information and total price {END print transaction information}

  8. Extension Points – At The Base Use Case Extension Points: PUBLIC EXTENSION POINT Grand Prize Giveaway Name of the extension point

  9. Extension Points – At The Extension Use Case Name of the extended UC PUBLIC EXTENSION POINT BEHAVIOR EXTENDING {Buy Team Merchandise : Grand Prize Giveaway} FLOW Basic Flow AT {a chance to win} IF winning ticket was entered {BEGIN grand prize giveaway} • SYSTEM notifies Customer the he/she won the grand prize • Customer enters phone number for a Customer service representative to call {END grand prize giveaway} CONTINUE {END Use Case} Name of the extension Point The flow inside the base UC Where to continue at base UC

  10. Abstraction, Implementation and Specialization • Keywords used in the Name section: • ABSTRACT • IMPLEMENTS • SPECIALIZES

  11. More Keywords (2) • INCLUDE – to perform an inclusion UC • PERFORM – to performed a Subflow • RESUME – what to perform next • AFTER – what needs to be performed first • AT/IF – what condition to evaluate and where • BEGIN/END – • PUBLIC EXTENSION POINT – at the base UC • PUBLIC EXTENSION POINT BEHAVIOR – at the extension UC • PRIVATE EXTENSION POINT – private to the UC • FLOW – which flow in the base UC • CONTINUE – where to go back in the base UC

More Related