Link to record
Permanent link

Direct link
BETA
Petersen, Kai
Alternative names
Publications (10 of 78) Show all publications
Irshad, M., Petersen, K. & Poulding, S. (2018). A systematic literature review of software requirements reuse approaches. Information and Software Technology, 93(Jan), 223-245.
Open this publication in new window or tab >>A systematic literature review of software requirements reuse approaches
2018 (English)In: Information and Software Technology, ISSN 0950-5849, E-ISSN 1873-6025, Vol. 93, no Jan, 223-245 p.Article in journal (Refereed) Published
Abstract [en]

Context: Early software reuse is considered as the most beneficial form of software reuse. Hence, previous research has focused on supporting the reuse of software requirements. Objective: This study aims to identify and investigate the current state of the art with respect to (a) what requirement reuse approaches have been proposed, (b) the methods used to evaluate the approaches, (c) the characteristics of the approaches, and (d) the quality of empirical studies on requirements reuse with respect to rigor and relevance. Method: We conducted a systematic review and a combination of snowball sampling and database search have been used to identify the studies. The rigor and relevance scoring rubric has been used to assess the quality of the empirical studies. Multiple researchers have been involved in each step to increase the reliability of the study. Results: Sixty-nine studies were identified that describe requirements reuse approaches. The majority of the approaches used structuring and matching of requirements as a method to support requirements reuse and text-based artefacts were commonly used as an input to these approaches. Further evaluation of the studies revealed that the majority of the approaches are not validated in the industry. The subset of empirical studies (22 in total) was analyzed for rigor and relevance and two studies achieved the maximum score for rigor and relevance based on the rubric. It was found that mostly text-based requirements reuse approaches were validated in the industry. Conclusion: From the review, it was found that a number of approaches already exist in literature, but many approaches are not validated in industry. The evaluation of rigor and relevance of empirical studies show that these do not contain details of context, validity threats, and the industrial settings, thus highlighting the need for the industrial evaluation of the approaches. © 2017 Elsevier B.V.

Place, publisher, year, edition, pages
Elsevier, 2018
Keyword
Artefact reuse, Relevance, Requirements reuse, Reusability, Rigor, Software requirements, Quality control, Requirements engineering, Search engines, Computer software reusability
National Category
Software Engineering
Identifiers
urn:nbn:se:bth-15356 (URN)10.1016/j.infsof.2017.09.009 (DOI)000414878200014 ()2-s2.0-85030849171 (Scopus ID)
Funder
Knowledge Foundation
Note

project "Professional Licentiate of Engineering Research School"

Available from: 2017-10-20 Created: 2017-10-20 Last updated: 2017-11-24Bibliographically approved
Usman, M., Börstler, J. & Petersen, K. (2017). An Effort Estimation Taxonomy for Agile Software Development. International journal of software engineering and knowledge engineering, 27(4), 641-674.
Open this publication in new window or tab >>An Effort Estimation Taxonomy for Agile Software Development
2017 (English)In: International journal of software engineering and knowledge engineering, ISSN 0218-1940, Vol. 27, no 4, 641-674 p.Article in journal (Refereed) Published
Abstract [en]

In Agile Software Development (ASD) effort estimation plays an important role during release and iteration planning. The state of the art and practice on effort estimation in ASD have been recently identified. However, this knowledge has not yet been organized. The aim of this study is twofold: (1) To organize the knowledge on effort estimation in ASD and (2) to use this organized knowledge to support practice and the future research on effort estimation in ASD. We applied a taxonomy design method to organize the identified knowledge as a taxonomy of effort estimation in ASD. The proposed taxonomy offers a faceted classification scheme to characterize estimation activities of agile projects. Our agile estimation taxonomy consists of four dimensions: estimation context, estimation technique, effort predictors and effort estimate. Each dimension in turn has several facets. We applied the taxonomy to characterize estimation activities of 10 agile projects identified from the literature to assess whether all important estimation-related aspects are reported. The results showed that studies do not report complete information related to estimation. The taxonomy was also used to characterize the estimation activities of four agile teams from three different software companies. The practitioners involved in the investigation found the taxonomy useful in characterizing and documenting the estimation sessions. © 2017 The Author(s).

