Scribd Logo
Upload

Welcome to Scribd!

  • Use Case

    Uploaded by

    Zoo Zoo
    3 views16 pages
    This document discusses use case modeling for a next generation point of sale (POS) system. It defines key use case modeling concepts like actors, scenarios, and use cases. It explains that actors are people or systems that interact with the system, primary actors use the system directly while supporting actors provide services. Scenarios describe specific sequences of actions between an actor and system. Use cases are collections of related scenarios. The document also covers use case types, common sections in use case documentation, best practices for defining proper use cases, and how to identify primary actors and their goals to derive use cases.

    Original Description:

    Original Title

    USE CASE

    Copyright

    © © All Rights Reserved

    Available Formats

    PPTX, PDF, TXT or read online from Scribd

    Did you find this document useful?

    Is this content inappropriate?

    Report this Document
    This document discusses use case modeling for a next generation point of sale (POS) system. It defines key use case modeling concepts like actors, scenarios, and use cases. It explains that actors are people or systems that interact with the system, primary actors use the system directly while supporting actors provide services. Scenarios describe specific sequences of actions between an actor and system. Use cases are collections of related scenarios. The document also covers use case types, common sections in use case documentation, best practices for defining proper use cases, and how to identify primary actors and their goals to derive use cases.

    Copyright:

    © All Rights Reserved
    Download as PPTX, PDF, TXT or read online from Scribd
    Flag for inappropriate content
    3 views16 pages

    Use Case

    Uploaded by

    Zoo Zoo
    This document discusses use case modeling for a next generation point of sale (POS) system. It defines key use case modeling concepts like actors, scenarios, and use cases. It explains that actors are people or systems that interact with the system, primary actors use the system directly while supporting actors provide services. Scenarios describe specific sequences of actions between an actor and system. Use cases are collections of related scenarios. The document also covers use case types, common sections in use case documentation, best practices for defining proper use cases, and how to identify primary actors and their goals to derive use cases.

    Copyright:

    © All Rights Reserved
    Download as PPTX, PDF, TXT or read online from Scribd
    Flag for inappropriate content
    of 16

    USE CASE

    - ARAVINDHRAJ NATARAJAN, AP/CSE, PSGITECH


    SUN UP MEETING
    • The NextGen POS System

    • Architectural Layers

    • Iterative Learning and Development

    • Inception

    • Definition

    • Sample Artifacts
    2
    AGENDA
    • Use Case Model
    • Actors
    • Scenarios
    • Use Case
    • Types and Formats
    • Steps
    • NextGen POS System Use Case Document

    3
    USE CASE MODEL

    4
    WHAT ARE ACTORS, SCENARIOS AND
    USE CASES?
    • Use cases are stories of how actors use the system to fulfill his goal
    • E.g. “ process sale”
    • actor: a person or a system with behavior
    • There are different kinds of actors: those who uses our system and
    those who is used by our system.
    • A “cashier” uses our system
    • A “tax calculator” is used by our system

    5
    WHAT ARE ACTORS, SCENARIOS AND
    USE CASES?
    • Primary actor
    • Has user goals fulfilled through using the services of the system
    • Supporting actor
    • Provides a service (for example information) to the system
    • Offstage actor
    • Has an interest in the behavior of a use case, but is not primary or
    supporting (e.g. tax agency)
    6
    WHAT ARE ACTORS, SCENARIOS AND
    USE CASES?
    • A scenario is a specific sequence of actions and interactions
    between an actor and the system.
    • A use case is a collection of related success and failure scenarios
    • Focus :
    • Describe actions that gives the actor observable value, not only a list of
    functions that the system offers.
    • Describe what, not how.
    7
    WHAT ARE ACTORS, SCENARIOS AND
    USE CASES?

    •
    Use-cases are text documents, not diagrams.

    • Use Case modeling is primarily an act of writing text, not drawing


    diagrams

    8
    USE-CASE TYPES AND FORMATS
    • Black-box use case
    • Most common and recommended
    • They do not describe the internal working of the system.
    • The system is described as having responsibilities.
    • Formats
    • Brief
    • Terse one-paragraph summary, usually the main success scenario
    • Casual
    • Informal, multiple paragraphs that cover various scenarios
    • Fully dressed
    • The most elaborate. All steps and variations are written in detail and there are supporting
    sections with preconditions etc.

    9
    USE CASE SECTIONS- FULLY DRESSED
    FORMAT
    • Scope
    • Level
    • Primary actor
    • Stakeholders and interests
    • Precondition and success guaranties
    • Main success scenario and steps
    • Extensions
    • Special requirements
    • Technology and data variations list
    • Frequency of occurrence
    • Open issues

    10
    EVALUATION – WHAT IS A PROPER USE CASE

    • Use cases for elementary business processes (EBP)


    a task performed by one person in one place at one time, in
    response to a business event, which add measurable business
    value and leaves the data in a consistent state. E.g. ‘approve
    credit’ or ‘price order’ or ‘process sale’

    11
    EVALUATION – WHAT IS A PROPER USE CASE

    • The Boss test


    • Your boss asks, “what have you been doing all day?”
    • What makes your boss happy?
    • The Size test
    • A use case is seldom a single action/step!

    12
    USE CASES AND GOALS

    • Recommended procedure:
    • Find the user goals
    • Define a use case for each

    • How?
    • Ask: what are your goals? (Instead of what do you do?)

    13
    FINDING PRIMARY ACTORS, GOALS AND
    USE CASES
    1. Choose the system boundary
    2. Identify the primary actors
    3. For each, identify their user goals
    4. Define use cases that satisfy user goals, name them according to
    their goal

    14
    SUN DOWN MEETING

    ?
    15
    THANK
    YOU

    16

    You might also like