Software testing is a vital part of the software development process, usually implemented at the coding stage, and costly. Due to the increased use of the Unified Modeling Language (UML) and Model Driven Architecture (MDA) approach in systems analysis and design, Model-Based Testing has been discussed as a prominent solution for software testing to reduce the cost of software testing. Prior researches proposed an integrated method which utilizes the artifacts from the Platform Independent Model (PIM) to construct the test paths and generate the test cases. This study develops a methodology which extracting the information from PIM (e.g., Sequence Diagram and Class diagram) to generate the test cases directly. The research methodology is articulated using the design science research methodology. A usability evaluation is performed to demonstrate its applicability. With this methodology, the test cases can be easily generated; thereby reducing the cost and enhancing the efficiency of Model-Based Testing.

Software testing is a vital part of the software development process and is costly. Due to the increased use of the unified modeling language and model driven architecture approach in systems analysis and design, model-based testing has been discussed as a prominent solution for software testing to reduce the cost of software testing. Prior researches proposed an integrated method which utilizes the artifacts from the Platform Independent Model (PIM) to construct the test path and constrained class tuples. These two can then be integrated to construct an Integrated Testing Model (ITM) for determining the test data and test cases for Model-Based Testing. This study develops a methodology which extracting the information from ITM to construct the test cases. The research methodology is articulated using the design science research methodology. A prototype embedded methodology has been developed to automatically generate the test cases. A usability evaluation is performed on the prototype to demonstrate its usability. With this methodology, the test cases can be generated automatically; thereby reducing the cost and enhancing the efficiency of Model-Based Testing.

Objectives. In this thesis I have, together with game developer and publisher Paradox Interactive, designed and implemented a level editor tool for use in their game Magicka 2. With this tool users can create, edit and share custom Challenge levels in the game. I have also done a more in-depth scientific study of usability in such level editor tools, especially pertaining to the disparity between various controller input schemes and platforms. Methods. I have performed a literary study of articles and books relevant to the field of game design, user interface design, general usability, controller input schemes and any other topic I found relevant. I have paired this with a study of similar level editor tools and their user interfaces and features in other console and PC games. This knowledge, together with feedback from both expert and non-expert testing, has then been analyzed and used to design and implement both the user interface and the features of the level editor. Results. Results of the literary study, level editor tool study and testing are presented together with their impact on the design of the user interface and all implemented features. The results of each iteration of the Challenge Creator are presented as well. Lastly, all results are analyzed and a set of design heuristics for creating a similar level editor tool is presented. Conclusions. I conclude that creating a platform independent level editor tool with high usability is very much possible, but that designing such a tool becomes far more difficult with each new platform and controller input scheme supported. I also conclude that additional features and further increase in tool complexity loses significant impact if the core user interface is lacking in usability. I also conclude that more time and testing will be needed to further empirically validate the design heuristics. Lastly, I conclude that additional iterations will be required upon the Challenge Creator to improve its usability in light of already known and established design flaws.

As transformações de modelos são um ponto vital para os enfoques de desenvolvimento dirigido por modelos, incluindo a MDA. No presente trabalho apresenta-se alguns dos conceitos da MDA relacionados a transformações de modelos. São vistos os conceitos de PIM, PSM, transformações, mapeamentos e marcas. Estes conceitos são analisados no contexto de três ferramentas MDA, a OptimalJ, a AndroMDA e a ArcStyler, para verificar se as ferramentas os implementam de acordo com a MDA. Também é analisado como e quais transformações e mapeamentos de modelos estão sendo implementados pelas ferramentas, através da comparação qualitativa de definições de conceitos e de exemplos do uso destes. Além de verificar os conceitos relacionados às transformações, faz-se um estudo de caso qualitativo para analisar as transformações e mapeamentos providos pelas ferramentas e como as ferramentas trabalham com eles. Mostram-se as dificuldades de se criar um modelo PIM do sistema do estudo de caso e adaptá-lo para cada uma das ferramentas. / Model transformations are a vital point for model driven development, including MDA. In the present essay we introduce some of the MDA concepts related with model transformations. We present the concept of PIM, PSM, transformations, mappings and marks. These concepts are analyzed in the context of three MDA tools, OptimalJ, AndroMDA and ArcStyler, to verify if the tools implement the concepts according to MDA. We also analyze how and which model transformations and model mappings are being implemented by the tools, through a qualitative comparison of the definition of these concepts and using some examples of their intended use. In addition to verifying the concepts related to transformations, we create a qualitative case study to analyze the model transformations and model mappings provided by the tools, and how the tools work with them. We show a few of the problems faced when creating a PIM model of the case study\'s system and the adaptations it required for each tool.

