Change search
Link to record
Permanent link

Direct link
BETA
Wnuk, Krzysztof
Publications (10 of 54) Show all publications
Ouriques, R., Britto, R., Wnuk, K., Ouriques, J. F. & Gorschek, T. (2019). A Method to Evaluate Knowledge Resources in Agile Software Development. In: Proceeding of The ACM/IEEE International Symposium on Empirical Software Engineering and Measurement ESEM 2019: . Paper presented at The ACM/IEEE International Symposium on Empirical Software Engineering and Measurement ESEM 2019 Porto de Galinhas, Brazil September 19th-20th, 2019. IEEE, Article ID 8870167.
Open this publication in new window or tab >>A Method to Evaluate Knowledge Resources in Agile Software Development
Show others...
2019 (English)In: Proceeding of The ACM/IEEE International Symposium on Empirical Software Engineering and Measurement ESEM 2019, IEEE, 2019, article id 8870167Conference paper, Published paper (Refereed)
Abstract [en]

Background: Organizations adopting Agile Software Development (ASD) use different Knowledge Management (KM) practices to retain and share knowledge. However, it is often the case that knowledge retention is carried out in an ad-hoc way.

Aims: In this study, we report our experience from proposing the Knowledge Critically Evaluation Method (KCEM) to evaluate knowledge items (KIT). Our main goal with KCEMs is to support companies to systematically retain knowledge in ASD contexts.

Method: We conducted an improvement case study to develop and evaluate KCEM. This research follows the guidelines for technology transfer between industry and academia. The case and unit of analysis is Ericsson, a Swedish company that develops telecommunication solutions.

Results: In this paper, we provide initial results of both lab and static validation, enriched by the lessons learned.

Conclusions: The preliminary results show that KCEM is easy to understand and use, provides a different perspective on the KIT by visualizing in the criticality chart, and reduces the level of abstraction associated to a knowledge subject area.

Place, publisher, year, edition, pages
IEEE, 2019
Keywords
Agile Software Development, Critical Knowledge, Knowledge Management
National Category
Computer Systems
Identifiers
urn:nbn:se:bth-18507 (URN)10.1109/ESEM.2019.8870167 (DOI)9781728129686 (ISBN)
Conference
The ACM/IEEE International Symposium on Empirical Software Engineering and Measurement ESEM 2019 Porto de Galinhas, Brazil September 19th-20th, 2019
Projects
S.E.R.T. Research Profile
Available from: 2019-08-01 Created: 2019-08-01 Last updated: 2019-11-18Bibliographically approved
Olsson, T., Wnuk, K. & Gorschek, T. (2019). An empirical study on decision making for quality requirements. Journal of Systems and Software, 149, 217-233
Open this publication in new window or tab >>An empirical study on decision making for quality requirements
2019 (English)In: Journal of Systems and Software, ISSN 0164-1212, E-ISSN 1873-1228, Vol. 149, p. 217-233Article in journal (Refereed) Published
Abstract [en]

Context: Quality requirements are important for product success yet often handled poorly. The problems with scope decision lead to delayed handling and an unbalanced scope. Objective: This study characterizes the scope decision process to understand influencing factors and properties affecting the scope decision of quality requirements. Method: We studied one company's scope decision process over a period of five years. We analyzed the decisions artifacts and interviewed experienced engineers involved in the scope decision process. Results: Features addressing quality aspects explicitly are a minor part (4.41%) of all features handled. The phase of the product line seems to influence the prevalence and acceptance rate of quality features. Lastly, relying on external stakeholders and upfront analysis seems to lead to long lead-times and an insufficient quality requirements scope. Conclusions: There is a need to make quality mode explicit in the scope decision process. We propose a scope decision process at a strategic level and a tactical level. The former to address long-term planning and the latter to cater for a speedy process. Furthermore, we believe it is key to balance the stakeholder input with feedback from usage and market in a more direct way than through a long plan-driven process. © 2018 Elsevier Inc.

Place, publisher, year, edition, pages
Elsevier Inc., 2019
Keywords
Non-functional requirements, Product management, Quality requirements, Requirements engineering, Requirements scope decision, Hardware, Software engineering, Decision process, Empirical studies, External stakeholders, Long term planning, Decision making
National Category
Software Engineering
Identifiers
urn:nbn:se:bth-17455 (URN)10.1016/j.jss.2018.12.002 (DOI)000457951800009 ()2-s2.0-85058167239 (Scopus ID)
Available from: 2019-01-09 Created: 2019-01-09 Last updated: 2019-02-21Bibliographically approved
Munir, H., Runeson, P. & Wnuk, K. (2019). How Companies Use OSS Tools Ecosystems for Open Innovation. IT Professional Magazine, 21(6), 40-45, Article ID 8896157.
Open this publication in new window or tab >>How Companies Use OSS Tools Ecosystems for Open Innovation
2019 (English)In: IT Professional Magazine, ISSN 1520-9202, E-ISSN 1941-045X, Vol. 21, no 6, p. 40-45, article id 8896157Article in journal (Refereed) Published
Abstract [en]

