Modeling

Especially for safety critical embedded software, an holistic system view is crucial to understand the context in which software is developed. Therefore, µRTE not only features modeling of software aspects such as:

• execution units
• data-flows
• hardware interfaces
• activation
• operational states
• memory assignment
• etc.

but also the software's ecosystem including hardware, functional specification and requirements according to common safety standards. For each of those so-called layers, easy to understand and intuitive diagrams are available for modeling. Layers are independent but reference among each other and are designed in a generic way only containing fundamental and necessary information. There is no order with which the layers have to be modeled and the model can be modified at any time at any point. An analyzer checks for inconsistencies and safety relevant dependencies also before code and report generation.

• modeling overview

Code generation

Focus software development on the functionality of the application itself rather than its ecosystem! An entire executable software framework is generated out of the model including code files, data abstraction layer, activation engine, error handling, memory allocation, RTOS configuration and more. The generated code follows proven in use patterns and is designed for simplicity and readability, easing debugging, verification and assessment. Moreover, documentation such as requirements are generated into the code for the developer to never lose track on what to do where and why.

• code overview

Report generation

Consistent documentation can be challenging not only because a system needs to be fully understood but also because architectures can change during development, making it hard to keep all documents up-to-date. µRTE generates an extensive and portable report, containing all dependencies of all elements in the model - always synchronous with the actual software and available at any time. Tables and diagrams allow easy and intuitive navigation trough the model and serve as a interface for the project specific documentation framework.

• example report