Makedonski, Filip Dobrinov

[["dc.bibliographiccitation.artnumber","S0950584921002093"],["dc.bibliographiccitation.firstpage","106763"],["dc.bibliographiccitation.journal","Information and Software Technology"],["dc.bibliographiccitation.volume","143"],["dc.contributor.author","Makedonski, Philip"],["dc.contributor.author","Grabowski, Jens"],["dc.date.accessioned","2022-02-01T10:32:10Z"],["dc.date.available","2022-02-01T10:32:10Z"],["dc.date.issued","2022"],["dc.identifier.doi","10.1016/j.infsof.2021.106763"],["dc.identifier.pii","S0950584921002093"],["dc.identifier.uri","https://resolver.sub.uni-goettingen.de/purl?gro-2/99021"],["dc.language.iso","en"],["dc.notes.intern","DOI-Import GROB-517"],["dc.relation.issn","0950-5849"],["dc.rights.uri","https://www.elsevier.com/tdm/userlicense/1.0/"],["dc.title","Facilitating the co-evolution of semantic descriptions in standards and models"],["dc.type","journal_article"],["dc.type.internalPublication","yes"],["dspace.entity.type","Publication"]]

[["dc.bibliographiccitation.issue","6"],["dc.bibliographiccitation.journal","Empirical Software Engineering"],["dc.bibliographiccitation.volume","27"],["dc.contributor.author","Herbold, Steffen"],["dc.contributor.author","Trautsch, Alexander"],["dc.contributor.author","Ledel, Benjamin"],["dc.contributor.author","Aghamohammadi, Alireza"],["dc.contributor.author","Ghaleb, Taher A."],["dc.contributor.author","Chahal, Kuljit Kaur"],["dc.contributor.author","Bossenmaier, Tim"],["dc.contributor.author","Nagaria, Bhaveet"],["dc.contributor.author","Makedonski, Philip"],["dc.contributor.author","Ahmadabadi, Matin Nili"],["dc.contributor.author","Erbel, Johannes"],["dc.date.accessioned","2022-09-01T09:49:20Z"],["dc.date.available","2022-09-01T09:49:20Z"],["dc.date.issued","2022"],["dc.description.abstract","Abstract\n \n Context\n Tangled commits are changes to software that address multiple concerns at once. For researchers interested in bugs, tangled commits mean that they actually study not only bugs, but also other concerns irrelevant for the study of bugs.\n \n \n Objective\n We want to improve our understanding of the prevalence of tangling and the types of changes that are tangled within bug fixing commits.\n \n \n Methods\n We use a crowd sourcing approach for manual labeling to validate which changes contribute to bug fixes for each line in bug fixing commits. Each line is labeled by four participants. If at least three participants agree on the same label, we have consensus.\n \n \n Results\n We estimate that between 17% and 32% of all changes in bug fixing commits modify the source code to fix the underlying problem. However, when we only consider changes to the production code files this ratio increases to 66% to 87%. We find that about 11% of lines are hard to label leading to active disagreements between participants. Due to confirmed tangling and the uncertainty in our data, we estimate that 3% to 47% of data is noisy without manual untangling, depending on the use case.\n \n \n Conclusion\n Tangled commits have a high prevalence in bug fixes and can lead to a large amount of noise in the data. Prior research indicates that this noise may alter results. As researchers, we should be skeptics and assume that unvalidated data is likely very noisy, until proven otherwise."],["dc.identifier.doi","10.1007/s10664-021-10083-5"],["dc.identifier.pii","10083"],["dc.identifier.uri","https://resolver.sub.uni-goettingen.de/purl?gro-2/113398"],["dc.language.iso","en"],["dc.notes.intern","DOI-Import GROB-597"],["dc.relation.eissn","1573-7616"],["dc.relation.issn","1382-3256"],["dc.rights.uri","https://creativecommons.org/licenses/by/4.0"],["dc.title","A fine-grained data set and analysis of tangling in bug fixing commits"],["dc.type","journal_article"],["dc.type.internalPublication","yes"],["dspace.entity.type","Publication"]]

[["dc.bibliographiccitation.firstpage","1036"],["dc.bibliographiccitation.issue","2"],["dc.bibliographiccitation.journal","Empirical Software Engineering"],["dc.bibliographiccitation.lastpage","1083"],["dc.bibliographiccitation.volume","23"],["dc.contributor.author","Trautsch, Fabian"],["dc.contributor.author","Herbold, Steffen"],["dc.contributor.author","Makedonski, Philip"],["dc.contributor.author","Grabowski, Jens"],["dc.date.accessioned","2019-07-24T15:05:15Z"],["dc.date.available","2019-07-24T15:05:15Z"],["dc.date.issued","2017"],["dc.description.abstract","The usage of empirical methods has grown common in software engineering. This trend spawned hundreds of publications, whose results are helping to understand and improve the software development process. Due to the data-driven nature of this venue of investigation, we identified several problems within the current state-of-the-art that pose a threat to the replicability and validity of approaches. The heavy re-use of data sets in many studies may invalidate the results in case problems with the data itself are identified. Moreover, for many studies data and/or the implementations are not available, which hinders a replication of the results and, thereby, decreases the comparability between studies. Furthermore, many studies use small data sets, which comprise of less than 10 projects. This poses a threat especially to the external validity of these studies. Even if all information about the studies is available, the diversity of the used tooling can make their replication even then very hard. Within this paper, we discuss a potential solution to these problems through a cloud-based platform that integrates data collection and analytics. We created SmartSHARK, which implements our approach. Using SmartSHARK, we collected data from several projects and created different analytic examples. Within this article, we present SmartSHARK and discuss our experiences regarding the use of it and the mentioned problems. Additionally, we show how we have addressed the issues that we have identified during our work with SmartSHARK."],["dc.identifier.doi","10.1007/s10664-017-9537-x"],["dc.identifier.uri","https://resolver.sub.uni-goettingen.de/purl?gro-2/62035"],["dc.language.iso","en"],["dc.relation.issn","1382-3256"],["dc.relation.issn","1573-7616"],["dc.title","Addressing problems with replicability and validity of repository mining studies through a smart data platform"],["dc.type","journal_article"],["dc.type.internalPublication","yes"],["dspace.entity.type","Publication"]]