Moving toward the open innovation (OI) model requires multifaceted transformations within companies. It often involves giving away the tools for product development or sharing future product directions with open tools ecosystems. Moving from the traditional closed innovation model toward an OI model for software development tools shows the potential to increase software development competence and efficiency of organizations. We report a case study in software-intensive company developing embedded devices (e.g., smartphones) followed by a survey in OSS communities such as Gerrit, Git, and Jenkins. The studied branch focuses on developing Android phones. This paper presents contribution strategies and triggers for openness. These strategies include avoid forking OSS tools, empower developers to participate in the ecosystem, steer ecosystems through contributions, create business through differentiation, and create new ecosystems. The triggers of openness are from 30 different companies with examples. Finally, openness requires a cultural change aligned with strategies and business models. © 1999-2012 IEEE.

Place, publisher, year, edition, pages
IEEE Computer Society, 2019
Keywords
Androids, Business, Open systems, Product development, Software development management, Strategic planning, Industry, Robots, Software design, Business models, Closed innovations, Cultural changes, Embedded device, Open innovation, Software development tools, Ecosystems
National Category
Software Engineering
Identifiers
urn:nbn:se:bth-18979 (URN)10.1109/MITP.2019.2893134 (DOI)000497454100007 ()2-s2.0-85075111122 (Scopus ID)
Available from: 2019-11-28 Created: 2019-11-28 Last updated: 2019-12-13Bibliographically approved
Ouriques, R., Wnuk, K., Gorschek, T. & Berntsson Svensson, R. (2019). Knowledge Management Strategies and Processes in Agile Software Development: A Systematic Literature Review. International journal of software engineering and knowledge engineering, 29(3), 345-380
Open this publication in new window or tab >>Knowledge Management Strategies and Processes in Agile Software Development: A Systematic Literature Review
2019 (English)In: International journal of software engineering and knowledge engineering, ISSN 0218-1940, Vol. 29, no 3, p. 345-380Article, review/survey (Refereed) Published
Abstract [en]

Knowledge-intensive companies that adopt Agile Software Development (ASD) relay on efficient implementation of Knowledge Management (KM) strategies to promotes different Knowledge Processes (KPs) to gain competitive advantage. This study aims to explore how companies that adopt ASD implement KM strategies utilizing practices that promote the KPs in the different organizational layers. Through a systematic literature review, we analyzed 32 primary studies, selected by automated search and snowballing in the extant literature. To analyze the data, we applied narrative synthesis. Most of the identified KM practices implement personalization strategies (81 %), supported by codification (19 %). Our review shows that the primary studies do not report KM practices in the strategic layer and two of them in the product portfolio layer; on the other hand, in the project layer, the studies report 33 practices that implement personalization strategy, and seven practices that implement codification. KM strategies in ASD promote mainly the knowledge transfer process with practices that stimulate social interaction to share tacit knowledge in the project layer. As a result of using informal communication, a significant amount of knowledge can be lost or not properly transferred to other individuals and, instead of propagating the knowledge, it remains inside a few individuals minds.

Place, publisher, year, edition, pages
World Scientific, 2019
Keywords
knowledge management, agile software development
National Category
Engineering and Technology
Identifiers
urn:nbn:se:bth-17336 (URN)10.1142/S0218194019500153 (DOI)000462508200002 ()
Available from: 2018-11-26 Created: 2018-11-26 Last updated: 2019-08-01Bibliographically approved
Silva, L., Unterkalmsteiner, M. & Wnuk, K. (2019). Monitoring and maintenance of telecommunication systems: Challenges and research perspectives (830ed.). In: Kosiuczenko, P; Zielinski, Z (Ed.), ENGINEERING SOFTWARE SYSTEMS: RESEARCH AND PRAXIS. Paper presented at KKIO Software Engineering Conference, Pultusk, POLAND SEP 27-28, 2018 (pp. 166-172). Springer Verlag, 830
Open this publication in new window or tab >>Monitoring and maintenance of telecommunication systems: Challenges and research perspectives
2019 (English)In: ENGINEERING SOFTWARE SYSTEMS: RESEARCH AND PRAXIS / [ed] Kosiuczenko, P; Zielinski, Z, Springer Verlag , 2019, 830, Vol. 830, p. 166-172Conference paper, Published paper (Refereed)
Abstract [en]

