Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <blockquote> <p>To my mind an extension is a weaker relationship than generalization as a direct substitution of the specialised use case for the base case must be possible in generalization but not necessarily in extensions.</p> </blockquote> <p>That is true.</p> <blockquote> <p>It seems to me that generalisation implies a polymorphic implementation is desired while extension implies some branching structure is to be used.</p> </blockquote> <p>The diagram does not dictate any implementation. You can interpret a hint from the diagram for yourself, though. UML remains independent of language and solution there.</p> <blockquote> <p>Isn't the Use Case stage far too early for such implementation specific concerns to be modelled? </p> </blockquote> <p>Well, as indicated above, UML does not enforce any specific kind of implementation. However, you are gathering some important functional requirements here that might greatly influence your time schedule and workload. ("Pay with credit card" is way more complex to handle than "pay in advance by bank transfer"). So you'd strive to capture that but remain open to different solution approaches.</p> <blockquote> <p>There are much more appropriate UML diagrams for that. </p> </blockquote> <p>You can really use them in parallel :) as they are different views on the same subject.</p> <blockquote> <p>Is there a hard and fast rule regarding which of the two to use and if so what is it?</p> </blockquote> <p>I prefer the generalization in this case because in fact the extensions falsely suggest there could be a way of paying without using any of the three named options. As you indicated yourself.</p>
    singulars
    1. This table or related slice is empty.
    1. POUse case generalization versus extension
      singulars
      1. PTQuestion
    1. PTAnswer
    1. This table or related slice is empty.
    1. USobserver
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POUse case generalization versus extension
      singulars
      1. PTQuestion
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTAcceptedByOriginator
    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.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload