Share This Post

To put it bluntly, requirements text is typically pretty bland to read. You don’t get the colorful variety of writing in passive voice, because it can confuse the audience. But also, you have to pick your words very carefully. English is actually quite challenging, in that words have different meanings.

There is a concept called Garden Path Sentences that illustrates this well. And the essence of it demonstrates how people read sentences one word at a time. If something doesn’t make sense in your intuitive first reading, you have to back up and re-read it. The example they give is:

The horse raced past the barn fell.

Technically this is a correct sentence, but it takes two readings to have it make sense.

This certainly something we want to avoid in writing requirements, and so we write in active voice with simple obvious word choices. Bland yes…but also very practical!

More To Explore

Email in toolbar

Getting More out of Transactional Emails

Are you taking advantage of all of the opportunities to promote your brand? Emails are great way to interact with your customers, and both marketing and transactional emails can be

Visuals in Requirements Mapping

In Praise of Requirements Mapping

Learn how to tie software requirements together with visual models and other artifacts created during the analysis process.