(1) Sequence diagrams represent (a) exactly what the use case diagram represents.

(b) the sequence for a scenario of a use case.

(c) exactly what the class diagram represents. (d) the sequences that connect multiple use cases together.

(2) Actors in a sequence diagram typically interact with (a) Boundary objects

(b) Entity objects (c) Any type of object (d) Control objects

(3) Are sequence and communication diagrams different from one another? (a) "Both diagrams present exactly the same information in exactly the same format. So if you have one, you don t need the other." (b) They both present very different kind of information. Sequence diagram is similar to a use case diagram. You can replace a use case diagram with a sequence diagram. Communication diagram is similar to a class diagram. You can replace a class diagram with a communication diagram. (c) "They both present the same information, but in different visual formats. Communication diagrams show flow of messages across time well whereas sequence diagrams show coupling well which will help in finding whether any associations are missing in the class diagram and to find navigability." (d) "They both present the same information, but in different visual formats. Sequence diagrams show flow of messages across time well whereas communication diagrams show coupling well which will help in finding whether any associations are missing in the class diagram and to find navigability."

(4) How do we find navigability of an association between two classes? (a) We cannot find navigability on our own. We ask the client. (b) Check the direction of messages between the objeects of those two classes across the sequence or communication diagrams in which those objects participate in. (c) We do this based on the direction of includes or extends in the class diagram. (d) Check how you read the relationship name. Navigability is based on what direction you are able to read the association in plain English.

(5) A message is a sequence diagram is (a) is related to an includes relationship in a use case diagram (b) A call to a method in the destination object (c) An attribute in the origin object (d) not related to anything in the class diagram