Sukurtos klasių diagramų generavimo iš Java kalbos šaltinio tekstų programos dokumentacija: reikalavimų bei architektūros specifikacijos, testavimo dokumentacija ir vartotojo vadovas. / Created class diagram generation from Java source code program's documentation: requirements and artchitecture specifications, testing documentation and users manual.

Darbe tyrinėjami žiniomis grindžiamos IS inžinerijos principai bei veiklos metamodelio vieta IS kūrime, siekiant išplėsti veiklos metamodelio galimybės, sudarant sąlygas automatiškai generuoti UML 2.0 klasių diagramas IS projektavimo etapui. Darbo metu buvo nustatyta, jog pasirinktas metamodelis neturi tam tikrų elementų, kurie būtini klasių diagramos generavimui. Metamodelis buvo papildytas šiais elementais. Klasių diagramos generavimui buvo sukurtas algoritmas, kuris išbandytas su testiniais duomenimis. / The work covers Knowledge-Based IS engineering and an enterprise metamodel’s place in creation of IS. The main purpose is to traverse possibility of generating UML 2.0 class diagram’s based on enterprise model. To achieve this goal there should be made these tasks: • familiarize with enterprise metamodels and UML class diagram; • determine and add missing elements in EMM for generation of class diagram; • create class diagram generation algorithm and implement it; • create prototype of using generation algorithm in creation of IS; After analysis was found that EMM doesn’t have some elements that are crucial for generation of class diagrams. For this reason enterprise metamodel was appended by two new elements. Created generation algorithm was tested with some case study data to check theoretical assumptions about relationships between EMM and class diagram. This work proved that there is possible to generate class diagrams from EMM. Although some new elements should be added for it.

Abstract The program analysis tool, VizzAnalyzer, works good for visualizing the program structure as graphs, but currently it does not allow for a UML conform visualization, which allows a effective communication among software engineers. In this thesis we describe the extension of the VizzAnalyzer to allow the visualization of software systems as UML class diagrams. The Eclipse platform provides an open source platform for creating an extensible integrated development environment. We create a plug-in that can be seamlessly integrated in the Eclipse platform through the third party tools in Eclipse to visualize the graph in VizzAnalyzer as UML class diagrams. The third party tools that are used in this thesis are the Graphical Editing Framework (GEF) and Draw2D. They are mainly used to create the UML class diagram view. In order to get a clear view on the diagram in the limited screen size, it is necessary to provide an appropriate layout for the diagram and drag and zoom actions on its figures. We provide the necessary means and document altogether in this thesis. We implement our solution as Eclipse plug-in and demonstrate feasibility.

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.

The modern time is characterized by strong competition in almost every field of doing, customers expect better and better services, demands are growing permanently. Capability to satisfy customers´ expectations became one of the key success factors. In many cases is this capability of delivering additional value the only significant benefit which differ you from competition. Customers rely on impressions and image of the company more and more. This work does not deal with complex customer relationship management, but is aimed at improving the position of financial advisors/consultants in this area. The purpose of application, designed in this work, is to improve effectiveness and save time in every day’s life which is wasted for unnecessary searching and browsing records. This goal is connected with capability of application to deliver methods which make possible easy and effective client portfolio management.

This thesis brings an overview about scene rendering using the ray tracing method. It describes aspects used when creating the application which uses this method such as intersection computation, lighting and shading models etc. It also describes the basic algorithm used for rendering one frame. Each class of the object oriented design is described. There is also detail explanation what is the purpose of the each class in the model and what are the most important used methods. The work also contains demonstration application showing the usage of model in practice.

No description available.

Modeliais paremtos architektūros (MDA) technologijos panaudojimo tikslas – automatizuoti kuriamos programų sistemos kuriamų modelių transformavimą ir kodo generavimą. Norint atlikti sukurtų modelių korektišką transformavimą, reikia užtikrinti modelių pilnumą ir suderinamumą tarpusavyje. Šie modeliai aprašomi UML modeliavimo kalba. Magistriniame darbe nagrinėjama nuo platformos nepriklausančio modelio kūrimo stadija, modelio klasių ir būsenų mašinų suderimo galimybės ir būsenų mašinų korektiškumo ir išbaigtumo metodikos. Taip pat bus pateikiamas sprendimas atliktas MagicDraw aplinkoje įskiepio pagalba. / The main goal of Model Driven Architecture (MDA) is the automation of software development process. According this technology, we need to create platform independent model (PIM), after that transform it to platform specific model (PSM); from PSM model we can generate program code. To do that, we need to ensure static and dynamic completeness of PIM. All these models are described using UML modeling language. In this work correctness and completeness of PIM is achieved by analyzing compatibility of class diagrams and state machines, as well as correctness and completeness of state machines themselves. To solve this problem, algorithms were created and implemented in a plug-in for MagicDraw CASE tool.

