Abstract
This tutorial explores some of the challenges of measuring performance and timing behaviour of reliable embedded systems and explains techniques and strategies for optimization of reliable software. The tutorial explains and compares different techniques for measurement and analysis of software on embedded targets including tracing methods, in-memory analysis and using hardware support. It shows how those techniques can be used for verification of non-functional properties on-target, including in the context of DO178B/C and the new ISO26262 standard to meet the requirements for safety in automobiles. The tutorial presents optimization at a high and low level, looking at strategies and the tradeoffs that occur in reliable software development, introducing a process that helps to ensure that optimization can have the maximum benefit for the minimum effort.
- RVS (Rapita Verification Suite). RapiTime WCET and Timing Analysis and RapiCover structural coverage tool. http://www.rapitasystems.com/Google Scholar
Index Terms
How to measure and optimize reliable embedded software
Recommendations
How to measure and optimize reliable embedded software
SIGAda '11: Proceedings of the 2011 ACM annual international conference on Special interest group on the ada programming languageThis tutorial explores some of the challenges of measuring performance and timing behaviour of reliable embedded systems and explains techniques and strategies for optimization of reliable software. The tutorial explains and compares different ...
Extending Contract theory with Safety Integrity Levels
HASE '15: Proceedings of the 2015 IEEE 16th International Symposium on High Assurance Systems EngineeringIn functional safety standards such as ISO 26262 and IEC 61508, Safety Integrity Levels (SILs) are assigned to top-level safety requirements on a system. The SILs are then either inherited or decomposed down to safety requirements on sub-systems, such ...
Predicting NFRs in the early stages of agile software engineering
ACMSE '18: Proceedings of the ACMSE 2018 ConferenceNon-Functional requirements (NFRs) are overlooked whereas Functional Requirements (FRs) take the center stage in developing agile software. Research has shown that ignoring NFRs can have negative impacts on the software and could potentially cost more ...







Comments