“Requirements Explosion”

In Response to InVivoVeritas, another commenter writes: Thanks for an interesting post. As you’re probably aware, there is a well-known phenomenon in software development called the “requirements explosion”. It’s documented, for example, in Robert Glass’s book, Facts and Fallacies of Software Engineering. Even after a specification is complete, and especially as concrete implementation of the specification gets underway (i.e. development of the actual software begins), a plethora of other requirements come out of the woodwork. Several things might account for this, including (1) the requirements were probably incomplete to begin with; (2) not all the implications of the requirements were thought through in advance; (3) the stakeholders don’t like what the “incarnation” of their specifications in functional software actually looks … Continue reading “Requirements Explosion”