Work you have to repeat
- Rework the code architecture
- Update the documents
- Redraw the diagrams
- Recheck the traceability
- Repackage every hand-off
For embedded engineering teams
The product definition and delivery
platform for embedded software
Capture and agree what your product does as you go.
Turn that definition into instant code architecture and supporting material.
// Our team has supported
- Siemens
- Schindler
- Philips
- Infineon
- Fujitsu
- G+D
// 01 · The Platform
Agree how your product works.
Get an instant code framework.
Plan and agree together
Capture features in plain English. Prioritise them with your team and decide what moves forward.
Create the engineering definition
Build out approved features with Structured English, use cases and requirements.
Get the code architecture you need
Check the agreed definition, then build code architecture for EOS Max, Zephyr or FreeRTOS.
// 02 · The work that goes away
Building embedded software doesn't have to be so painful.
One product change can mean updating code, documents, diagrams and traceability by hand. With Solaros, they all come from the same definition.
Change the specification once
- Code architecture rebuilds
- Documents stay current
- Diagrams regenerate
- Traceability carries through
- Context stays ready to export
// 03 · What you get
Put your effort into thinking.
Let tools do the typing.
Agree what the product does in English.
Get the code architecture deterministically from that definition, as well as updated supporting material.
REVIEW PACK
Project updates. Current from the live definition, and ready to export or edit.
BUILD OUTPUT
Traceable code architecture. Built from Structured English and ready for application logic.
VISUALISATIONS
Visualisations. Ready for presentation without manual creation.
CHANGESET
Full history. See what features changed and when.
CHECKS
Live checks. Know what's inconsistent or missing in your spec.
// 04 · The Build Engine
Choose your preferred RTOS. Get reproducible code architecture instantly.
Ready for engineers and AI tools.
Take the framework and source definition into your development environment. Engineers and AI tools can work from the agreed behaviour, with calls already placed & stubbed and requirement references retained in the code.
How the Build Engine works// 05 · Hand-off
Accurate to your specifications, every time. Present, share or hand off without losing context.
01 · Present
Present accurate information every time.
Produce reports, diagrams and presentations from the current definition, ready to export or edit.
02 · Export
Export and edit in the tools you already use.
Export reports, data and diagrams into their native formats.
03 · Continue
Keep using your existing project management.
Carry feature and feature-set identifiers into the work your team manages elsewhere.
04 · Implement
Ready for your application logic.
State machines, events and APIs are placed and compiled for your target.
05 · Context
Give agents the context they need.
Export the definition and its documentation in machine-friendly formats.
// See it work
See how a project
gets built.
See a reference project get built from specification to code architecture.