DOCSLIB.ORG

Download Full Volume

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text

Load more

2019 volume 13 issue 1 2019 volume 13 issue 1 Editors Zbigniew Huzar ([email protected]) Lech Madeyski ([email protected], http://madeyski.e-informatyka.pl) Department of Software Engineering, Faculty of Computer Science and Management, Wrocław University of Science and Technology, 50-370 Wrocław, Wybrzeże Wyspiańskiego 27, Poland e-Informatica Software Engineering Journal www.e-informatyka.pl, DOI: 10.5277/e-informatica Editorial Office Manager: Wojciech Thomas Typeset by Wojciech Myszka with the LATEX 2ε Documentation Preparation System All rights reserved. No part of this publication may be reproduced, stored in a retrieval system, transmitted in any form, or by any means, electronic, mechanical, photocopying, recording, or otherwise, without the prior written permission of the publishers. © Copyright by Oficyna Wydawnicza Politechniki Wrocławskiej, Wrocław 2019 OFICYNA WYDAWNICZA POLITECHNIKI WROCŁAWSKIEJ Wybrzeże Wyspiańskiego 27, 50-370 Wrocław www.oficyna.pwr.edu.pl; e-mail: [email protected]; [email protected] ISSN 1897-7979 Print and binding: beta-druk, www.betadruk.pl Editorial Board Co-Editors-in-Chief Zbigniew Huzar (Wrocław University of Science and Technology, Poland) Lech Madeyski (Wrocław University of Science and Technology, Poland) Editorial Board Members Pekka Abrahamsson (NTNU, Norway) Jerzy Nawrocki (Poznan University Apostolos Ampatzoglou (University of of Technology, Poland) Macedonia, Thessaloniki, Greece) Mirosław Ochodek (Poznan University Sami Beydeda (ZIVIT, Germany) of Technology, Poland) Miklós Biró (Software Competence Center Janis Osis (Riga Technical University, Latvia) Hagenberg, Austria) Mike Papadakis (Luxembourg University, Markus Borg (SICS Swedish ICT AB Lund, Luxembourg) Sweden) Kai Petersen (Hochschule Flensburg, University Pearl Brereton (Keele University, UK) of Applied Sciences, Germany) Mel Ó Cinnéide (UCD School of Computer Łukasz Radliński (West Pomeranian University Science & Informatics, Ireland) of Technology in Szczecin, Poland) Steve Counsell (Brunel University, UK) Guenther Ruhe (University of Calgary, Canada) Norman Fenton (Queen Mary University Krzysztof Sacha (Warsaw University of London, UK) of Technology, Poland) Joaquim Filipe (Polytechnic Institute Martin Shepperd (Brunel University London, of Setúbal/INSTICC, Portugal) UK) Thomas Flohr (University of Hannover, Rini van Solingen (Drenthe University, Germany) The Netherlands) Francesca Arcelli Fontana (University Miroslaw Staron (IT University of Göteborg, of Milano-Bicocca, Italy) Sweden) Félix García (University of Castilla-La Mancha, Tomasz Szmuc (AGH University of Science and Spain) Technology Kraków, Poland) Carlo Ghezzi (Politecnico di Milano, Italy) Iwan Tabakow (Wrocław University of Science Janusz Górski (Gdańsk University of Technology, and Technology, Poland) Poland) Guilherme Horta Travassos (Federal Tracy Hall (Lancaster University, UK) University of Rio de Janeiro, Brazil) Andreas Jedlitschka (Fraunhofer IESE, Adam Trendowicz (Fraunhofer IESE, Germany) Germany) Burak Turhan (University of Oulu, Finland) Barbara Kitchenham (Keele University, UK) Rainer Unland (University of Duisburg-Essen, Stanisław Kozielski (Silesian University Germany) of Technology, Poland) Sira Vegas (Polytechnic University of Madrit, Ludwik Kuźniarz (Blekinge Institute Spain) of Technology, Sweden) Corrado Aaron Visaggio (University of Sannio, Pericles Loucopoulos (The University Italy) of Manchester, UK) Bartosz Walter (Poznan University Kalle Lyytinen (Case Western Reserve of Technology, Poland) University, USA) Bogdan Wiszniewski (Gdańsk University Leszek A. Maciaszek (Wrocław University of Technology, Poland) of Economics, Poland Dietmar Winkler (Technische Universität Wien, and Macquarie University Sydney, Australia) Austria) Jan Magott (Wrocław University of Science and Marco Zanoni (University of Milano-Bicocca, Technology, Poland) Italy) Zygmunt Mazur (Wrocław University of Science Jaroslav Zendulka (Brno University and Technology, Poland) of Technology, The Czech Republic) Bertrand Meyer (ETH Zurich, Switzerland) Krzysztof Zieliński (AGH University of Science Matthias Müller (IDOS Software AG, Germany) and Technology Kraków, Poland) Jürgen Münch (University of Helsinki, Finland) Contents Usage, Retention and Abandonment of Agile Practices: A Survey and Interviews Results Indira Nurdiani, Jürgen Börstler, Samuel Fricker, Kai Petersen ............7 Do Software Firms Collaborate or Compete? A Model of Coopetition in Community-initiated OSS Projects Anh Nguyen-Duc, Daniela S. Cruzes, Snarby Terje, Pekka Abrahamsson ....... 37 Representation of UML Class Diagrams in OWL 2 on the Background of Domain Ontologies Małgorzata Sadowska, Zbigniew Huzar .......................... 63 A Three Dimensional Empirical Study of Logging Questions from Six Popular Q&A Websites Harshit Gujral, Abhinav Sharma, Sangeeta Lal, Lov Kumar .............. 105 Empirical Studies on Software Product Maintainability Prediction: A Systematic Mapping and Review Sara Elmidaoui, Laila Cheikhi, Ali Idri, Alain Abran .................. 141 Measuring Goal-Oriented Requirements Language Actor Stability Jameleddine Hassine, Mohammad Alshayeb ....................... 203 Software Change Prediction: A Systematic Review and Future Guidelines Ruchika Malhotra, Megha Khanna ............................ 227 e-Informatica Software Engineering Journal, Volume 13, Issue 1, 2019, pages: 7–35, DOI 10.5277/e-Inf190101 Usage, Retention, and Abandonment of Agile Practices: A Survey and Interviews Results Indira Nurdiani∗, Jürgen Börstler∗∗, Samuel Fricker∗∗∗, Kai Petersen∗∗∗∗ ∗Department of Software Engineering/DTU Compute – Software and Process Engineering Section, Blekinge Institute of Technology, Sweden/Technical University of Denmark, Denmark ∗∗Department of Software Engineering, Blekinge Institute of Technology, Sweden ∗∗∗Institute for Interactive Technologies, Fachhochschule Nordwestschweiz, Switzerland ∗∗∗∗Chair for Software Engineering, University of Applied Sciences Flensburg, Germany [email protected]/[email protected], [email protected], [email protected], [email protected] Abstract Background: A number of Agile maturity models (AMMs) have been proposed to guide software organizations in their adoption of Agile practices. Typically the AMMs suggest that higher maturity levels are reached by gradually adding more practices. However, recent research indicates that certain Agile practices, like test-driven development and continuous integration, are being abandoned. Little is known on the rationales for abandoning Agile practices. Aim: We aim to identify which Agile practices are abandoned in industry, as well as the reasons for abandoning them. Method: We conducted a web survey with 51 respondents and interviews with 11 industry practitioners with experience in Agile adoption to investigate why Agile practices are abandoned. Results: Of the 17 Agile practices that were included in the survey, all have been abandoned at some point. Nevertheless, respondents who retained all practices as well as those who abandoned one or more practices, perceived their overall adoption of Agile practices as successful. Conclusion: Going against the suggestions of the AMMs, i.e. abandoning Agile one or more practices, could still lead to successful outcomes. This finding indicates that introducing Agile practices gradually in a certain order, as the AMMs suggest, may not always be suitable in different contexts. Keywords: Agile practices, Agile maturity models, survey 1. Introduction being abandoned [3]. Abandoning Agile practices seems contradictory to common guidelines such The software industry is highly competitive. Ag- as Agile maturity models (AMMs) [4–6] that ile methods, like Scrum and eXtreme Program- prescribe which practices should be implemented ming (XP), help to tackle the challenges of rapid and when according to certain maturity levels. changes in the environment of software organi- According to the AMMs, the more mature an or- zations and help to reduce time to market, min- ganization becomes, the more Agile practices are imize development costs, and improve software adopted. However, the indication of abandonment quality [1]. Agile practices are the enactment of of practices could also be due to lack of guidance. Agile principles [2]. Perhaps such practices were not introduced at A recent survey indicates that some prac- the right time, given the maturity of the software tices like test-driven development (TDD), pair development teams or organization, because Agile programming, and continuous integration are practices dependencies are not well known. Submitted: 6 February 2018; Revised: 17 July 2018; Accepted: 17 July 2018; Available online: 30 September 2018 8 Indira Nurdiani et al. Table 1. Allocation of Agile practices to maturity levels in three AMMs Sidky et al. [6] Patel & Ramachandran [5] Nawrocki et al. [4] Context Agile practice adoption based Agile practice adoption based Adoption of XP based on on a measurement index on CMM(I) other maturity models Level 1 On-site customer, collabora- –– tive planning, coding standard Level 2 Tracking progress, continuous Tracking progress, on-site cus- Planning game, collaborating delivery tomer, planning game, TDD customer (on-site customer), user stories, metaphors Level 3 F2F meeting, continuous inte- Refactoring, pair program- Pair programming, coding gration, self-organizing team ming, continuous integration, standard, collective ownership, TDD, coding standard, collec-
Recommended publications
  • A Machine Learning Approach Towards Automatic Software Design Pattern Recognition Across Multiple Programming Languages

    A Machine Learning Approach Towards Automatic Software Design Pattern Recognition Across Multiple Programming Languages

    ICSEA 2020 : The Fifteenth International Conference on Software Engineering Advances A Machine Learning Approach Towards Automatic Software Design Pattern Recognition Across Multiple Programming Languages Roy Oberhauser[0000-0002-7606-8226] Computer Science Dept. Aalen University Aalen, Germany e-mail: [email protected] Abstract—As the amount of software source code increases, languages of programmers that affect naming, tribal manual approaches for documentation or detection of software community effects, the programmer's (lack of) knowledge of design patterns in source code become inefficient relative to the these patterns and use of (proper) naming and notation or value. Furthermore, typical automatic pattern detection tools markers, make it difficult to identify pattern usage by experts are limited to a single programming language. To address this, or tooling. While many code repositories are accessible to our Design Pattern Detection using Machine Learning the public on the web, many more repositories are hidden (DPDML) offers a generalized and programming language within companies or other organizations and are not agnostic approach for automated design pattern detection necessarily accessible for analysis. While determining actual based on Machine Learning (ML). The focus of our evaluation pattern usage is beneficial for identifying which patterns are was on ensuring DPDML can reasonably detect one design used where and can help avoid unintended pattern pattern in the structural, creational, and behavioral category for two popular programming languages (Java and C#). 60 degradation and associated technical debt and quality issues, unique Java and C# code projects were used to train the the investment necessary for manual pattern extraction, artificial neural network (ANN) and 15 projects were then recovery, and archeology is not economically viable.
  • Comparison of Static Analysis Tools for Quality Measurement of RPG Programs

    Comparison of Static Analysis Tools for Quality Measurement of RPG Programs

    View metadata, citation and similar papers at core.ac.uk brought to you by CORE provided by SZTE Publicatio Repozitórium - SZTE - Repository of Publications Comparison of Static Analysis Tools for Quality Measurement of RPG Programs Zolt´anT´oth1, L´aszl´oVid´acs2, and Rudolf Ferenc1 1 Department of Software Engineering, University of Szeged, Hungary [email protected], [email protected] 2 MTA-SZTE Research Group on Artificial Intelligence, Hungary [email protected] Abstract. The RPG programming language is a popular language em- ployed widely in IBM i mainframes nowadays. Legacy mainframe systems that evolved and survived the past decades usually data intensive and even business critical applications. Recent, state of the art quality assur- ance tools are mostly focused on popular languages like Java, C++ or Python. In this work we compare two source code based quality man- agement tools for the RPG language. The study is focused on the data obtained using static analysis, which is then aggregated to higher level quality attributes. SourceMeter is a command line tool-chain capable to measure various source attributes like metrics and coding rule viola- tions. SonarQube is a quality management platform with RPG language support. To facilitate the objective comparison, we used the SourceMe- ter for RPG plugin for SonarQube, which seamlessly integrates into the framework extending its capabilities. The evaluation is built on analysis success and depth, source code metrics, coding rules and code duplica- tions. We found that SourceMeter is more advanced in analysis depth, product metrics and finding duplications, while their performance of cod- ing rules and analysis success is rather balanced.
  • Incremental Static Analysis of Large Source Code Repositories

    Incremental Static Analysis of Large Source Code Repositories

    Budapest University of Technology and Economics Faculty of Electrical Engineering and Informatics Department of Measurement and Information Systems Incremental Static Analysis of Large Source Code Repositories Bachelor’s Thesis Author Advisors Dániel Stein Gábor Szárnyas, PhD Student Dr. István Ráth, Research Fellow 2014 Contents Kivonat i Abstract ii 1 Introduction 1 1.1 Context ..................................... 1 1.2 Problem Statement and Requirements .................... 2 1.3 Objectives and Contributions ......................... 2 1.4 Structure of the Thesis ............................. 3 2 Background and Related Work 4 2.1 Big Data and the NoSQL Movement ..................... 4 2.1.1 Sharding ................................ 5 2.1.2 High Availability ............................ 5 2.1.3 4store .................................. 6 2.1.4 Query Languages and Evaluation Strategies ............. 6 2.2 Modeling .................................... 7 2.2.1 Metamodels and Instance Models ................... 8 2.2.2 The Eclipse Modeling Framework .................. 8 2.2.3 JaMoPP ................................. 9 2.2.4 Graph Data Models ........................... 10 2.2.5 Model Queries over EMF and RDF .................. 13 2.3 Static Analysis in Practice ........................... 14 2.3.1 Checkstyle ............................... 14 2.3.2 FindBugs ................................ 15 2.3.3 PMD ................................... 15 2.4 Well-formedness Checking over Code Models ................ 16 3 Overview of the Approach 18
  • Bachelor Degree Project Do Software Code Smell Checkers Smell Themselves?

    Bachelor Degree Project Do Software Code Smell Checkers Smell Themselves?

    Bachelor Degree Project Do Software Code Smell Checkers Smell Themselves? A Self Reflection Author: Amelie Löwe Author: Stefanos Bampovits Supervisor: Francis Palma Semester: VT/HT 2020 Subject: Computer Science Abstract Code smells are defined as poor implementation and coding practices, and as a result decrease the overall quality of a source code. A number of code smell detection tools are available to automatically detect poor implementation choices, i.e., code smells. The detection of code smells is essential in order to improve the quality of the source code. This report aims to evaluate the accuracy and quality of seven different open-source code smell detection tools, with the purpose of establishing their level of trustworthiness. To assess the trustworthiness of a tool, we utilize a controlled experiment in which several versions of each tool are scrutinized using the most recent version of the same tool. In particular, we wanted to verify to what extent the code smell detection tools that reveal code smells in other systems, contain smells themselves. We further study the evolution of code smells in the tools in terms of number, types of code smells and code smell density. Keywords: Code smells, Automatic detection, Code smell density, Refactoring, Best practices. Preface We would like to thank our supervisor Francis Palma for the continuous support, helpful advice and valuable guidance throughout this bachelor thesis process. Furthermore, we would also like to acknowledge all of the cups of coffee we consumed in the past couple
  • Challenges of Sonarqube Plug-In Maintenance

    Challenges of Sonarqube Plug-In Maintenance

    Challenges of SonarQube Plug-In Maintenance Bence Barta, Günter Manz, István Siket Rudolf Ferenc University of Szeged, Department of Software Engineering FrontEndART Software Ltd. Árpád tér 2. H-6720 Szeged, Hungary Zászló u. 3 I./5. H-6722 Szeged, Hungary {bartab,magun,siket}@inf.u-szeged.hu [email protected] Abstract—The SONARQUBE™ platform is a widely used only 49% of the cases when the appropriate documentation open-source tool for continuous code quality management. It was missing. Brito et al. [1] asked developers to justify all provides an API to extend the platform with plug-ins to upload their API changes that break compatibility. They found that the additional data or to enrich its functionalities. The SourceMeter plug-in for SONARQUBE™ platform integrates the SourceMeter reason for most of the compatibility-breaking modifications static source code analyzer tool into the SONARQUBE™ plat- were generally inspired by the need to implement new features form, i.e., uploads the analysis results and extends the GUI to be and evolutionary purposes. In addition, the two other common able to present the new results. The first version of the plug-in reasons were that they wanted to simplify the API and improve was released in 2015 and was compatible with the corresponding maintenance. However, there were cases where we cannot say SONARQUBE™ version. However, the platform – and what is more important, its API – have evolved a lot since then, what the reason of the change was. Zhou and Walker [10] therefore the plug-in had to be adapted to the new API. It found that an API item is much more frequently removed was not just a slight adjustment, though, because we had to than marked as obsolete.
  • A Comparative Case Study on Tools for Internal Software Quality Measures

    A Comparative Case Study on Tools for Internal Software Quality Measures

    A Comparative Case Study on Tools for Internal Software Quality Measures Bachelor of Science Thesis in Software Engineering and Management MAYRA NILSSON Department of Computer Science and Engineering UNIVERSITY OF GOTHENBURG CHALMERS UNIVERSITY OF TECHNOLOGY Gothenburg, Sweden 2018 The Author grants to University of Gothenburg and Chalmers University of Technology the non-exclusive right to publish the Work electronically and in a non-commercial purpose make it accessible on the Internet. The Author warrants that he/she is the author to the Work, and warrants that the Work does not contain text, pictures or other material that violates copyright law. The Author shall, when transferring the rights of the Work to a third party (for example a publisher or a company), acknowledge the third party about this agreement. If the Author has signed a copyright agreement with a third party regarding the Work, the Author warrants hereby that he/she has obtained any necessary permission from this third party to let University of Gothenburg and Chalmers University of Technology store the Work electronically and make it accessible on the Internet. {A Comparative Case Study on Tools for Internal Software Quality Measures} {MAYRA G. NILSSON } © {MAYRA G. NILSSON}, June 2018. Supervisor: {LUCAS GREN}{VARD ANTINYAN} Examiner: {JENIFFER HORKOFF} University of Gothenburg Chalmers University of Technology Department of Computer Science and Engineering SE-412 96 Göteborg Sweden Telephone + 46 (0)31-772 1000 [Cover: Generated image based on keywords used in this
  • Sistema Qsource En La Calidad Del Software Desarrollado En RPG

    Sistema Qsource En La Calidad Del Software Desarrollado En RPG

    Sistema Qsource en la calidad del software desarrollado en RPG TESIS PARA OPTAR EL GRADO ACADÉMICO DE: Maestro en Gestión de Tecnologías de Información AUTOR: Br. Giovanni Barrero Ortiz ASESOR: Dr. Willian Sebastián Flores Sotelo SECCIÓN: Ingeniería LÍNEA DE INVESTIGACIÓN: Sistemas Basados en Gestión de Procesos de Negocio PERÚ – 2018 ii Página del Jurado Presidente Dr. Cesar Humberto Del Castillo Talledo Secretario Dr. Willian Sebastián Flores Sotelo Vocal iii Dedicatoria Este trabajo de investigación se lo dedico a mi madre Ligia Ortiz y a mi padre Rafael Barrero quienes siempre me han apoyado, a mi esposa Virna Lira y mis hijos Paolo Barrero y Camila Barrero quienes alegran mi vida y me dan apoyo constante para el cumplimiento de mis metas y objetivos y a mis hermanos. Giovanni Barrero Ortiz. iv Agradecimiento Agradezco a la universidad Cesar Vallejo por su aporte a mi vida profesional, También expreso mi sincero agradecimiento al Dr. Willian Sebastián Flores Sotelo, por el importante soporte en el desarrollo de la tesis. De manera especial y sincera a la institución donde laboro al Banco AGROBANCO, por darme la oportunidad de laborar en tan prestigiosa institución, pero a la vez por darme las facilidades para el desarrollo de mi tesis. A Dios y a mis familiares, compañeros de trabajo, amigos y a todas aquellas personas que de una u otra forma contribuyeron con el desarrollo de la tesis. Giovanni Barrero Ortiz. v Declaratoria de autenticidad Yo, Giovanni Barrero Ortiz, estudiante del Programa de Maestría en Gestión de Tecnologías de Información de la Escuela de Postgrado de la Universidad César Vallejo, identificado con DNI N° 48839223, respectivamente, con la tesis titulada Sistema QSOURCE en la calidad del software desarrollado en RPG, declaro bajo juramento que: 1) La tesis es de autoría propia.
  • Arxiv:1912.02179V3 [Cs.SE] 27 Aug 2020

    Arxiv:1912.02179V3 [Cs.SE] 27 Aug 2020

    Empirical Software Engineering manuscript No. (will be inserted by the editor) A Longitudinal Study of Static Analysis Warning Evolution and the Effects of PMD on Software Quality in Apache Open Source Projects Alexander Trautsch · Steffen Herbold · Jens Grabowski Received: date / Accepted: date Abstract Automated static analysis tools (ASATs) have become a major part of the software development workflow. Acting on the generated warnings, i.e., changing the code indicated in the warning, should be part of, at latest, the code review phase. Despite this being a best practice in software development, there is still a lack of empirical research regarding the usage of ASATs in the wild. In this work, we want to study ASAT warning trends in software via the example of PMD as an ASAT and its usage in open source projects. We analyzed the commit history of 54 projects (with 112,266 commits in total), taking into account 193 PMD rules and 61 PMD releases. We investigate trends of ASAT warnings over up to 17 years for the selected study subjects regarding changes of warning types, short and long term impact of ASAT use, and changes in warning severities. We found that large global changes in ASAT warnings are mostly due to coding style changes regarding braces and naming conventions. We also found that, surprisingly, the influence of the presence of PMD in the build process of the project on warning removal trends for the number of warnings per lines of code is small and not statistically significant. Regardless, if we consider defect density as a proxy for external quality, we see a positive effect if PMD is present in the build configuration of our study subjects.
  • Software Project Longevity – a Case Study on Open Source Software Development Projects

    Software Project Longevity – a Case Study on Open Source Software Development Projects

    Die approbierte Originalversion dieser Diplom-/ Masterarbeit ist in der Hauptbibliothek der Tech- nischen Universität Wien aufgestellt und zugänglich. http://www.ub.tuwien.ac.at The approved original version of this diploma or master thesis is available at the main library of the Vienna University of Technology. http://www.ub.tuwien.ac.at/eng Software Project Longevity – A Case Study on Open Source Software Development Projects MAGISTERARBEIT zur Erlangung des akademischen Grades Magister der Sozial- und Wirtschaftswissenschaften im Rahmen des Studiums Wirtschaftsinformatik eingereicht von Bernhard Kiselka Matrikelnummer 0125881 an der Fakultät für Informatik der Technischen Universität Wien Betreuung Betreuer: Ao.Univ.Prof. Dipl.-Ing. Mag. Mag.rer.soc.oec. Dr.techn. Stefan Biffl Mitwirkung: Projektass. Dipl.-Ing. Dietmar Winkler Wien, 30.11.2015 (Unterschrift Verfasser) (Unterschrift Betreuer) Technische Universität Wien A-1040 Wien ▪ Karlsplatz 13 ▪ Tel. +43-1-58801-0 ▪ www.tuwien.ac.at Bernhard Kiselka 0125881, 066 926 Master Thesis Software Project and Product Longevity A Case Study on Open Source Software Development Projects E-Mail: [email protected] Phone: 0664/33 23 269 Date: 2015-11-30 For Raphaël - Für Raphaël Software Project Longevity – A Case Study on Open Source Software Projects Contents Contents............................................................................................................................. i Erklärung zur Verfassung der Arbeit..................................................................................iii
  • Thesis Adrian Yankov

    Thesis Adrian Yankov

    Eindhoven University of Technology MASTER Re-engineering the re-engineering process Yankov, A.G. Award date: 2018 Link to publication Disclaimer This document contains a student thesis (bachelor's or master's), as authored by a student at Eindhoven University of Technology. Student theses are made available in the TU/e repository upon obtaining the required degree. The grade received is not published on the document as presented in the repository. The required complexity or quality of research of student theses may vary by program, and the required minimum study period may vary in duration. General rights Copyright and moral rights for the publications made accessible in the public portal are retained by the authors and/or other copyright owners and it is a condition of accessing publications that users recognise and abide by the legal requirements associated with these rights. • Users may download and print one copy of any publication from the public portal for the purpose of private study or research. • You may not further distribute the material or use it for any profit-making activity or commercial gain Department of Mathematics and Computer Science Model Driven Software Engineering Research Group Re-engineering the re-engineering process Master Thesis Adrian Yankov Supervisors: prof.dr. M.G.J. (Mark) van den Brand dr. Y. (Yaping) Luo ir. M. (Marc) Hamilton dr. N. (Natalia) Sidorova Eindhoven, Jan 2018 Abstract The number of legacy systems around the world that still function is high. Their maintenance has turned problematic, due to the original developers leaving or lack of proper documentation. Re-engineering can be one of the solutions to these problems.
  • D3.1 Software, Tools, and Repositories for The

    D3.1 Software, Tools, and Repositories for The

    D3.1 Software, tools, and repositories for code mining Modelling and Orchestrating heterogeneous Executive summary Resources and Polymorphic applications for This document provides a detailed description of the software and the Holistic Execution and adaptation of Models tools to be used for code mining. In the MORPHEMIC project, Code In the Cloud mining is needed to define application profiles, to be used for better adapting the available polymorphic deployment configuration to the H2020-ICT-2018-2020 requirements specific of the application. The applications’ Leadership in Enabling and Industrial deployment models provided by MORPHEMIC must be dynamic and Technologies: Information and adaptive, and capable of handling any expected or unexpected Communication Technologies situation. In this way MORPHEMIC assists, the application to supply a more or less constant level of service. The Polymorphic Adaptation Grant Agreement Number works at both the architecture and cloud service level, by defining the 871643 most optimal deployment model according to internal (e.g., available infrastructures) and external (e.g., load) constraints. This means that Duration the code mining functionality helps to define an application profile, 1 January 2020 – which, in turn, is used to obtain the best possible adaptation of the 31 December 2022 application deployment to the available infrastructures and component configurations/forms. The process of Code Mining in www.morphemic.cloud MORPHEMIC is composed by three tasks: web crawling, code analysis and data storage. The three aforementioned tasks define the Deliverable reference three components on which this deliverable is focused. In particular, D3.1 the web crawler has been identified among some candidates in order better support the extraction of sets of information associated with Date projects available on known source repositories (for example 31 December 2020 GitHub).