What Goes Up Must Come Down

Writing requirements purely top-down or only bottom-up is risky to say the least. The devil's in the details, and those details are likely to be missed when working from a single direction. What if you could tackle your requirements from both directions by incorporating use cases and user centered design? Learn how balancing your approach to writing requirements can result in more detailed, pragmatic documentation.