15.04.2018 Views

programming-for-dummies

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

286<br />

Writing Software Documentation<br />

Because most people don’t read user manuals,<br />

many companies are resorting to video tutorials<br />

that show movies of the program in action.<br />

That way users can see exactly how to use<br />

the program without having to search <strong>for</strong> that<br />

in<strong>for</strong>mation buried somewhere inside a thick<br />

manual.<br />

Un<strong>for</strong>tunately, video tutorials are limited. They<br />

take time to create, so they usually cover only<br />

the more common features of a program. If you<br />

need help with a specific command, you need<br />

Video tutorials<br />

to first find the video file that contains the<br />

answer and then you have to skim through the<br />

video until you find your answer.<br />

As a result, video tutorials act more as supplements<br />

to the user manual than as replacements.<br />

Video tutorials work best when they’re<br />

kept short and focused on common tasks that<br />

every user needs to know. After users get familiar<br />

with a program with the help of video tutorials,<br />

they’ll feel more confident using the help<br />

files and reading the user manual.<br />

Technical design<br />

Programmers use a technical design document to organize how to write the<br />

program. This means specifying how the program will work, what <strong>programming</strong><br />

language and compiler to use, how to divide the program into parts,<br />

and assigning teams of programmers to work on each part.<br />

Technical design documents usually start off being fairly complete and accurate,<br />

but trying to design a program is much different than actually writing<br />

that same program. There<strong>for</strong>e, the design of a program can change as programmers<br />

run into obstacles that they didn’t <strong>for</strong>esee ahead of time.<br />

When this happens, the programmers often focus on solving the problem<br />

and <strong>for</strong>get about updating the technical design documents, so the technical<br />

design documents eventually become inaccurate and obsolete.<br />

Programmers rarely want to update technical design documents because the<br />

program may likely change again later anyway.<br />

User manuals<br />

User manuals are meant to teach people how to use the program. Ideally, a<br />

program should be so intuitive that users don’t need a user manual. Because<br />

that rarely happens, most programs include a user manual that explains how<br />

to use every feature in a program.<br />

Documentation tools<br />

Un<strong>for</strong>tunately, most user manuals are notoriously inaccurate, confusing, and<br />

incomplete:

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!