API Documentation

Including a technical writer in the development team allowed developers to focus on the software while still ensuring the API document was delivered on time.
Tools Used: MS Word, MS Visio, Adobe Acrobat
The client was a high-tech company that develops semiconductor devices for broadband networking applications. The device in this project contained embedded software. The software's procedural application programming interface (API) provided an extensive set of functions to allow application developers to interact with the underlying hardware.
The software developers were under significant deadline pressure to develop and test the software. The API document was an added burden that they really didn't have time for, and the project was at risk of slipping the delivery date.
Thanks to my engineering background, my knowledge of software and the programming language (C++) was sufficient to produce the API document independently, directly from the source code, without the need to continually interrupt the developers with questions.
The lead developer had this to say about the project:
He followed up this commendation by referring me to another organization that needed help creating a set of software user manuals.