Let’s look at the focus words we commonly use in our requirements documents. Requirements use many words to signal their focus and intent, such as ‘will’, ‘must’, ‘may’, ‘can’, ‘shall’, or ‘should’. There are some legal ramifications to certain focus words if they appear in a written contract. These concerns may govern what words can be used in what document regardless of what word the business analysts on the project team might prefer to use.
The IEEE looks at focus words in their standards style manual at http://standards.ieee.org/guides/style/section5.html. Here’s a quick summary of their recommendations:
I like the IEEE perspective on focus words, and use it on many of my more formal requirements development efforts.
Of course, there is another approach to the focus word dilemma –use a plain technical writing style. Plain style does not use any focus words! The subject is simply the ‘doer’ of the verb in a statement defining a capability. For example, “The user shall locate a course title within five seconds.” becomes “The user locates a course title within five seconds.” Pretty cool, eh? Of course, some folks just don’t think it is a requirement if there isn’t at least one ‘shall’ in there somewhere!