Welcome, Guest
Username: Password: Remember me
  • Page:
  • 1

TOPIC: Migration & translation in response to Re: TTCN-2 TS Var:s and its TTCN-3 counterpart

Migration & translation in response to Re: TTCN-2 TS Var:s and its TTCN-3 counterpart 09 Jan 2002 01:10 #6070

Hi all,

I agree with Claude's comment that it is much more realistic to think of
preserving and using TTCN-2 test suites and test systems as is and
developing new systems in TTCN-3 or TTCN-2 as it is seems to be
suitable. We have prepared some slides about the topic that are
available from:
www.openttcn.com/Publications/Migration

Claude Desroches wrote:
>> I fully agree given the fact that the need for global variables is
>> only to allow2 to 3 transformation. One can always choose to
>> transform as much as possible from TTCN-2 to TTCN-3 then redesign
>> any parts related to global variables directly in TTCN-3. Who says
>> that the transformation needs to be 100% automated? (It is better of
>> course, but then again, how much of a problem does or will it
>> present). The likely situation is that most existing TTCN-2 ATSs
>> will continue to be maintained using TTCN-2, and only new ATSs will
>> be developed from scratch using TTCN-3.
>>
>> Only in rare cases will there be a real need to transform an existing
>> ATS from TTCN2 to TTCN-3 to take advantage of TTCN-3 features. In
>> most cases however, I suspect that the cheapest and easiest approach
>> will be to keep the apples with the apples and plant some orange
>> trees. (apples = TTCN2) orange trees = TTCN3). [:-)] .
>> ATS needs Keep in mind that we are only talking about existing TTCN-2
>> test suites that

I think that it is as realistic to interpret the TTCN-3 and TTCN-2 code
directly and interface to the existing code using some kind of
middleware solution as it is to generate C code...

Johan Nordin wrote:
>> are to be converted into TTCN-3. Today, these test suites are used
>> for generating C code (there's no realistic alternative). The users
>> are likely to have written other code to be compiled with the
>> generated C code, like encoders/decoders, user I/F etc.
>> If this is to be reused, the user would have to go for a C solution
>> in their TTCN-3 system as well.

Excellent New Year for all!
Vesa-Matti

--

Vesa-Matti Puro
Expert
Open Environment Software Oy
www.openttcn.com
The administrator has disabled public write access.
  • Page:
  • 1

FacebookTwitterGoogle BookmarksRedditNewsvineTechnoratiLinkedin