<p>Syftet med detta arbete var att undersöka möjligheten att få ett väl fungerande interface mellan ©VizzAnalyzer [3] och Javadoc, och därmed kunna producera htmldokumentation av de analyserade klasserna. VizzAnalyzer analyserar javaprogram och producerar därvid ett abstrakt syntaxträd (AST) som representerar det analyserade programmet. Detta AST kan sedan kopplas till javadocs interna AST-modell för att representera de klasser som förekommer vid analysen. Resultatet av detta blir då en komplett dokumentation av de analyserade klasserna. Det finns även möjligheter att dynamiskt lägga in ytterligare information om dem som kommit fram vid analysen. Utöver interfacet till VizzAnalyzer gjordes också ett mer generellt interface som kan kopplas till vilket program som helst som kan producera en lämplig representation av ett analyserat program. Detta gäller då främst javakod, men i och med att klasser, metoder, fält mm. enbart är representerade som text innan de behandlas av javadocinterfacet, finns det också möjligheter att använda det för andra objektorienterade språk.</p> / <p>The purpose of this work was to examine the possibility to get a well functioning interface between ©VizzAnalyzer [3] and Javadoc, thereby be able to produce html documentation of the analysed classes. The VizzAnalyzer analyses java programs and so produces an abstract syntax tree (AST) that represents the analysed program. This AST can then be coupled to the internal AST model of javadoc to represent the classes that were part of the analysis. The result of this is a complete documentation of the analysed classes. There is also the possibility to add further information about them that may have been discovered during analysis. A more general interface was also made in addition to the interface for VizzAnalyzer. This interface can be coupled with any program that can produce a suitable representation of the analysed program. This is mostly pertinent to java code, but due to classes being represented only as text before they are processed by the interface, there is a possibility to use it for other object oriented languages.</p>

Syftet med detta arbete var att undersöka möjligheten att få ett väl fungerande interface mellan ©VizzAnalyzer [3] och Javadoc, och därmed kunna producera htmldokumentation av de analyserade klasserna. VizzAnalyzer analyserar javaprogram och producerar därvid ett abstrakt syntaxträd (AST) som representerar det analyserade programmet. Detta AST kan sedan kopplas till javadocs interna AST-modell för att representera de klasser som förekommer vid analysen. Resultatet av detta blir då en komplett dokumentation av de analyserade klasserna. Det finns även möjligheter att dynamiskt lägga in ytterligare information om dem som kommit fram vid analysen. Utöver interfacet till VizzAnalyzer gjordes också ett mer generellt interface som kan kopplas till vilket program som helst som kan producera en lämplig representation av ett analyserat program. Detta gäller då främst javakod, men i och med att klasser, metoder, fält mm. enbart är representerade som text innan de behandlas av javadocinterfacet, finns det också möjligheter att använda det för andra objektorienterade språk. / The purpose of this work was to examine the possibility to get a well functioning interface between ©VizzAnalyzer [3] and Javadoc, thereby be able to produce html documentation of the analysed classes. The VizzAnalyzer analyses java programs and so produces an abstract syntax tree (AST) that represents the analysed program. This AST can then be coupled to the internal AST model of javadoc to represent the classes that were part of the analysis. The result of this is a complete documentation of the analysed classes. There is also the possibility to add further information about them that may have been discovered during analysis. A more general interface was also made in addition to the interface for VizzAnalyzer. This interface can be coupled with any program that can produce a suitable representation of the analysed program. This is mostly pertinent to java code, but due to classes being represented only as text before they are processed by the interface, there is a possibility to use it for other object oriented languages.

<p>Nowadays, assessing software quality and making predictions about the software are not</p><p>possible. Software metrics are useful tools for assessing software quality and for making</p><p>predictions. But currently the interpretation of the measured values is based on personal</p><p>experience. In order to be able to assess software quality, quantitative data has to be</p><p>obtained.</p><p>VizzAnalyzer is a program for analyzing open source Java Projects. It can be used</p><p>for collecting quantitative data for defining thresholds that can support the interpretation</p><p>of the measurement values. It helps to assess software quality by calculating over 20</p><p>different software metrics. I define a process for obtaining, storing and maintaining</p><p>software projects. I have used the defined process to analyze 60-80 software projects</p><p>delivering a large database with quantitative data.</p>

<p>This thesis describes the new development of a command-line interface. The</p><p>background of this assignment is a concept, which was developed at the University of</p><p>Växjö, Sweden and is concerned with the quality analysis of software products.</p><p>Out of this research an application was created. This application gives a developer the</p><p>possibility to analyze the quality of his software products. This application is called</p><p>VizzAnalyzer™ and is distributed by the company Arisa AB. The VizzAnalyzer™ is</p><p>already available in various versions and the command-line interface enables the</p><p>possibility to analyze software in a server environment. The interface requires the</p><p>possibility to analyze and interpret any user input. The thesis concerned with various</p><p>concepts and ways of implementation.</p>

