Change search
Link to record
Permanent link

Direct link
Publications (10 of 166) Show all publications
Zabardast, E., Gonzalez-Huerta, J., Gorschek, T., Šmite, D., Alégroth, E. & Fagerholm, F. (2023). A taxonomy of assets for the development of software-intensive products and services. Journal of Systems and Software, 202, Article ID 111701.
Open this publication in new window or tab >>A taxonomy of assets for the development of software-intensive products and services
Show others...
2023 (English)In: Journal of Systems and Software, ISSN 0164-1212, E-ISSN 1873-1228, Vol. 202, article id 111701Article in journal (Refereed) Published
Abstract [en]

Context:Developing software-intensive products or services usually involves a plethora of software artefacts. Assets are artefacts intended to be used more than once and have value for organisations; examples include test cases, code, requirements, and documentation. During the development process, assets might degrade, affecting the effectiveness and efficiency of the development process. Therefore, assets are an investment that requires continuous management.

Identifying assets is the first step for their effective management. However, there is a lack of awareness of what assets and types of assets are common in software-developing organisations. Most types of assets are understudied, and their state of quality and how they degrade over time have not been well-understood.

Methods:We performed an analysis of secondary literature and a field study at five companies to investigate and identify assets to fill the gap in research. The results were analysed qualitatively and summarised in a taxonomy.

Results:We present the first comprehensive, structured, yet extendable taxonomy of assets, containing 57 types of assets.

Conclusions:The taxonomy serves as a foundation for identifying assets that are relevant for an organisation and enables the study of asset management and asset degradation concepts.

Place, publisher, year, edition, pages
Elsevier, 2023
Keywords
Assets in software engineering, Asset management in software engineering, Assets for software-intensive products or services, Taxonomy
National Category
Software Engineering
Identifiers
urn:nbn:se:bth-24426 (URN)10.1016/j.jss.2023.111701 (DOI)000984121100001 ()2-s2.0-85152899759 (Scopus ID)
Funder
Knowledge Foundation, 20170176Knowledge Foundation, 20180010
Available from: 2023-04-11 Created: 2023-04-11 Last updated: 2023-06-02Bibliographically approved
Yu, L., Alégroth, E., Chatzipetrou, P. & Gorschek, T. (2023). Automated NFR testing in continuous integration environments: a multi-case study of Nordic companies. Empirical Software Engineering, 28(6), Article ID 144.
Open this publication in new window or tab >>Automated NFR testing in continuous integration environments: a multi-case study of Nordic companies
2023 (English)In: Empirical Software Engineering, ISSN 1382-3256, E-ISSN 1573-7616, Vol. 28, no 6, article id 144Article in journal (Refereed) Published
Abstract [en]

Context: Non-functional requirements (NFRs) (also referred to as system qualities) are essential for developing high-quality software. Notwithstanding its importance, NFR testing remains challenging, especially in terms of automation. Compared to manual verification, automated testing shows the potential to improve the efficiency and effectiveness of quality assurance, especially in the context of Continuous Integration (CI). However, studies on how companies manage automated NFR testing through CI are limited. Objective: This study examines how automated NFR testing can be enabled and supported using CI environments in software development companies. Method: We performed a multi-case study at four companies by conducting 22 semi-structured interviews with industrial practitioners. Results: Maintainability, reliability, performance, security and scalability, were found to be evaluated with automated tests in CI environments. Testing practices, quality metrics, and challenges for measuring NFRs were reported. Conclusions: This study presents an empirically derived model that shows how data produced by CI environments can be used for evaluation and monitoring of implemented NFR quality. Additionally, the manuscript presents explicit metrics, CI components, tools, and challenges that shall be considered while performing NFR testing in practice. © 2023, The Author(s).

