[SystemSafety] C for OSs

[paul_e.bennett at topmail.co.uk]

On 16/09/2019 at 8:05 AM, "Gergely Buday" <gbuday at gmail.com> wrote:
>
>"The problem is the industry was flooded with a huge number of 
>self-taught
>programmers."
>
>What book should we base the teaching of software engineers? Where 
>is the
>holy grail of true software engineering?

I would recommend one for starters. Phil Koopman's "Better Embedded
Software Systems", along with following his blog associated with the book.

There are others, but this one gets you asking a few of the most important
questions and should be on every software engineers work desk.

The biggest grip I have with software by others is the lack of adequate levels
of documentation in the source code.

I know Chris often puts out a contest at with shows and exhibitions with a prize
for seeing what is wrong with a piece of C code, but that is put out without one
iota of document or comment about its intended function. To those who know C
(I don't) it speaks nothing to me, but I did enter and wrote my answer to that test
that 'due to the lack of documentation it was an immediate fail. Without reference
to intended function there was no way of a person knowing what the coders
intentions were.' Of course tools he sells have no such qualms about that and
can check the logic structure of the code without a problem.

Sadly, I am not sure our academia is teaching the importance of including a worth
while amount of documentation in their source code, even if it is just a reference
a separate document that does a credibly descriptive job.

Regards

Paul E. Bennett IEng MIET
Systems Engineer
Lunar Mission One Ambassador
-- 
********************************************************************
Paul E. Bennett IEng MIET.....
Forth based HIDECS Consultancy.............
Mob: +44 (0)7811-639972
Tel: Due to relocation - new number TBA. Please use Mobile.
Going Forth Safely ..... EBA. www.electric-boat-association.org.uk..
********************************************************************