safety-critical

State Machine with no function pointer

徘徊边缘 提交于 2019-12-13 11:35:24
问题 I have implemented a complex state machine with numerous state transitions for a safety SIL 4 system. The back bone for this implementation was done using function pointers. When all was sailing smoothly, the V&V opposed the use of function pointers in a SIL 4 system. Reference- Rule 9 NASA.Misra C 2004 however doesnt say that function pointers cant be used. Is there any other way to implement complex state machines without any function pointers? 回答1: First of all, that NASA document is not

Alternatives to dynamic allocations in safety critical projects (C)

依然范特西╮ 提交于 2019-12-10 15:19:52
问题 Safety critical projects do not recommend any dynamic allocations or freeing allocated memory. Only during elaboration/initialization phase of the program execution, it is allowed. I know most of you will argue to implement SW in terms where it should do all static allocations only or do some justification in the code that dynamic allocations will not harm the overall program,etc but still, Is there any alternative to this problem? Is there any way or any example to kind of allocate some

Qt Research/Academic/Journal Papers/Articles

烂漫一生 提交于 2019-12-06 07:04:35
问题 I'm trying to find any research/academic/journal papers/articles that analyze recent versions of Qt and Qt Creator. Specifically, I'm trying to evaluate Qt from a real-time safety critical perspective, so any information is helpful. P.S. I've tried the typical search approach: Google scholar, IEEE Explore, ACM Digital Libray, etc. Maybe I'm not using the right search terms, but nothing useful is turning up when I search for the following: "Software safety Qt GUI" or any permutation of that.

Qt Research/Academic/Journal Papers/Articles

半腔热情 提交于 2019-12-04 14:36:16
I'm trying to find any research/academic/journal papers/articles that analyze recent versions of Qt and Qt Creator. Specifically, I'm trying to evaluate Qt from a real-time safety critical perspective, so any information is helpful. P.S. I've tried the typical search approach: Google scholar, IEEE Explore, ACM Digital Libray, etc. Maybe I'm not using the right search terms, but nothing useful is turning up when I search for the following: "Software safety Qt GUI" or any permutation of that. Thanks again for any helpful insights. To get the best info on Qt for research, contact Qt's leadership

What is the best resource for learning about Safety Critical Systems Development (C/C++) [closed]

若如初见. 提交于 2019-12-04 13:36:39
问题 Closed. This question is off-topic. It is not currently accepting answers. Want to improve this question? Update the question so it's on-topic for Stack Overflow. Closed 4 years ago . I'm looking to locate a good resource (book or otherwise) on safety critical systems development techniques/methodologies, especially something that will cover both hardware and software . I have a sound working knowledge of C/C++, so even if it is just code on SourceForge etc I would still appreciate a link to

What is the best resource for learning about Safety Critical Systems Development (C/C++) [closed]

雨燕双飞 提交于 2019-12-03 08:30:55
I'm looking to locate a good resource (book or otherwise) on safety critical systems development techniques/methodologies, especially something that will cover both hardware and software . I have a sound working knowledge of C/C++, so even if it is just code on SourceForge etc I would still appreciate a link to it to have a browse. Thanks. The podcast Software Engineering Radio has some episodes which talk about e.g. real-time and fault tolerant systems which I found very informative. Those episodes also had good references to books. 来源: https://stackoverflow.com/questions/81832/what-is-the

Rulesets for cppcheck

社会主义新天地 提交于 2019-12-03 06:30:56
问题 Cppcheck allows you to create your own rules files, but I don't know how much of cppcheck's functionality is exposed. Is anyone working on a set that would enforce JSF or MISRA rules? 回答1: You won't be able to implement all MISRA/JSF rules and directives as cppcheck rules, mostly only the straightforward ones restricting certain C language features and constructions or that are style-related (some that come to mind: spaces before/after ./->, # of arguments on a single line, use of unions to