Review: Just Enough Systems Engineering

Summary: This relatively short, free eBook explains in an entertaining way what system development actually is. Using everyday examples such as a pantry or watering can, it explains what architecture is, what design is, why traceability is important and how to test. And most importantly, how to deal with people.

Update 2025: Even 15 years later, I still think this book is a great primer that every systems engineer should have read.

Target group: A must-read for people who want to know what systems engineering is.

Rating: ★★★★☆ Excellent book, but only deals with industrial systems engineering to a limited extent.

Download: Just Enough Systems Engineering by Dwayne Phillips (2010)

Details: The book begins by clarifying what a systems engineer actually is (read here). This is vividly explained using the example of a "wise potato farmer".

Also worth reading: What is Architecture? from Tom Westbury

After laying the foundation for the reader's understanding, some systems engineering concepts are explained in detail and enriched with examples, building on each other: requirements, architecture, interfaces and traceability. The examples are taken from everyday life and are therefore understandable for everyone.

Chapter 7 deals with social skills, which are also very important for a systems engineer. After all, we build systems for people, not as an end in itself. The topics covered include questioning, thinking in general and systems thinking.

[after a long series of repetitive questions]
Systems Engineer: And why is it a problem for you if your houseplants wither?
Customer: A long pause, a desperate look on his face, no answer.
The systems engineer recognizes this as a sign to stop here.

The book is also enriched with nice, professionally drawn cartoons (as can be seen in the picture), which lightens up the text.