As transformações de modelos são um ponto vital para os enfoques de desenvolvimento dirigido por modelos, incluindo a MDA. No presente trabalho apresenta-se alguns dos conceitos da MDA relacionados a transformações de modelos. São vistos os conceitos de PIM, PSM, transformações, mapeamentos e marcas. Estes conceitos são analisados no contexto de três ferramentas MDA, a OptimalJ, a AndroMDA e a ArcStyler, para verificar se as ferramentas os implementam de acordo com a MDA. Também é analisado como e quais transformações e mapeamentos de modelos estão sendo implementados pelas ferramentas, através da comparação qualitativa de definições de conceitos e de exemplos do uso destes. Além de verificar os conceitos relacionados às transformações, faz-se um estudo de caso qualitativo para analisar as transformações e mapeamentos providos pelas ferramentas e como as ferramentas trabalham com eles. Mostram-se as dificuldades de se criar um modelo PIM do sistema do estudo de caso e adaptá-lo para cada uma das ferramentas. / Model transformations are a vital point for model driven development, including MDA. In the present essay we introduce some of the MDA concepts related with model transformations. We present the concept of PIM, PSM, transformations, mappings and marks. These concepts are analyzed in the context of three MDA tools, OptimalJ, AndroMDA and ArcStyler, to verify if the tools implement the concepts according to MDA. We also analyze how and which model transformations and model mappings are being implemented by the tools, through a qualitative comparison of the definition of these concepts and using some examples of their intended use. In addition to verifying the concepts related to transformations, we create a qualitative case study to analyze the model transformations and model mappings provided by the tools, and how the tools work with them. We show a few of the problems faced when creating a PIM model of the case study\'s system and the adaptations it required for each tool.

The main goal of testing is to find errors in the System Under Test (SUT). Prior research indicated that Model-Based Testing is indeed good at finding SUT errors, can lead to less time and effort spent on testing if the time needed to write and maintain the model plus the time spent on directing the test generation is less than the cost of manually designing and maintaining a test suite. This study proposed a methodology for Model-Based Testing. In this approach, Sequence Diagrams and Class Diagram are used to determine the testing path and test case and Object Constraint Language is used to specify the business logic constraint. Three real-world cases and a CASE tool are used to test the usability (including the concepts, application, and advantages) of the proposed methodology. With this approach, SUT errors can be found at the systems analysis and design stage and thereby reduce the cost of software testing and enhance the efficiency of system development.

The main goal of model testing is to find system errors at the systems analysis and design stage and thereby reduce the cost of software testing and enhance the efficiency of system development. Prior researches proposed an Integrated Method which utilizes the artifacts from the Platform Independent Model (PIM) to construct the test path and constrained class tuples (CCT). These two can then be integrated to construct an Integrated Testing Model (ITM) for determining the test data and test cases for Model-Based Testing. This study develops a methodology which extracting the information from the Sequence Diagram and Class Diagram from the PIM to construct an ITM. The research methodology is articulated using the design science research methodology. A prototype embedded methodology has been developed. A usability evaluation is performed on the prototype to demonstrate its usability in terms of the factors, efficiency and effectiveness. With this methodology, the test paths, CCT and ITM can be generated automatically; thereby reducing the costs and increasing the efficiency of Model-Based Testing.