[["dc.bibliographiccitation.firstpage","227"],["dc.bibliographiccitation.issue","3"],["dc.bibliographiccitation.journal","INTERNATIONAL JOURNAL ON SOFTWARE TOOLS FOR TECHNOLOGY TRANSFER"],["dc.bibliographiccitation.lastpage","246"],["dc.bibliographiccitation.volume","16"],["dc.contributor.author","Makedonski, Philip"],["dc.contributor.author","Grabowski, Jens"],["dc.contributor.author","Philipp, Florian"],["dc.date.accessioned","2018-11-07T09:39:52Z"],["dc.date.available","2018-11-07T09:39:52Z"],["dc.date.issued","2014"],["dc.description.abstract","Ten years of maintenance, nine published revisions of the standards for the Testing and Test Control Notation version 3 (TTCN-3), more than 500 change requests since 2006, and 10 years of activity on the official TTCN-3 mailing list add up to a rich history, not unlike that of many successful Open Source Software (OSS) projects. In this article, we contemplate TTCN-3 in the context of software evolution and examine its history quantitatively. We mined the changes in the textual content of the standards, the data in change requests from the past 5 years, and the mailing list archives from the past 10 years. In addition, to characterize the use of the TTCN-3 we investigated the meta-data of the contributions at the TTCN-3 User Conference, and the use of language constructs in a large-scale TTCN-3 test suite. Based on these data sets, we first analyze the amount, density, and location of changes within the different parts of the standard. Then, we analyze the activity and focus of the user community and the maintenance team in both the change request management system and the official TTCN-3 mailing list. Finally, we analyze the distribution of contributions at the TTCN-3 User Conference across different topics over the past 8 years and construct use anomalies during the development of a large-scale test suite. Our findings indicate that the TTCN-3 is becoming increasingly stable as the overall change density and intensity, aswell as the number of change requests are decreasing, despite the monotonous increase in the size of the standards."],["dc.identifier.doi","10.1007/s10009-013-0282-1"],["dc.identifier.isi","000209673100002"],["dc.identifier.uri","https://resolver.sub.uni-goettingen.de/purl?gro-2/33386"],["dc.notes.status","zu prüfen"],["dc.notes.submitter","Najko"],["dc.relation.issn","1433-2787"],["dc.relation.issn","1433-2779"],["dc.title","Quantifying the evolution of TTCN-3 as a language"],["dc.type","journal_article"],["dc.type.internalPublication","yes"],["dc.type.peerReviewed","yes"],["dspace.entity.type","Publication"]]

[["dc.bibliographiccitation.firstpage","885"],["dc.bibliographiccitation.issue","2"],["dc.bibliographiccitation.journal","Software Quality Journal"],["dc.bibliographiccitation.lastpage","917"],["dc.bibliographiccitation.volume","27"],["dc.contributor.author","Makedonski, Philip"],["dc.contributor.author","Adamis, Gusztáv"],["dc.contributor.author","Käärik, Martti"],["dc.contributor.author","Kristoffersen, Finn"],["dc.contributor.author","Carignani, Michele"],["dc.contributor.author","Ulrich, Andreas"],["dc.contributor.author","Grabowski, Jens"],["dc.date.accessioned","2019-11-13T09:22:33Z"],["dc.date.available","2019-11-13T09:22:33Z"],["dc.date.issued","2018"],["dc.description.abstract","To address the need for abstract, high-level test descriptions that can be shared among different stakeholders, the ETSI commissioned the design of the Test Description Language (TDL). TDL is designed as a domain-specific language for testing, consisting of a standardised abstract syntax (meta-model) and concrete syntaxes for textual specification, graphical design, and model exchange between tools. Its main purpose is to support a test methodology that is followed in the standardisation work for software-intense systems at ETSI and is also applicable in industrial projects. TDL offers a standardised language that enables the formal specification of both test objectives derived from system requirements and test descriptions that refine the test objectives and serve as blueprints for the implementation of executable tests. A standardised mapping of TDL specifications to test scripts in the standardised test execution language Testing and Test Control Notation version 3 (TTCN-3) widens the reach of TDL to ensure compatibility and consistency in generated executable tests. An open-source toolset for TDL has been developed as a common platform to accelerate the adoption of TDL and lower the barrier to entry for both, users and tool-vendors. Reports from pilot applications of TDL within three ETSI standardisation groups demonstrate the practicability of the chosen approach."],["dc.identifier.doi","10.1007/s11219-018-9423-9"],["dc.identifier.uri","https://resolver.sub.uni-goettingen.de/purl?gro-2/62621"],["dc.language.iso","en"],["dc.relation.issn","0963-9314"],["dc.relation.issn","1573-1367"],["dc.title","Test descriptions with ETSI TDL"],["dc.type","journal_article"],["dc.type.internalPublication","yes"],["dspace.entity.type","Publication"]]