StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
14967838
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
2
CommunityOwnedDate
CreationDate
2013-02-19T21:32:46.363
FavoriteCount
0
LastActivityDate
2013-02-21T15:45:42.627
LastEditDate
2013-02-21T15:45:42.627
LastEditorUserId
1297272
OwnerUserId
1297272
ParentId
14945618
PostTypeId
2
Score
-2
ViewCount
0
LastEditorDisplayName
text
Body
Yes! (and final too, since UseCase is a specialization of Classifier). Quoting the Unified Modeling Language (OMG UML),Superstructure: Generalizations <ul> <li>UseCase (from UseCases) specializes BehavioredClassifier (from BasicBehaviors, Communications). </li> <li>BehavioredClassifier specializes Classifier (from Kernel, Dependencies, PowerTypes, Interfaces).</li> </ul> Attributes: Classifier has the following attributes: <ul> <li>isAbstract: Boolean (if true, the Classifier does not provide a complete declaration and can typically not be instantiated).</li> <li>isFinalSpecialization: Boolean (if true, the Classifier cannot be specialized by generalization).</li> </ul> Constraints: a classifier may only specialize classifiers of a valid type. <pre><code> self.parents()->forAll(c | self.maySpecializeType(c)) </code></pre> Additional operations The query <code>maySpecializeType()</code> determines whether this classifier may have a generalization relationship to classifiers of the specified type. By default a classifier may specialize classifiers of the same or a more general type. <pre><code>Classifier::maySpecializeType(c : Classifier) : Boolean; maySpecializeType = self.oclIsKindOf(c.oclType) </code></pre> And last, but not least, even though it says that <code>maySpecializeType()</code> "is intended to be redefined by classifiers that have different specialization constraints"... there is no redefinition of <code>maySpecializeType()</code> for UseCase or BehavioredClassifier. Source: Unified Modeling Language (OMG UML),Superstructure, Version 2.4.1.
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POUse case diagram - Extend a use case, but never use the parent use case?
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USJavier
UserOwnerUserId
1. USJavier
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. This table or related slice is empty.
PostsParentIdCreationDate
1. This table or related slice is empty.
VotesPostIdCreationDate
1. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTDownMod
2. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTDownMod
CommentsPostId
1. COPlease expand on your answer; do you have a source/reference, or some specific guidance on how to do what the asker wants?
 singulars
 PostPostId
 PO
 UserUserId
 USkwah
2. COIt's clear that you don't know the semanthics of the use case diagram elements or either you didn't understand his question. @observer has a better answer.
 singulars
 PostPostId
 PO
 UserUserId
 USgustavogbc

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.