1 / 18

Introduction to the Sequence Diagrams with stereotypes

Introduction to the Sequence Diagrams with stereotypes. Department of Information Systems and Computation (DSIC) Valencia Polytechnic University. Requirements Analysis Process Sequence Diagram.

brett-odonnell
Download Presentation

Introduction to the Sequence Diagrams with stereotypes

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. Introduction to the Sequence Diagrams with stereotypes Department of Information Systems and Computation (DSIC) Valencia Polytechnic University

  2. Requirements Analysis ProcessSequence Diagram • A Use Case functionality is specified identifying interacting classes and messages that they interchange • Structure and Notation

  3. Requirements Analysis ProcessSequence Diagram • Blocks: they are used to specify conditions or iterations that affect to one or many messages • NOT ALL the messages are of the same nature… • An UML extension is introduced (stereotypes) to classify messages according to its nature:«signal», «service», «query», «connect»

  4. Sequence DiagramStereotypes extension • «Signal» stereotype

  5. Sequence DiagramStereotypes extension • «Service» stereotype

  6. Sequence DiagramStereotypes extension • «Query» stereotype

  7. Sequence DiagramStereotypes extension • «Connect» stereotype

  8. Sequence DiagramStereotypes extension • «Connect» stereotype example

  9. Sale items Cashier An example 1- Use Case is identified and its actor(s) specified 2- Functionality is specified identifying object classes and interactions

  10. Sale items Cashier RAP – Sequence Diagram (1/8)(Relevant actors are identified)

  11. Sale items Cashier RAP – Sequence Diagram (2/8)(Messages between actors and the system)

  12. RAP – Sequence Diagram (3/8)(Internal messages, Sale and Sale-line are identified)

  13. until end of lines RAP – Sequence Diagram (4/8)(To create a sale-line it’s necessary an item)

  14. RAP – Sequence Diagram (5/8)(the cashier finishes the data entry) until end of lines

  15. RAP – Sequence Diagram (6/8)(Subtotal has to be calculated and also the item stock has to be updated) until end of lines

  16. until end of lines RAP – Sequence Diagram (7/8)(Final information about the sale is shown)

  17. RAP – Sequence Diagram (8/8)(Messages are stereotyped) <<signal>> <<signal>> <<service/new>> until end of lines <<service/new>> <<connect/1,1>> <<query>> <<signal>> <<query>> <<service>> <<signal>>

  18. Summary • Sequence Diagrams (SD) are used to specify functionality in terms of object interactions (they are not algorithm specifications!) • Objects from classes communicate each other by sending messages • A SD is structured in three regions: • External:actors outside of the system – users • Interface: user interface (boundary class) to receive information from actors or to show information produced by the system • Internal: classes in which the system is structured • Depending on the nature of messages they are classified in: • Signal: messages to get information into the system or to show information from the system • Service: messages that change the state of the system (create, destroy, update) • Query: messages to query the state of an object or a set of objects • Connect: messages that relates objects to each other (when an object needs to be “connected” to other objects)

More Related