Welcome to class An Essay by Bill Tozier vaguery.com I differ from almost all your previous instructors in three ways: First, I acknowledge that this is true, whereas they have for the most part lied to you (and themselves) and declared you competent, even though they’ve had to re-train you from scratch in every damned class. Second, unlike them I intend to do something about it. And, third, in order to do something about it, I will let you—no, make you—cheat. teaching
A grossly obese set of requirements Who advocates in the requirements process for the product itself—its conceptual integrity, its efficiency, its economy, it’s robustness? Often, no one. As often, an architect or engineer who can offer only opinion based on taste and instinct, unbuttressed as yet by facts. For in a classical Waterfall Model product process, requirements are set before design is begun. The result, of course, is a grossly obese set of requirements, the union of many wish lists, assembled without constraints. Usually, the list is neither prioritized nor weighted. The social forces in the committee forbid the painful conflicts occasioned by even weighting, much less prioritizing. Frederick P. Brooks, Jr., The Design of Design Requirements proliferationA Plea for Lean Software features