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: to be an Application or not to be From:"Nancy C Kendall" <Nancy -dot- C -dot- Kendall -at- aexp -dot- com> To:"Techwr-L%lists.raycomm.com" <Techwr-L -at- lists -dot- raycomm -dot- com> Date:17 May 2000 15:33:01 -0700
>> Have you had to describe an ODBC, SQL-Server, ActiveX-based web application
>> lately? What did you call it? A program? A software solution? Software? An
>> application? A web application? A group of joined web applications?
I had the same problem when I started my current job. We settled on using "the
XYZ system". Most of the applications are related, intertwined software. It is
sometimes difficult to determine where one leaves off and the next takes over.
Thus, it's considered a "system". The users are all "in house" so the
terminology is well understood. Also, it keeps the Legal-Eagles happy because
we are not using "XYZ" as a noun in the generic sense, as in, please make a
Xerox(R) of this.
