search

openETCS / validation

WP4: Validation and verification strategy
8 stars 22 forks source link

Coding Rules #276

Open MarcBehrens opened 9 years ago

MarcBehrens commented 9 years ago

related to https://github.com/openETCS/product-backlog/issues/29

The coding rules for hand written code need to be detailed.

MarcBehrens commented 9 years ago

relates to https://github.com/openETCS/modeling/issues/522 basically there are two different ways to proceed. Either a generic way to handle real typed variables and their conversion or to try to avoid real typed variables.

It should be taken into account that according to Mü8004 from 01.08.2003 Teil 42 720 (6) the german national authority only allows
"char, unsigned char, short, unsigned short, int, unsigned int, long, unsigned long, enum, void" as part of structured datatypes.

Type conversion between SCADE types and API types is one topic for the verification. Mapping the SCADE API to the API definition has type conversions which need to be verified.

MarcBehrens commented 9 years ago

Concerning significance length see https://github.com/openETCS/modeling/issues/303