•Journal•ISSN: 1897-7979
e-Informatica Software Engineering Journal
Wrocław University of Science and Technology
About: e-Informatica Software Engineering Journal is an academic journal published by Wrocław University of Science and Technology. The journal publishes majorly in the area(s): Computer science & Software. It has an ISSN identifier of 1897-7979. It is also open access. Over the lifetime, 114 publications have been published receiving 877 citations. The journal is also known as: e-Informatica Software Engineering Journal & E-Informatica.
Topics: Computer science, Software, Software development, Agile software development, Domain (software engineering)
Papers
More filters
••
Blekinge Institute of Technology1, Norwegian University of Science and Technology2, Free University of Bozen-Bolzano3, National University of Ireland, Galway4, Technical University of Madrid5, Tampere University of Technology6, University of São Paulo7, University of Cagliari8, Maynooth University9, University of Oulu10, Konstanz University of Applied Sciences11
TL;DR: Software startup companies develop innovative, software-intensive products within limited timeframes and with few resources, searching for sustainable and scalable business models.
Abstract: Software startup companies develop innovative, software-intensive products within limited timeframes and with few resources, searching for sustainable and scalable business models. Software startup ...
128 citations
•
TL;DR: This paper analyzes to what extent the CMMI process areas can be covered by XP and where adjustments of XP have to be made and describes the limitations of CMMI in an agile environment and shows that level 4 or 5 are not feasible under the current specifications ofCMMI and XP.
Abstract: During the last years, agile methods like eXtreme Programming have become increasingly popular. Parallel to this, more and more organizations rely on process maturity models to assess and improve their own processes or those of suppliers, since it has been getting clear that most project failures can be imputed to inconsistent, undisciplined processes. Many organizations demand CMMI compliance of projects where agile methods are employed. In this situation it is necessary to analyze the interrelations and mutual restrictions between agile methods and approaches for software process analysis and improvement. This paper analyzes to what extent the CMMI process areas can be covered by XP and where adjustments of XP have to be made. Based on this, we describe the limitations of CMMI in an agile environment and show that level 4 or 5 are not feasible under the current specifications of CMMI and XP.
69 citations
•
TL;DR: The analysis of secondary variables provides hints on advantages of the refactoring technique like reduced resource consumption and a reduced occurrence of complicated control structures and the overhead of applyingRefactoring appears to even weaken other, positive eects.
Abstract: This paper presents a process evaluation for the agile technique of refactoring based on the language C. The basis for this evaluation is made up by an experiment which is targeted on the aspects of increased maintainability and modifiability. Although the maintainability test shows a slight advantage for refactoring, results show no significant strength here. Concerning modifiability, the overhead of applying refactoring appears to even weaken other, positive eects. The analysis of secondary variables provides hints on advantages of the refactoring technique like reduced resource consumption and a reduced occurrence of complicated control structures.
45 citations
•
TL;DR: This work presents a novel methodology for test case generation based on UML sequence diagrams that achieves slice test coverage with few test cases and formulates a test adequacy criterion named slice coverage criterion.
Abstract: We present a novel methodology for test case generation based on UML sequence diagrams. We create message dependence graphs (MDG) from UML sequence diagrams. Edge marking dynamic slicing method is applied on MDG to create slices. Based on the slice created with respect to each predicate on the sequence diagram, we generate test data. We formulate a test adequacy criterion named slice coverage criterion. Test cases that we generate achieves slice coverage criterion. Our approach achieves slice test coverage with few test cases. We generate eective test cases for cluster level testing.
34 citations
••
TL;DR: An analysis of 83 versions of industrial, open-source and academic projects has empirically evaluated whether those project types constitute separate classes of projects with regard to defect prediction and proved that there exist significant dierences between the models trained on the aforementioned project classes.
Abstract: The paper presents an analysis of 83 versions of industrial, open-source and academic projects. We have empirically evaluated whether those project types constitute separate classes of projects with regard to defect prediction. Statistical tests proved that there exist significant dierences between the models trained on the aforementioned project classes. This work makes the next step towards cross-project reusability of defect prediction models and facilitates their adoption, which has been very limited so far.
21 citations