Baigiamajame magistro darbe nagrinėjamas verslo taisyklių vaizdavimas informacinės sistemos lygmenyje. Pateikiamas bendras verslo taisyklių supratimas, jų svarba bei tipai. Nagrinėjama, kokie metodai naudojami verslo taisyklėms atvaizduoti informacinės sistemos lygmenyje. Aprašomi šių metodų privalumai ir trūkumai. Nustatoma, kad tinkamiausias verslo taisyklių atvaizdavimo metodas yra UML klasių diagrama naudojama kartu su OCL kalba. Nagrinėjamos problemos, su kuriomis susiduria naudotojas užrašydamas OCL išraiškas. Sukuriamas įrankis, išsprendžiantis šias problemas. Šis įrankis leidžia naudotojui generuoti keturias dažniausiai naudojamas OCL išraiškas. Baigiamojo darbo pabaigoje pateikiamos išvados. Darbas sudarytas iš tokių pagrindinių dalių: įvado, verslo taisyklių užrašymo IS lygmenyje analizės, OCL išraiškų užrašymo metodo patobulinimo, išvadų, literatūros sąrašo. Darbo apimtis – 75 puslapiai teksto be priedų, 40 paveikslėliai, 7 lentelės, 27 bibliografiniai šaltiniai. Atskirai pridedami darbo priedai. / In final master thesis representation of business rules at information system level is analyzed. General understanding about business rules, its importance and types is described. It is analyzed, which methods are used for business rules representation at information system level. Is described the advantages and disadvantages of this methods. It is identified that the best method of business rules representation is UML class diagram using with OCL language. Problems, which occurs when user is trying to write OCL expression, is analyzed. Tool, which let to avoid this problems, is created. This tool helps user to generate four most used OCL expressions. Conclusions are represented in the end of master thesis. Structure: introduction, analysis of business rules representation at information system level, improvement of OCL expression representation method, conclusions and references. Thesis consists of: 75 pages text without appendixes, 40 pictures, 7 tables, 27 bibliographical entries. Appendixes included.

The Unified Modelling Language (UML) and object-oriented analysis and design (OOAD) have become essential topics in both academia and industry. UML is the accepted standard modelling language for describing object-oriented (OO) systems for analysis and design, and many UML CASE tools have been built and are used in academia and industry. OO technology and UML is an ongoing area of research, and many applications have been developed using OO technology. However, observations on current software development practices in some computer companies have shown that many OO software developers are not adopting recognised OOAD techniques. Both information technology (IT) students at higher educational institutions and professionals have in general found difficulty in grasping OO concepts, and the role that UML diagrams play in the design of the analysis and design solution. They particularly find difficulty in performing abstractions of real-world problems within the context of OOAD. They are unable to effectively build class diagrams from the problem domain because they essentially do not know ‘what’ to model. They therefore prefer to start coding software applications before building the analysis and design artifacts. Most of these students invariably prefer to focus on the implementation phase of a software development lifecycle and consider the preceding analysis and design phases superfluous. The overall goal of this thesis is to contribute to a significant improvement in the way students and software developers analyse and design their OO systems. We present a new approach by introducing concept mapping as a tool to help novices in OOAD produce more appropriate UML class and sequence diagrams. The class and sequence diagrams are selected because they represent the essential static and behavioural aspects of a problem domain. The former is fundamental to the OO modelling process and the latter is one of the most widely used dynamic diagrams in UML. Concept mapping is a popular tool used in education for facilitating learning, comprehension and the development of knowledge. Within the context of OOAD, we propose to use concept maps as a graphical representation of fundamental concepts, and their relationships and responsibilities within a problem domain. A static concept map derived from expanded use cases (use case narratives) can subsequently evolve into a class diagram containing information on classes, attributes, associations and generalisation-specialisation hierarchies. A dynamic concept map derived from an expanded use case can evolve into a sequence diagram containing information on the interaction of objects (and their messages) to fulfil the responsibilities of a particular scenario of the use case. In this thesis, a study is initially conducted to investigate in detail the difficulties undergraduate students have when producing UML class and sequence diagrams. The results of the study reveal and confirm some of the fundamental problems that students have with OO modelling. In order to address these problems, a concept-driven approach is developed to help novices produce more appropriate UML class and sequence diagrams. The effectiveness of this approach is evaluated by three different experiments. The data from these experiments is analysed and there is sufficient statistical evidence to support the claim that the participants produce more appropriate class and sequence diagrams after being taught concept mapping techniques. As a result of this positive outcome, a set of guidelines is developed for teaching OO modelling with concept maps. These guidelines could be integrated into existing OOAD courses to help software engineering educators resolve some of the difficulties they face when teaching OOAD.