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.
At Intel, we also had a sign-off sheet up front, so that the engineers who
had to deliver what was in the ERD could formally endorse the plan. We also
had a change history log in the front, because the ERD is a living document
throughout the project. (At least, it should be. If it is not kept up to
date, the plan-of-record quickly reverts to some awful combination of what
the lead engineer intends and what the design engineers are actually doing;
one must never assume those two camps are synchronized.)
We had a competition section, where the engineering team states what they
think their envisioned product will be up against in the marketplace.
We had a risks section, where we stated what we thought the biggest risks to
the plan were, and what we intended to do about them.
There was also a scheduling section, with major milestones shown.
-BobC
-----Original Message-----
From: techwr-l-bounces+bob -dot- colwell=comcast -dot- net -at- lists -dot- techwr-l -dot- com
[mailto:techwr-l-bounces+bob -dot- colwell=comcast -dot- net -at- lists -dot- techwr-l -dot- com] On
Behalf Of Ankur Parekh
Sent: Wednesday, May 14, 2008 3:27 AM
To: techwr-l -at- lists -dot- techwr-l -dot- com
Subject: More light on Engineering Response Document
Hello writers,
Can anyone tell me more on the likely content of an Engineering Response
Document?
What i already know is that it has a feature matrix proposed in the PRD,
along with the response (+ve/-ve) of the engineering team and the reasons
thereof.
What else can it have? Can anyone who has worked on an ERD respond, or point
me to some references. Google didn't point to any good resources.
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
True single source, conditional content, PDF export, modular help.
Help & Manual is the most powerful authoring tool for technical
documentation. Boost your productivity! http://www.helpandmanual.com
---
You are currently subscribed to TECHWR-L as archive -at- web -dot- techwr-l -dot- com -dot-