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: Dlocumentation set for on-demand software From:Robert Lauriston <robert -at- lauriston -dot- com> To:techwr-l -at- lists -dot- techwr-l -dot- com Date:Thu, 15 Oct 2009 08:41:36 -0700
You aren't by any chance filling out a questionnaire from a
salesforce.com recruiter?
"On-demand software" aka "software as a service" (SaaS) = software
(usually Web-based) hosted by an application service provider (ASP),
such as Google Apps and Salesforce.com.
The documentation for a SaaS application is basically the same as for
any client-server application. The biggest difference is that the
installation guide may be for internal use only, though in my
experience it's often needed by partners, OEMs, and large or
particularly security-conscious customers who work out special
arrangements to host their own instances.
And of course there's a steep learning curve the first time you create
online help for the Web.
More generally, how much difference does it make to the user whether
an application runs in their operating system, a Java VM, or their Web
browser? If the answer is, not much, that's how much difference it
makes to the tech writer documenting the app.
On Wed, Oct 14, 2009 at 11:22 AM, <p -dot- vuncanon -at- att -dot- net> wrote:
> What would you consider the components of a enterprise documentation set to be for an on-demand software company vs. the traditional enterprise software company?
>
> Are there differences in the way you would approach writing for on-demand software as well?
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Free Software Documentation Project Web Cast: Covers developing Table of
Contents, Context IDs, and Index, as well as Doc-To-Help
2009 tips, tricks, and best practices. http://www.doctohelp.com/SuperPages/Webcasts/
Help & Manual 5: The complete help authoring tool for individual
authors and teams. Professional power, intuitive interface. Write
once, publish to 8 formats. Multi-user authoring and version control! http://www.helpandmanual.com/
---
You are currently subscribed to TECHWR-L as archive -at- web -dot- techwr-l -dot- com -dot-
