Program documentation

a. describes the inputs, outputs, and processing logic for all program modules
b. includes data dictionary entries, data flow diagrams, screen layouts, and the systems request that initiated the program
c. consists of instructions and information for users who will interact with the system and includes user manuals, screens, programs, and online tutorials
d. creates links within the program that will take a user to the appropriate documentation

My favorite is "be concise."have you ever received an email and had to read a page full of information? by the time you finished reading it, you had to re-read it? i have even hit "reply" so that i could break it down into separate paragraphs and send it back to myself.what is concise? get to the point, fast. when opening an email like this, some will close it or print it to read later.i learned to use the subject line to prepare the reader for content. such as, "need on (blank), " "info only re: (blank)," "request input on (blank)," "read before (blank) meeting." these are just some.if you are asking for something, make that your first sentence. follow this by who, what, when, where, and how. use these, as necessary. example; (1) who (who needs it and or who does it), (2) what (specific description of what is needed), (3) when (specific, i need this by 8: 00 am monday or i need this by 10: 00 am today), (4) where (does it have to be printed and taken to someone, maybe the place of the meeting), (5) how (i need it scanned or faxed back to me at this email address, provide me with a hard copy).do not send yet. re-read it. did some spell check change a word? maybe let someone else read it for understanding. you want to avoid multiple emails asking for clarification. if important, put a read receipt on it. you will know it was opened, not necessarily read.end with a you.