Definition
Documentation, in the context of computer programs, includes all written descriptions and instructions pertaining to computer software. It serves various purposes, such as providing support to users, aiding developers in maintaining and updating code, and ensuring that every aspect of the program is systematically and comprehensively covered. Documentation falls into several categories:
- Internal Documentation: Comments within the program code that help explain how the program functions, making it easier for developers to understand and maintain the software.
- On-line Documentation: Information displayed on-screen while the program runs or called up via commands like
HELP
, offering instant assistance to the user. - Reference Cards: Concise documents containing easily forgotten details and quick commands for fast reference.
- Reference Manuals: Comprehensive documents setting out detailed instructions for the program in a systematic way.
- Tutorials: Guides introducing new users to the software, often providing step-by-step instructions.
Examples
-
Internal Documentation Example:
1# This function calculates the factorial of a number 2def factorial(n): 3 if n == 0: 4 return 1 5 else: 6 return n * factorial(n-1)
-
On-line Documentation: Users can type
HELP
in the terminal to get immediate support and guidance on using specific commands or features. -
Reference Cards: A quick reference for a programming language might include basic syntax and commonly used functions.
-
Reference Manuals: A comprehensive user manual for an accounting software might explain every feature in detail, including screenshots and examples.
-
Tutorials: A beginner’s guide to a new software application, starting from installation and covering basic usage with visual aids.
Frequently Asked Questions (FAQs)
-
Why is documentation important in software development? Documentation is crucial as it provides a clear and comprehensive guide for users and developers, ensuring the software can be effectively used and maintained.
-
What is the difference between internal and on-line documentation? Internal documentation consists of comments within the code aimed at developers, while on-line documentation is meant for end-users and is often accessed through the software interface.
-
How often should documentation be updated? Documentation should be updated whenever changes or updates are made to the software to ensure it remains accurate and useful.
-
Can tutorials replace reference manuals? Tutorials and reference manuals serve different purposes; tutorials help new users get started, while reference manuals provide comprehensive, detailed information for all users.
-
What makes good documentation? Clear, concise, and comprehensive information that is well-organized and easily accessible helps make good documentation.
Related Terms
- API Documentation: Describes the functions, classes, return types, and arguments provided by an API.
- Technical Writing: The craft of documenting complex technical processes in an easy-to-understand manner.
- Version Control Systems: Tools like Git that help keep track of changes in the software and their documentation.
Online References
- W3Schools - Technical Writing Examples
- MDN Web Docs - Writing Documentation
- GitHub Guides - Mastering Markdown
Suggested Books for Further Study
- “The Elements of Style” by William Strunk Jr. and E.B. White
- “The Complete Idiot’s Guide to Technical Writing” by Krista Van Laan and Catherine Julian
- “Developing Quality Technical Information” by Gretchen Hargis and Michelle Carey
Fundamentals of Documentation: Computing Basics Quiz
Thank you for exploring the comprehensive documentation for computer programs and engaging with our informative quiz! Enhance your technical writing skills for improved software usability and maintenance.