TechWhirl (TECHWR-L) is a resource for technical writing and technical communications professionals of all experience levels and in all industries to share their experiences and acquire information.
For two decades, technical communicators have turned to TechWhirl to ask and answer questions about the always-changing world of technical communications, such as tools, skills, career paths, methodologies, and emerging industries. The TechWhirl Archives and magazine, created for, by and about technical writers, offer a wealth of knowledge to everyone with an interest in any aspect of technical communications.
Subject:Re: Use of "shall" From:"Jacobson, Avi (PBD)" <Avi -dot- Jacobson -at- PBDIR -dot- COM> Date:Mon, 2 Feb 1998 11:54:10 -0800
In article <3 -dot- 0 -dot- 32 -dot- 19980130172700 -dot- 006ad5c0 -at- mail -dot- celerity -dot- com>,
Dianna Massey <dmassey -at- celerity -dot- com> wrote:
>
> Matthew Bin wrote:
>
> >
> > Er, is shall archaic? I think it depends where you are. And I find
> > that it adds a certain amount of tone to others' writing that is not
> > easily achieved in the written medium. (I make no claim about my
own
> > writing, of course.) I'm not going to crusade to bring it into more
> > common usage, but it's worth knowing and using in my opinion.
>
> In a recent past life, I documented policies and procedures. The
> appropriate use of "shall" not only gave the policies the proper tone,
but
> also pleased the company's lawyers. If you are involved in
contractual or
> legal writing of any kind, the difference in meaning between "shall"
and
> "will" is important. Outside the legal profession, I find people
react
> negatively to the use of "shall." They tend to find it stuffy and
heavy
> handed.
Grady, J.O. (1993). _System Requirements Analysis_, New York: McGraw
Hill Inc. (cited on http://www.sie.arizona.edu/sysengr/requirements/, a
System Requirements Discovery resource page from the University of
Arizona), says the following:
"A mandatory requirement should be expressed using the word _shall_
(e.g., The system shall conform to all state laws.). A preference
requirement can be expressed using _should_ or _may_ (e.g., The total
cost for the car's accessories should be about 10% of the total cost of
the car.). The term will can be used to express a declaration of purpose
on the part of a contracting agency, to express simple future tense and
for statement of fact (e.g., The resistors will be supplied by an
outside manufacturer.)"
This seems to be an industry standard in the world of software
requirements analysis. I have recently delved into (read: "begun to
scratch the thick surface of") the world of OOSE (Object-Oriented
Software Engineering) and found that the use of _shall_ and _will_ is
very specialized and the differentiation between them is critical. I
won't elaborate, because I am not sure I understand all of the
ramifications yet. What is abundantly clear is that "shall" is not
merely an "antiquated" usage: it expresses a mandatory system
requirement, as opposed to a mere indication of something which is
expected to happen in the future.
--
Avi Jacobson, email: Avi -dot- Jacobson -at- pbdir -dot- com | When an idea is
or: AviJ -at- amdocs -dot- com | wanting, a word
| can always be found
Opinions are those of the poster, =NOT= of | to take its place.
Amdocs, Inc. or Pacific Bell Directory. | -- Goethe