the language should have a better name

TTCN version 3 is explained as a powerful test harness for software. It grew out of earlier versions used primarily in telecommunications. It's a very specialised language, unlike C or Java. With many features not typically seen in those. For example, for communicating between 2 programs using remote procedure calls, these are typically synchronous or blocking. But within TTCN-3, you can alter this to describe a non-blocking signature of a remote routine. This lets you test systems that can be more robust than those depending on blocking. Experience has shown that the latter can be fragile.

The text suggests that TTCN-3 is moving outside telecoms in its usages. But this may be overstating the case. Within general purpose Java programming, for example, it seems to be little known. Try looking through Java books, elementary or advanced. You will rarely see a mention of this. Let alone any usages.

Another flaw is in its very name. TTCN-3?! Most computer languages have names that can be easily pronounced. Even if the name is a made up one, like Fortran or Basic. A catchy name does help in garnering mindshare. Think Java. Think WiFi, as opposed to 802.11*. The people who maintain TTCN should have realised this.

Other Reviews

• THE reference about TTCN-3, but already (partly) obsolete
• Big frame work for testing.
• the language should have a better name