Only visible to XING members.

Formal Methods

This content will be displayed once you're logged in.
+6 more comments
Last comment:
Only visible to XING members.

Good morning Marc,

that reads quite fascinating.
I'd appreciate to read the one or other update. on this topic.
Well, a thesis is at least providing timing restrictions and budget limitations.
Good luck for your students, I hope they're working out a thesis worth a distinction

Have a nice and productive day
Jörg

Only visible to XING members.

Writing plattform independent software

Which are the methods of choice for writing plattform independent sofware?
This will surely wake up all the Java gurus, but ... isn't there anything else?
We are using OSAL here. This is a bunch of code, which offers a defined interface to all layers above. The Drivers below either exist as stubs or real implementations. This is somehow a Java approach but not using the Java language. However, this requires a complete set of drivers for each plattform, and it increases runtime on the target a bit, but offers benefits when it comes to debugging on a PC.

Joaquim Duran Comas
+2 more comments
Last comment:
Joaquim Duran Comas Joaquim Duran Comas

Hans Adams escribió:
> Jörg Neumann schrieb:
> > Which are the methods of choice for writing plattform independent
> > sofware?
>
> If you are indeed willing to write "platform independent software",
> you have to enforce the full abstraction of each layer, anyway you
> do it ;>! This starts from definition and specification of a layer
> and does not end with its implementation, but you will have to ensure
> an approbriate test environment.
>
> Be adviced to have a look at the OSI by ITU, its implementation and
> its testing ;->
>
> > This will surely wake up all the Java gurus, but ... isn't there
> > anything else?
>
> Sure, there are much more out there. You do not need an abstraction
> by classes....

The fact is that if you want to write code for several platforms, you need manage the different interface to each architecture. But you should evaluate how to implement them. There are several options, with its pros and cons:

- Based on a multi-platform library: boost, ACE, OBAP...

- Based on a abstract base class and an implementation class for each platform.

- Based on the implementation of a class and using #ifdef #endif to choose the proper implementation for each platform.

- Based on a template parameter to choose the concrete platform details.
For example, a sensor connected to a serial port. I could write a class like 'template <class TSerial> class Sensor : public ISensor' and then define a class to access to a serial port for each platform: PCSerial, ARMServial,...... (all them should share the same interface) and then you should instantiate the template Sensor with the proper serial class. Serial classes could also be used in other interfaces.

-... (Sure, there are more alternatives)

Joaquim Duran

Only visible to XING members.

RTRT - Rational Realtime Test, anyone?

New year - new tasks - new tooling landscape.
Suddenly there is a hype concerning Rational Real Time Test in my current project and I wonder, what is so special about it.
So who has ever used RTRT in his project and how was the result? Would you do it again?