I have created many types of products using varied technologies and tools. Most recent are shown first.

  • Programming guides, how-to articles - Manual, developer guide, coding standards, API publishing procedure (DITA, oXygen, Sphinx, reStructuredText, Markdown, wiki, Word)
  • API specifications - System software APIs, REST API (OpenAPI [Swagger], DITA, Doxygen, Sphinx, reStructuredText, MATLAB, Doc-o-Matic, Word)
  • Data sheets - Neuromorphic platform hardware (Word)
  • Interface specifications - Neuromorphic platform, medical device, video systems, call center systems (Word, Visio, OmniGraffle)
  • Requirements and design specifications - For multiple communications products and medical device (Word, RequisitePro, DOORS, Visure, Visio)
  • Test plans and procedures - Medical robot, fast packet services, Fujitsu digital loop carrier (Word)
  • Use cases, user stories - Video systems, contact center system, car buying service CRM system (Word, Rational, PlantUML, Rally)
  • Protocols and schemas - Remote DVR, settings, billing system (XML, Stylus Studio)
  • Course portfolio - Research report, illustrated document, graphs, abstract, letter, press release, manuscript, feature article, brochure (InDesign, Word). PSA, Podcast, Multimedia presentation with audio, video, and scripts (Audacity, iMovie, PowerPoint, Acrobat, Prezi). Grifter email (Mailchimp).
  • Wikipedia pages - Artists and neighborhoods (Wikimedia)
  • Web site, personal - Career and science resources (HTML5, CSS, Dreamweaver, Coppermine)
  • Screen layouts - Controller server for video devices (JavaScript)
  • Presentations - Architecture, VoIP market, computer-telephony opportunities, project updates (PowerPoint)
  • RFI and RFP - Insurance company call center, car buying service CRM system (WordPro, Word)
  • Class diagrams, Sequence diagrams, Flowcharts (Visio, OmniGraffle, Rational, StarUML, PlantUML)
  • Functional specifications - Fast packet services (Word)
  • System design specifications (Word)
  • Network and infrastructure diagrams - Call center systems (Visio, Rational)
  • Spreadsheet solutions - Capacity calculations (Excel)
  • White papers - Protocol proposals, evaluation of 150 vendors (Word)
  • Case studies - Implementations for CRM (Word)
  • Quality procedures - ISO 13485 procedures and instructions, ISO 9001 development and manufacturing processes (Word)
  • Thesis - Research in medical electronics (word processor)

Although I have a rich and varied portfolio, I am unable to show much of my work portfolio because it is not my intellectual property. On this site, the samples from work are older and brief.


Front pages of guides and data sheets
I created the collection of guides and data sheets for users of the neuromorphic system. The guides helped users to install, configure, and operate the systems. I wrote most of the content in DITA (as 29,000 lines of XML code) and published the content externally as PDF and internally as HTML.
Programmer's guide thumbnail
I worked with a technical writer and subject matter experts to create this guide of 170 pages. We used illustrations, descriptions, and many code examples to illustrate how a developer would create code to work on our set-top box.


Work Procedure thumbnail
I wrote many procedures for the development processes under quality control, a popular thing in the early 90s. As Technical Operations Manager, I was responsible for processes in the research and development department.

Research report

Research report thumbnail
In this 60-page report, a precursor to the thesis, I described the initial medical and electronic research and showed preliminary results of the prototype in action.


Interface spec cover page thumbnail
I wrote this REST interface specification from scratch. It evolved from ideas to formal protocol specification over several months.
Business spec cover page thumbnail
I wrote how the human-related processes linked with the contact center technology. I used real example scenarios with mini-personas to bring the content to life.
Use case model cover page thumbnail
Working with a co-author, I followed a formal modeling practice to create descriptions of how the phone and email would be used by the contact center agents. This was the first time I wrote use case descriptions. It was great to formalize what I had been doing all along.
Test design spec cover page thumbnail
In this test design document I used several diagrams and tables to help the reader understand the many combinations and connections that seemed to be a big part of the testing. To show many-to-many associations, I used a ring with nodes on its edge, with lines showing the associations. I had seen this in a forensic package.
Request for proposal cover page thumbnail
This is the first RFP (Request for Proposal) that I wrote and it served the purpose well. Because it exposed a lot of new and detailed domain knowledge, I wrote the requirements very carefully so that they would be less likely to be misunderstood. Vendors outside of our company read the document.
Test procedure spec cover page thumbnail
I was particularly proud of this test procedure document. It was early days for PC-based word processors but I still produced a solid, useful, and readable document using advanced features of MS Word. I applied the table of contents and indexing features extensively to help the reader navigate and follow cross-references in what turned out to be a large document (150 pages).
Software requirements spec cover page thumbnail
Almost every other page of this spec had a diagram illustrating the concepts, such as the flow of calls or of information within the call center. I was following a standard template structure, but I was careful to keep the message clear. I also drew a big picture of the objects being used and how they related to one another.
Functional requirements spec cover page thumbnail
This is one of my favorite documents. As principal author, I re-used what I had written for the RFP (Request for Proposal) to create consistent, detailed requirements. To keep the requirements easy to use, I placed the text separate from the control numbers and wrote the key phrase in bold font. At the time, use cases were not well established as a discipline, but I created the equivalent in what I called scenarios, using what I now know as personas. The readers loved them.
System spec cover page thumbnail
As a co-author but as the main writer, I showed how the call center system components would hang together. I created several diagrams accompanied by formal descriptions.

Various products from course work

Report cover thumbnail
I wrote a feasibility report, a proposal, and then a final report (shown) on home energy saving for a fictitious client. Read more.
Web site redesign thumbnail
This document shows my redesign of a web site for an animal clinic. I created the site pages with InDesign. Read more.
Mobile site redesign wireframe thumbnail
I designed two pages for a gastronomy club site suitable for viewing on a mobile device. This was not part of the course but an extra. I created the site pages with InDesign. I was the sole author. Read more.
Mini portfolio of graphics thumbnail
This small portfolio shows the graphics-oriented products I created for a course: flyer, creative resume, article as a spread, logo, research report, and article with graphs. Read more.
Abstract of article thumbnail
I wrote this abstract for an article on a study of accuracy of oximeter readings. The original abstract was not shown to me. Read more.
Medical portfolio
This small portfolio for the Medical Communication course contains a scientific abstract, a press release, a feature article, and two patient information brochures. Read more.
First page of manuscript
I wrote this analytical synthesis manuscript that explores the ideas surrounding the philosophy of technology, the digital divide, and the big picture of media. The document conforms to APA format. Read more.