In this paper, we present challenges associated with monitoring and maintaining a large telecom system at Ericsson that was developed with high degree of component reuse. The system constitutes of multiple services, composed of both legacy and modern systems that are constantly changing and need to be adapted to changing business needs. The paper is based on firsthand experience from architecting, developing and maintaining such a system, pointing out current challenges and potential avenues for future research that might contribute to addressing them. © Springer Nature Switzerland AG 2019.

Place, publisher, year, edition, pages
Springer Verlag, 2019 Edition: 830
Series
Advances in Intelligent Systems and Computing, ISSN 2194-5357 ; 830
Keywords
Legacy system evolution, Telecommunication services, Virtualization, Legacy systems, Business needs, Component reuse, Ericsson, Multiple services, System evolution, Telecom systems
National Category
Software Engineering Telecommunications
Identifiers
urn:nbn:se:bth-17184 (URN)10.1007/978-3-319-99617-2_11 (DOI)000461025600011 ()2-s2.0-85054716129 (Scopus ID)978-3-319-99617-2 (ISBN)
Conference
KKIO Software Engineering Conference, Pultusk, POLAND SEP 27-28, 2018
Available from: 2018-10-31 Created: 2018-10-31 Last updated: 2019-04-04Bibliographically approved
Munir, H., Runeson, P. & Wnuk, K. (2019). Open tools for software engineering: Validation of a theory of openness in the automotive industry. In: PROCEEDINGS OF EASE 2019 - EVALUATION AND ASSESSMENT IN SOFTWARE ENGINEERING: . Paper presented at 23rd Evaluation and Assessment in Software Engineering Conference, EASE 2019,Copenhagen, 14 April 2019 through 17 April (pp. 2-11). Association for Computing Machinery
Open this publication in new window or tab >>Open tools for software engineering: Validation of a theory of openness in the automotive industry
2019 (English)In: PROCEEDINGS OF EASE 2019 - EVALUATION AND ASSESSMENT IN SOFTWARE ENGINEERING, Association for Computing Machinery , 2019, p. 2-11Conference paper, Published paper (Refereed)
Abstract [en]

Context: Open tools (e.g., Jenkins, Gerrit and Git) offer a lucrative alternative to commercial tools. Many companies and developers from OSS communities make a collaborative effort to improve the tools. Prior to this study, we developed an empirically based theory for companies’ strategic choices on the development of these tools, based on empirical observations in the telecom domain. Aim: The aim of this study is to validate the theory of openness for tools in software engineering, in another domain, automotive. Specifically, we validated the theory propositions and mapped the case companies onto the model of openness. Method: We run focus groups in two automotive companies, collecting data in a survey and followup discussions. We used the repertory grid technique to analyze the survey responses, in combination with qualitative data from the focus group, to validate the propositions. Results: Openness of tools has the potential to reduce development costs and time, and may lead to process and product innovation. This study confirms three out of five theory propositions, on cost and time reduction, and the complementary role of open tools. One propositions was not possible to validate due to lack of investment in OSS tools communities by both companies. However, our findings extend the fifth proposition to require management being involved for both the proactive and reactive strategy. Further, we observe that the move towards open tools happen with a paradigm shift towards openness in the automotive domain, and lead to standardization of tools. Both companies confirm that they need legal procedures for the contribution, as well as an internal champion, driving the open tools strategy. Conclusion: We validated the theory, originating from the telecom domain, partially using two automotive companies. Both case companies are classified as laggards (reactive, cost saving) in the model of openness presented in the theory. Furthermore, we would like to have more validations studies to validate the remaining quadrants (e.g., leverage, lucrativeness and leaders). © 2019 Association for Computing Machinery.

Place, publisher, year, edition, pages
Association for Computing Machinery, 2019
Keywords
Open innovation, Open tools, Theory of openness, Automotive industry, Cost reduction, Distributed computer systems, Surveys, Automotive companies, Automotive domains, Development costs, Product innovation, Repertory grid technique, Strategic choice, Software engineering
National Category
Software Engineering
Identifiers
urn:nbn:se:bth-17892 (URN)10.1145/3319008.3319014 (DOI)000493383400001 ()2-s2.0-85064750085 (Scopus ID)9781450371452 (ISBN)
Conference
23rd Evaluation and Assessment in Software Engineering Conference, EASE 2019,Copenhagen, 14 April 2019 through 17 April
Available from: 2019-05-21 Created: 2019-05-21 Last updated: 2019-11-14Bibliographically approved
Borg, M., Chatzipetrou, P., Wnuk, K., Alégroth, E., Gorschek, T., Papatheocharous, E., . . . Axelsson, J. (2019). Selecting component sourcing options: A survey of software engineering's broader make-or-buy decisions. Information and Software Technology, 112, 18-34
Open this publication in new window or tab >>Selecting component sourcing options: A survey of software engineering's broader make-or-buy decisions
Show others...
2019 (English)In: Information and Software Technology, ISSN 0950-5849, E-ISSN 1873-6025, Vol. 112, p. 18-34Article in journal (Refereed) Published
Abstract [en]

