Extend Telelogic® Tau® to Suit Your Domain

The Telelogic Tau Model Driven Development (MDD) environment has been designed to be highly extensible by its users. Featuring an open architecture that is strictly based on the UML® 2.1 meta-model, Tau can be extended and customized to meet your domain-specific needs. Extensibility includes ways that the user can:

  • Write and use Add-Ins
  • Extend the information contents of UML models using profiles
  • Extend Telelogic Tau's error checker with custom semantic checks
  • Extend or constrain Telelogic Tau's user interface and diagrams
  • Start Telelogic Tau from the command-line
  • Access and modify the contents of UML models using a programmable interface (public APIs in various technologies)
  • Define custom code generators and other tools integrated with Telelogic Tau's Application Builder

Domain and framework support via add-ins and profiles

Add-ins provide the basic mechanism that you can use to package your user-developed set of features. Telelogic Tau offers you built-in add-ins that enable features required to support specific functions like generating application code. Users can easily use Telelogic Tau to modify these add-ins or even construct new add-ins to support a particular purpose.

The Profile mechanism uses UML to describe extensions to UML, so that tool vendors and users have a "sensible" way of extending the language. This capability fosters re-use, as a profile could be developed to support a UML extension (like Real Time Types) and then shared with other users without regard to the solution that they are using.

Diagrams and menus can be constrained to meet company process

In many cases, the program manager has to restrict the use of diagrams, design elements, or language constructs to a smaller subset. The reasons for this include:

  1. Restrictions in the target language or compiler. Not every C++ language construct is supported by every C++ compiler.
  2. Although supported, a particular element or construct could be inefficiently implemented or even disallowed by regulatory or safety guidelines.
  3.   Best-practice rules may limit the choices of accepted approaches. The purpose of these rules is to make the application easier to maintain and understand for a particular class of user, and to avoid procedures or constructs that could introduce errors into the application.

Custom error checks which support design and regulatory specifications and limits

Telelogic Tau's rules-based model checking will compare the design model against over 1,000 to enterprise rules and guidelines to ensure adherence to industry standards and best practices. Users may develop and extend rules for their domain or project, such as to ensure design-level compliance with industry-constrained development practices or guidelines.