The Reverse Detective: Pragmatic Software Requirements & Analysis

Software failure is a CRIME! Here‘s how to prevent it.

The Reverse Detective is an easy–to–read, breakthrough book that shows you how to prevent software failure by using the same disciplined, step–by–step process used by professional detectives to solve crimes.

There‘s just one difference: You put the traditional Sherlock Holmes approach in reverse.

The result? Instead of solving the crime of software failure, you prevent it by precisely determining and modeling the right requirements before you begin writing code.

Getting software development right from the start ... when you put the Reverse Detective process to work, you‘ll minimize the chance of blown budgets, missed timelines, endless revision rounds, and other career–busting problems.

Now you know why this practical, enjoyable guide is destined to become a must–read for everyone with a major stake in software development, including: executives, business managers and process owners, and hands–on software engineers.

Tom Bullinger is President and founder of Isotope28, a company devoted to software architecture and development practices. Tom developed his first embedded system in 1984 and has since worked on projects spanning the embeded domain, the desktop, and enterprise information technology applications.

Throughout his career, his focus has been the practical application of process, architecture, and object technology. Tom is also an Adjunct Professor at Rochester Institute of Technology, teaching courses in Computer Science and Software Engineering.

Sandeep Mitra received his Bachelor‘s and Master‘s degrees in Computer Science from the Indian Institute of Technology, Bombay, in 1985 and 1987, and his PhD in Computer Science from SUNY Binghamton in 1995. He is currently an Associate Professor of Computer Science at SUNY Brockport and a Research Scientist at Isotope28.

Dr. Mitra has over thirteen years of academic and industrial experience in large–scale software development, object–oriented development, and distributed computing. He is a co–author of The Software Engineering Effectiveness Method (SEEM) and has been involved with the SEEM research effort for over six years.