Play now
Play Video
Play now
Play Video
Close
How can I create the needed millions of scenarios?
How can I avoid the test explosion problem?
How can I find out if my tests are passed or failed?
How can I create the needed millions of scenarios?
How can I avoid the test explosion problem?
How can I find out if my tests are passed or failed?
Intuitive formal specification of safety requirements
Formalization of requirements transforms your requirements to machine-readable representation. That is essential basis of automation and replaces manual efforts on testing and verification steps with intelligent technologies.
You can easily formalize your requirements on BTC EmbeddedPlatform.
In most development projects today, requirements are created and managed using informal natural language.
As natural language typically leaves some room for interpretation, there’s the possibility that function developers or test engineers ultimately implement a different behavior than intended.
With a semi-formal or formal specification in BTC EmbeddedPlatform, you can transform your requirements into a clear, unambiguous and machine-readable representation – improving their quality and making them much more valuable for the following steps in the development workflow.
No need to be afraid, formal specification is not only for academic experts anymore. A graphical and intuitive formal language named Universal Pattern is available on BTC EmbeddedPlatform. Universal Pattern is a declarative language suitable for requirements specification. You can easily specify your system or software under development with a set of requirements.
Individual requirement is a statement which expresses a need and its associated constraints and conditions. Universal Pattern represents a requirement with Trigger – Action relationship. Each Trigger/Action phase consists of conditions and timings, and they are filled by Macros. The Macros are later mapped to intefaces of the system/software under development. That structure makes the requirement machine-readable while keeping its readability.
In the “ACC following control” and the “ACC speed control” states, braking by the driver shall deactivate ACC function within 100 ms.
$ACCState_FollowingControl : State >= 10 || State <= 14
$ACCState_SpeedControl : State == 20
$BrakingPedal_Pressed : BrakingForce > 10.0
$ACC_deactivate : tr(State == 2)
Thanks to the machine-readable nature of the formalized requirements, you can directly use them within several verification use cases and dramatically improve the quality and completeness of the verification process with intelligent technologies.
The power of proof for safety-critical systems, your achieve more than testing with less effort
Ultimate frontloading, failure detection even before modeling and/or implementation
If you would like to try out our tools, we will gladly provide an evaluation license free of charge. Evaluations include a free launch workshop and also provide an opportunity for you to meet one-on-one with our support and engineering teams.
Do you have any questions or want to see our tools in action? If so, please use the link below to schedule a meeting, where a member of our engineering team will be happy to show you the features and use cases and directly answer any questions you might have.
If you would like to try out our tools, we will gladly provide an evaluation license free of charge. Evaluations include a free launch workshop and also provide an opportunity for you to meet one-on-one with our support and engineering teams.
Do you have any questions or want to see our tools in action? If so, please use the link below to schedule a meeting, where a member of our engineering team will be happy to show you the features and use cases and directly answer any questions you might have.
Sharing insights on embedded software development, model-based design, automatic code generation and ISO 26262 compliant testing.
Intuitive formal specification of functional requirements as a basis of automation
We provide intelligent and automated test solutions which enable our customers to deal with the growing complexity of embedded software while achieving high quality in compliance with the ISO 26262 standard.
Copyright © 2024 BTC Embedded Systems & BTC Japan