Place, publisher, year, edition, pages
Springer, 2023
Keywords
Automated testing, Case study, CI, Continuous integration, Metrics, NFR, Non-functional requirements, Automation, Integration, Integration testing, Quality control, Software design, Case-studies, Continuous integrations, Integration environments, Metric, Nordic companies, System quality, Quality assurance
National Category
Software Engineering
Identifiers
urn:nbn:se:bth-25556 (URN)10.1007/s10664-023-10356-1 (DOI)001087927600001 ()2-s2.0-85174862814 (Scopus ID)
Funder
Knowledge Foundation, 20180010Knowledge Foundation, 20170213
Available from: 2023-11-06 Created: 2023-11-06 Last updated: 2024-01-02Bibliographically approved
Bauer, A., Coppola, R., Alégroth, E. & Gorschek, T. (2023). Code review guidelines for GUI-based testing artifacts. Information and Software Technology, 163, Article ID 107299.
Open this publication in new window or tab >>Code review guidelines for GUI-based testing artifacts
2023 (English)In: Information and Software Technology, ISSN 0950-5849, E-ISSN 1873-6025, Vol. 163, article id 107299Article, review/survey (Refereed) Published
Abstract [en]

Context: Review of software artifacts, such as source or test code, is a common practice in industrial practice. However, although review guidelines are available for source and low-level test code, for GUI-based testing artifacts, such guidelines are missing. Objective: The goal of this work is to define a set of guidelines from literature about production and test code, that can be mapped to GUI-based testing artifacts. Method: A systematic literature review is conducted, using white and gray literature to identify guidelines for source and test code. These synthesized guidelines are then mapped, through examples, to create actionable, and applicable, guidelines for GUI-based testing artifacts. Results: The results of the study are 33 guidelines, summarized in nine guideline categories, that are successfully mapped as applicable to GUI-based testing artifacts. Of the collected literature, only 10 sources contained test-specific code review guidelines. These guideline categories are: perform automated checks, use checklists, provide context information, utilize metrics, ensure readability, visualize changes, reduce complexity, check conformity with the requirements and follow design principles and patterns. Conclusion: This pivotal set of guidelines provides an industrial contribution in filling the gap of general guidelines for review of GUI-based testing artifacts. Additionally, this work highlights, from an academic perspective, the need for future research in this area to also develop guidelines for other specific aspects of GUI-based testing practice, and to take into account other facets of the review process not covered by this work, such as reviewer selection. © 2023 The Author(s)

Place, publisher, year, edition, pages
Elsevier, 2023
Keywords
Code review, GUI testing, GUI-based testing, Guidelines, Modern code review, Practices, Software testing, Graphical user interfaces, Guideline, Practice, Software testings, Source codes, Test code
National Category
Software Engineering
Identifiers
urn:nbn:se:bth-25235 (URN)10.1016/j.infsof.2023.107299 (DOI)001051358500001 ()2-s2.0-85165535690 (Scopus ID)
Funder
Knowledge Foundation, 20180010
Available from: 2023-08-08 Created: 2023-08-08 Last updated: 2023-09-18Bibliographically approved
Sjöberg, P., Mendez, D. & Gorschek, T. (2023). Contemporary Challenges when Developing Cyber-Physical Systems of Systems - A Case Study. In: Proceedings - 2023 IEEE/ACM 11th International Workshop on Software Engineering for Systems-of-Systems and Software Ecosystems, SESoS 2023: . Paper presented at 11th IEEE/ACM International Workshop on Software Engineering for Systems-of-Systems and Software Ecosystems, SESoS 2023, Hybrid, Melbourne, 14 May 2023 (pp. 46-53). Institute of Electrical and Electronics Engineers (IEEE)
Open this publication in new window or tab >>Contemporary Challenges when Developing Cyber-Physical Systems of Systems - A Case Study
2023 (English)In: Proceedings - 2023 IEEE/ACM 11th International Workshop on Software Engineering for Systems-of-Systems and Software Ecosystems, SESoS 2023, Institute of Electrical and Electronics Engineers (IEEE), 2023, p. 46-53Conference paper, Published paper (Refereed)
Abstract [en]

Digitalization has created service business opportunities for machine manufacturing companies. But creating these cyber-physical systems of systems effectively constitutes a critical measure of success in practice. At the same time, the body of knowledge in software engineering provides little guidance on how to manage this evolution. To contribute to closing this gap in the long run via problem-driven research, we need to first understand which contemporary challenges and needs are encountered in industry. To this end, we conducted a series of semi-structured interviews at a machine manufacturing company, that is expanding its service offerings utilizing digitalization, where we explored how such systems are engineered and what challenges and needs are encountered. © 2023 IEEE.

