Using Version Control System to Construct Ownership Architecture Documentations

Conference paper
Part of the Lecture Notes in Electrical Engineering book series (LNEE, volume 156)

Abstract

Ownership architecture was usually constructed by investigating the comments at the top of source files. That is, to associate developer names with source files is to examine the comments manually. If such documentation can be produced automatically, it will be more immediate to indicate the status of the project. This research focus on the logs in the version control system. The data within version control logs is in a regular form and information can be retrieved quickly. The importance of developers can also be estimated by the number of own files and frequency of making a change. In order to understand the system architecture, the directory structure of source code can be used to identify function components of the system essentially. The source files in a directory implement the same function component, and the owners of these source files can be considered a team. Using the documents, researcher can know the ownership architecture and more information about the status of the project.

Keywords

Source Code Software Architecture Software Project Directory Structure Open Source Project 
These keywords were added by machine and not by the authors. This process is experimental and the keywords may be updated as the learning algorithm improves.

Preview

Unable to display preview. Download preview PDF.

Unable to display preview. Download preview PDF.

References

  1. 1.
    Bowman, I.T., Holt, R.C.: Reconstructing ownership architectures to help understand software systems. In: International Conference on Program Comprehension, p. 28 (1999)Google Scholar
  2. 2.
    Ganesan, D., Muthig, D., Knodel, J., Yoshimura, K.: Discovering organizational aspects from the source code history log during the product line planning phase–a case study. In: Proceedings of the 13th Working Conference on Reverse Engineering, pp. 211–220. IEEE Computer Society, Washington, DC, USA (2006)Google Scholar
  3. 3.
    Girba, T., Kuhn, A., Seeberger, M., Ducasse, S.: How developers drive software evolution. In: Proceedings of the Eighth International Workshop on Principles of Software Evolution, pp. 113–122. IEEE Computer Society, Washington, DC, USA (2005)Google Scholar
  4. 4.
    Hassan, A.E., Holt, R.C.: Using development history sticky notes to understand software architecture. In: Proceedings of the 12th IEEE International Workshop on Program Comprehension, pp. 183–193. IEEE Computer Society, Washington, DC, USA (2004)Google Scholar
  5. 5.
    Luis, G.B., Robles, G.: Applying Social Network Analysis to the Information in CVS Repositories. In: Proceedings of the Mining Software Repositories Workshop. 26th International Conference on Software Engineering (2004)Google Scholar
  6. 6.
    Mockus, A., Herbsleb, J.D.: Expertise browser: a quantitative approach to identifying expertise. In: Proceedings of the 24th International Conference on Software Engineering, ICSE 2002, pp. 503–512. ACM, New York (2002)Google Scholar
  7. 7.
  8. 8.
  9. 9.

Copyright information

© Springer-Verlag GmbH Berlin Heidelberg 2013

Authors and Affiliations

  1. 1.Graduate Institute of Information EducationNational Kaohsiung Normal UniversityKaohsiungTaiwan
  2. 2.Department of Software EngineeringNational Kaohsiung Normal UniversityKaohsiungTaiwan

Personalised recommendations