Standar Dokumentasi Perangkat Lunak
-
Keywords:
documentation, documents, softwareAbstract
Every software development project produces various documents that support the design, implementation, and maintenance of a system. In medium-sized systems, the number of documents may fill several filing cabinets, while large-scale systems may require multiple storage rooms. Incomplete, inaccurate, or neglected documentation can lead to user errors and increase the risk of system failures, which may result in additional costs and operational disruptions. Therefore, project managers and software engineers must pay adequate attention to documentation management, including its planning, preparation, and maintenance, in addition to the software development process itself. This paper discusses the principles of developing effective software documentation and explains the main functions and benefits of different types of documents in supporting the development, usage, and maintenance of software systems efficiently.
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
