Just Enough Requirements Management: Where Software Development Meets Marketing

Preface

When I first started studying requirements specifications and teaching classes on them in the late 1970’s, I recognized that writing good requirements is very difficult. I worked hard to remove and help others to remove every trace of ambiguity from each and every requirement. I was convinced back then that a polished, word-processed requirements document was the only right way to record requirements. As I gained more and more experience, though, I started to realize that ambiguity can never be entirely removed from a requirements document that is written in natural language. So, I started to explore alternate ways of documenting requirements.

By the mid 1980’s, my solution to the problem of ambiguity in requirements was to use more and ...