StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
20532007
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2013-12-11T23:19:40.450
FavoriteCount
0
LastActivityDate
2013-12-12T01:53:06.143
LastEditDate
2013-12-12T01:53:06.143
LastEditorUserId
2362356
OwnerUserId
2362356
ParentId
20491501
PostTypeId
2
Score
19
ViewCount
0
LastEditorDisplayName
text
Body
Your code is represented in the following class diagram: <img src="https://i.stack.imgur.com/32Lxl.png" alt="enter image description here"> It represents the relationships between the classes: <ul> <li><code>Implementation</code> implements <code>ICallback</code></li> <li><code>Implementation</code> depends on <code>AnotherImplementation</code> (it creates one in its constructor)</li> <li><code>AnotherImplementation</code> has a <code>ICallback</code> (named mCallback)</li> </ul> A class diagram does not represent method functionality. Method functionality is visualized with a sequence or a Collaboration diagram. In your example, the sequence diagram for <code>testFucntion()</code> is very simple: <img src="https://i.stack.imgur.com/ljvgw.png" alt="sequence diagram"> Note that the <code>Implementation</code> class does not show in the sequence diagram. This happens because the <code>mCallback</code> member is declared as <code>ICallback</code>. It could be anything that implements the <code>ICallback</code> interface. I think that the more interesting question is how to visualize the method that triggers the callback. You don't mention which method of <code>Implementation</code> calls the <code>testFunction()</code> of <code>AnotherImplementation</code>, so I guess that this happens inside the constructor of <code>Implementation</code>. I created the following sequence diagram for this constructor: <img src="https://i.stack.imgur.com/VcQUk.png" alt="callback sequence"> Here you can see: <ol> <li><code>Implementation</code> creates the <code>AnotherImplementation</code></li> <li><code>Implementation</code> invokes <code>testFunction</code> on <code>AnotherImplementation</code></li> <li><code>AnotherImplementation</code> invokes <code>informFunction</code> on <code>Implementation</code></li> </ol>
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POHow to represent Callback in UML Class Diagram
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USnakosspy
UserOwnerUserId
1. USnakosspy
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. POHow to represent Callback in UML Class Diagram
 singulars
 PostTypePostTypeId
 PTQuestion
PostsParentIdCreationDate
1. This table or related slice is empty.
VotesPostIdCreationDate
1. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTAcceptedByOriginator
2. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
CommentsPostId
1. This table or related slice is empty.

Querying!

Guidance

A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.