01.01.2015 Views

UML Weekend Crash Course™ - To Parent Directory

UML Weekend Crash Course™ - To Parent Directory

UML Weekend Crash Course™ - To Parent Directory

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

PART<br />

IV #<br />

Saturday Evening<br />

Part Review<br />

1. What do you typically use for the basis of a Sequence diagram<br />

2. How would you show the data returned by an operation<br />

3. If a scenario covers interactions that are already modeled in another scenario,<br />

do you have to repeat them<br />

4. How do you know where to place an activation bar<br />

5. What information describes a synchronous event<br />

6. The Collaboration diagram uses the Object diagram as the basis for modeling<br />

events. Why is this advantageous<br />

7. How does the Collaboration diagram model the order of events<br />

8. What cannot be seen on the Collaboration diagram that can be seen on the<br />

Sequence diagram<br />

9. On a Collaboration diagram, how do you show that an object refers to one of its<br />

own operations<br />

10. How do you model iteration on a Collaboration diagram<br />

11. What is the first step in constructing a Collaboration diagram<br />

12. What is the second step in the construction of the Collaboration diagram<br />

13. What is the third step in the construction of the Collaboration diagram<br />

14. What is the fourth step in the construction of the Collaboration diagram<br />

15. When you encounter a synchronous event, what else can appear on the diagram<br />

16. How do you start the construction of a Statechart diagram<br />

17. How is the state of the object actually recorded<br />

18. What are the elements that make up a state transition<br />

19. What is a final state Does every Statechart have to have one<br />

20. Can there be more than one transition between the same two states

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!