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:Thesis Topic From:Damien Braniff <Damien_Braniff -at- PAC -dot- CO -dot- UK> Date:Mon, 5 Jan 1998 11:35:50 +0000
I'm doing a distance 3 year MA in Tech Authorship (Certificate, Diploma,
MA) and about to start the MA year. This can either be a traditional
thesis on an approved TW topic (apparently publishing on Internet has been
very popular!) or it can be project based (recognising the fact that people
on the course may be sponsored by employers and prefer the work to be
relevant). We have a couple of upcoming projects which are possibles:
About to implement an Intranet and move docs to this for general access.
Tech docs, Staff handbook etc.
Our next generation of access control systems and associated admin
software - initial release later this year.
Both these, I feel, provide scope to be a project based "thesis" which
would cover the documentation, background research, reasons why done this
way etc. Basically covering the whole doc process from inception (?) to
implementation.
What I would like (possibly from those who have done something similar) are
some ideas for a more "theoretical" thesis subject. One which appeals to
me (due to background) is how Help/Online information has developed. Why
it's developed that way, where it's going etc.
Basically I'd like to have as wide a choice as possible before my meeting
later this month with the tutors when I find out exactly how it is
structured - what's allowed etc. It seems to be fairly flexible as long as
any suggestion is TW orientated or, if the connection is a little "loose",
it can be justified.