2. How do you design embedded software?

The first step in designing embedded software is to draw up a technical specification of what the software is expected to do. This must include a description of what the software is intended to achieve, as well as the expected performance or reliability.

It must be written by the customer, or with the customer who initiated the need for software for an automated system.

It must contain a set of requirements detailing what the software must do for the system. These requirements must be comprehensible to the person in charge of preliminary design or software architecture. To check that the customer understands them correctly, a requirements review meeting can be organized, at which all the requirements are reread together, and any uncertainties clarified.

Example requirement: the software must control the heating system...