Spelling suggestions: "subject:"common metamodel"" "subject:"common metalmodel""
1 |
UML 2.0 with VizzAnalyzerModesto, Francisco January 2007 (has links)
<p>Analyzing software contains two different tasks. First of all we are analyzing the software and try to calculate some metrics for software quality. Then those results have to be presented to the software engineers. VizzAnalyzer is a tool for analysis and visualization of software. It visualization allow not for a standardized diagram representation. Therefore it is difficult for others to understand, and we need to explain the meaning of our non-standard diagram elements. The solution is to use a standardized representation which can be understood by both sides. UML is such a collection of intuitively diagrams with standardized elements. Their meaning is clear to most software engineers.</p><p>We extended our analysis tool, the VizzAnalyzer, allowing it to view software systems as UML Class diagrams. We reused the existing plug-in architecture to connect our analysis tool with yEd, a graph visualization program. This plug-in is responsible for exchanging the data between the two applications.</p><p>We solve this conversion defining an UML Class Diagram Model and the mapping function between this model and the Common Meta-Model used by VizzAnalyzer and our Class Diagram Model. After that, we export this Class Diagram Model to a format suitable for yEd to display.</p><p>Now we can generate Class Diagrams with the VizzAnalyzer tool. This will allow a better communication of the results derived by different analysis with the software engineers.</p><p>This thesis describes the evolution of different alternatives and the design and implementation of our solution.</p>
|
2 |
Implementation of a Recoder Front-EndSong, Yuanjun January 2009 (has links)
<p>VizzAnalyzer is a program analysis tool that can be used for analyzing software programs. It relies on so called Front-Ends for information extraction from various sources like C or Java source code. It allows analyzing different source code by mapping the language specific front-end meta-model onto a common meta-model, on which analysis are defined. Right now we use the Eclipse Parser for parsing Java source code. This requires an Eclipse installation involving a large number of dependencies in order to work with Java source code. Yet, this is not always feasible; we want to be independent from Eclipse using an alternative parser.</p><p>Recoder is a Java meta-programming application program interface (API) that can be used to write Java programs that manipulate and analyze other Java programs. The Recoder framework provides over an application programming interface detailed access to the source code in form of an abstract syntax tree (AST). It has a small footprint and no external dependencies.</p><p>We create the Recoder Front-End as alternative to the existing Eclipse front-end. This includes the definition of a mapping between Recoder Front-End Meta-Model to Common Meta-Model. The mapping result will be used by VizzAnalyzer to do further analysis work. This Bachelor thesis documents relevant theory regarding Recoder Front-End and discusses its development and implementation.</p>
|
3 |
Development of a Java Bytecode Front-EndModesto, Francisco January 2009 (has links)
<p>The VizzAnalyzer is a powerful software analysis tool. It is able to extract information from various software representations like source code but also other specifications like UML. The extracted information is input to static analysis of these software projects. One programming language the VizzAnalyzer can extract information from is Java source code.</p><p>Analyzing the source code is sufficient for most of the analysis. But, sometimes it is necessary to analyze compiled classes either because the program is only available in byte-code, or the scope of analysis includes libraries that exist usually in binary form. Thus, being able to extract information from Java byte-code is paramount for the extension of some analyses, e.g., studying the dependecy structure of a project and the libraries it uses.</p><p>Currently, the VizzAnalyzer does not feature information extraction from Java byte-code. To allow, e.g., the analysis of the project dependency structure, we extend the VizzAnalyzer tool with a bytecode front-end that will allow the extraction of information from Java bytecode.</p><p>This thesis describes the design and implementation of the bytecode front-end. After we implemented and integrated the new front-end with the VizzAnalyzer, we are now able to perform new analyses that work on data extracted from both, source- and bytecode.</p>
|
4 |
UML 2.0 with VizzAnalyzerModesto, Francisco January 2007 (has links)
Analyzing software contains two different tasks. First of all we are analyzing the software and try to calculate some metrics for software quality. Then those results have to be presented to the software engineers. VizzAnalyzer is a tool for analysis and visualization of software. It visualization allow not for a standardized diagram representation. Therefore it is difficult for others to understand, and we need to explain the meaning of our non-standard diagram elements. The solution is to use a standardized representation which can be understood by both sides. UML is such a collection of intuitively diagrams with standardized elements. Their meaning is clear to most software engineers. We extended our analysis tool, the VizzAnalyzer, allowing it to view software systems as UML Class diagrams. We reused the existing plug-in architecture to connect our analysis tool with yEd, a graph visualization program. This plug-in is responsible for exchanging the data between the two applications. We solve this conversion defining an UML Class Diagram Model and the mapping function between this model and the Common Meta-Model used by VizzAnalyzer and our Class Diagram Model. After that, we export this Class Diagram Model to a format suitable for yEd to display. Now we can generate Class Diagrams with the VizzAnalyzer tool. This will allow a better communication of the results derived by different analysis with the software engineers. This thesis describes the evolution of different alternatives and the design and implementation of our solution.
|
5 |
Implementation of a Recoder Front-EndSong, Yuanjun January 2009 (has links)
VizzAnalyzer is a program analysis tool that can be used for analyzing software programs. It relies on so called Front-Ends for information extraction from various sources like C or Java source code. It allows analyzing different source code by mapping the language specific front-end meta-model onto a common meta-model, on which analysis are defined. Right now we use the Eclipse Parser for parsing Java source code. This requires an Eclipse installation involving a large number of dependencies in order to work with Java source code. Yet, this is not always feasible; we want to be independent from Eclipse using an alternative parser. Recoder is a Java meta-programming application program interface (API) that can be used to write Java programs that manipulate and analyze other Java programs. The Recoder framework provides over an application programming interface detailed access to the source code in form of an abstract syntax tree (AST). It has a small footprint and no external dependencies. We create the Recoder Front-End as alternative to the existing Eclipse front-end. This includes the definition of a mapping between Recoder Front-End Meta-Model to Common Meta-Model. The mapping result will be used by VizzAnalyzer to do further analysis work. This Bachelor thesis documents relevant theory regarding Recoder Front-End and discusses its development and implementation.
|
6 |
Development of a Java Bytecode Front-EndModesto, Francisco January 2009 (has links)
The VizzAnalyzer is a powerful software analysis tool. It is able to extract information from various software representations like source code but also other specifications like UML. The extracted information is input to static analysis of these software projects. One programming language the VizzAnalyzer can extract information from is Java source code. Analyzing the source code is sufficient for most of the analysis. But, sometimes it is necessary to analyze compiled classes either because the program is only available in byte-code, or the scope of analysis includes libraries that exist usually in binary form. Thus, being able to extract information from Java byte-code is paramount for the extension of some analyses, e.g., studying the dependecy structure of a project and the libraries it uses. Currently, the VizzAnalyzer does not feature information extraction from Java byte-code. To allow, e.g., the analysis of the project dependency structure, we extend the VizzAnalyzer tool with a bytecode front-end that will allow the extraction of information from Java bytecode. This thesis describes the design and implementation of the bytecode front-end. After we implemented and integrated the new front-end with the VizzAnalyzer, we are now able to perform new analyses that work on data extracted from both, source- and bytecode.
|
Page generated in 0.0447 seconds