Scribd Logo
Upload

Welcome to Scribd!

  • Use Case in Table Format + Example: Use Case Goal

    Uploaded by

    thebanyak
    8 views1 page
    • Scenario is one instance of an use case / describes a use case in which an alternative course is worked through in detail. • Scenario consists of a goal and a sequence of actions that lead to it (actions should be simple and concrete, avoid vagueness). • Scenario is a useful way to identify what the users want the system to do for them.

    Original Title

    Use Case Example in Programming Flow with example and its Alternative Flow

    Copyright

    © Attribution Non-Commercial (BY-NC)

    Available Formats

    DOC, PDF, TXT or read online from Scribd

    Did you find this document useful?

    Is this content inappropriate?

    Report this Document
    • Scenario is one instance of an use case / describes a use case in which an alternative course is worked through in detail. • Scenario consists of a goal and a sequence of actions that lead to it (actions should be simple and concrete, avoid vagueness). • Scenario is a useful way to identify what the users want the system to do for them.

    Copyright:

    Attribution Non-Commercial (BY-NC)
    Download as DOC, PDF, TXT or read online from Scribd
    Flag for inappropriate content
    8 views1 page

    Use Case in Table Format + Example: Use Case Goal

    Uploaded by

    thebanyak
    • Scenario is one instance of an use case / describes a use case in which an alternative course is worked through in detail. • Scenario consists of a goal and a sequence of actions that lead to it (actions should be simple and concrete, avoid vagueness). • Scenario is a useful way to identify what the users want the system to do for them.

    Copyright:

    Attribution Non-Commercial (BY-NC)
    Download as DOC, PDF, TXT or read online from Scribd
    Flag for inappropriate content
    of 1

    Use case in table format + example : Use Case Goal <a longer statement of the goal in context if needed>

    Preconditions <what we expect is already the state of the world> Success End Condition <the state of the world upon successful completion> Failed End Condition <the state of the world if goal abandoned> Primary Actors; Secondary Actors Trigger <the action upon the system that starts use case> Description / Main Success Scenario <the steps of the scenario from trigger to goal delivery and any clean up after> Buy Goods Buyer issues request directly to the company, expects goods shipped and to be billed.

    Buyer has goods. Company has money for the goods. Company has not sent the goods. Buyer has not spent the money. Buyer Credit card company, bank, shipping service Purchase request comes in. Step 1 1.1 1.2 1.3 2 3 4 5 6 7 7.1 7.2 7.3 Step 3a 3a1 4a 4a1 7a 7a1 Action Buyer calls in with a purchase request. Buyer calls in via phone Buyer sends fax Buyer submits web order form, etc Company captures buyers name, address, requested goods. Company gives buyer information on goods, prices, delivery dates. Buyer signs for order. Company creates order and ships order to buyer. Company ships invoice to buyer. Buyer pays invoice. Buyer pays by cash Buyer pays by cheque etc Branching Action Company is out of one of the ordered items. Renegotiate order. Buyer pays directly with credit card. Use Case Take payment by credit card Buyer returns goods. Use Case Handle returned goods

    Alternative Flows <a: condition causing branching> <a1: action or name of sub use case>

    Scenario: Scenario is one instance of an use case / describes a use case in which an alternative course is worked through in detail. Scenario consists of a goal and a sequence of actions that lead to it (actions should be simple and concrete, avoid vagueness). Scenario is a useful way to identify what the users want the system to do for them.

    You might also like