Responding to Riemenschneider... ... Note "...in the first example". In your first example you had a single instance already in hand and navigated down the...
... Ah! The semantics of OO! ;-) Maybe we need to clarify whether we are talking about set instances, OOA instances, or OOPL instances, or what the rules are...
Responding to Riemenschneider... ... As you point out, there is a rational for defining the sets. But the syntax "create object instance" of c2 seems highly...
The concept of "assigner" is defined [pg 219] as "a state machine that serves as a single point of control for creating links on competitive associations"....
Responding to Ring... ... No. I believe it is best to think of critters like the Assigner as examples of a GoF Singleton design pattern where it is important...
... Well, this could be said to be confusing, but a superclass and subclass are distinct OOA elements. "create object instance" just denotes creating an...
Responding to Riemenschneider... ... Class2 is an OOA model element that is _part of_ an OOA subclassing definition. When that definition is implemented there...
... Where's the discriminator? i.e., You're creating an instance of subset A, and all instances of subset A will also reside in subset B, C, or D. Somewhere B,...
... easy ... By MDS, I mean the R1 != R2; IMO, R1 = R2 is nonsense due to having two identifiers for the same generalization. We were talking about creating an...
Responding to Riemenschneider... ... How soon they forget. We had a discussion over this last year and you won! R1 = R2 means /all/ subclasses are disjoint...
... Someday we'll have to learn to talk the same language, so we don't have these long discussions to reach the same conclusion. ;-) However, since no one else...
Hi. Where can I find more info (docs, tutorials, etc.) about UML 2 diagrams, specially Activity Diagram and Composite Structure Diagram? Thanks....
niksa_os
niksa_os@...
Sep 17, 2004 4:41 am
773
I was (re)reading the section on Use Cases in the Executable UML book today and got to section 4.4.1 when it occured to me that a Use Case diagram isn't all...
... I have also never found Use Case diagrams to be of assistance. identifying Use Cases is *extremely* important, but the text is always adequate for my own...
The book I've liked the best on use case modeling is Kurt Bittner and Ian Spence's by the same name "Use Case Modeling". In their book I believe they say...
Responding to Riemenschneider... ... NS, DT. B-)) Use cases are a form of requirements specification so they really aren't part of either UML or eUML....
More thoughts while rereading the Executable UML book. In the section, 5.5.3 Attribute checks, I am wondering about the justification for "composite value"...
... What distinguishes an executable UML model from a mere data model is that these classes have lifecycles. Objects (instances of classes) progress through...
... The classic justification for avoiding multiplicity in analysis is that the problem is better stated with full normalization and without repeating...
... Not exactly. From a modeling perspective, there is no justification in dividing an atomic value into constituent pieces if the value is atomic in the...
Responding to Balcer... ... I agree with Riemenschneider that I don't like this _for this example_. It is not a simple domain. It combines two distinct...
... example ... address are ... structure ... Suppose other domains need to deal with Address? The UI obviously needs a way to enter in address, and the label...
... The problem I cited, an authorization set, is an example of this. Specifically, it is a type understood in the problem domain where both the composite and...
... OK, so this is just plain wrong. Sorry. Three of the addresses are distinct, customer, billing, and delivery. The fourth, Shipment.deliveryAddress, is...
... easily abused ... meaningful ... of ugly ... I looked at Date's An Introduction to Database Systems chapter on "nulls". He discusses two approaches, 3...
... problem: A ... separate ... Further clarification of my response is needed to really express my heartburn with composite value attributes. The reasoning...
Responding to Riemenschneider... ... But isn't this why knowledge attributes are ADTs? All we need to know at the higher level of abstraction is the ADT...
... must be ... In so ... Two things have occured to me from your response: 1) I'm approaching this from the wrong direction. There exists a real maintenance...
Responding to Riemenschneider... ... I still see it as a matter of abstraction. The semantics of the bridges that connect subsystems must be defined when the...