Place, publisher, year, edition, pages
Institute of Electrical and Electronics Engineers (IEEE), 2023
Keywords
Case Study, Cyber-physical systems, Information and communication technology, Internet of things, Interview Study, System of systems, Cyber Physical System, Embedded systems, Software engineering, Business opportunities, Case-studies, Cybe-physical systems, Information and Communication Technologies, Machine manufacturing, Manufacturing companies, Service business, System-of-systems
National Category
Software Engineering
Identifiers
urn:nbn:se:bth-25351 (URN)10.1109/SESoS59159.2023.00012 (DOI)001042226500008 ()2-s2.0-85169121482 (Scopus ID)9798350301748 (ISBN)
Conference
11th IEEE/ACM International Workshop on Software Engineering for Systems-of-Systems and Software Ecosystems, SESoS 2023, Hybrid, Melbourne, 14 May 2023
Funder
Knowledge Foundation, 20170213Knowledge Foundation, 20180010
Available from: 2023-09-08 Created: 2023-09-08 Last updated: 2023-09-08Bibliographically approved
Klotins, E., Gorschek, T. & Wilson, M. (2023). Continuous Software Engineering: Introducing an Industry Readiness Model. IEEE Software, 40(4), 77-87
Open this publication in new window or tab >>Continuous Software Engineering: Introducing an Industry Readiness Model
2023 (English)In: IEEE Software, ISSN 0740-7459, E-ISSN 1937-4194, Vol. 40, no 4, p. 77-87Article in journal (Refereed) Published
Abstract [en]

Software is becoming essential for most products, manufacturing processes, and back-office functions. The speed of delivering new features and refining the product is critical to remaining competitive. Software organizations may adopt continuous engineering practices to become more efficient. However, retrofitting an organization with a pipeline is challenging. Importantly, the most significant challenges and opportunities, are related to, but stem from outside the engineering realm and require rethinking customer relationships and business models. This paper presents a hierarchy of continuous engineering benefits and challenges. It is aimed to guide the adoption of continuous practices in an organization to determine the current and target level of adoption, given organizational context, ambitions, and domain constraints. IEEE

Place, publisher, year, edition, pages
IEEE Computer Society, 2023
Keywords
Automation, Companies, Investment, Pipelines, Software, Software engineering, Testing, Public relations, Software testing, Back office, Continuous software engineerings, Customer relationships, Engineering practices, Manufacturing process, Product manufacturing, Readiness models, Relationship model, Software organization
National Category
Software Engineering
Identifiers
urn:nbn:se:bth-24486 (URN)10.1109/MS.2023.3263190 (DOI)001032645500012 ()2-s2.0-85153369631 (Scopus ID)
Available from: 2023-05-05 Created: 2023-05-05 Last updated: 2023-08-11Bibliographically approved
Alexandre, R. C., Martins, L. E. & Gorschek, T. (2023). Cybersecurity Risk Assessment for Medium-Risk Drones: A Systematic Literature Review. IEEE Aerospace and Electronic Systems Magazine, 38(6), 28-43
Open this publication in new window or tab >>Cybersecurity Risk Assessment for Medium-Risk Drones: A Systematic Literature Review
2023 (English)In: IEEE Aerospace and Electronic Systems Magazine, ISSN 0885-8985, E-ISSN 1557-959X, Vol. 38, no 6, p. 28-43Article, review/survey (Refereed) Published
Abstract [en]

The increased demand for Remotely Piloted Aircraft Systems (RPAS) in Beyond Visual Line-Of-Sight (BVLOS) operations gives rise to a set of concerns regarding cybersecurity that, if not addressed, can lead to the unsafe operation of RPASs. To assist the airworthiness evaluation that is performed by Civil Aviation Authorities (CAAs), we identified several processes that are used to evaluate the cybersecurity of RPAS. We conducted a Systematic Literature Review (SLR) by selecting 30 papers (out of 211 screened) that were published during the past five years. The results of our SLR indicate the importance of cybersecurity to the safe operation of RPAS. It is evident that there is a lack of a systematic process to enable a cybersecurity review of RPAS. We observe that common cyber threats to RPAS are related to jamming, spoofing, and DOS/DDOS (Denial of Service/Distributed Denial of Service). Processes relevant to the assessment of RPAS cybersecurity exist, however they differ in safety concerns from our perspective. In addition, with only one exception, the methods have not been used, and/or the use has not been reported as pertaining to industrial application. The most frequently cited vulnerabilities are those related to GPS and datalinks. 

