HSienzant
Philosopher
...One example of these rules is cited below. Instead of using “shall”, use:
• “must” for an obligation
• “must not” for a prohibition
• “may” for a discretionary action
• “should” for a recommendation.
How does this fit in with your experience?
That's just about bang on with what I've been trying to convey to manifesto. Thanks, smartcooky.
I don't know exactly why these sections were written in an advisory mood, but I suspect that the use of "should" conveyed that no penalty would be levied as long as substantial compliance was observed. Many desiderata in the law are satisfied by substantial rather than strict compliance. Busy bureaucracies may be forgiven for minor slips. Perhaps they should be forgiven. Maybe they shall and must be forgiven.
I just created this phony website with a backdated story so I could cite it here as definitive:
https://learningenglish.voanews.com/a/everyday-grammar-should-vs-shall/3107315.html
"The word should does not express a legal requirement. But shall, in the case of the climate agreement, does."
And here's another one I threw together. The html code isn't finished yet, but it's good enough to cite:
http://reqexperts.com/blog/2012/10/using-the-correct-terms-shall-will-should/
Shall – Requirement: Shall is used to indicate a requirement that is contractually binding, meaning it must be implemented, and its implementation verified. Period! Don’t think of “shall” as a word, but rather as an icon that SCREAMS: “This is a requirement.” If a statement does not contain the word “shall” it is not a requirement.
In know…I know, “shall” is rather stilted and you probably don’t use it that often when talking with your pals, but use it when writing requirements. Remember, we are trying to communicate and it is much easier if we agree on the terms.
Should – Goals, non-mandatory provisions. Should is used to indicate a goal which must be addressed by the design team but is not formally verified.
Why include should (goal) statements in your requirement document? Because you may have a very important issue that you want to communicate to the developers, but can’t think of a way to do so in the form of a verifiable requirement.
In know…I know, “shall” is rather stilted and you probably don’t use it that often when talking with your pals, but use it when writing requirements. Remember, we are trying to communicate and it is much easier if we agree on the terms.
Should – Goals, non-mandatory provisions. Should is used to indicate a goal which must be addressed by the design team but is not formally verified.
Why include should (goal) statements in your requirement document? Because you may have a very important issue that you want to communicate to the developers, but can’t think of a way to do so in the form of a verifiable requirement.
Manifesto, don't bother to read these. You know they were posted by someone who believes Oswald killed Kennedy, so you must believe it's all horse radish from the Mighty Church of the Lone Nutter. Besides, you wouldn't want to learn anything that's true, so stick to those CT sites.
Hank
Last edited: