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.
At what point does software become an application?
Subject:At what point does software become an application? From:John Posada <jposada01 -at- YAHOO -dot- COM> Date:Tue, 29 Jun 1999 11:49:31 -0700
OK, kiddies...thinking caps on.
I have an application. We'll call it "Bill".
Before Bill can be run, it has to be installed. (duh)
I have a manager taking the following approach.
Before Bill is installed, it is "the Bill software"
After Bill is installed, it is just plain Bill.
In practice, it goes something like this (samples are
out of context):
During installation:
"Specify the directory where you would like to install
the Bill software. The default directory is C:\PROGRAM
FILES\BILL."
After Installation:
"Bill gives you the ability to name a location by a
descriptive term. You are limited to 50 characters."
What think yee? I almost agree with him, but then I
like whipped cream placed...well, never mind where I
like whipped cream, it's off topic. ;-)
===
John Posada
Western Union International
(w) jposada -at- westernunion -dot- com
(p) john -at- tdandw -dot- com
_________________________________________________________
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com