Place, publisher, year, edition, pages
Institute of Electrical and Electronics Engineers (IEEE), 2023
Keywords
Cybersecurity, Denial-of-service attack, NASA, Remote control, Risk assessment, Safety engineering, Software engineering, Aircraft systems, Airworthiness, Beyond visual line-of-sight, Conops, Cyber security, Line of Sight, Lines-of-sight, Regulation, Remotely piloted aircraft, Remotely piloted aircraft system, Risks assessments, UAS, Visual line, Vulnerability, Drones, Aircraft, BVLOS, Computer security, RPAS, Safety, Visualization, vulnerabilities
National Category
Software Engineering Computer Systems
Identifiers
urn:nbn:se:bth-24375 (URN)10.1109/MAES.2023.3251969 (DOI)001004539500003 ()2-s2.0-85149452274 (Scopus ID)
Funder
Knowledge Foundation, 20180010
Available from: 2023-03-17 Created: 2023-03-17 Last updated: 2023-08-08Bibliographically approved
Peixoto, M., Silva, C., Araújo, J., Gorschek, T., Vasconcelos, A. & Vilela, J. (2023). Evaluating a privacy requirements specification method by using a mixed-method approach: results and lessons learned. Requirements Engineering, 28(2), 229-255
Open this publication in new window or tab >>Evaluating a privacy requirements specification method by using a mixed-method approach: results and lessons learned
Show others...
2023 (English)In: Requirements Engineering, ISSN 0947-3602, E-ISSN 1432-010X, Vol. 28, no 2, p. 229-255Article in journal (Refereed) Published
Abstract [en]

Although agile software development (ASD) has been adopted in the industry, requirements approaches for ASD still neglect non-functional requirements. Privacy has become a concern due to new user demands and data protection laws. Hence, privacy needs to be properly specified, but agile requirements engineering techniques do not explicitly represent privacy requirements and, therefore, are not able to proper analyze such requirements. In this context, Privacy Criteria Method (PCM), an approach to specify privacy in requirements activities, was proposed to produce more complete and detailed privacy requirements. By considering PCM a promising approach to be used in ASD and the importance of empirical evaluation of new methods, we have as objectives: 1 evaluate the ability of PCM to support systems analysts in specifying privacy requirements when used in conjunction with some agile specification methods; and 2 show our lessons learned in conducting empirical research based on an mix-method approach defined to empirically evaluate the suitability of a requirements specification in specifying privacy requirements. Mixed-method approach is a controlled experiment as a quantitative evaluation and a feasibility study (questionnaire and task analysis based) study as a qualitative and quantitative evaluation. The requirements specifications following PCM allow to represent privacy aspects, such as user’s personal data and the privacy mechanism that can be used to mitigate a privacy risk scenario. We also observed that some extra time is necessary to specify privacy requirements with PCM, but it does not imply a greater perceived effort. Specifications produced with PCM are of good quality and more privacy detailed. Additionally, we attest to the importance of conducting empirical research to evaluate new methods. PCM assists in specifying more complete and detailed in relation to traditional techniques used in ASD, which facilitates communication between the requirements analysts and developers. © 2022, The Author(s), under exclusive licence to Springer-Verlag London Ltd., part of Springer Nature.

