It is a very simplistic view, but, broadly speaking, there are two ways to design an embedded software application [or pretty much anything really]: either top-down or bottom-up. There are pros and cos of each approach and it is hard to say, in the general sense, that one is better than the other.

So much for design, but how development is approached is another matter … (more…)

Away from my immediate professional colleagues, if I talk about my work, I am commonly asked questions like: What is an embedded system? Where can I see one? The answer to the first question can be framed in various ways – I just need to shy away from presenting a digital electronics or computer science 101; it is usually best addressed by reference to examples: mobile phone, washing machine, laser printer, etc. I normally address the second question by suggesting that my questioner imagine the start of an ordinary day. Wake up and cancel the alarm [embedded system #1]; put on the news on your smart speaker [#2]; prepare breakfast using the toaster [#3] or microwave [#4] or induction hob [#5] and coffee machine [#6]; eat your food while reading on your e-reader [#7]; get in the car to go to work [#8 …]. Before you leave the house, you have probably interacted with at least 6 embedded systems – it might be quite a few more. But, when you get into your car, things get very interesting … (more…)