Place, publisher, year, edition, pages
World Scientific Publishing Co. Pte Ltd, 2017
Keyword
agile software development, Effort estimation, taxonomy, Iterative methods, Software design, Taxonomies, Complete information, Effort estimates, Estimation techniques, Faceted Classification, Iteration planning, Software company, Software engineering
National Category
Software Engineering
Identifiers
urn:nbn:se:bth-14472 (URN)10.1142/S0218194017500243 (DOI)000402062200006 ()2-s2.0-85019610980 (Scopus ID)
Available from: 2017-06-13 Created: 2017-06-13 Last updated: 2017-06-13Bibliographically approved
Ghazi, A. N., Garigapati, R. P. & Petersen, K. (2017). Checklists to Support Test Charter Design in Exploratory Testing. In: Baumeister H., Lichter H., Riebisch M. (Ed.), Agile Processes in Software Engineering and Extreme Programming: . Paper presented at 18th International Conference on Agile Software Development. XP 2017 (pp. 251-258). Springer, 283.
Open this publication in new window or tab >>Checklists to Support Test Charter Design in Exploratory Testing
2017 (English)In: Agile Processes in Software Engineering and Extreme Programming / [ed] Baumeister H., Lichter H., Riebisch M., Springer, 2017, Vol. 283, 251-258 p.Conference paper, Published paper (Refereed)
Abstract [en]

During exploratory testing sessions the tester simultaneously learns, designs and executes tests. The activity is iterative and utilizes the skills of the tester and provides flexibility and creativity. Test charters are used as a vehicle to support the testers during the testing. The aim of this study is to support practitioners in the design of test charters through checklists. We aimed to identify factors allowing practitioners to critically reflect on their designs and contents of test charters to support practitioners in making informed decisions of what to include in test charters. The factors and contents have been elicited through interviews. Overall, 30 factors and 35 content elements have been elicited.

Place, publisher, year, edition, pages
Springer, 2017
Series
Lecture Notes in Business Information Processing, ISSN 1865-1348 ; 283
Keyword
Software Testing, Exploratory Testing, SBTM, Session based test management, Test Charter, Test Mission
National Category
Software Engineering
Identifiers
urn:nbn:se:bth-14123 (URN)10.1007/978-3-319-57633-6_17 (DOI)9783319576329 (ISBN)
Conference
18th International Conference on Agile Software Development. XP 2017
Note

open access

Available from: 2017-04-19 Created: 2017-04-19 Last updated: 2017-05-26Bibliographically approved
Engström, E., Petersen, K., Ali, N. & Bjarnason, E. (2017). SERP-test: a taxonomy for supporting industry-academia communication. Paper presented at 1269--1305. Software quality journal, 25(4), 1269-1305.
Open this publication in new window or tab >>SERP-test: a taxonomy for supporting industry-academia communication
2017 (English)In: Software quality journal, ISSN 0963-9314, E-ISSN 1573-1367, Vol. 25, no 4, 1269-1305 p.Article in journal (Refereed) Epub ahead of print
Abstract [en]

This paper presents the construction and evaluation of SERP-test, a taxonomy aimed to improve communication between researchers and practitioners in the area of software testing. SERP-test can be utilized for direct communication in industry academia collaborations. It may also facilitate indirect communication between practitioners adopting software engineering research and researchers who are striving for industry relevance. SERP-test was constructed through a systematic and goal-oriented approach which included literature reviews and interviews with practitioners and researchers. SERP-test was evaluated through an online survey and by utilizing it in an industry–academia collaboration project. SERP-test comprises four facets along which both research contributions and practical challenges may be classified: Intervention, Scope, Effect target and Context constraints. This paper explains the available categories for each of these facets (i.e., their definitions and rationales) and presents examples of categorized entities. Several tasks may benefit from SERP-test, such as formulating research goals from a problem perspective, describing practical challenges in a researchable fashion, analyzing primary studies in a literature review, or identifying relevant points of comparison and generalization of research.

Place, publisher, year, edition, pages
Springer-Verlag New York, 2017
Keyword
Classification (of information); Software engineering; Taxonomies; Testing, Context; Industry relevance; Intervention; Methodology; Scope, Software testing
National Category
Software Engineering
Identifiers
urn:nbn:se:bth-13103 (URN)10.1007/s11219-016-9322-x (DOI)2-s2.0-84976367380 (Scopus ID)
Conference
1269--1305
Available from: 2016-10-04 Created: 2016-10-03 Last updated: 2017-12-08
Oliinyk, O., Petersen, K., Schoelzke, M., Becker, M. & Schneickert, S. (2017). Structuring automotive product lines and feature models: an exploratory study at Opel. Requirements Engineering, 22, 105-135.
Open this publication in new window or tab >>Structuring automotive product lines and feature models: an exploratory study at Opel
Show others...
2017 (English)In: Requirements Engineering, ISSN 0947-3602, E-ISSN 1432-010X, Vol. 22, 105-135 p.Article in journal (Refereed) Published
Abstract [en]