Place, publisher, year, edition, pages
Springer Science+Business Media B.V., 2023
Keywords
Agile software development, Empirical study, Privacy criteria method, Privacy requirements specification, Job analysis, Requirements engineering, Risk perception, Software design, Specifications, Empirical research, Empirical studies, Industry requirements, Mixed method, Privacy requirement specification, Privacy requirements, Quantitative evaluation, Requirements specifications, Data privacy
National Category
Software Engineering
Identifiers
urn:nbn:se:bth-23724 (URN)10.1007/s00766-022-00388-2 (DOI)000857797700001 ()2-s2.0-85138227443 (Scopus ID)
Funder
Knowledge Foundation, 20180010
Available from: 2022-10-06 Created: 2022-10-06 Last updated: 2023-06-19Bibliographically approved
Fabiola Moyón, C., Mendez, D., Gorschek, T., Angermeir, F., Bonvin, P.-L. & Voggenreiter, M. (2023). RefA: Reference Architecture for Security-compliant DevOps. Karlskrona
Open this publication in new window or tab >>RefA: Reference Architecture for Security-compliant DevOps
Show others...
2023 (English)Report (Refereed)
Abstract [en]

This technical report presents RefA, a reference architecture for security-compliant DevOps. RefA consists of a set of models that illustrate the artefacts and practice areas to consider when implementing secure DevOps lifecycles. In addition, RefA describes people, proceses, and technology aspects to be considered in each practice area. Practitioners can use RefA for the purposes of designing and assessing security compliance of their DevOps lifecycles, while researchers may use RefA as a reference for setting up research roadmaps. RefA models result from combining the profound analysis of the IEC 62443-4-1 standard for secure industrial products development, continuous software engineering literature review, and observations made in practice in context of a large industrial company during the past 5 years. The manuscript constitutes original, previously unpublished research.

Place, publisher, year, edition, pages
Karlskrona: , 2023. p. 112
Series
Blekinge Tekniska Högskola Forskningsrapport, ISSN 1103-1581 ; 2023:01
Keywords
DevOps, Secure software engineering, DevSecOps, Security compliance, Continuous software engineering
National Category
Software Engineering
Identifiers
urn:nbn:se:bth-24873 (URN)BTH-RES-01/23-SE (ISRN)
Available from: 2023-06-20 Created: 2023-06-20 Last updated: 2023-06-20Bibliographically approved
Peixoto, M., Ferreira, D., Cavalcanti, M., Silva, C., Vilela, J., Araújo, J. & Gorschek, T. (2023). The perspective of Brazilian software developers on data privacy. Journal of Systems and Software, 195, Article ID 111523.
Open this publication in new window or tab >>The perspective of Brazilian software developers on data privacy
Show others...
2023 (English)In: Journal of Systems and Software, ISSN 0164-1212, E-ISSN 1873-1228, Vol. 195, article id 111523Article in journal (Refereed) Published
Abstract [en]

Context: Maintaining the privacy of user data is a concern in software development to satisfy customer needs or to comply with privacy laws. Recent studies have shown that software development approaches still neglect non-functional requirements, including privacy. Concern about privacy may increase in the period between when a privacy law is initially announced and when it is passed into law. During this period, companies will be challenged to comply with the new law. Research has shown that many developers do not have sufficient knowledge to develop privacy-preserving software systems.

Objective: We investigate the level of knowledge and understanding that developers possess regarding privacy. We explore the personal, behavioural, and external environmental factors affecting a developer's decision-making regarding privacy requirements.

Methods: We replicated a study by means of in-depth, semi-structured interviews with thirteen practitioners at six companies. Our data analysis is based on the principles of ‘grounded theory codification’.

Results: We identified nine personal factors, five behavioural factors, and seven external environment factors that are relevant to how software developers make decisions regarding.

Conclusion: Our identification of factors that influence the development of privacy-preserving software systems can be seen as a contribution to the specification of effective methods for securing privacy. © 2022 Elsevier Inc.

