TextUML Toolkit 1.6 declared!

Posted on by

The TextUML Toolkit version 1.6 has been released. It is the same RC1 build mentioned here a week ago. The listing on the Eclipse Marketplace has been updated, so in addition to the regular update site (http://abstratt.com/update/), if you are using Eclipse 3.6, you can get it even more conveniently using the brand new Eclipse Marketplace Client.

Take a look at the new notation features:

  • preconditions on operations
operation withdraw(amount : Real);
precondition { amount > 0 and amount < self.balance }
begin
    self.balance := self.balance - amount;
end;
  • derived properties
reference employees : Employee[*]

/* calculated field */
derived attribute employeeCount : Integer := ():Integer { return self->employees.size() };
  • initial values on properties
attribute available : Boolean := true;

You can also try these new features online on AlphaSimple. Sign up or start a guest session to create, validate and run your models on the spot, there is nothing to install!

EmailFacebookLinkedInGoogle+Twitter

7 thoughts on “TextUML Toolkit 1.6 declared!”

  1. Permalink

    Walter

    August 23, 2010 at 6:48am

    Hi Rafael,
    I didn’t find info about the allowed syntax in the operation code. Could you please give me a hint ?
    Thanks,
    Walter

  2. Permalink

    rafael.chaves

    August 23, 2010 at 8:16am

    Hi Walter,

    I have been postponing documenting the syntax for behavior until someone asked for it… :)

    Will let you know when that has been done. Meanwhile, the TextUML EBNF might help.

  3. Permalink

    Walter

    August 23, 2010 at 11:00am

    Thank you. Are you following some standard ?

  4. Permalink

    rafael.chaves

    August 23, 2010 at 11:24am

    Sorry, standard for what? The resulting models follow as much the UML specification as possible. Areas where we need things UML didn’t do (for instance, closures and meta-references) were addressed by using a profile. The notation is ‘proprietary’, as until very recently, the OMG didn’t have any standards for textual notations (but the OMG does not require notation compliance).

  5. Permalink

    Walter

    August 23, 2010 at 12:14pm

    >>standard for what?<<
    I’m asking if the operation (and precondition) language is based in some other language…

  6. Permalink

    rafael.chaves

    August 23, 2010 at 12:21pm

    I see now.

    The abstract syntax is UML (action semantics) with an extension profile to support a few things not in UML (mostly closures). The concrete syntax/notation is not standard (there isn’t one).

Comments are closed.