The odor of raisins What would be the use, for instance, in giving the plan of the room that was really my room, in describing the little room at the end of the garret, in saying that from the window, across the indentations of the roofs, one could see the hill. I alone, in my memories of another century, can open the deep cupboard that still retains for me alone that unique odor, the odor of raisins drying on a wicker tray. The odor of raisins! It is an odor that is beyond description, one that it takes a lot of imagination to smell. But I've already said too much. If I said more, the reader, back in his own room, would not open that unique wardrobe, with its unique smell, which is the signature of intimacy. Gaston Bachelard, The Poetics of Space smellmemory
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