What can you say about the control flow of each of the following systems? Is it centralized? Is it distributed? If one sequence diagram is too large or refers to another diagram, indicate it with either: an unfinished arrow and comment a "ref" frame that names the other diagram when would this occur in our system? Notice that an object created after the start of the scenario appears lower than the others deletion: an X at bottom of object's lifeline Java doesn't explicitly delete objects they fall out of scope and are garbage-collectedĪctivation: thick box over object's life line drawn when object's method is on the stack either that object is running its code, or it is on the stack waiting for another object's method to finish nest to indicate recursion Activation Nestingįrame: box around part of a sequence diagram to indicate selection or loop if -> (opt) if/else -> (alt), separated by horizontal dashed line loop -> (loop) Message (method call) indicated by horizontal arrow to other object write message name and arguments above arrowĥ Messages, continued message (method call) indicated by horizontal arrow to other object dashed arrow back indicates return different arrowheads for normal / concurrent (asynchronous) methodsĦ Lifetime of objects creation: arrow with 'new' written above it ![]() Participant: an object or entity that acts in the sequence diagram sequence diagram starts with an unattached "found message" arrow message: communication between participant objects the axes in a sequence diagram: horizontal: which object/participant is acting vertical: time (down -> forward in time)ģ Representing objects Squares with object type, optionally preceded by object name and colon write object's name if it clarifies the diagram object's "life line" represented by dashed vert. Presentation on theme: "Sequence Diagram."- Presentation transcript:
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |