Message Formats in SSD
8 Questions
0 Views

Choose a study mode

Play Quiz
Study Flashcards
Spaced Repetition
Chat to lesson

Podcast

Play an AI-generated podcast conversation about this lesson

Questions and Answers

What is the purpose of a message-name in UML format?

  • It denotes the service requested, written as a verb-noun. (correct)
  • It identifies the system's operational capacity in response to events.
  • It indicates the type of external actor interacting with the system.
  • It describes the data being returned from the destination object.
  • What does an asterisk (*) indicate in message notation for SSD?

  • The message is optional and may not be sent.
  • The message is sent in a repeating or looping manner. (correct)
  • The message is conditional based on parameters.
  • The message has no parameters to pass.
  • How are parameters listed in a UML message format?

  • Parameters are separated by commas within parentheses. (correct)
  • Parameters are separated by semicolons.
  • Parameters are grouped without any separators.
  • Parameters use spaces to separate each entry.
  • In system operations, how are they typically triggered?

    <p>By external input or system events from actors.</p> Signup and view all the answers

    What is indicated by brackets [] in message notation?

    <p>A true/false condition that determines message delivery.</p> Signup and view all the answers

    What does the term 'return-value' represent in SSD message notation?

    <p>The data returned from the destination object to the source object.</p> Signup and view all the answers

    Which of the following is NOT a type of diagram used in extending and integrating requirements models?

    <p>System Testing Diagram</p> Signup and view all the answers

    When a use case is realized, what type of diagram is typically used?

    <p>Use case realization diagram detailing specific use case implementations.</p> Signup and view all the answers

    Study Notes

    Message Formats in SSD

    • Messages in SSD consist of a message name followed by parameters (in parentheses)
    • Names begin with a lowercase letter
    • No spaces in names; use uppercase letters to separate words
    • Names in parameters are separated by commas
    • Empty parentheses () are used if no parameters

    Outgoing Messages (System Outputs)

    • System outputs are responses to complete an event
    • Messages from the system to another system require action and a reply
    • Every output is derived from input and stored data

    Message Notation for SSD

    • [true/false condition] return-value := message-name (parameter-list)
    • * indicates repeating or looping messages
    • [] indicates a true/false condition (only tests the message)
    • Message name is verb-noun describing a service
    • Parameter list (in/without parentheses) shows data passed with the message
    • Return value (like :) describes data returned to the original sender

    Studying That Suits You

    Use AI to generate personalized quizzes and flashcards to suit your learning preferences.

    Quiz Team

    Related Documents

    ITM305 Week 7 PDF

    Description

    This quiz explores the intricacies of message formats used in Structured System Design (SSD). It covers outgoing messages, message notation, and the roles of parameters in system outputs. Test your understanding of these concepts and how they are applied in system communication.

    More Like This

    Use Quizgecko on...
    Browser
    Browser