Context: Component-based software engineering (CBSE) is a common approach to develop and evolve contemporary software systems. When evolving a system based on components, make-or-buy decisions are frequent, i.e., whether to develop components internally or to acquire them from external sources. In CBSE, several different sourcing options are available: (1) developing software in-house, (2) outsourcing development, (3) buying commercial-off-the-shelf software, and (4) integrating open source software components. Objective: Unfortunately, there is little available research on how organizations select component sourcing options (CSO) in industry practice. In this work, we seek to contribute empirical evidence to CSO selection. Method: We conduct a cross-domain survey on CSO selection in industry, implemented as an online questionnaire. Results: Based on 188 responses, we find that most organizations consider multiple CSOs during software evolution, and that the CSO decisions in industry are dominated by expert judgment. When choosing between candidate components, functional suitability acts as an initial filter, then reliability is the most important quality. Conclusion: We stress that future solution-oriented work on decision support has to account for the dominance of expert judgment in industry. Moreover, we identify considerable variation in CSO decision processes in industry. Finally, we encourage software development organizations to reflect on their decision processes when choosing whether to make or buy components, and we recommend using our survey for a first benchmarking. © 2019

Place, publisher, year, edition, pages
Elsevier B.V., 2019
Keywords
Component-based software engineering, Decision making, Software architecture, Sourcing, Survey, Decision support systems, Open systems, Software design, Surveying, Surveys, Commercial off-the-shelf softwares, Industry practices, Make-or-buy decisions, Online questionnaire, Software development organizations, Software Evolution, Open source software
National Category
Software Engineering
Identifiers
urn:nbn:se:bth-17871 (URN)10.1016/j.infsof.2019.03.015 (DOI)000469899100002 ()2-s2.0-85064013176 (Scopus ID)
Available from: 2019-05-02 Created: 2019-05-02 Last updated: 2019-06-20Bibliographically approved
Wnuk, K., Borg, M. & Gorschek, T. (2019). Towards new ways of evaluating methods of supporting requirements management and traceability using signal-to-noise ratio. In: ENASE 2019 - Proceedings of the 14th International Conference on Evaluation of Novel Approaches to Software Engineering: . Paper presented at 14th International Conference on Evaluation of Novel Approaches to Software Engineering, ENASE 2019, 4 May 2019 through 5 May 2019 (pp. 330-339). SciTePress
Open this publication in new window or tab >>Towards new ways of evaluating methods of supporting requirements management and traceability using signal-to-noise ratio
2019 (English)In: ENASE 2019 - Proceedings of the 14th International Conference on Evaluation of Novel Approaches to Software Engineering, SciTePress , 2019, p. 330-339Conference paper, Published paper (Refereed)
Abstract [en]

Developing contemporary software solutions requires many processes and people working in synergy to achieve a common goal. Any misalignment between parts of the software production cycle can severely impede the quality of the development process and its resulting products. In this paper, we focus on improving means for measuring the quality of methods used to support finding similarities between software product artifacts, especially requirements. We propose a new set of measures, Signal-to-Noise ratios which extends the commonly used precision and recall measures. We test the applicability of all three types of SNR on two methods for finding similar requirements: the normalized compression distance (NCD) originating from the domain of information theory, and the Vector Space Model originating from computer linguistics. The results obtained present an interesting property of all types of SNR, all the values are centered around 1 which confirms our hypothesis that the analyzed methods can only limit the search space for the analysis. The analyst may still have difficulties in manually assessing the correct links among the incorrect ones. Copyright © 2019 by SCITEPRESS - Science and Technology Publications, Lda. All rights reserved