Automotive systems are highly complex and customized systems containing a vast amount of variability. Feature modeling plays a key role in customization. Empirical evidence through industry application, and in particular methodological guidance of how to structure automotive product lines and their feature models is needed. The overall aim of this work is to provide guidance to practitioners how to structure automotive product lines and their feature models, understanding strengths and weaknesses of alternative structures. The research was conducted in three phases. In the first phase, the context situation was understood using interviews and workshops. In the second phase, possible structures of product lines and feature models were evaluated based on industry feedback collected in workshops. In the third phase, the structures were implemented in the tool GEARS and practitioner feedback was collected. One key challenge was the unavailability of structuring guidelines, which was the focus of this research. The structures considered most suitable for the automotive product line were multiple product lines with modular decomposition. The structures most suitable for the feature model were functional decomposition, using context variability, models corresponding to assets, and feature categories. Other structures have been discarded, and the rationales have been presented. It was possible to support the most suitable structures with the commercial tool GEARS. The implementation in GEARS and the feedback from the practitioners provide early indications for the potential usefulness of the structures and the tool implementation.

Place, publisher, year, edition, pages
Springer, 2017
Keyword
Requirements engineering; Software engineering Automotive; Empirical; Feature modeling; Product line engineering; Variability model
National Category
Software Engineering
Identifiers
urn:nbn:se:bth-10715 (URN)10.1007/s00766-015-0237-z (DOI)000394464600005 ()
Available from: 2015-09-21 Created: 2015-09-21 Last updated: 2017-12-04Bibliographically approved
Ickin, S., Petersen, K. & Gonzalez-Huerta, J. (2017). Why do users install and delete apps?: A survey study. In: Lecture Notes in Business Information Processing: . Paper presented at 8th International Conference on Software Business, (ICSOB), Essen (pp. 186-191). Springer Verlag, 304.
Open this publication in new window or tab >>Why do users install and delete apps?: A survey study
2017 (English)In: Lecture Notes in Business Information Processing, Springer Verlag , 2017, Vol. 304, 186-191 p.Conference paper, Published paper (Refereed)
Abstract [en]

Practitioners on the area of mobile application development usually rely on set of app-related success factors, the majority of which are directly related to their economical/business profit (e.g., number of downloads, or the in-app purchases revenue). However, gathering also the user-related success factors, that explain the reasons why users choose, download, and install apps as well as the user-related failure factors that explain the reasons why users delete apps, might help practitioners understand how to improve the market impact of their apps. The objectives were to: identify (i) the reasons why users choose and installing mobile apps from app stores; (ii) the reasons why users uninstall the apps. A questionnaire-based survey involving 121 users from 26 different countries was conducted. © Springer International Publishing AG 2017.

Place, publisher, year, edition, pages
Springer Verlag, 2017
Series
Lecture Notes in Business Information Processing, ISSN 1865-1348 ; 304
Keyword
Failure factors, Mobile application development, Success factors, Users survey, Mobile computing, Mobile telecommunication systems, App stores, Market impacts, Mobile apps, Surveys
National Category
Software Engineering
Identifiers
urn:nbn:se:bth-15613 (URN)10.1007/978-3-319-69191-6_13 (DOI)2-s2.0-85034246129 (Scopus ID)9783319691909 (ISBN)
Conference
8th International Conference on Software Business, (ICSOB), Essen
Available from: 2017-12-07 Created: 2017-12-07 Last updated: 2017-12-07Bibliographically approved
Carlson, J., Papatheocharous, E. & Petersen, K. (2016). A Context Model for Architectural Decision Support. In: PROCEEDINGS 2016 1ST INTERNATIONAL WORKSHOP ON DECISION MAKING IN SOFTWARE ARCHITECTURE: . Paper presented at 1st International Workshop on Decision Making in Software ARCHitecture (MARCH), APR 05, 2016, Venice, ITALY (pp. 9-15). IEEE Computer Society.
Open this publication in new window or tab >>A Context Model for Architectural Decision Support
2016 (English)In: PROCEEDINGS 2016 1ST INTERNATIONAL WORKSHOP ON DECISION MAKING IN SOFTWARE ARCHITECTURE, IEEE Computer Society, 2016, 9-15 p.Conference paper, Published paper (Refereed)
Abstract [en]

