RE: "Allow" vs. "Require"

Subject: RE: "Allow" vs. "Require"
From: "Dan Goldstein" <DGoldstein -at- riveraintech -dot- com>
To: <techwr-l -at- lists -dot- techwr-l -dot- com>
Date: Tue, 10 Apr 2012 14:52:57 -0400

You did misinterpret, but it's my fault. The trouble probably started
when I tried to get cute with the Yiddish. We're actually talking about
an optional field in a dialog box.

For example, let's say you have a Teddy Bear Ordering dialog box. The
Number of Bears field is mandatory. The Color of Bears field is
optional. Thus:

* The RCP shall require the user to specify the number of teddy bears.
* The RCP shall allow but not require the user to specify the color of
the teddy bear.

Why the longer versions? Why not just, "the Number of Bears field is
mandatory, the Color of Bears field is optional"? Because some of my
target audience prefers requirements that begin with, "The RCP shall..."
or "The RCP shall not..."

The only exception is when the requirement is conditional: "If the user
is rich and gullible, the RCP shall allow but not require the user to
specify the number of teddy bears."

I'm sure there are situations where "allow but not require" would not be
a satisfactory solution. For our situation, it's perfect.


-----Original Message-----
From: Tony Chung
Sent: Tuesday, April 10, 2012 2:39 PM
To: TECHWR-L
Subject: Re: "Allow" vs. "Require"

In both cases, enable refers to something that would otherwise be
disabled. It's not about features or settings that exist, which is what
Dan's RCP stuff does.

Unless I misinterpreted that "pekele schlepping" is a usually disabled
feature that is enabled on a certain screen.




This message contains confidential information intended only for the use of the addressee(s). If you are not the addressee, or the person responsible for delivering it to the addressee, you are hereby notified that reading, disseminating, distributing, copying, electronic storing or the taking of any action in reliance on the contents of this message is strictly prohibited. If you have received this message by mistake, please notify us, by replying to the sender, and delete the original message immediately thereafter. Thank you.


^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Create and publish documentation through multiple channels with Doc-To-Help. Choose your authoring formats and get any output you may need.

Try Doc-To-Help, now with MS SharePoint integration, free for 30-days.

http://bit.ly/doc-to-help

^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

You are currently subscribed to TECHWR-L as archive -at- web -dot- techwr-l -dot- com -dot-

To unsubscribe send a blank email to
techwr-l-leave -at- lists -dot- techwr-l -dot- com


Send administrative questions to admin -at- techwr-l -dot- com -dot- Visit
http://www.techwhirl.com/email-discussion-groups/ for more resources and info.

Looking for articles on Technical Communications? Head over to our online magazine at http://techwhirl.com

Looking for the archived Techwr-l email discussions? Search our public email archives @ http://techwr-l.com/archives


Follow-Ups:

References:
"Allow" vs. "Require": From: Dan Goldstein

Previous by Author: RE: OFF TOPIC - RE: "Allow" vs. "Require"
Next by Author: RE: "Allow" vs. "Require"
Previous by Thread: RE: "Allow" vs. "Require"
Next by Thread: Re: "Allow" vs. "Require"


What this post helpful? Share it with friends and colleagues:

Sponsored Ads


Sponsored Ads