Book a Demo

Author Topic: What didn't make it into 7.0 Beta  (Read 2830 times)

Paolo F Cantoni

  • EA Guru
  • *****
  • Posts: 8626
  • Karma: +259/-129
  • Inconsistently correct systems DON'T EXIST!
    • View Profile
What didn't make it into 7.0 Beta
« on: May 22, 2007, 05:02:39 am »
Looks like the ability to create formatted notes didn't make it in.

Can the Sparxians confirm?

Paolo
Inconsistently correct systems DON'T EXIST!
... Therefore, aim for consistency; in the expectation of achieving correctness....
-Semantica-
Helsinki Principle Rules!

Graham_Moir

  • EA User
  • **
  • Posts: 749
  • Karma: +10/-15
    • View Profile
Re: What didn't make it into 7.0 Beta
« Reply #1 on: May 23, 2007, 11:57:52 pm »
DDL to manage a changing schema.....

thomaskilian

  • Guest
Re: What didn't make it into 7.0 Beta
« Reply #2 on: May 24, 2007, 01:37:54 am »
What did make it except for eye candy? I'm not very convinced this time.

jeshaw2

  • EA User
  • **
  • Posts: 701
  • Karma: +0/-0
  • I'm a Singleton, what pattern are you?
    • View Profile
Re: What didn't make it into 7.0 Beta
« Reply #3 on: May 24, 2007, 05:50:21 am »
To be fair, Database Views made it, but I haven't tried it yet. The ability to include external images on a diagram is useful and a bit more than eye-candy.

However, Support for Aspect Oriented Design didn't make it yet; it won't be long before that becomes a must have for UML tools.  I'm starting to need it in my college and continuing education lectures now, but AOP is off and running hard with AspectJ and Aspect.NET.  Jacobson & Ng provide a good discussion and suggested notation for AOD.  Properly implemented, EA would provide tremendous support to the modeling process by supporting aspect sliced diagrams.

With the addition of a Point Cut compartment to a Class element, we could probably handle the rest with judicious use of a <<merge>> relation between classes until the OMG gets around to addressing the AOD issues.  EA could either provide a user defined compartment, or isolate the compartment in an <<aspect>> stereotype.  Apologies for my rant here in this thread, but I feel strongly about this.
Verbal Use Cases aren't worth the paper they are written upon.