Place, publisher, year, edition, pages
Elsevier, 2023
Keywords
Computer software, Customer satisfaction, Privacy-preserving techniques, Software design, Customer need, Empirical studies, Non-functional requirements, Privacy law, Privacy preserving, Privacy requirements, Software developer, Software development approach, Software-systems, User data, Decision making, Empirical study, Software development
National Category
Software Engineering
Identifiers
urn:nbn:se:bth-23859 (URN)10.1016/j.jss.2022.111523 (DOI)000875835500004 ()2-s2.0-85139857676 (Scopus ID)
Funder
Knowledge Foundation, 20180010
Available from: 2022-11-08 Created: 2022-11-08 Last updated: 2022-11-10Bibliographically approved
Ouriques, R., Wnuk, K., Gorschek, T. & Svensson, R. B. (2023). The role of knowledge-based resources in Agile Software Development contexts. Journal of Systems and Software, 197, Article ID 111572.
Open this publication in new window or tab >>The role of knowledge-based resources in Agile Software Development contexts
2023 (English)In: Journal of Systems and Software, ISSN 0164-1212, E-ISSN 1873-1228, Vol. 197, article id 111572Article in journal (Refereed) Published
Abstract [en]

The software value chain is knowledge-based since it is highly dependant on people. Consequently, a lack of practice in managing knowledge as a resource may jeopardise its application in software development. Knowledge-Based Resources (KBRs) relate to employees’ intangible knowledge that is deemed to be valuable to a company's competitive advantage. In this study, we apply a grounded theory approach to examine the role of KBRs in Agile Software Development (ASD). To this aim, we collected data from 18 practitioners from five companies. We develop the Knowledge-Push theory, which explains how KBRs boost the need for change in ASD. Our results show that the practitioners who participated in the study utilise, as primary strategies, task planning, resource management, and social collaboration. These strategies are implemented through the team environment and settings and incorporate an ability to codify and transmit knowledge. However, this process of codification is non-systematic, which consequently introduces inefficiency in the domain of knowledge resource utilisation, resulting in potential knowledge waste. This inefficiency can generate negative implications for software development, including meaningless searches in databases, frustration because of recurrent problems, the unnecessary redesign of solutions, and a lack of awareness of knowledge sources. © 2022 The Authors

Place, publisher, year, edition, pages
Elsevier, 2023
Keywords
Application programs, Competition, Knowledge based systems, Software design, Agile software development, Competitive advantage, Grounded theory, Grounded theory approach, ITS applications, Knowledge based, Knowledge-based resources, Resource management, Task planning, Value chains, Knowledge management, Software development
National Category
Software Engineering
Identifiers
urn:nbn:se:bth-24144 (URN)10.1016/j.jss.2022.111572 (DOI)000903909200003 ()2-s2.0-85144082256 (Scopus ID)
Funder
Knowledge Foundation, 20180010
Note

open access

