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 06:48:15 -0400

With all due respect to the ever-talented Tony Chung, "pekele" is Yiddish, not Gibberish!

To schlep a pekele is to drag along a package - often used metaphorically to mean your own personal bag of troubles. There's a nice description at
It's also morphed into a common word in the Israeli army.

As for the software requirements, in this case they have several possible target audiences: coders, testers, users (or their proxies), regulatory and quality staff, marketing, management, etc. For all of those, Fred's solution was immediately and obviously the best choice: "The RCP shall allow but not require the user to schlep the pekele."

-----Original Message-----
From: Keith Hood
Sent: Monday, April 09, 2012 9:13 PM
To: Dan Goldstein; techwr-l -at- lists -dot- techwr-l -dot- com
Subject: Re: "Allow" vs. "Require"

These are requirements you're working with. A requirement is just that - something that is required. It's something that the software must do. So the requirement should be written as an imperative - the software will or the software must.

For the purpose statement of the requirement, just put "The RCP will provide the user a mechanism for schlepping the pekele."

That says what functionality has to be built in but allows a lot of slop in deciding exactly how to implement it, just the way programmers want it.

When you write the specs for that requirement, there's where you can put in nitpicking about whether the pekele schlepping dialog box is modal, whether or not it has a cancel button, etc. 

What the frabjapping bleep is a pekele?

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.


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 for more resources and info.

Looking for articles on Technical Communications? Head over to our online magazine at

Looking for the archived Techwr-l email discussions? Search our public email archives @

"Allow" vs. "Require": From: Dan Goldstein
Re: "Allow" vs. "Require": From: Keith Hood

Previous by Author: RE: "Allow" vs. "Require"
Next by Author: RE: OFF TOPIC - 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