Scribd Logo
Upload

Welcome to Scribd!

  • 51 views

    Use-Case Model: Drawing System Sequence Diagrams

    Uploaded by

    Nithin
    This document discusses use case models and system sequence diagrams (SSDs) for describing system behavior without explaining internal implementation. It provides guidelines for defining system operations and contracts to describe the public interface of a system as a black box. Key points include: - Use cases describe external actor interactions with a system, which generate events. SSDs show the order of events for a use case scenario. - System operations are determined by identifying required system events. Contracts describe pre- and post-conditions for each operation. - An example contract is provided for the "addLineItem" operation, specifying instance creation, attribute modification, and associations formed as post-conditions.

    Copyright:

    © All Rights Reserved
    Download as PPT, PDF, TXT or read online from Scribd

    Use-Case Model: Drawing System Sequence Diagrams

    Uploaded by

    Nithin
    51 views15 pages
    This document discusses use case models and system sequence diagrams (SSDs) for describing system behavior without explaining internal implementation. It provides guidelines for defining system operations and contracts to describe the public interface of a system as a black box. Key points include: - Use cases describe external actor interactions with a system, which generate events. SSDs show the order of events for a use case scenario. - System operations are determined by identifying required system events. Contracts describe pre- and post-conditions for each operation. - An example contract is provided for the "addLineItem" operation, specifying instance creation, attribute modification, and associations formed as post-conditions.

    Original Description:

    OOAD

    Original Title

    OOAD_Drawing Using UML

    Copyright

    © © All Rights Reserved

    Available Formats

    PPT, PDF, TXT or read online from Scribd

    Did you find this document useful?

    Is this content inappropriate?

    This document discusses use case models and system sequence diagrams (SSDs) for describing system behavior without explaining internal implementation. It provides guidelines for defining system operations and contracts to describe the public interface of a system as a black box. Key points include: - Use cases describe external actor interactions with a system, which generate events. SSDs show the order of events for a use case scenario. - System operations are determined by identifying required system events. Contracts describe pre- and post-conditions for each operation. - An example contract is provided for the "addLineItem" operation, specifying instance creation, attribute modification, and associations formed as post-conditions.

    Copyright:

    © All Rights Reserved
    Download as PPT, PDF, TXT or read online from Scribd
    Download as ppt, pdf, or txt
    51 views15 pages

    Use-Case Model: Drawing System Sequence Diagrams

    Uploaded by

    Nithin
    This document discusses use case models and system sequence diagrams (SSDs) for describing system behavior without explaining internal implementation. It provides guidelines for defining system operations and contracts to describe the public interface of a system as a black box. Key points include: - Use cases describe external actor interactions with a system, which generate events. SSDs show the order of events for a use case scenario. - System operations are determined by identifying required system events. Contracts describe pre- and post-conditions for each operation. - An example contract is provided for the "addLineItem" operation, specifying instance creation, attribute modification, and associations formed as post-conditions.

    Copyright:

    © All Rights Reserved
    Download as PPT, PDF, TXT or read online from Scribd
    Download as ppt, pdf, or txt
    You are on page 1of 15

    Use-Case Model: Drawing System

    Sequence Diagrams\
    System Behavior and
    UML Sequence Diagrams
    • It is useful to investigate and define the
    behavior of the software as a “black box”.
    • System behavior is a description of what the
    system does (without an explanation of how it
    does it).
    • Use cases describe how external actors
    interact with the software system. During this
    interaction, an actor generates events.
    • A request event initiates an operation upon
    the system.
    System Behavior and
    System Sequence Diagrams (SSDs)
    • A sequence diagram is a picture that
    shows, for a particular scenario of a use
    case, the events that external actors
    generate, their order, and possible inter-
    system events.
    • All systems are treated as a black box; the
    diagram places emphasis on events that
    cross the system boundary from actors to
    systems.
    SSDs for Process Sale Scenario
    SSD and Use Cases
    Naming System Events and
    Operations
    • The set of all required system operations
    is determined by identifying the system
    events.
    – makeNewSale()
    – addLineItem(itemID, quantity)
    – endSale()
    – makePayment(amount)
    Use-Case Model: Adding Detail
    with Operation Contracts
    Contracts
    • Contracts are documents that describe
    system behavior.
    • Contracts may be defined for system
    operations.
    – Operations that the system (as a black box) offers
    in its public interface to handle incoming system
    events.
    • The entire set of system operations across all
    use cases, defines the public system
    interface.
    System Operations and the System
    Interface
    • In the UML the system as a whole can be
    represented as a class.
    • Contracts are written for each system
    operation to describe its behavior.
    Example Contract: addLineItem

    Operation: addLineItem (itemID: integer, quantity: integer)


    Cross References: Use Cases: Process Sale.
    Pre-conditions: There is a sale underway.
    Post-conditions:
    – A SalesLineItem instance sli was created. (instance creation)
    – sli was associated with the Sale. (association formed)
    – sli.quantity was set to quantity. (attribute modification)
    – sli was associated with a ProductSpecification, based on itemID
    match (association formed)
    Pre- and Postconditions
    • Preconditions are assumptions about the state of
    the system before execution of the operation.
    • A postcondition is an assumption that refers to the
    state of the system after completion of the
    operation.
    – The postconditions are not actions to be performed during
    the operation.
    – Describe changes in the state of the objects in the Domain
    Model (instances created, associations are being
    formed or broken, and attributes are changed)
    addLineItem postconditions
    • Instance Creation and Deletion
    After the itemID and quantity of an item
    have been entered by the cashier, what
    new objects should have been created?
    – A SalesLineItem instance sli was created.
    addLineItem postconditions
    • Attribute Modification
    After the itemID and quantity of an item
    have been entered by the cashier, what
    attributes of new or existing objects should
    have been modified?
    – sli.quantity was set to quantity (attribute
    modification).
    addLineItem postconditions
    • Associations Formed and Broken
    After the itemID and quantity of an item have
    been entered by the cashier, what
    associations between new or existing objects
    should have been formed or broken?
    – sli was associated with the current Sale
    (association formed).
    – sli was associated with a ProductSpecification,
    based on itemID match (association formed).
    Guidelines for Contracts

    You might also like