Indonesia Indonesia
Indonesia
Keywords:
IndonesiaAbstract
All software development projects, regardless of outcome, generate a number of related documents.For a mid-size system it might fill several filing cabinets, for a large system it might fill several rooms.
Errors and logging delays will lead to end-user errors and consequent system failure with associated costs and disruption.
Therefore, software managers and engineers must pay attention to documentation problems and the costs that arise because of them,
in addition to the development of the software itself.
This paper discusses the creation of good software documentation, as well as the description of the uses of these documents.
References
R. S. Pressman, Software Engineering: A Practitioner’s Approach. New York: Mc Graw-Hill Companies, Inc, 1997.
R. A.S and M. Shalahuddin, Modul Pembelajaran Rekayasa Perangkat Lunak (Terstruktur dan Berorientasi Objek). Bandung: Modula, 2011.
A. Forward, “Software Documentation – Building and Maintaining Artefacts of Communication,” University of Ottawa, 2002.
I. Sommerville, “Software Documentation,” 2011.
D. L. Parnas, “Precise Documentation : The Key To Better Software,” Joburg Centre for Software Engineering.
R. Shujaat, “Types of Software Documentation,” 2009. [Online]. Available: http://rafia-shujaat.suite101.com/types-of-softwaredocumentation-a107716. [Accessed: 23-Apr-2012].
I. Sommerville, Software Engineering, 06 ed. London: Pearson Education, 2000.
IEEE, IEEE Standard for Software User Documentation, IEEE-Std1063-2001. New York: Institute of Electrical and Electronics Engineers, 2001
