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: Access to software versions: a rant From:Michelle Vina-Baltsas <Michelle_Vina-Baltsas -at- datascope -dot- com> To:"'TECHWR-L'" <techwr-l -at- lists -dot- techwr-l -dot- com>, techwr-l-bounces+michelle_vina-baltsas=datascope -dot- com -at- lists -dot- techwr-l -dot- com Date:Wed, 30 May 2007 09:23:25 -0400
I frequently have this argument but it is not with QA it is with SW
Engineering. When there is an update to our software, the UI/GUI document
is updated, which I can access immediately. I can generate a compare
document to the previous UI version and that helps a lot. Do you have UI
documents that are updated when the SW changes? If so, this might help.
"Gordon McLean" <Gordon -dot- McLean -at- GrahamTechnology -dot- com>
Sent by:
techwr-l-bounces+michelle_vina-baltsas=datascope -dot- com -at- lists -dot- techwr-l -dot- com
05/30/2007 05:20 AM
To
"'TECHWR-L'" <techwr-l -at- lists -dot- techwr-l -dot- com>
cc
Subject
RE: Access to software versions: a rant
How you USE software is only learnable if you have access to the software
itself.
You can read all the specs in the world but they will only ever give you
how
the person who wrote it thinks the software should be used.
The best argument I can come up with is this:
If you give me access to the software I can learn it and take less time
from
the developers when asking them "what if...". You need to cover 'non-happy
path' usage of the software in the docs and that only way you get to that
is
by having the software.
I'd be tempted to say that it wasn't something that was really up for
discussion at all, you either get access or you can't do your job. Do they
expect testing to test the software based on screenshots or specs?
Ohh you've got me all ranty too!!
HTH
Gordon
P.S. If I don't get access to builds of the software, then I won't provide
any documentation. I was lucky to establish that fact within the first two
weeks, with buy-in from the CTO (it helps that he is my boss mind you..)
-----Original Message-----
From:
techwr-l-bounces+gordon -dot- mclean=grahamtechnology -dot- com -at- lists -dot- techwr-l -dot- com
[mailto:techwr-l-bounces+gordon -dot- mclean=grahamtechnology -dot- com -at- lists -dot- techwr-l -dot- c
om] On Behalf Of Carrie Baker
Sent: 30 May 2007 10:14
To: TECHWR-L
Subject: Access to software versions: a rant
I am documenting software, a new version is compiled about every week and
goes into QA.
After lots of battles, I got authorization to access the drive the
software
version is on so I can run the applications and document them!
A few years ago, my authorization disappeared and I got it back again,
once
I talked to the head of R&D etc.
This week, I couldn't see that drive again.
It turned out that the relatively new head of QA had done some tidying up
and taken the Technical Writer's authorization for accessing new versions
of
the application away.
I sent an email cc'ed to all the world about this, then went to talk to
the
QA manager.
So she asked me: "But why do you need access to the software??????"
Well.....I need to document it, for example, once they forgot to tell me
that all the menus were changed, and I only knew by looking at the
software
that the menus had been changed.
I hate working with screen captures, I like to run the applications
(whenever possible) and see what happens when I click the buttons, as well
as making my own captures.
What other impressive reasons do you think a TW can have for wanting to
"run
the application"?
Do other writers documenting software generally have access to the
applications?
--
Carrie Baker
carriebak -at- gmail -dot- com
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Create HTML or Microsoft Word content and convert to Help file formats or
printed documentation. Features include support for Windows Vista & 2007
Microsoft Office, team authoring, plus more. http://www.DocToHelp.com/TechwrlList
Now shipping: Help & Manual 4 with RoboHelp(r) import! New editor,
full
Unicode support. Create help files, web-based help and PDF in up to 106
languages with Help & Manual: http://www.helpandmanual.com
---
You are currently subscribed to TECHWR-L as
Gordon -dot- McLean -at- grahamtechnology -dot- com -dot-
To subscribe, send a blank email to techwr-l-join -at- lists -dot- techwr-l -dot- com
Send administrative questions to admin -at- techwr-l -dot- com -dot- Visit http://www.techwr-l.com/ for more resources and info.
No virus found in this incoming message.
Checked by AVG Free Edition.
Version: 7.5.472 / Virus Database: 269.8.3/824 - Release Date: 29/05/2007
13:01
____________________________________________________________________________________________________
This email (and any attachments) is private and confidential, and is
intended solely for the
addressee. If you have received this communication in error please remove
it and inform us via
telephone or email. Although we take all possible steps to ensure mail and
attachments
are free from malicious content, malware and viruses, we cannot accept any
responsibility
whatsoever for any changes to content outwith our administrative bounds.
The views represented
within this mail are solely the view of the author and do not reflect the
views of the organisation
as a whole.
____________________________________________________________________________________________________
Graham Technology plc
Registered in Scotland company no. SC143434
Registered Office India of Inchinnan, Renfrewshire, Scotland PA4 9LH
Create HTML or Microsoft Word content and convert to Help file formats or
printed documentation. Features include support for Windows Vista & 2007
Microsoft Office, team authoring, plus more. http://www.DocToHelp.com/TechwrlList
Now shipping: Help & Manual 4 with RoboHelp(r) import! New editor,
full Unicode support. Create help files, web-based help and PDF in up
to 106 languages with Help & Manual: http://www.helpandmanual.com
---
You are currently subscribed to TECHWR-L as
michelle_vina-baltsas -at- datascope -dot- com -dot-
Create HTML or Microsoft Word content and convert to Help file formats or
printed documentation. Features include support for Windows Vista & 2007
Microsoft Office, team authoring, plus more. http://www.DocToHelp.com/TechwrlList
Now shipping: Help & Manual 4 with RoboHelp(r) import! New editor,
full Unicode support. Create help files, web-based help and PDF in up
to 106 languages with Help & Manual: http://www.helpandmanual.com
---
You are currently subscribed to TECHWR-L as archive -at- web -dot- techwr-l -dot- com -dot-
