« State API-Editor Progress | Main | Polymorphic creation events? »
Sunday
Jan222012

Update: State and Polymorphism Subsystems

New versions of each subsystem are now available.  Both subsystems have been adjusted so that Creation Events are always non-polymorphic.  The reasoning is discussed in the previous news post (and in the relevant descriptions, of course).   To help illustrate the tangled web of generalization / specialization relationships necessary to model polymorphism, I have cobbled together this color coded Venn diagram which you can also find under the Event specialization (R560) relationship in the Polymorphism description document.  (If you save the image below, it should open up larger in whatever picture viewer you have).  Then you can look at it side by side with the Polymorphism Subsystem class diagram.

Reader Comments (4)

And, yes, I know it's not really a Venn diagram. Closer to an Euler diagram, really and not exactly that due to the inartistic license with the imprecise borders and lack of circles. Let's just call it a diagram.

January 22, 2012 | Registered CommenterLeon Starr

While creating the database schema I tripped on a cut & paste error on the Polymorphism Subsystem class diagram. In the Local Effective Event, R550 should be R557 instead since it is referring to Monomorphic Event Specification. I will post an updated diagram and news update sometime this week.

January 24, 2012 | Registered CommenterLeon Starr

Did I say this week? Should have said tonight. Finished the schema and didn't find any other issues, so I have reposted the revised Polymorphism Subsystem class diagrams.

January 24, 2012 | Registered CommenterLeon Starr

Just updated Polymorphism Subsystem files to 3.1.2. Minor change. Creation boolean removed from Event Specification class. (Not needed since the spec will always be monomorphic and so a Creation Event specialization will be immediately created along with the Event Spec.

January 25, 2012 | Registered CommenterLeon Starr
Member Account Required
Welcome to miUML. We want your input, but to ward off evil spam, we request that you create a user account first.