Last updated on 2024-06-28 | Edit this page

References

  • Aghajani, E., Nagy, C., Vega-Márquez, O. L., Linares-Vásquez, M., Moreno, L., Bavota, G., & Lanza, M. (2019, May). Software documentation issues unveiled. In 2019 IEEE/ACM 41st International Conference on Software Engineering (ICSE) (pp. 1199-1210). IEEE.
  • Briand, L. C. (2003, March). Software documentation: how much is enough?. In Seventh European Conference onSoftware Maintenance and Reengineering, 2003. Proceedings. (pp. 13-15). IEEE.
  • Code Documentation Best Practices. (2022). https://swimm.io/blog/developer-documenting-done-right/
  • Documentation Best Practices. (2019). Google Style Guide. https://google.github.io/styleguide/docguide/best_practices.html
  • Filazzola, A., & Lortie, C. J. (2022). A call for clean code to effectively communicate science. Methods in Ecology and Evolution, 13(10), 2119-2128.
  • Forward, A. (2002). Software documentation: Building and maintaining artefacts of communication. University of Ottawa (Canada).
  • Kipyegen, N. J., & Korir, W. P. (2013). Importance of software documentation. International Journal of Computer Science Issues (IJCSI), 10(5), 223.
  • Martin, R. C. (2009). Clean code: a handbook of agile software craftsmanship. Pearson Education.
  • Sommerville, I. (2001). Software documentation. Software engineering, 2, 143-154.

Documentation Tools