When Requirements Collide


I could have calculated how much money to spend to buy just enough time, but not everyone wears a calculator watch.

I'm not big on conspiracy theories, and I'm not accusing anyone of devilish design here. But is it possible that designing the kiosk's user interface not to show the amount of parking time requested was a conscious decision? I'm going to watch out for this kind of disconnect the next time I drill down from business requirements into the detailed requirements that are intended to achieve the business objectives.

About the author

Karl E. Wiegers's picture Karl E. Wiegers

Karl Wiegers, Ph.D., is the Principal Consultant at Process Impact in Portland, Oregon, and the author of Software Requirements (Microsoft Press, 1999) and Creating a Software Engineering Culture (Dorset House, 1996). You can reach him at www.processimpact.com. You can find more than 35 of Karl's articles at www.processimpact.com/pubs.shtml

AgileConnection is one of the growing communities of the TechWell network.

Featuring fresh, insightful stories, TechWell.com is the place to go for what is happening in software development and delivery.  Join the conversation now!