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: Structure of a Research Project From:JIMCHEVAL -at- AOL -dot- COM Date:Sun, 7 Jun 1998 22:14:08 EDT
In a message dated 98-06-07 22:02:13 EDT, caradura -at- HOTMAIL -dot- COM writes:
<< The topic of my research is about implementing a surveillance
camera system on campus. Can somebody help me giving me a logic
structure that my project must follow. >>
Well, gosh, I doubt there's any set formula for such a thing (except maybe in
France: these, anti-these, synthese AKA thesis, antithesis, synthesis). But
my own approach would grosso modo be the following:
- The Problem (what the precipitating event was and why it's worthy of study)
- The history of the current proposal
- The existing response to this proposal
- The history of similar initiatives
- The larger issues involved (security, privacy, technological advances vs.
ethics)
- An analysis of all the preceding relative to each other
- A summary (more or less opinionated)
The whole liberally sprinkled with charts and graphs, and a few provocative
pics.
FYI Los Angeles just had a big to-do about using automatic surveillance to
catch people running red lights - the final outcome was that the number of
deaths due to this little indulgence outweighed the Big Brother quality of
cameras perched at stop signs.