Place, publisher, year, edition, pages
SciTePress, 2019
Keywords
Information Distance, Information Retrieval, Requirements Management, Traceability, Requirements engineering, Software engineering, Vector spaces, Development process, Normalized compression distance, Precision and recall, Software production, Vector space models, Signal to noise ratio
National Category
Software Engineering
Identifiers
urn:nbn:se:bth-18580 (URN)2-s2.0-85067445428 (Scopus ID)9789897583759 (ISBN)
Conference
14th International Conference on Evaluation of Novel Approaches to Software Engineering, ENASE 2019, 4 May 2019 through 5 May 2019
Available from: 2019-09-06 Created: 2019-09-06 Last updated: 2019-09-20Bibliographically approved
Wnuk, K. & Mudduluru, P. (2019). Value-based requirements engineering: Challenges and opportunities (830ed.). In: Kosiuczenko, P; Zielinski, Z (Ed.), ENGINEERING SOFTWARE SYSTEMS: RESEARCH AND PRAXIS. Paper presented at KKIO Software Engineering Conference,Pultusk, POLAND SEP 27-28, 2018 (pp. 20-33). Springer Verlag
Open this publication in new window or tab >>Value-based requirements engineering: Challenges and opportunities
2019 (English)In: ENGINEERING SOFTWARE SYSTEMS: RESEARCH AND PRAXIS / [ed] Kosiuczenko, P; Zielinski, Z, Springer Verlag , 2019, 830, p. 20-33Conference paper, Published paper (Refereed)
Abstract [en]

In this study, we investigate the state of the literature and practice about Value-Based Requirements Engineering. We focus on identifying what models for VBRE were presented and what challenges were discussed. We triangulate our results with industrial practitioners by conducting an industrial survey with 59 respondents. We identified 26 primary and 3 secondary studies and synthesized the findings using content analysis. VBRE was identified to be having a positive impact among survey practitioners. However, challenges like aligning product, project and organization opinions, selecting a most valuable requirement for a particular release, and including time-dependent requirements were identified to be impacting the organizations. The results from the study also suggest that, value dimensions like stakeholder value and customer value were not so frequently discussed in RE processes in both literature and among our industry respondents. © Springer Nature Switzerland AG 2019.

Place, publisher, year, edition, pages
Springer Verlag, 2019 Edition: 830
Series
Advances in Intelligent Systems and Computing, ISSN 2194-5357 ; 830
Keywords
Industrial challenges, Literature review, Value-based requirements engineering, Requirements engineering, Content analysis, Industrial practitioners, Industrial surveys, Literature reviews, Stakeholder values, Value dimensions, Value-based, Surveys
National Category
Software Engineering
Identifiers
urn:nbn:se:bth-17183 (URN)10.1007/978-3-319-99617-2_2 (DOI)000461025600002 ()2-s2.0-85054769950 (Scopus ID)
Conference
KKIO Software Engineering Conference,Pultusk, POLAND SEP 27-28, 2018
Available from: 2018-10-31 Created: 2018-10-31 Last updated: 2019-04-04Bibliographically approved
Badampudi, D., Wnuk, K., Wohlin, C., Franke, U., Šmite, D. & Cicchetti, A. (2018). A decision-making process-line for selection of software asset origins and components. Journal of Systems and Software, 135, 88-104
Open this publication in new window or tab >>A decision-making process-line for selection of software asset origins and components
Show others...
2018 (English)In: Journal of Systems and Software, ISSN 0164-1212, E-ISSN 1873-1228, Vol. 135, p. 88-104Article in journal (Refereed) Published
Abstract [en]

Selecting sourcing options for software assets and components is an important process that helps companies to gain and keep their competitive advantage. The sourcing options include: in-house, COTS, open source and outsourcing. The objective of this paper is to further refine, extend and validate a solution presented in our previous work. The refinement includes a set of decision-making activities, which are described in the form of a process-line that can be used by decision-makers to build their specific decision-making process. We conducted five case studies in three companies to validate the coverage of the set of decision-making activities. The solution in our previous work was validated in two cases in the first two companies. In the validation, it was observed that no activity in the proposed set was perceived to be missing, although not all activities were conducted and the activities that were conducted were not executed in a specific order. Therefore, the refinement of the solution into a process-line approach increases the flexibility and hence it is better in capturing the differences in the decision-making processes observed in the case studies. The applicability of the process-line was then validated in three case studies in a third company. © 2017 Elsevier Inc.

Place, publisher, year, edition, pages
Elsevier Inc., 2018
Keywords
Case study, Component-based software engineering, Decision-making, Competition, Concrete pavements, Open source software, Software engineering, Competitive advantage, Decision makers, Decision making process, Open sources, Selection of software, Software assets, Specific ordering, Decision making
National Category
Software Engineering
Identifiers
urn:nbn:se:bth-15512 (URN)10.1016/j.jss.2017.09.033 (DOI)000418308800006 ()2-s2.0-85032856583 (Scopus ID)
Available from: 2017-12-07 Created: 2017-12-07 Last updated: 2019-01-16Bibliographically approved
Organisations

Search in DiVA

Show all publications