<p>The VizzAnalyzer Framework is a stand-alone tool for analyzing and visualizing the structures of large software systems. Today, it has its own limited Swing based GUI lacking a professional look & feel. Furthermore, the effort needed to extend the VizzAnalyzer with new features like automatic update, progress monitoring, help system, and integration of the Eclipse Java and C/C++ AST API is high.</p><p>In order to improve current limitations and ease the future maintenance effort we refactored the VizzAnalyzer to be a plug-in to the Eclipse platform. We removed the burden of GUI development from the authors of the VizzAnalyzer replacing the Swing GUI with a SWT based GUI, which utilizes the rich feature set provided by the Eclipse Platform. Furthermore, the we did not only provide existing features of the VizzAnalyzer as loading and binding graphs, a complex system to load dynamic plug-ins functionalities for analysis, retrieval and visualization. We implemented an update and help manager, allowed for an easy use of third party plug-ins, which are available for Eclipse, and provided product branding.</p><p>We propose that the newly created VizzAnalyzer 2.0 solved the aforementioned limitations and provides a good foundation for the future evolution of the VizzAnalyzer tool.</p><p>This master thesis documents our how the VizzAnalyzer 2.0 has been developed and implemented for the Eclipse platform, and how developers shall use the new VizzAnalyzer version.</p>

<p>One source of input data for software evolution research is data stored inside a software configuration management repository. The data includes different versions of a software system’s source code as well as version history metadata, such as check-in dates or log messages. Inherently, extracting this data manually is a time- and labor intensive task. The subsequent preprocessing step and the appropriate storage of the results, necessary to utilize the data for further analysis, is an additional effort for the researcher.</p><p>The goal of this thesis is to design and implement a front-end plug-in for an existing software comprehension tool, the VizzAnalyzer, providing the capability to extract and analyze multiple versions and evolutional information of software systems from SCM repositories and to store the results. Thereby, the implemented solution provides the infrastructure for software evolution research.</p>

<p>By the increasing needs of software industry, software systems became more complex constructions than ever before. As a result of increasing complexity in software systems, functional decomposition of these systems gains the status of the most important aspect in the software development process. Dividing problems to sub-problems and producing specific solutions for divided parts makes it easier to solve the main problem.</p><p>Component Based Software Engineering is a way of developing software systems that consists of logically or functionally decomposed components which integrated to each other by the help of well-defined interfaces. CBSE relies on architectural design of a software system.</p><p>Planning phase and implementation of a software project may differ time to time. Because of the complexity of software systems, solving specific problems may affect the architecture of the whole system.</p><p>In spite of sophisticated software engineering processes and CASE tools there is still a large gap between the planned and implemented architecture of software systems. Finding deviations from architecture in source code is a non-trivial task requiring tool support.</p><p>Since, matching operation of designed software architecture and implemented software architecture needs to check design documents against implementation code. This manual checking operation is nearly impossible for major software systems. Software Architecture Checker provides a great approach to check the architecture of any software system.</p><p>This bachelor thesis examines the approach behind the Software Architecture Checker.</p>

Nowadays, assessing software quality and making predictions about the software are not possible. Software metrics are useful tools for assessing software quality and for making predictions. But currently the interpretation of the measured values is based on personal experience. In order to be able to assess software quality, quantitative data has to be obtained. VizzAnalyzer is a program for analyzing open source Java Projects. It can be used for collecting quantitative data for defining thresholds that can support the interpretation of the measurement values. It helps to assess software quality by calculating over 20 different software metrics. I define a process for obtaining, storing and maintaining software projects. I have used the defined process to analyze 60-80 software projects delivering a large database with quantitative data.

The VizzAnalyzer Framework is a stand-alone tool for analyzing and visualizing the structures of large software systems. Today, it has its own limited Swing based GUI lacking a professional look &amp; feel. Furthermore, the effort needed to extend the VizzAnalyzer with new features like automatic update, progress monitoring, help system, and integration of the Eclipse Java and C/C++ AST API is high. In order to improve current limitations and ease the future maintenance effort we refactored the VizzAnalyzer to be a plug-in to the Eclipse platform. We removed the burden of GUI development from the authors of the VizzAnalyzer replacing the Swing GUI with a SWT based GUI, which utilizes the rich feature set provided by the Eclipse Platform. Furthermore, the we did not only provide existing features of the VizzAnalyzer as loading and binding graphs, a complex system to load dynamic plug-ins functionalities for analysis, retrieval and visualization. We implemented an update and help manager, allowed for an easy use of third party plug-ins, which are available for Eclipse, and provided product branding. We propose that the newly created VizzAnalyzer 2.0 solved the aforementioned limitations and provides a good foundation for the future evolution of the VizzAnalyzer tool. This master thesis documents our how the VizzAnalyzer 2.0 has been developed and implemented for the Eclipse platform, and how developers shall use the new VizzAnalyzer version.

By the increasing needs of software industry, software systems became more complex constructions than ever before. As a result of increasing complexity in software systems, functional decomposition of these systems gains the status of the most important aspect in the software development process. Dividing problems to sub-problems and producing specific solutions for divided parts makes it easier to solve the main problem. Component Based Software Engineering is a way of developing software systems that consists of logically or functionally decomposed components which integrated to each other by the help of well-defined interfaces. CBSE relies on architectural design of a software system. Planning phase and implementation of a software project may differ time to time. Because of the complexity of software systems, solving specific problems may affect the architecture of the whole system. In spite of sophisticated software engineering processes and CASE tools there is still a large gap between the planned and implemented architecture of software systems. Finding deviations from architecture in source code is a non-trivial task requiring tool support. Since, matching operation of designed software architecture and implemented software architecture needs to check design documents against implementation code. This manual checking operation is nearly impossible for major software systems. Software Architecture Checker provides a great approach to check the architecture of any software system. This bachelor thesis examines the approach behind the Software Architecture Checker.