Within this loop box, we see our first example of a return message, which is the dashed arrow with integer above it, indicating the return type. The loop is depicted as a combined fragment, as depicted by the grey box labeled “loop”. Next, as part of the process_action message, we see a loop with two calls to the write function in the activesupport package. This means that the package is now “active” in the system. The next message is the function call to process_action in the actionpack package, which then “activates” the actionpack lifeline, as can be seen from the lifeline changing from a dashed line to a rectangular box, which is the activation bar. In the case of this diagram, the external source is whatever entity made the POST request. The first message begins from outside of the diagram, indicating that it originates from a source external to the system being diagrammed. Here’s what this particular sequence diagram can tell us about the code that it models. It is shown as a box with a label that indicates the condition under which it is executed.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |