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.
Ahh, some days the pain of the mainframe pays off, allow me :-)
Configuration Management
All the settings, preferences, options etc that need to be set for each
product. It's all well and good knowing you need the app loaded - but what
settings need to be set?!
System Administration
Daily/weekly/monthly/periodical procs and their supporting refs for keeping
the system running. Eg: For an accounts system, this might include regular
archiving of old records. As a rule of thumb, if it needs to be done more
than once, and its not actually providing a direct customer service, its an
admin proc.
Security Administration
Definitions of the accesses of the access groups, who belongs to them, procs
for changing etc
Also includes physical security
System Backup and Restore
What files get backed up how to where by whom and when. Should clearly state
the apps required for the backup and the restore. Can even include the procs
for doing it: kick machine a, load tape c into drive d, boot machine e.
Archive and Recovery
Archiving is done by the app, and its subsequent restore. You will need to
check whether they have a second def for this and the prev cat - its
possible they mean SYSTEM backup to be only OS components, and Archive is
done for all app data, on an app by app basis.
Application Help/Support
Contacts, troubleshooting guides, operating procs, user guides etc
Contingency Plan
What to do when a given resource is unavailable. Eg Power outage, water
outage, dunny outage :-) Id all critical resources that must be present for
the business processes to complete, and plan for a complete failure.
Documentation Control
Describe the system used to ensure changes to the dox are controlled. Naming
systems, style guides, design registers etc. Describe the areas where doco
is to be found, describe how it is designed, developed, tested and
"produced" (published).
System Monitoring
status/health checks, monitoring teams and software and their procs and
refs. Eg reference to network diags etc
Training
tutorials and exercises for any product. Can also include external and
internal courses. Should mention what training is mandatory to gain
experience on a given system.
Need more detail? Juz ask.
Steve Hudson
Lead Technical Writer
Wright Technologies (Aus)
steve -at- www -dot- wright -dot- com -dot- au
(612) 9518-1822
The best way to predict the future... is to create it!
*** Deva(tm) Tools for Dreamweaver and Deva(tm) Search ***
Build Contents, Indexes, and Search for Web Sites and Help Systems
Available now at http://www.devahelp.com or info -at- devahelp -dot- com
TECH*COMM 2001 Conference, July 15-18 in Washington, DC
The Help Technology Conference, August 21-24 in Boston, MA
Details and online registration at http://www.SolutionsEvents.com
---
You are currently subscribed to techwr-l as: archive -at- raycomm -dot- com
To unsubscribe send a blank email to leave-techwr-l-obscured -at- lists -dot- raycomm -dot- com
Send administrative questions to ejray -at- raycomm -dot- com -dot- Visit http://www.raycomm.com/techwhirl/ for more resources and info.
