Two great software engineering books to note: The Art of Software Testing 2nd Edition by Glenford Myers (2004) revised and updated by Tom Badgett and Todd M. Thomas with Corey Sandler. This is a great software testing guide. The book concludes that incremental unit testing is better than non-incremental, to set up equivalence classes for determining test cases, it depends on the system as to whether top down or bottom up testing is chosen. The psychology of software testing is also addressed - looking at finding errors as successful rather than unsuccessful. Overall, this is a great read, easy to follow, with a lot of good information and useful information.
The second book is "Wicked Problems, Righteous Solutions, A Catalogue of Modern Software Engineering Paradigms" by Peter DeGrace and Leslie Hulet Stahl. Wicked problems are any that are complex and not easy to divide and conquer. Then coming up with solutions for these becomes a bit tricky, especially when trying to use "Righteous solutions" such as the waterfall model. Several models are considered (spiral, prototype, whirlpool, incremental, all at once(team, two man and one man), video model, cleanroom model and then finally the book wraps up with a critique of software engineering as a profession and a science. This is a must read for considering those wicked problems and forcing software professionals to take a step back and see what else besides a hammer can be used (if only know a hammer, everything looks like a nail).
The second book is "Wicked Problems, Righteous Solutions, A Catalogue of Modern Software Engineering Paradigms" by Peter DeGrace and Leslie Hulet Stahl. Wicked problems are any that are complex and not easy to divide and conquer. Then coming up with solutions for these becomes a bit tricky, especially when trying to use "Righteous solutions" such as the waterfall model. Several models are considered (spiral, prototype, whirlpool, incremental, all at once(team, two man and one man), video model, cleanroom model and then finally the book wraps up with a critique of software engineering as a profession and a science. This is a must read for considering those wicked problems and forcing software professionals to take a step back and see what else besides a hammer can be used (if only know a hammer, everything looks like a nail).