System sequence diagram

download System sequence diagram

of 12

  • date post

    06-Jan-2016
  • Category

    Documents

  • view

    44
  • download

    0

Embed Size (px)

description

Asper School of Business University of Manitoba. Systems Analysis & Design. Instructor: Bob Travica. System sequence diagram. Updated: October 2013. Outline. Concept of SSD Global SSD Creating global SSD Detailed SSD (reading) First cut Full. Concept of System Sequence Diagram (SSD). - PowerPoint PPT Presentation

Transcript of System sequence diagram

  • Asper School of Business University of ManitobaSystems Analysis & DesignInstructor: Bob TravicaSystem sequence diagramUpdated: 2014

    3510 Systems Analysis & Design * Bob Travica

  • 3510 Systems Analysis & Design * Bob Travica* of 12OutlineConcept of SSDGlobal SSDCreating global SSDDetailed SSD (reading)First cut Full

    3510 Systems Analysis & Design * Bob Travica

  • 3510 Systems Analysis & Design * Bob Travica* of 12Concept of System Sequence Diagram (SSD)Part of system design. Communicates to OO programmers.SSD shows interaction between actors and system (global SSD), and among objects (detailed SSD)SSD specifies flow of data (messages) Messages are actions (resemble commands) invoked on destination object

    3510 Systems Analysis & Design * Bob Travica

  • 3510 Systems Analysis & Design * Bob Travica* of 12Global SSDContent of Item: item details

    3510 Systems Analysis & Design * Bob Travica

  • 3510 Systems Analysis & Design * Bob Travica* of 12Global SSD loopsFigure 6-15True/FalseConditionInputExpected outputLoopNote: extendedPrice = price * quantity

    3510 Systems Analysis & Design * Bob Travica

  • 3510 Systems Analysis & Design * Bob Travica* of 12Creating global SSD 1. Start with an activity diagram and/or use case description.2. Identify the input messages from actor to system. For figuring attributes (input parameters), use class diagram.3. Identify/apply special conditions (iteration) to input messages, if any.4. Identify output messages.

    3510 Systems Analysis & Design * Bob Travica

  • * of 12Creating global SSD (cont.)Figure 6-16. Activity diagram of Create New Order use case, Telephone Scenario at RMOFigure 6-17. Global SSD of the same

    Figure 5-31 (detail). Class diagram of RMO

  • 3510 Systems Analysis & Design * Bob Travica* of 12Detailed SSDUses the same elements as an SSD

    Has extra elements:The :System object is replaced by objects and messages within computer systemObjects are differentiated (e.g., control handler, domain, user interface)Object activation period indicated

    3510 Systems Analysis & Design * Bob Travica

  • 3510 Systems Analysis & Design * Bob Travica* of 12Detailed SSD for Look Up Item Availability - first cut (actor and domain classes)Domain objects (replace :System)Figure 8-14SSD for Look Up ItemAvailabilityuse case

    3510 Systems Analysis & Design * Bob Travica

  • 3510 Systems Analysis & Design * Bob Travica* of 12Reading detailed SSD (first cut)The system object is broken down to specific objects.

    Inputs & outputs among objects are specified. Class diagram essential (follow associations).

    3510 Systems Analysis & Design * Bob Travica

  • 3510 Systems Analysis & Design * Bob Travica* of 12Adding user interface and database to SSD Add user interface and database objects to domain objects. Example function: Create new student.

    3510 Systems Analysis & Design * Bob Travica

  • 3510 Systems Analysis & Design * Bob Travica* of 12Detailed SSD (final) - readingReading: Specific catalog and inventory objects are initialized by users input, and it will get data from the corresponding database objects.Figure 8-17: Final SSD for the use caseLook Up Item Availability(product description, price, quantity in inventory)User InterfaceDatabase (DA=Data Access Layer)

    3510 Systems Analysis & Design * Bob Travica

    *Note: After the loop, another input can be added finalizeOrder(), which will prompt system to calculate the total (sum of extendedPrice, shipping+handling, tax. The output would returned the total. Then, the last input completeOrder(paymentAmt) can be a confirmation of the total; payment methods can be added to the input.*