Developing efficient and effective decision making support includes identifying means to reduce repeated manual work and providing possibilities to take advantage of the experience gained in previous decision situations. For this to be possible, there is a need to explicitly model the context of a decision case, for example to determine how much the evidence from one decision case can be trusted in another, similar context. In earlier work, context has been recognized as important when transferring and understanding outcomes between cases. The contribution of this paper is threefold. First, we describe different ways of utilizing context in an envisioned decision support system. Thereby, we distinguish between internal and external context usage, possibilities of context representation, and context inheritance. Second, we present a systematically developed context model comprised of five types of context information, namely organization, product, stakeholder, development method & technology, and market & business. Third, we exemplary illustrate the relation of the context information to architectural decision making using existing literature.

Place, publisher, year, edition, pages
IEEE Computer Society, 2016
National Category
Software Engineering
Identifiers
urn:nbn:se:bth-13056 (URN)10.1109/MARCH.2016.6 (DOI)000382526100002 ()978-1-5090-2573-2 (ISBN)
Conference
1st International Workshop on Decision Making in Software ARCHitecture (MARCH), APR 05, 2016, Venice, ITALY
Available from: 2016-09-30 Created: 2016-09-30 Last updated: 2016-11-10Bibliographically approved
Jabangwe, R., Wohlin, C., Petersen, K., Šmite, D. & Börstler, J. (2016). A method for investigating the quality of evolving object-oriented software using defects in global software development projects. Journal of Software: Evolution and Process, 28(8), 622-641.
Open this publication in new window or tab >>A method for investigating the quality of evolving object-oriented software using defects in global software development projects
Show others...
2016 (English)In: Journal of Software: Evolution and Process, ISSN 2047-7473, E-ISSN 2047-7481, Vol. 28, no 8, 622-641 p.Article in journal (Refereed) Published
Abstract [en]

Context: Global software development (GSD) projects can have distributed teams that work independently in different locations or team members that are dispersed. The various development settings in GSD can influence quality during product evolution. When evaluating quality using defects as a proxy, the development settings have to be taken into consideration. Objective: The aim is to provide a systematic method for supporting investigations of the implication of GSD contexts on defect data as a proxy for quality. Method: A method engineering approach was used to incrementally develop the proposed method. This was done through applying the method in multiple industrial contexts and then using lessons learned to refine and improve the method after application. Results: A measurement instrument and visualization was proposed incorporating an understanding of the release history and understanding of GSD contexts. Conclusion: The method can help with making accurate inferences about development settings because it includes details on collecting and aggregating data at a level that matches the development setting in a GSD context and involves practitioners at various phases of the investigation. Finally, the information that is produced from following the method can help practitioners make informed decisions when planning to develop software in comparable circumstances. Copyright © 2016 John Wiley & Sons, Ltd. Copyright © 2016 John Wiley & Sons, Ltd.

Place, publisher, year, edition, pages
John Wiley & Sons, 2016
Keyword
Computer software selection and evaluation; Copyrights; Defects; Software design, Defect analysis; Distributed software development; Global software development; Object oriented software; Software Evolution; Software Quality, Object oriented programming
National Category
Software Engineering
Identifiers
urn:nbn:se:bth-12980 (URN)10.1002/smr.1788 (DOI)000388301300001 ()2-s2.0-84981275207 (Scopus ID)
Available from: 2016-08-31 Created: 2016-08-31 Last updated: 2017-11-21Bibliographically approved
Sentilles, S., Papatheocharous, E., Ciccozzi, F. & Petersen, K. (2016). A Property Model Ontology. In: 2016 42ND EUROMICRO CONFERENCE ON SOFTWARE ENGINEERING AND ADVANCED APPLICATIONS (SEAA): . Paper presented at 42nd Euromicro Conference Series on Software Engineering and Advanced Applications (SEAA), AUG 31-SEP 02, 2016, Limassol, CYPRUS (pp. 165-172). .
Open this publication in new window or tab >>A Property Model Ontology
2016 (English)In: 2016 42ND EUROMICRO CONFERENCE ON SOFTWARE ENGINEERING AND ADVANCED APPLICATIONS (SEAA), 2016, 165-172 p.Conference paper, Published paper (Refereed)
Abstract [en]

