Automatically Documenting Software Artifacts

Abstract

Software artifacts, such as database schema and unit test cases, constantly change during evolution and maintenance of software systems. Co-evolution of code and DB schemas in Database-Centric Applications (DCAs) often leads to two types of challenging scenarios for developers, where (i) changes to the DB schema need to be incorporated in the source code, and (ii) maintenance of a DCAs code requires understanding of how the features are implemented by relying on DB operations and corresponding schema constraints. On the other hand, the number of unit test cases often grows as new functionality is introduced into the system, and maintaining these unit tests is important to reduce the introduction of regression bugs due to outdated unit tests. Therefore, one critical artifact that developers need to be able to maintain during evolution and maintenance of software systems is up-to-date and complete documentation.

Os produtos de conhecimento dentro das organizações do setor de software: uma nova perspectiva sobre artefatos de software

“…Therefore, new requirements, functionalities or bugs may arise in the software development process (Li, 2016). In this way, a dynamic is created in which the organization creates and renews its knowledge, providing the basis for the innovation of its products and services (Nonaka &Hirotaka, 2008).…”