Juan’s Reviews > Software Engineering: A Practitioner's Approach > Status Update

The book has examples of usage case scenarios (templates) and helps understand why the information is needed. In other words, the author gives an excellent example after explaining the need for this activity in the requirements elicitation phase. The material becomes so self-explanatory through it.

The second chapter (earlier) was a bit cumbersome as it introduced the reader to a symphony of unfamiliar terms.

Ch. Title "Principles that Guide Practice" goes over four universal elements (principles, concepts, methods, & tools), but it isn't the main focus. The principles that guide practice include being agile and adaptable, creating work products that deliver value to its users, manage change, assess risk, and "establish mechanisms for communication and coordination".

I had to re-read the principles to remember them

It's going over the psychology and human aspects of software engineering, and prior to this it talked about resource estimation, dishing out a prototype and creating a spiral in which increments are added. The authors note there's a risk in an architecturally-unsound prototype being used. The authors note the biggest challenges developers have with evolutionary process models are scope creep, which requires changes

I read most of my progress a while ago, but the authors did talk about process models and... I really have to review! The most memorable moment was the bathtub curve shown in the first chapter or two.