Logo blue background.png

Bruce Powel Douglass, Ph.D.

  • Content

    • Resources
    • Embedded World
    • Papers
    • Presentations
    • Models
    • Harmony aMBSE Overview
    • Harmony aMBSE Functional Analysis
    • Harmony Embedded Software Overview
    • Harmony ESW Nanocycle
    • Safety Analysis and Design
    • Books
    • On the Web
    • Links
  • Services

  • Public Interest

  • Blog

  • What's New

  • Forum

  • About

  • Comments

  • Site Map

  • Geekosphere

  • Members

    • Members Only
  • More

    Use tab to navigate through the menu items.
    To see this working, head to your live site.
    • Categories
    • All Posts
    • My Posts
    cramos
    Jun 29, 2018
      ·  Edited: Jun 29, 2018

    Specific Parameters in a sequence Diagram

    in UML / SysML

    When modeling a use case using a sequence diagram, do you use specific values for the values of parameters, or do you depict the parameters themselves? For example, suppose you have a message SetPosition. The message takes two parameters, PosX and PosY. When drawing a sequence diagram where 'A' calls 'B', which is preferred?


    SetPosition(144, 25)


    or


    SetPosition(PosX, PosY)


    Because it's a use case scenario, I thought using specific values like the first option would be preferred because you are illustraing a particular scenario. On the other hand, the second option is more generic and would apply to many scenarios. However, if you have a scenario, where the flow of control changes based on a particular parameters' value, the second option is not as obvious.


    On checking the IBM Rational Harmony for SE Deskkbook 4.1, on page 94 for example, they use the second option. In the ALT frame, there is a check on the value of CardStatus for example.

    1 comment
    0
    Bruce Douglass
    Jul 01, 2018

    You can do either, but I usually use the more general parameters, UNLESS interactions differ based on specific values being passed. For example if SetPosition(0,0) caused the system to reorient and reboot while SetPosition(1,1) just caused something to move, then I would show specific values. If every time, the interaction was the same, then I'd use the more general form SetPosition(X,Y).


    0
    1 comments
    Site Map

    (c) Bruce Powel Douglass, Ph.D. 2019, 2020

    bruce.douglass@outlook.com