Visualizing Object-oriented Software for Understanding and Documentation
Furkejuvvon:
| Publikašuvnnas: | arXiv.org (Jan 28, 2016), p. n/a |
|---|---|
| Váldodahkki: | |
| Almmustuhtton: |
Cornell University Library, arXiv.org
|
| Fáttát: | |
| Liŋkkat: | Citation/Abstract Full text outside of ProQuest |
| Fáddágilkorat: |
Eai fáddágilkorat, Lasit vuosttaš fáddágilkora!
|
MARC
| LEADER | 00000nab a2200000uu 4500 | ||
|---|---|---|---|
| 001 | 2078151479 | ||
| 003 | UK-CbPIL | ||
| 022 | |a 2331-8422 | ||
| 035 | |a 2078151479 | ||
| 045 | 0 | |b d20160128 | |
| 100 | 1 | |a AL-msie'deen, Ra'Fat | |
| 245 | 1 | |a Visualizing Object-oriented Software for Understanding and Documentation | |
| 260 | |b Cornell University Library, arXiv.org |c Jan 28, 2016 | ||
| 513 | |a Working Paper | ||
| 520 | 3 | |a Understanding or comprehending source code is one of the core activities of software engineering. Understanding object-oriented source code is essential and required when a programmer maintains, migrates, reuses, documents or enhances source code. The source code that is not comprehended cannot be changed. The comprehension of object-oriented source code is a difficult problem solving process. In order to document object-oriented software system there are needs to understand its source code. To do so, it is necessary to mine source code dependencies in addition to quantitative information in source code such as the number of classes. This paper proposes an automatic approach, which aims to document object-oriented software by visualizing its source code. The design of the object-oriented source code and its main characteristics are represented in the visualization. Package content, class information, relationships between classes, dependencies between methods and software metrics is displayed. The extracted views are very helpful to understand and document the object-oriented software. The novelty of this approach is the exploiting of code dependencies and quantitative information in source code to document object-oriented software efficiently by means of a set of graphs. To validate the approach, it has been applied to several case studies. The results of this evaluation showed that most of the object-oriented software systems have been documented correctly. | |
| 653 | |a Object oriented programming | ||
| 653 | |a Code reuse | ||
| 653 | |a Source code | ||
| 653 | |a Software engineering | ||
| 653 | |a Problem solving | ||
| 773 | 0 | |t arXiv.org |g (Jan 28, 2016), p. n/a | |
| 786 | 0 | |d ProQuest |t Engineering Database | |
| 856 | 4 | 1 | |3 Citation/Abstract |u https://www.proquest.com/docview/2078151479/abstract/embedded/L8HZQI7Z43R0LA5T?source=fedsrch |
| 856 | 4 | 0 | |3 Full text outside of ProQuest |u http://arxiv.org/abs/1601.07742 |