Abstract
Many IT organizations are faced with the ongoing issue of good product documentation. Documentation has been classically defined as having two components: user documentation and technical documentation. User documentation consists of the necessary instructions required for users to operate and maintain the system. Technical documentation, on the other hand, contains detailed information about the inner components of the product itself. Technical documentation should be designed to provide developers with the ability to support and maintain the system from a programming and engineering perspective.
This is a preview of subscription content, log in via an institution to check access.
Access this chapter
Tax calculation will be finalised at checkout
Purchases are for personal use only
Author information
Authors and Affiliations
Corresponding author
Rights and permissions
Copyright information
© 2011 Springer-Verlag London Limited
About this chapter
Cite this chapter
Langer, A.M. (2011). Documentation and Acceptance Testing. In: Guide to Software Development. Springer, London. https://doi.org/10.1007/978-1-4471-2300-2_13
Download citation
DOI: https://doi.org/10.1007/978-1-4471-2300-2_13
Published:
Publisher Name: Springer, London
Print ISBN: 978-1-4471-2299-9
Online ISBN: 978-1-4471-2300-2
eBook Packages: Computer ScienceComputer Science (R0)