Available from: 2022-12-30 Created: 2022-12-30 Last updated: 2023-08-18Bibliographically approved
Projects
PLEng – Professional Licentiate of Engineering School [20170213]; Blekinge Institute of Technology; Publications
Yu, L., Alégroth, E., Chatzipetrou, P. & Gorschek, T. (2023). Automated NFR testing in continuous integration environments: a multi-case study of Nordic companies. Empirical Software Engineering, 28(6), Article ID 144. Sjöberg, P., Mendez, D. & Gorschek, T. (2023). Contemporary Challenges when Developing Cyber-Physical Systems of Systems - A Case Study. In: Proceedings - 2023 IEEE/ACM 11th International Workshop on Software Engineering for Systems-of-Systems and Software Ecosystems, SESoS 2023: . Paper presented at 11th IEEE/ACM International Workshop on Software Engineering for Systems-of-Systems and Software Ecosystems, SESoS 2023, Hybrid, Melbourne, 14 May 2023 (pp. 46-53). Institute of Electrical and Electronics Engineers (IEEE)Singh, S. P., Ali, N. b. & Lundberg, L. (2022). Smart and Adaptive Architecture for a Dedicated Internet of Things Network Comprised of Diverse Entities: A Proposal and Evaluation. Sensors, 22(8), Article ID 3017. Sundelin, A., Gonzalez-Huerta, J., Wnuk, K. & Gorschek, T. (2022). Towards an Anatomy of Software Craftsmanship. ACM Transactions on Software Engineering and Methodology, 31(1), Article ID 6. wilson, M. & Wnuk, K. (2018). Towards Multi-context Goal Modeling and Analysis with the Help of Intents. In: Moreira A.,Mussbacher G.,Sanchez P.,Araujo J. (Ed.), Proceedings - 2018 8th International Model-Driven Requirements Engineering Workshop, MoDRE 2018: . Paper presented at 8th International Model-Driven Requirements Engineering Workshop, MoDRE 2018; Banff; Canada; 20 August 2018 (pp. 68-72). IEEE Computer Society Digital Library, Article ID 8501496.
SERT- Software Engineering ReThought [20180010]; Blekinge Institute of Technology; Publications
Treidler, O., Kunz, T.-E., Capraro, M. & Dorner, M. (2024). Sustaining Arm’s Length Cost Allocations for Highly Integrated Development Functions: An Explorative Case Study of Transfer Pricing for InnerSource Communities. Karlskrona: Blekinge Tekniska HögskolaUnterkalmsteiner, M. & Abdeen, W. (2023). A compendium and evaluation of taxonomy quality attributes. Expert systems (Print), 40(1), Article ID e13098. Zabardast, E., Gonzalez-Huerta, J., Gorschek, T., Šmite, D., Alégroth, E. & Fagerholm, F. (2023). A taxonomy of assets for the development of software-intensive products and services. Journal of Systems and Software, 202, Article ID 111701. Tanveer, B., Zabardast, E. & Gonzalez-Huerta, J. (2023). An approach to align socio-technical dependencies in large-scale software development. In: Proceedings - IEEE 20th International Conference on Software Architecture Companion, ICSA-C 2023: . Paper presented at 20th IEEE International Conference on Software Architecture Companion, ICSA-C 2023, L'Aquila, 13 March through 17 March 2023 (pp. 341-347). Institute of Electrical and Electronics Engineers (IEEE)Frattini, J., Fucci, D., Mendez, D., Spinola, R., Mandic, V., Tausan, N., . . . Gonzalez-Huerta, J. (2023). An initial Theory to Understand and Manage Requirements Engineering Debt in Practice. Information and Software Technology, 159, Article ID 107201. Ouriques, R., Fagerholm, F., Mendez, D. & Bern, B. G. (2023). An investigation of causes and effects of trust in Boundary Artefacts. Information and Software Technology, 158, Article ID 107170. Yu, L., Alégroth, E., Chatzipetrou, P. & Gorschek, T. (2023). Automated NFR testing in continuous integration environments: a multi-case study of Nordic companies. Empirical Software Engineering, 28(6), Article ID 144. Fischbach, J., Frattini, J., Vogelsang, A., Mendez, D., Unterkalmsteiner, M., Wehrle, A., . . . Wiecher, C. (2023). Automatic creation of acceptance tests by extracting conditionals from requirements: NLP approach and case study. Journal of Systems and Software, 197, Article ID 111549. Frattini, J., Fischbach, J., Mendez, D., Unterkalmsteiner, M., Vogelsang, A. & Wnuk, K. (2023). Causality in requirements artifacts: prevalence, detection, and impact. Requirements Engineering, 28(1), 49-74Frattini, J., Fischbach, J. & Bauer, A. (2023). CiRA: An Open-Source Python Package for Automated Generation of Test Case Descriptions from Natural Language Requirements. In: Schneider K., Dalpiaz F., Horkoff J. (Ed.), Proceedings - 31st IEEE International Requirements Engineering Conference Workshops, REW 2023: . Paper presented at 31st IEEE International Requirements Engineering Conference Workshops, REW 2023, Hannover, 4 Sept - 8 Sept 2023 (pp. 68-71). Institute of Electrical and Electronics Engineers (IEEE)
Professional Master in Information Security (PROMIS) [20210026]; Blekinge Institute of Technology; Publications
Bendler, D. & Felderer, M. (2023). Competency Models for Information Security and Cybersecurity Professionals: Analysis of Existing Work and a New Model. ACM Transactions on Computing Education, 23(2), Article ID 25. Nygren, Å., Alégroth, E., Eriksson, A. & Pettersson, E. (2023). Does Previous Experience with Online Platforms Matter? A Survey about Online Learning across Study Programs. Education Sciences, 13(2), Article ID 181.
Organisations
Identifiers
ORCID iD: ORCID iD iconorcid.org/0000-0002-3646-235x

Search in DiVA

Show all publications