Šiomis dienomis labai greitai tobulėja mobilios technologijos. Į išmaniuosius įrenginius montuojamų procesorių taktinis dažnis jau pasiekė 1Ghz, ekranai tapo labai didelės raiškos, jautrūs lietimui bei pasižymintys labai kokybišku spalvų atkūrimu. Dėl daugybės į išmaniuosius telefonus montuojamų papildomų įtaisų, jų panaudojimo sritis vis plečiasi, jų populiarumas auga. Kartu su aparatūros tobulėjimu, tobulėja ir jiems skirta programinė įranga. Per paskutinius kelis metus pasirodė net trys naujos išmaniesiems telefonams skirtos operacinės sistemos. Visos šios naujovės ir greitas jų tobulėjimas labai apsunkina programuotojų darbą. Labai sunku suspėti su visomis naujomis technologijomis. Kiekviena atsiradusi platforma atsineša ir savo programavimo principus. Norint, kad sukurta programinė įranga pasiektų kuo didesnę vartotojų auditoriją, būtina ją pateikti kelioms skirtingoms ir dažnai nesuderinamoms platformoms. Tai pareikalauja didesnių laiko sąnaudų, daugiau žmogiškųjų resursų kas sąlygoja ir didesnius programinės įrangos kūrimo kaštus. Taip pat, labai trūksta profesionalių specialistų gerai išmanančių šias visai neseniai rinkoje pasirodžiusias technologijas. Tyrimo objektas – nuo platformos nepriklausomos programinės įrangos išmaniesiems telefonams kūrimo galimybės. Tyrimo tikslas – realizuoti ir ištirti nuo platformos nepriklausomą programinės įrangos karkasą, palengvinantį programinės įrangos išmaniesiems telefonams kūrimą. Tyrimo uždaviniai: 1. išanalizuoti nuo... [toliau žr. visą tekstą] / With the introduction and popularity of wireless devices, the diversity of the platforms has also been increased. There are different platforms and tools from different vendors such as Microsoft, Sun, Nokia, SonyEricsson and many more. Because of the relatively low-level programming interface, software development for wireless devices platforms, such as Symbian, is a tiresome and error prone task. This paper introduces the problem of the software development for incompatible mobile platforms, moreover, it provides a solution based on easy to use web technologies – JavaScript and XML. In the presented approach, the platform-independence lies in JavaScript interpretation and XML structures based user interface. The subject of research, object and subject relevance were detectable through literature analysis and through existing approaches are presented in the first part. The platform independent mobile application framework was implemented to demonstrate the proposed solution. System components design and programming process are presented in the second part. The implemented system static view is provided by using class diagrams and dynamic view - by sequences and activities diagrams. In the third part are provided assessment of the platform independent mobile software framework capabilities and quality. Program developed by using this framework was compared to program developed by using standard Symbian OS native means.

La especificación Model Driven Architecture (MDA), es una especialización del desarrollo dirigido por modelos que separa la lógica del negocio del software y las plataformas tecnológicas. Para ello MDA define tres tipos de modelos. Los CIM, Computation Independent Model, asociados al dominio del negocio, los PIM, Platform Independent Model, asociados a modelos abstractos del software, y los PSM, Platform Specific Model, relacionados con modelos de software específicos de plataformas tecnológicas. Sin embargo MDA no detalla cómo deben ser los modelos CIM y tampoco describe cómo deben ser transformados a modelos PIM. Como solución a dicho problema, esta tesis presenta una recomendación que propone un proceso de desarrollo de software basado en la creación de modelos de procesos del negocio, clasificados como CIM, que son asociados a los modelos iniciales del software, considerados PIM. Partiendo de una interpretación válida de MDA, la recomendación propuesta se apoya además en la aplicación de otras disciplinas de gran actualidad. Entre ellas destacamos el uso de desarrollo ágil de software, para la definición adecuada de los procesos del negocio.

With the rapid migration of physical layer design of radio towards software, it becomes necessary to select or develop the platform and tools that help in achieving rapid design and development along with flexibility and reconfigurability. The availability of field programmable gate arrays (FPGAs) has promoted the concept of reconfigurable hardware for software defined radio (SDR). It enables the designer to create high speed radios with flexibility, low latency and high throughput. Generally, the traditional method of designing FPGA based radios limits productivity. Productivity can be improved using Model based design (MBD) tools. These tools encourage a modular way of developing waveforms for radios. The tools based on MBD have been the focus of recent research exploring the concept of the platform independent model (PIM) and portability across platforms by the platform specific model (PSM). The thesis presented here explores the tools based on MBD to achieve prototyping for wireless standards like IEEE 802.11a and IEEE 802.16e on reconfigurable hardware. It also describes the interfacing of the universal software radio peripheral (USRP2), acting as a radio frequency (RF) front end, with an additional FPGA board for baseband processing. / Master of Science