Efficient development of high quality software is tightly coupled to the ability of quickly taking complex decisions based on trustworthy facts. In component-based software engineering, the decisions related to selecting the most suitable component among functionally-equivalent ones are of paramount importance. Despite sharing the same functionality, components differ in terms of their extra-functional properties. Therefore, to make informed selections, it is crucial to evaluate extra-functional properties in a systematic way. To date, many properties and evaluation methods that are not necessarily compatible with each other exist. The property model ontology presented in this paper represents the first step towards providing a systematic way to describe extra-functional properties and their evaluation methods, and thus making them comparable. This is beneficial from two perspectives. First, it aids researchers in identifying comparable property models as a guide for empirical evaluations. Second, practitioners are supported in choosing among alternative evaluation methods for the properties of their interest. The use of the ontology is illustrated by instantiating a subset of property models relevant in the automotive domain.

Keyword
WCET ANALYSIS; SOFTWARE; ARCHITECTURE; QUALITY; TIME
National Category
Software Engineering
Identifiers
urn:nbn:se:bth-13720 (URN)10.1109/SEAA.2016.26 (DOI)000386649000026 ()978-1-5090-2819-1 (ISBN)
Conference
42nd Euromicro Conference Series on Software Engineering and Advanced Applications (SEAA), AUG 31-SEP 02, 2016, Limassol, CYPRUS
Available from: 2017-01-05 Created: 2017-01-05 Last updated: 2017-07-06Bibliographically approved
Irshad, M., Torkar, R., Petersen, K. & Afzal, W. (2016). Capturing cost avoidance through reuse: Systematic literature review and industrial evaluation. In: ACM International Conference Proceeding Series: . Paper presented at 20th International Conference on Evaluation and Assessment in Software Engineering, EASE 2016; Limerick. ACM Press, 01-03-June-2016.
Open this publication in new window or tab >>Capturing cost avoidance through reuse: Systematic literature review and industrial evaluation
2016 (English)In: ACM International Conference Proceeding Series, ACM Press, 2016, Vol. 01-03-June-2016Conference paper, Published paper (Refereed)
Abstract [en]

Background: Cost avoidance through reuse shows the benefits gained by the software organisations when reusing an artefact. Cost avoidance captures benefits that are not captured by cost savings e.g. spending that would have increased in the absence of the cost avoidance activity. This type of benefit can be combined with quality aspects of the product e.g. costs avoided because of defect prevention. Cost avoidance is a key driver for software reuse. Objectives: The main objectives of this study are: (1) To assess the status of capturing cost avoidance through reuse in the academia; (2) Based on the first objective, propose improvements in capturing of reuse cost avoidance, integrate these into an instrument, and evaluate the instrument in the software industry. Method: The study starts with a systematic literature review (SLR) on capturing of cost avoidance through reuse. Later, a solution is proposed and evaluated in the industry to address the shortcomings identified during the systematic literature review. Results: The results of a systematic literature review describe three previous studies on reuse cost avoidance and show that no solution, to capture reuse cost avoidance, was validated in industry. Afterwards, an instrument and a data collection form are proposed that can be used to capture the cost avoided by reusing any type of reuse artefact. The instrument and data collection form (describing guidelines) were demonstrated to a focus group, as part of static evaluation. Based on the feedback, the instrument was updated and evaluated in industry at 6 development sites, in 3 different countries, covering 24 projects in total. Conclusion: The proposed solution performed well in industrial evaluation. With this solution, practitioners were able to do calculations for reuse costs avoidance and use the results as decision support for identifying potential artefacts to reuse.

Place, publisher, year, edition, pages
ACM Press, 2016
Keyword
Costs; Data acquisition; Decision support systems; Software engineering, Cost avoidances; Cost saving; Decision supports; Defect prevention; Industrial evaluations; Software organisations; Systematic literature review; Systematic literature review (SLR), Computer software reusability
National Category
Software Engineering
Identifiers
urn:nbn:se:bth-13116 (URN)10.1145/2915970.2915989 (DOI)2-s2.0-84978540065 (Scopus ID)978-145033691-8 (ISBN)
Conference
20th International Conference on Evaluation and Assessment in Software Engineering, EASE 2016; Limerick
Note

 Conference of 20th International Conference on Evaluation and Assessment in Software Engineering, EASE 2016 ; Conference Date: 1 June 2016 Through 3 June 2016; Conference Code:122245

Available from: 2016-10-04 Created: 2016-10-03 Last updated: 2016-11-08Bibliographically approved
Organisations
Identifiers

Search in DiVA

Show all publications