SwePub
Sök i SwePub databas

  Utökad sökning

Träfflista för sökning "WFRF:(Gorschek Tony 1972 ) "

Sökning: WFRF:(Gorschek Tony 1972 )

  • Resultat 1-50 av 89
Sortera/gruppera träfflistan
   
NumreringReferensOmslagsbildHitta
1.
  • Pernstal, J., et al. (författare)
  • FLEX-RCA: a lean-based method for root cause analysis in software process improvement
  • 2019
  • Ingår i: Software Quality Journal. - : Springer Science and Business Media LLC. - 1573-1367 .- 0963-9314. ; 27:1, s. 389-428
  • Tidskriftsartikel (refereegranskat)abstract
    • Software process improvement (SPI) is an instrument to increase the productivity of, and the quality of work, in software organizations. However, a majority of SPI frameworks are too extensive or provide guidance and potential improvement areas at a high level, indicating only the symptoms, not the causes. Motivated by the industrial need of two Swedish automotive companies to systematically uncover the underlying root causes of high-level improvement issues identified in an SPI project-assessing inter-departmental interactions in large-scale software systems development-this paper advances a root cause analysis (RCA) method building on Lean Six Sigma, called Flex-RCA. Flex-RCA is used to delve deeper into challenges identified to find root causes as a part of the evaluation and subsequent improvement activities. We also demonstrate and evaluate Flex-RCA's industrial applicability in a case study. An overall conclusion is that the use of Flex-RCA was successful, showing that it had the desired effect of both producing a broad base of causes on a high level and, more importantly, enabling an exploration of the underlying root causes.
  •  
2.
  • Pernstål, Joakim, et al. (författare)
  • Communication Problems in Software Development : A Model and Its Industrial Application
  • 2019
  • Ingår i: International journal of software engineering and knowledge engineering. - : World Scientific Publishing Co. Pte Ltd. - 0218-1940. ; 29:10, s. 1497-1538
  • Tidskriftsartikel (refereegranskat)abstract
    • Attaining effective communication within and across organizational units is among the most critical challenges for success in software development organizations. This paper presents a novel model, supporting analysis of problems in inter-departmental communication events. The model was developed and designed based on industrial needs emphasizing flexibility, applicability and scalability. The model covers central communication aspects in order to provide a useful approximation of communication problems rather than in-depth modeling on message-by message basis. Other event-specific information, such as costs, can then be attached to enrich analysis and understanding. To exemplify and evaluate the model and collect feedback from industry, it was applied to 16 events at a Swedish automotive manufacturer where communication between two departments had broken down during development of software-intensive systems. The evaluation showed that the model helped structure and conduct systematic data collection and analysis of dysfunctional communication patterns. We found that insufficient understanding of the matters being communicated was prevalent, but also more specifically, requirements were insufficiently balanced, detailed and specified over the full system development cycle. Besides, the long-term cost for the company was analyzed in depth for each event, yielding a total estimated cost for the analyzed communication events of 11.2MUS$. © 2019 World Scientific Publishing Company.
  •  
3.
  • Afzal, Wasif, et al. (författare)
  • Genetic programming for cross-release fault count predictions in large and complex software projects
  • 2010
  • Ingår i: Evolutionary Computation and Optimization Algorithms in Software Engineering. - : IGI Global, Hershey, USA. - 9781615208098
  • Bokkapitel (refereegranskat)abstract
    • Software fault prediction can play an important role in ensuring software quality through efficient resource allocation. This could, in turn, reduce the potentially high consequential costs due to faults. Predicting faults might be even more important with the emergence of short-timed and multiple software releases aimed at quick delivery of functionality. Previous research in software fault prediction has indicated that there is a need i) to improve the validity of results by having comparisons among number of data sets from a variety of software, ii) to use appropriate model evaluation measures and iii) to use statistical testing procedures. Moreover, cross-release prediction of faults has not yet achieved sufficient attention in the literature. In an attempt to address these concerns, this paper compares the quantitative and qualitative attributes of 7 traditional and machine-learning techniques for modeling the cross-release prediction of fault count data. The comparison is done using extensive data sets gathered from a total of 7 multi-release open-source and industrial software projects. These software projects together have several years of development and are from diverse application areas, ranging from a web browser to a robotic controller software. Our quantitative analysis suggests that genetic programming (GP) tends to have better consistency in terms of goodness of fit and accuracy across majority of data sets. It also has comparatively less model bias. Qualitatively, ease of configuration and complexity are less strong points for GP even though it shows generality and gives transparent models. Artificial neural networks did not perform as well as expected while linear regression gave average predictions in terms of goodness of fit and accuracy. Support vector machine regression and traditional software reliability growth models performed below average on most of the quantitative evaluation criteria while remained on average for most of the qualitative measures.
  •  
4.
  • Alahyari, Hiva, 1979, et al. (författare)
  • An exploratory study of waste in software development organizations using agile or lean approaches : A multiple case study at 14 organizations
  • 2019
  • Ingår i: Information and Software Technology. - : Elsevier B.V.. - 0950-5849 .- 1873-6025. ; 107, s. 78-94
  • Tidskriftsartikel (refereegranskat)abstract
    • Context: The principal focus of lean is the identification and elimination of waste from the process with respect to maximizing customer value. Similarly, the purpose of agile is to maximize customer value and minimize unnecessary work and time delays. In both cases the concept of waste is important. Through an empirical study, we explore how waste is approached in agile software development organizations. Objective: This paper explores the concept of waste in agile/lean software development organizations and how it is defined, used, prioritized, reduced, or eliminated in practice Method: The data were collected using semi-structured open-interviews. 23 practitioners from 14 embedded software development organizations were interviewed representing two core roles in each organization. Results: Various wastes, categorized in 10 different categories, were identified by the respondents. From the mentioned wastes, not all were necessarily waste per se but could be symptoms caused by wastes. From the seven wastes of lean, Task-switching was ranked as the most important, and Extra-features, as the least important wastes according to the respondents’ opinion. However, most companies do not have their own or use an established definition of waste, more importantly, very few actively identify or try to eliminate waste in their organizations beyond local initiatives on project level. Conclusion: In order to identify, recognize and eliminate waste, a common understanding, and a joint and holistic view of the concept is needed. It is also important to optimize the whole organization and the whole product, as waste on one level can be important on another, thus sub-optimization should be avoided. Furthermore, to achieve a sustainable and effective waste handling, both the short-term and the long-term perspectives need to be considered. © 2018 Elsevier B.V.
  •  
5.
  • Alégroth, Emil, 1984-, et al. (författare)
  • Characteristics that affect Preference of Decision Models for Asset Selection : An Industrial Questionnaire Survey
  • 2020
  • Ingår i: Software quality journal. - : Springer. - 0963-9314 .- 1573-1367. ; 28:4, s. 1675-1707
  • Tidskriftsartikel (refereegranskat)abstract
    • Modern software development relies on a combination of development and re-use of technical asset, e.g. software components, libraries and APIs.In the past, re-use was mostly conducted with internal assets but today external; open source, customer off-the-shelf (COTS) and assets developed through outsourcing are also common.This access to more asset alternatives presents new challenges regarding what assets to optimally chose and how to make this decision.To support decision-makers, decision-theory has been used to develop decision models for asset selection.However, very little industrial data has been presented in literature about the usefulness, or even perceived usefulness, of these models.Additionally, only limited information has been presented about what model characteristics that determine practitioner preference towards one model over another.Objective: The objective of this work is to evaluate what characteristics of decision models for asset selection that determine industrial practitioner preference of a model when given the choice of a decision-model of high precision or a model with high speed.Method: An industrial questionnaire survey is performed where a total of 33 practitioners, of varying roles, from 18 companies are tasked to compare two decision models for asset selection.Textual analysis and formal and descriptive statistics are then applied on the survey responses to answer the study's research questions.Results: The study shows that the practitioners had clear preference towards the decision model that emphasised speed over the one that emphasised decision precision.This conclusion was determined to be because one of the models was perceived faster, had lower complexity, had, was more flexible in use for different decisions, was more agile how it could be used in operation, its emphasis on people, its emphasis on ``good enough'' precision and ability to fail fast if a decision was a failure.Hence, seven characteristics that the practitioners considered important for their acceptance of the model.Conclusion: Industrial practitioner preference, which relates to acceptance, of decision models for asset selection is dependent on multiple characteristics that must be considered when developing a model for different types of decisions such as operational day-to-day decisions as well as more critical tactical or strategic decisions.The main contribution of this work are seven identified characteristics that can serve as industrial requirements for future research on decision models for asset selection.
  •  
6.
  •  
7.
  • Alexandre, Rui Carlos Josino, et al. (författare)
  • Cybersecurity Risk Assessment for Medium-Risk Drones : A Systematic Literature Review
  • 2023
  • Ingår i: IEEE Aerospace and Electronic Systems Magazine. - : Institute of Electrical and Electronics Engineers (IEEE). - 0885-8985 .- 1557-959X. ; 38:6, s. 28-43
  • Forskningsöversikt (refereegranskat)abstract
    • 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. 
  •  
8.
  • Badampudi, Deepika, 1984-, et al. (författare)
  • An Evaluation of Knowledge Translation in Software Engineering
  • 2019
  • Ingår i: International Symposium on Empirical Software Engineering and Measurement. - : IEEE Computer Society. - 9781728129686 ; , s. 13-18
  • Konferensbidrag (refereegranskat)abstract
    • Knowledge translation is defined, in health sciences, as 'the exchange, synthesis and ethically sound application of research results in practice'. The objective of this paper is to implement and conduct a feasibility evaluation of a knowledge translation framework in software engineering. We evaluated the outcome of the knowledge translation framework in an industrial setting, along with the effectiveness of the interventions undertaken as part of knowledge translation in a multi-case study. The results of the evaluation suggest that the practitioners perceive the knowledge translation framework to be valuable and useful. In conclusion, this paper contributes towards the reporting of a systematic implementation of knowledge translation and evaluating its use in software engineering. © 2019 IEEE.
  •  
9.
  • Badampudi, Deepika, 1984-, et al. (författare)
  • Contextualizing research evidence through knowledge translation in software engineering
  • 2019
  • Ingår i: PROCEEDINGS OF EASE 2019 - EVALUATION AND ASSESSMENT IN SOFTWARE ENGINEERING. - New York, NY, USA : Association for Computing Machinery. - 9781450371452 ; , s. 306-311
  • Konferensbidrag (refereegranskat)abstract
    • Usage of software engineering research in industrial practice is a well-known challenge. Synthesis of knowledge from multiple research studies is needed to provide evidence-based decision-support for industry. The objective of this paper is to present a vision of how a knowledge translation framework may look like in software engineering research, in particular how to translate research evidence into practice by combining contextualized expert opinions with research evidence. We adopted the framework of knowledge translation from health care research, adapted and combined it with a Bayesian synthesis method. The framework provided in this paper includes a description of each step of knowledge translation in software engineering. Knowledge translation using Bayesian synthesis intends to provide a systematic approach towards contextualized, collaborative and consensus-driven application of research results. In conclusion, this paper contributes towards the application of knowledge translation in software engineering through the presented framework. © 2019 Association for Computing Machinery.
  •  
10.
  •  
11.
  • Bauer, Andreas, et al. (författare)
  • Code review guidelines for GUI-based testing artifacts
  • 2023
  • Ingår i: Information and Software Technology. - : Elsevier. - 0950-5849 .- 1873-6025. ; 163
  • Forskningsöversikt (refereegranskat)abstract
    • 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)
  •  
12.
  • Berntsson Svensson, Richard, 1978-, et al. (författare)
  • BAM : backlog assessment method
  • 2019
  • Ingår i: Lecture Notes in Business Information Processing. - Cham : Springer Verlag. - 1865-1348. - 9783030190330 ; , s. 53-68
  • Konferensbidrag (refereegranskat)abstract
    • The necessity of software as stand-alone products, and as central parts of non-traditional software products have changed how software products are developed. It started with the introduction of the agile manifesto and has resulted in a change of how software process improvements (SPI) are conducted. Although there are agile SPI methods and several agile practices for evaluating and improving current processes and ways-of-working, no method or practices for evaluating the backlog exists. To address this gap, the Backlog Assessment Method (BAM) was developed and applied in collaboration with Telenor Sweden. BAM enables agile organizations to assess backlogs, and assure that the backlog items are good-enough for their needs and well aligned with the decision process. The results from the validation show that BAM is feasible and relevant in an industrial environment, and it indicates that BAM is useful as a tool to perform analysis of items in a specific backlog. © The Author(s) 2019.
  •  
13.
  • Berntsson Svensson, Richard, 1978, et al. (författare)
  • Quality Requirements in Industrial Practice - An Extended Interview Study at Eleven Companies
  • 2011
  • Ingår i: IEEE Transactions on Software Engineering. - 0098-5589 .- 1939-3520.
  • Tidskriftsartikel (refereegranskat)abstract
    • In order to create a successful software product and assure its quality, it is not enough to fulfill the functional requirements, it is also crucial to find the right balance among competing quality requirements (QR). An extended, previously piloted, interview study was performed to identify specific challenges associated with the selection, trade-off, and management of QR in industrial practice. Data was collected through semi-structured interviews with eleven product managers and eleven project leaders from eleven software companies. The contribution of this study is fourfold: First, it compares how QR are handled in two cases, companies working in business-to-business markets, and companies that are working in business-to-consumer markets. These two are also compared in terms of impact on the handling of QRs. Second, it compares the perceptions and priorities of QR by product and project management respectively. Third, it includes an examination of the interdependencies among quality requirements perceived as most important by the practitioners. Fourth, it characterizes the selection and management of QR in down-stream development activities.
  •  
14.
  • Bjarnason, Elizabeth, et al. (författare)
  • Challenges and practices in aligning requirements with verification and validation : a case study of six companies
  • 2014
  • Ingår i: Empirical Software Engineering. - : Springer. - 1382-3256 .- 1573-7616. ; 19:6, s. 1809-1855
  • Tidskriftsartikel (refereegranskat)abstract
    • Weak alignment of requirements engineering (RE) with verification and validation (VV) may lead to problems in delivering the required products in time with the right quality. For example, weak communication of requirements changes to testers may result in lack of verification of new requirements and incorrect verification of old invalid requirements, leading to software quality problems, wasted effort and delays. However, despite the serious implications of weak alignment research and practice both tend to focus on one or the other of RE or VV rather than on the alignment of the two. We have performed a multi-unit case study to gain insight into issues around aligning RE and VV by interviewing 30 practitioners from 6 software developing companies, involving 10 researchers in a flexible research process for case studies. The results describe current industry challenges and practices in aligning RE with VV, ranging from quality of the individual RE and VV activities, through tracing and tools, to change control and sharing a common understanding at strategy, goal and design level. The study identified that human aspects are central, i.e. cooperation and communication, and that requirements engineering practices are a critical basis for alignment. Further, the size of an organisation and its motivation for applying alignment practices, e.g. external enforcement of traceability, are variation factors that play a key role in achieving alignment. Our results provide a strategic roadmap for practitioners improvement work to address alignment challenges. Furthermore, the study provides a foundation for continued research to improve the alignment of RE with VV.
  •  
15.
  • Borg, Markus, et al. (författare)
  • Selecting component sourcing options : A survey of software engineering's broader make-or-buy decisions
  • 2019
  • Ingår i: Information and Software Technology. - : Elsevier B.V.. - 0950-5849 .- 1873-6025. ; 112, s. 18-34
  • Tidskriftsartikel (refereegranskat)abstract
    • 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.
  •  
16.
  • Chatzipetrou, Panagiota, Assistant Professor, 1984-, et al. (författare)
  • Component attributes and their importance in decisions and component selection
  • 2020
  • Ingår i: Software quality journal. - : Springer Science and Business Media LLC. - 0963-9314 .- 1573-1367. ; 28, s. 567-593
  • Tidskriftsartikel (refereegranskat)abstract
    • Component-based software engineering is a common approach in the development and evolution of contemporary software systems. Different component sourcing options are available, such as: (1) Software developed internally (in-house), (2) Software developed outsourced, (3) Commercial off-the-shelf software, and (4) Open-Source Software. However, there is little available research on what attributes of a component are the most important ones when selecting new components. The objective of this study is to investigate what matters the most to industry practitioners when they decide to select a component. We conducted a cross-domain anonymous survey with industry practitioners involved in component selection. First, the practitioners selected the most important attributes from a list. Next, they prioritized their selection using the Hundred-Dollar ($100) test. We analyzed the results using compositional data analysis. The results of this exploratory analysis showed that cost was clearly considered to be the most important attribute for component selection. Other important attributes for the practitioners were: support of the component, longevity prediction, and level of off-the-shelf fit to product. Moreover, several practitioners still consider in-house software development to be the sole option when adding or replacing a component. On the other hand, there is a trend to complement it with other component sourcing options and, apart from cost, different attributes factor into their decision. Furthermore, in our analysis, nonparametric tests and biplots were used to further investigate the practitioners’ inherent characteristics. It seems that smaller and larger organizations have different views on what attributes are the most important, and the most surprising finding is their contrasting views on the cost attribute: larger organizations with mature products are considerably more cost aware.
  •  
17.
  • Chatzipetrou, Panagiota, Assistant Professor, 1984-, et al. (författare)
  • Component selection in software engineering - Which attributes are the most important in the decision process?
  • 2018
  • Ingår i: Proceedings - 44th Euromicro Conference on Software Engineering and Advanced Applications, SEAA 2018. - : IEEE conference proceedings. - 9781538673829 ; , s. 198-205, s. 198-205
  • Konferensbidrag (refereegranskat)abstract
    • Component-based software engineering is a common approach to develop and evolve contemporary software systems where different component sourcing options are available: 1)Software developed internally (in-house), 2)Software developed outsourced, 3)Commercial of the shelf software, and 4) Open Source Software. However, there is little available research on what attributes of a component are the most important ones when selecting new components. The object of the present study is to investigate what matters the most to industry practitioners during component selection. We conducted a cross-domain anonymous survey with industry practitioners involved in component selection. First, the practitioners selected the most important attributes from a list. Next, they prioritized their selection using the Hundred-Dollar ($100) test. We analyzed the results using Compositional Data Analysis. The descriptive results showed that Cost was clearly considered the most important attribute during the component selection. Other important attributes for the practitioners were: Support of the component, Longevity prediction, and Level of off-the-shelf fit to product. Next, an exploratory analysis was conducted based on the practitioners' inherent characteristics. Nonparametric tests and biplots were used. It seems that smaller organizations and more immature products focus on different attributes than bigger organizations and mature products which focus more on Cost. .
  •  
18.
  • Chatzipetrou, Panagiota, Assistant Professor, 1984-, et al. (författare)
  • Requirements' Characteristics : How do they Impact on Project Budget in a Systems Engineering Context?
  • 2019
  • Ingår i: EUROMICRO Conference Proceedings. - : Institute of Electrical and Electronics Engineers Inc.. - 9781728132853 ; , s. 260-267, s. 260-267
  • Konferensbidrag (refereegranskat)abstract
    • Background: Requirements engineering is of a principal importance when starting a new project. However, the number of the requirements involved in a single project can reach up to thousands. Controlling and assuring the quality of natural language requirements (NLRs), in these quantities, is challenging. Aims: In a field study, we investigated with the Swedish Transportation Agency (STA) to what extent the characteristics of requirements had an influence on change requests and budget changes in the project. Method: We choose the following models to characterize system requirements formulated in natural language: Concern-based Model of Requirements (CMR), Requirements Abstractions Model (RAM) and Software-Hardware model (SHM). The classification of the NLRs was conducted by the three authors. The robust statistical measure Fleiss' Kappa was used to verify the reliability of the results. We used descriptive statistics, contingency tables, results from the Chi-Square test of association along with post hoc tests. Finally, a multivariate statistical technique, Correspondence analysis was used in order to provide a means of displaying a set of requirements in two-dimensional graphical form. Results: The results showed that software requirements are associated with less budget cost than hardware requirements. Moreover, software requirements tend to stay open for a longer period indicating that they are 'harder' to handle. Finally, the more discussion or interaction on a change request can lower the actual estimated change request cost. Conclusions: The results lead us to a need to further investigate the reasons why the software requirements are treated differently from the hardware requirements, interview the project managers, understand better the way those requirements are formulated and propose effective ways of Software management. © 2019 IEEE.
  •  
19.
  • Dehghani, Razieh, et al. (författare)
  • On Understanding the Relation of Knowledge and Confidence to Requirements Quality
  • 2021
  • Ingår i: REQUIREMENTS ENGINEERING: FOUNDATION FOR SOFTWARE QUALITY (REFSQ 2021). - Cham : Springer Science and Business Media Deutschland GmbH. - 9783030731274 ; , s. 208-224
  • Konferensbidrag (refereegranskat)abstract
    • [Context and Motivation] Software requirements are affected by the knowledge and confidence of software engineers. Analyzing the interrelated impact of these factors is difficult because of the challenges of assessing knowledge and confidence. [Question/Problem] This research aims to draw attention to the need for considering the interrelated effects of confidence and knowledge on requirements quality, which has not been addressed by previous publications. [Principal ideas/results] For this purpose, the following steps have been taken: 1) requirements quality was defined based on the instructions provided by the ISO29148:2011 standard, 2) we selected the symptoms of low qualified requirements based on ISO29148:2011, 3) we analyzed five Software Requirements Specification (SRS) documents to find these symptoms, 3) people who have prepared the documents were categorized in four classes to specify the more/less knowledge and confidence they have regarding the symptoms, and 4) finally, the relation of lack of enough knowledge and confidence to symptoms of low quality was investigated. The results revealed that the simultaneous deficiency of confidence and knowledge has more negative effects in comparison with a deficiency of knowledge or confidence. [Contribution] In brief, this study has achieved these results: 1) the realization that a combined lack of knowledge and confidence has a larger effect on requirements quality than only one of the two factors, 2) the relation between low qualified requirements and requirements engineers’ needs for knowledge and confidence, and 3) variety of requirements engineers’ needs for knowledge based on their abilities to make discriminative and consistent decisions. © 2021, Springer Nature Switzerland AG.
  •  
20.
  • Duarte, Carlos Henrique C., et al. (författare)
  • Technology Transfer - Requirements Engineering Research to Industrial Practice An Open (Ended) Debate
  • 2015
  • Ingår i: 2015 IEEE 23RD INTERNATIONAL REQUIREMENTS ENGINEERING CONFERENCE (RE). - : IEEE. - 9781467369053 ; , s. 414-415
  • Konferensbidrag (refereegranskat)abstract
    • Technology and knowledge have been recognized as main sources of competitive advantage of corporations, industries and nations, particularly in the software domain. They have led to the creation of local ecosystems devoted to development and transfer activities, which ensure not only personal and institutional motivation/recognition, but also social and economic gains. An open (ended) debate panel is proposed in order to develop greater awareness and seek deeper understanding of such activities from Requirements Engineering research to industrial practice. The panel involves researchers and practitioners with the perspective of eliciting: (i) experiences in knowledge and technology development and transfer; (ii) awareness and effectiveness of models and patterns; and (iii) factors for having successful collaboration between research institutions and industry. The organizers also plan to run a survey during and after the conference, summarizing their conclusions in specific post-conference reports.
  •  
21.
  • Fabiola Moyón, Constante, et al. (författare)
  • RefA : Reference Architecture for Security-compliant DevOps
  • 2023
  • Rapport (refereegranskat)abstract
    • 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.
  •  
22.
  • Femmer, Henning, et al. (författare)
  • Which requirements artifact quality defects are automatically detectable? : A case study
  • 2017
  • Ingår i: Proceedings - 2017 IEEE 25th International Requirements Engineering Conference Workshops, REW 2017<em></em>. - : IEEE. - 9781538634882 ; , s. 400-406
  • Konferensbidrag (refereegranskat)abstract
    • [Context:] The quality of requirements engineeringartifacts, e.g. requirements specifications, is acknowledged tobe an important success factor for projects. Therefore, manycompanies spend significant amounts of money to control thequality of their RE artifacts. To reduce spending and improvethe RE artifact quality, methods were proposed that combinemanual quality control, i.e. reviews, with automated approaches.[Problem:] So far, we have seen various approaches to auto-matically detect certain aspects in RE artifacts. However, westill lack an overview what can and cannot be automaticallydetected. [Approach:] Starting from an industry guideline forRE artifacts, we classify 166 existing rules for RE artifacts alongvarious categories to discuss the share and the characteristics ofthose rules that can be automated. For those rules, that cannotbe automated, we discuss the main reasons. [Contribution:] Weestimate that 53% of the 166 rules can be checked automaticallyeither perfectly or with a good heuristic. Most rules need onlysimple techniques for checking. The main reason why some rulesresist automation is due to imprecise definition. [Impact:] Bygiving first estimates and analyses of automatically detectable andnot automatically detectable rule violations, we aim to provide anoverview of the potential of automated methods in requirementsquality control.
  •  
23.
  • Franch, Xavier, et al. (författare)
  • On the Requirements Engineer Role
  • 2021
  • Ingår i: Communications of the ACM. - : ASSOC COMPUTING MACHINERY. - 0001-0782 .- 1557-7317. ; 64:6, s. 69-75
  • Tidskriftsartikel (refereegranskat)abstract
    • The requirements engineer role is defined differently within most organizations.
  •  
24.
  • Franch, Xavier, et al. (författare)
  • The state-of-practice in requirements specification : an extended interview study at 12 companies
  • 2023
  • Ingår i: Requirements Engineering. - : Springer. - 0947-3602 .- 1432-010X. ; 28:3, s. 377-409
  • Tidskriftsartikel (refereegranskat)abstract
    • Requirements specification is a core activity in the requirements engineering phase of a software development project. Researchers have contributed extensively to the field of requirements specification, but the extent to which their proposals have been adopted in practice remains unclear. We gathered evidence about the state of practice in requirements specification by focussing on the artefacts used in this activity, the application of templates or guidelines, how requirements are structured in the specification document, what tools practitioners use to specify requirements, and what challenges they face. We conducted an interview-based survey study involving 24 practitioners from 12 different Swedish IT companies. We recorded the interviews and analysed these recordings, primarily by using qualitative methods. Natural language constitutes the main specification artefact but is usually accompanied by some other type of instrument. Most requirements specifications use templates or guidelines, although they seldom follow any fixed standard. Requirements are always structured in the document according to the main functionalities of the system or to project areas or system parts. Different types of tools, including MS Office tools, are used, either individually or combined, in the compilation of requirements specifications. We also note that challenges related to the use of natural language (dealing with ambiguity, inconsistency, and incompleteness) are the most frequent challenges that practitioners face in the compilation of requirements specifications. These findings are contextualized in terms of demographic factors related to the individual interviewees, the organization they are affiliated with, and the project they selected to discuss during our interviews. A number of our findings have been previously reported in related studies. These findings show that, in spite of the large number of notations, models and tools proposed from academia for improving requirements specification, practitioners still mainly rely on plain natural language and general-purpose tool support. We expect more empirical studies in this area in order to better understand the reason of this low adoption of research results.
  •  
25.
  • Gorschek, Tony, 1972- (författare)
  • Evolution toward soft(er) products
  • 2018
  • Ingår i: Communications of the ACM. - : Association for Computing Machinery. - 0001-0782 .- 1557-7317. ; 61:3, s. 78-84
  • Tidskriftsartikel (refereegranskat)abstract
    • SOFTWARE IS A cornerstone of the economy, historically led by companies like Apple, Google, and Microsoft. However, the past decade has seen software become increasingly pervasive, while traditionally hardware-intensive products are increasingly dependent on software, meaning that major global companies like ABB, Ericsson, Scania, and Volvo are likewise becoming soft(er).(10) Where software was bundled with hardware it is now increasingly the main product differentiator.(10) This shift has radical implications, as software delivers notable advantages, including a faster pace of release and improved cost effectiveness in terms of development, ease of update, customization, and distribution. These characteristics of software open a range of possibilities, though software's inherent properties also pose several significant challenges in relation to a company's ability to create value.(10) To investigate them, we conducted in-depth interviews from 2012 to 2016 with 13 senior product managers in 12 global companies.
  •  
26.
  • Gorschek, Tony, 1972-, et al. (författare)
  • Solving Problems or Enabling Problem-Solving? : from Purity in Empirical Software Engineering to Effective Co-production (Invited Keynote)
  • 2021
  • Ingår i: Software Quality. - Cham : Springer Science and Business Media Deutschland GmbH. - 9783030658533 ; , s. 109-116
  • Konferensbidrag (refereegranskat)abstract
    • Studying and collaborating with any software-intensive organization demands for excellence in empirical software engineering research. The ever-growing complexity and context-dependency of software products, however, demands for more pragmatic and solution-focused research. This is a great opportunity but it also conflicts with the traditional quest for “purity” in research and a very narrow focus of the work. In this short positioning, we elaborate on challenges which emerge from academia-industry collaborations and discuss touch upon pragmatic ways of approaching them along the co-production model which emerged from SERL Sweden. © 2021, Springer Nature Switzerland AG.
  •  
27.
  • Gorschek, Tony, 1972-, et al. (författare)
  • Third Generation Industrial Co-production in Software Engineering
  • 2020
  • Ingår i: Contemporary Empirical Methods in Software Engineering. - Cham : Springer Nature. - 9783030324889 ; , s. 503-525
  • Bokkapitel (refereegranskat)abstract
    • Industry–academia collaboration is one of the cornerstones of empirical software engineering. The role of researchers should be developing new practices and principles that enable industry in meeting the engineering challenges today and in the future. This chapter describes the third generation of industrial co-production in software engineering that includes seven steps. The co-production model and experiences associated with its use represent deep and long-term co-production with over thirty companies, many of which are still active partners in Software Engineering Research Lab (SERL).
  •  
28.
  • Hyrynsalmi, Sami, et al. (författare)
  • What is a minimum viable (video) game? : Towards a research agenda
  • 2018
  • Ingår i: Lect. Notes Comput. Sci.. - Cham : Springer Verlag. - 9783030021306 ; , s. 217-231
  • Konferensbidrag (refereegranskat)abstract
    • The concept of ‘Minimum Viable Product’ (MVP) is largely adapted in the software industry as well as in academia. Minimum viable products are used to test hypotheses regarding the target audience, save resources from unnecessary development work and guide a company towards a stable business model. As the game industry is becoming an important business domain, it is not surprise that the concept has been adopted also in the game development. This study surveys how a Minimum Viable Game (MVG) is defined, what is reported in extant literature as well as present results from a small case study survey done to nine game development companies. The study shows that despite popularity of minimum viable games in the industrial fora, the presented views on the concept are diverged and there is lack of practical guidelines and research supporting game companies. This study points out research gaps in the area as well as calls for actions to further develop the concept and to define guidelines. © IFIP International Federation for Information Processing 2018.
  •  
29.
  • Klotins, Eriks, 1985-, et al. (författare)
  • A collaborative method for identification and prioritization of data sources in MDRE
  • Annan publikation (övrigt vetenskapligt/konstnärligt)abstract
    • Requirements engineering (RE) literature acknowledges the importance of stakeholder identification early in the software engineering activities. However, literature overlooks the challenge of identifying and selecting the right stakeholders and the potential of using other inanimate requirements sources for RE activities for market-driven products.Market-driven products are influenced by a large number of stakeholders. Consulting all stakeholders directly is impractical, and companies utilize indirect data sources, e.g. documents and representatives of larger groups of stakeholders. However, without a systematic approach, companies often use easy to access or hard to ignore data sources for RE activities. As a consequence, companies waste resources on collecting irrelevant data or develop the product based on the input from a few sources, thus missing market opportunities.We propose a collaborative and structured method to support analysts in the identification and selection of the most relevant data sources for market-driven product engineering. The method consists of four steps and aims to build consensus between different perspectives in an organization and facilitates the identification of most relevant data sources. We demonstrate the use of the method with two industrial case studies.Our results show that the method can support market-driven requirements engineering in two ways: (1) by providing systematic steps to identify and prioritize data sources for RE, and (2) by highlighting and resolving discrepancies between different perspectives in an organization.
  •  
30.
  • Klotins, Eriks, et al. (författare)
  • A progression model of software engineering goals, challenges, and practices in start-ups
  • 2021
  • Ingår i: IEEE Transactions on Software Engineering. - : IEEE. - 0098-5589 .- 1939-3520. ; 47:3, s. 498-521
  • Tidskriftsartikel (refereegranskat)abstract
    • Context: Software start-ups are emerging as suppliers of innovation and software-intensive products. However, traditional software engineering practices are not evaluated in the context, nor adopted to goals and challenges of start-ups. As a result, there is insufficient support for software engineering in the start-up context.Objective: We aim to collect data related to engineering goals, challenges, and practices in start-up companies to ascertain trends and patterns characterizing engineering work in start-ups. Such data allows researchers to understand better how goals and challenges are related to practices. This understanding can then inform future studies aimed at designing solutions addressing those goals and challenges. Besides, these trends and patterns can be useful for practitioners to make more informed decisions in their engineering practice.Method: We use a case survey method to gather first-hand, in-depth experiences from a large sample of software start-ups. We use open coding and cross-case analysis to describe and identify patterns, and corroborate the findings with statistical analysis.Results: We analyze 84 start-up cases and identify 16 goals, 9 challenges, and 16 engineering practices that are common among startups. We have mapped these goals, challenges, and practices to start-up life-cycle stages (inception, stabilization, growth, and maturity). Thus, creating the progression model guiding software engineering efforts in start-ups.Conclusions: We conclude that start-ups to a large extent face the same challenges and use the same practices as established companies. However, the primary software engineering challenge in start-ups is to evolve multiple process areas at once, with a little margin for serious errors.
  •  
31.
  • Klotins, Eriks, 1985-, et al. (författare)
  • Continuous Software Engineering : Introducing an Industry Readiness Model
  • 2023
  • Ingår i: IEEE Software. - : IEEE Computer Society. - 0740-7459 .- 1937-4194. ; 40:4, s. 77-87
  • Tidskriftsartikel (refereegranskat)abstract
    • 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
  •  
32.
  • Klotins, Eriks, 1985-, et al. (författare)
  • Continuous Software Engineering in the Wild
  • 2022
  • Ingår i: Software Quality. - Cham : Springer. - 9783031041143 ; , s. 3-12
  • Konferensbidrag (refereegranskat)abstract
    • Software is becoming a critical component of most products and organizational functions. The ability to continuously improve software determines how well the organization can respond to market opportunities. Continuous software engineering promises numerous advantages over sprint-based or plan-driven development. However, implementing a continuous software engineering pipeline in an existing organization is challenging. In this invited position paper, we discuss the adoption challenges and argue for a more systematic methodology to drive the adoption of continuous engineering. Our discussion is based on ongoing work with several industrial partners as well as experience reported in both state-of-practice and state-of-the-art. We conclude that the adoption of continuous software engineering primarily requires analysis of the organization, its goals, and constraints. One size does not fit all purposes, meaning that many of the principles behind continuous engineering are relevant for most organizations, but the level of realization and the benefits may still vary. The main hindrances to continuous flow of software arise from sub-optimal organizational structures and the lack of alignment. Once those are removed, the organization can implement automation to further improve the software delivery. © 2022, Springer Nature Switzerland AG.
  •  
33.
  • Klotins, Eriks, et al. (författare)
  • Exploration of technical debt in start-ups
  • 2018
  • Ingår i: Proceedings - International Conference on Software Engineering. - New York, NY, USA : IEEE Computer Society. - 9781450356596 ; , s. 75-84
  • Konferensbidrag (refereegranskat)abstract
    • Context: Software start-ups are young companies aiming to build and market software-intensive products fast with little resources. Aiming to accelerate time-to-market, start-ups often opt for ad-hoc engineering practices, make shortcuts in product engineering, and accumulate technical debt. Objective: In this paper we explore to what extent precedents, dimensions and outcomes associated with technical debt are prevalent in start-ups. Method: We apply a case survey method to identify aspects of technical debt and contextual information characterizing the engineering context in start-ups. Results: By analyzing responses from 86 start-up cases we found that start-ups accumulate most technical debt in the testing dimension, despite attempts to automate testing. Furthermore, we found that start-up team size and experience is a leading precedent for accumulating technical debt: larger teams face more challenges in keeping the debt under control. Conclusions: This study highlights the necessity to monitor levels of technical debt and to preemptively introduce practices to keep the debt under control. Adding more people to an already difficult to maintain product could amplify other precedents, such as resource shortages, communication issues and negatively affect decisions pertaining to the use of good engineering practices. © 2018 ACM.
  •  
34.
  • Klotins, Eriks, et al. (författare)
  • Software Engineering Anti-Patterns in Start-Ups
  • 2019
  • Ingår i: IEEE Software. - : IEEE Computer Society. - 0740-7459 .- 1937-4194. ; 36:2, s. 118-126
  • Tidskriftsartikel (refereegranskat)abstract
    • Software start-up failures are often explained with a poor business model, market issues, insufficient funding, or simply a bad product idea. However, inadequacies in software engineering are relatively unexplored and could be a significant contributing factor to the high start-up failure rate. In this paper we present the analysis of 88 start-up experience reports, revealing three anti-patterns associated with start-up progression phases. The anti-patterns address challenges of releasing the first version of the product, attracting customers, and expanding the product into new markets. The anti-patterns show that challenges and failure scenarios that appear to be business or market related are, at least partially, rooted in engineering inadequacies.
  •  
35.
  • Klotins, Eriks, et al. (författare)
  • Software engineering in start-up companies : An analysis of 88 experience reports
  • 2019
  • Ingår i: Empirical Software Engineering. - : Springer New York LLC. - 1382-3256 .- 1573-7616. ; 24:1, s. 68-102
  • Tidskriftsartikel (refereegranskat)abstract
    • Context: Start-up companies have become an important supplier of innovation and software-intensive products. The flexibility and reactiveness of start-ups enables fast development and launch of innovative products. However, a majority of software start-up companies fail before achieving any success. Among other factors, poor software engineering could be a significant contributor to the challenges experienced by start-ups. However, the state-of-practice of software engineering in start-ups, as well as the utilization of state-of-the-art is largely an unexplored area. Objective: In this study we investigate how software engineering is applied in start-up context with a focus to identify key knowledge areas and opportunities for further research. Method: We perform a multi-vocal exploratory study of 88 start-up experience reports. We develop a custom taxonomy to categorize the reported software engineering practices and their interrelation with business aspects, and apply qualitative data analysis to explore influences and dependencies between the knowledge areas. Results: We identify the most frequently reported software engineering (requirements engineering, software design and quality) and business aspect (vision and strategy development) knowledge areas, and illustrate their relationships. We also present a summary of how relevant software engineering knowledge areas are implemented in start-ups and identify potentially useful practices for adoption in start-ups. Conclusions: The results enable a more focused research on engineering practices in start-ups. We conclude that most engineering challenges in start-ups stem from inadequacies in requirements engineering. Many promising practices to address specific engineering challenges exists, however more research on adaptation of established practices, and validation of new start-up specific practices is needed. © 2018 The Author(s)
  •  
36.
  • Klotins, Eriks, 1985- (författare)
  • Software Engineering in Start-up Companies
  • 2019
  • Doktorsavhandling (övrigt vetenskapligt/konstnärligt)abstract
    • Start-up companies have emerged as suppliers of innovation and software-intensive products. Small teams, lack of legacy products, experimental nature, and absence of any organizational processes enable start-ups to develop and market new products and services quickly. However, most start-ups fail before delivering any value. Start-up failures can be attributed to market factors, shortcomings in business models, lack of motivation, or self-destruction, among other reasons. However, inadequacies in product engineering precede any market or business-related challenges and could be a significant contributing factor to start-up failures. At the same time, state-of-the-art software engineering (SE) practices are often neglected by start-ups as inadequate. At the beginning of this work, SE in start-ups had attracted very little attention from researchers. Thus, there was no coherent view of SE state-of-practice in start-ups and no starting point for a focused investigation. In this thesis, we explore how start-ups practice SE, what specific SE challenges should be addressed, and what new SE practices are needed to support the engineering of innovative software-intensive products and services. A substantial part of this work is exploratory and aimed to explore SE state-of-practice in start-ups. Our initial findings suggest that start-ups overlook the best SE practices. Teams of a few people working on relatively experimental and straightforward software see no upside of following the best practices. However, late start-ups face substantial challenges as their teams grow, and products become more complex. The key difficulties concern installing adequate SE practices supporting collaboration, coordination of work, and management of accumulated technical debt. To support the evolution of engineering practices in start-ups, we propose the start-up progression model outlining engineering goals, common challenges, and useful practices with regards to the start-up life-cycle phases. Further findings suggest inadequate support for market-driven requirements engineering (MDRE). Specifically, on how to aggregate needs and wishes of a large and loosely defined set of stakeholders who may not be able to articulate their needs and expectations. To address this challenge, we propose a method for the identification and prioritization of data sources and stakeholders in MDRE. Analyzing SE context in start-ups and other organizations developing innovative and market-driven products, we have found many similarities. While start-ups have challenges, they do not appear to be unique. Thus, most start-up challenges can be addressed by transferring the best practices from other engineering contexts. We conclude that there is a little need for start-up specific engineering practices. Best software engineering practices are relevant to address challenges in start-ups. The key engineering challenge in start-ups is the management of the evolution of SE practices to match the growing complexity of the product and the organization. Our work also highlights the need for better MDRE practices to support new market-driven product development in both start-ups and other types of organizations. 
  •  
37.
  • Klotins, Eriks, et al. (författare)
  • Software-intensive product engineering in start-ups : a taxonomy
  • 2018
  • Ingår i: IEEE Software. - : IEEE Computer Society. - 0740-7459 .- 1937-4194. ; 35:4, s. 44-52
  • Tidskriftsartikel (refereegranskat)abstract
    • Software start-ups are new companies aiming to launch an innovative product to mass markets fast with minimal resources. However a majority of start-ups fail before realizing their potential. Poor software engineering, among other factors, could be a significant contributor to the challenges experienced by start-ups.Very little is known about the engineering context in start-up companies. On the surface, start-ups are characterized by uncertainty, high risk and minimal resources. However, such characterization is not granular enough to support identification of specific engineering challenges and to devise start-up specific engineering practices.The first step towards understanding on software engineering in start-ups is definition of the Start-up Context Map - a taxonomy of engineering practices, environment factors and goals influencing the engineering process. Goal of the Start-up Context Map is to support further research on the field and to serve as an engineering decision support tool for start-ups. 
  •  
38.
  • Klotins, Eriks, 1985-, et al. (författare)
  • Towards cost-benefit evaluation for continuous software engineering activities
  • 2022
  • Ingår i: Empirical Software Engineering. - : SPRINGER. - 1382-3256 .- 1573-7616. ; 27:6
  • Tidskriftsartikel (refereegranskat)abstract
    • Context: Software companies must become better at delivering software to remain relevant in the market. Continuous integration and delivery practices promise to streamline software deliveries to end-users by implementing an automated software development and delivery pipeline. However, implementing or retrofitting an organization with such a pipeline is a substantial investment, while the reporting on benefits and their relevance in specific contexts/domains are vague. Aim: In this study, we explore continuous software engineering practices from an investment-benefit perspective. We identify what benefits can be attained by adopting continuous practices, what the associated investments and risks are, and analyze what parameters determine their relevance. Method: We perform a multiple case study to understand state-of-practice, organizational aims, and challenges in adopting continuous software engineering practices. We compare state-of-practice with state-of-the-art to validate the best practices and identify relevant gaps for further investigation. Results: We found that companies start the CI/CD adoption by automating and streamlining the internal development process with clear and immediate benefits. However, upgrading customers to continuous deliveries is a major obstacle due to existing agreements and customer push-back. Renegotiating existing agreements comes with a risk of losing customers and disrupting the whole organization. Conclusions: We conclude that the benefits of CI/CD are overstated in literature without considering the contextual and domain complexities rendering some benefits infeasible. We identify the need to understand the customer and organizational perspectives further and understand the contextual requirements towards the CI/CD.
  •  
39.
  • Klotins, Eriks, 1985-, et al. (författare)
  • Use of agile practices in start-up companies
  • 2021
  • Ingår i: e-Informatica Software Engineering Journal. - : Wrocław University of Science and Technology. - 1897-7979 .- 2084-4840. ; 15:1, s. 47-64
  • Tidskriftsartikel (refereegranskat)abstract
    • Context Software start-ups have shown their ability to develop and launch innovative software products and services. Small, motivated teams and uncertain project scope makes start-ups good candidates for adopting Agile practices. Objective We explore how start-ups use Agile practices and what effects can be associated with the use of those practices. Method We use a case survey to analyze 84 start-up cases and 56 Agile practices. We apply statistical methods to test for statistically significant associations between the use of Agile practices, team, and product factors. Results Our results suggest that development of the backlog, use of version control, code refactoring, and development of user stories are the most frequently reported practices. We identify 22 associations between the use of Agile practices, team, and product factors. The use of Agile practices is associated with effects on source code and overall product quality. A teams’ positive or negative attitude towards best engineering practices is a significant indicator for either adoption or rejection of certain Agile practices. To explore the relationships in our findings, we set forth a number of propositions that can be investigated in future research. Conclusions We conclude that start-ups use Agile practices, however without following any specific methodology. We identify the opportunity for more fine-grained studies into the adoption and effects of individual Agile practices. Start-up practitioners could benefit from Agile practices in terms of better overall quality, tighter control over team performance, and resource utilization. © 2021 Wroclaw University of Science and Technology. All rights reserved.
  •  
40.
  • Klotins, Eriks, 1985-, et al. (författare)
  • Use of Agile Practices in Start-ups
  • Annan publikation (övrigt vetenskapligt/konstnärligt)abstract
    • Context. Software start-ups have shown their ability to develop and launch in- novative software products and services. Small, motivated teams and uncertain project scope makes start-ups good candidates for adopting Agile practices.Objective. We explore how start-ups use Agile practices and what effects can be associated with the use of those practices.Method. We use a case survey to analyze 84 start-up cases and 56 Agile prac- tices. We apply statistical methods to test for statistically significant associa- tions between the use of Agile practices, team, and product factors.Results. Our results suggest that backlog, version control, refactoring, and user stories are the most frequently reported practices. We identify 22 associations between the use of Agile practices, team, and product factors. The use of Agile practices is associated with effects on source code and overall product quality. A teams’ positive or negative attitude towards best engineering practices is a significant indicator for either adoption or rejection of certain Agile practices. To explore the relationships in our findings, we set forth a number of propositions that can be investigated by future research.Conclusions. We conclude that start-ups use Agile practices, however without following any specific methodology. We identify the opportunity for more fine- grained studies into the adoption and effects of individual Agile practices. Start- up practitioners could benefit from Agile practices in terms of better overall quality, tighter control over team performance and resource utilization.
  •  
41.
  • Martins, Luiz Eduardo Galvão, et al. (författare)
  • Requirements Engineering for Safety-Critical Systems : An Interview Study with Industry Practitioners
  • 2020
  • Ingår i: IEEE Transactions on Software Engineering. - : Institute of Electrical and Electronics Engineers Inc.. - 0098-5589 .- 1939-3520. ; 46:4, s. 346-361
  • Tidskriftsartikel (refereegranskat)abstract
    • We have conducted in-depth interviews with experienced practitioners in the Safety-Critical Systems (SCS) domain in order to investigate several aspects related to requirements specification and safety analysis for SCS. We interviewed 19 practitioners from eleven SCS companies in different domains with the intention of verifying which approaches they use day-today, and what their perceptions are in relation to the approaches used to elicit, analyze, specify and validate safety requirements. The aim of this study is to obtain an in-depth understanding of how requirements engineering is carried out in companies that develop SCS. IEEE
  •  
42.
  • Minhas, Nasir Mehmood, et al. (författare)
  • SWVP-A Requirements Prioritization Technique for Global Software Development
  • 2019
  • Ingår i: EUROMICRO Conference Proceedings. - : Institute of Electrical and Electronics Engineers Inc.. - 9781728132853 ; , s. 1-9
  • Konferensbidrag (refereegranskat)abstract
    • Requirements prioritization plays a vital role in software release planning, and the process requires good interaction between stakeholders. Requirement prioritization process is challenging in global software development (GSD) context, where communication and coordination are core bottlenecks. Based on the issues found in the literature and industry survey, this paper proposes a requirements prioritization technique for GSD settings based on stakeholders' weight, vote, and priority (SWVP). The technique has two phases: (1) a calculation of stakeholders' profile weights and setting up communication parameters and (2) a voting process supporting the actual prioritization, based on the weights from phase (1). The proposed technique was applied to three industrial projects. The feedback of the practitioners after using SWVP was encouraging, and the feedback results indicate that SWVP could be a practical solution for requirements prioritization in GSD contexts. © 2019 IEEE.
  •  
43.
  • Olsson, Thomas, et al. (författare)
  • An empirical study on decision making for quality requirements
  • 2019
  • Ingår i: Journal of Systems and Software. - : Elsevier BV. - 0164-1212 .- 1873-1228. ; 149, s. 217-233
  • Tidskriftsartikel (refereegranskat)abstract
    • 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.
  •  
44.
  • Olsson, Thomas (författare)
  • Understanding and Supporting Quality Requirements Engineering in Software-intensive Product Development
  • 2020
  • Doktorsavhandling (övrigt vetenskapligt/konstnärligt)abstract
    • [Background] Quality requirements deal with how well a product should perform the intended functionality. Failure to meet essential quality requirements can result in customer dissatisfaction, unusable products, or extra costs. [Objective] The aim is to identify challenges and needs in practice and design solutions for quality requirements engineering which can be applied in practice. [Results] In the two exploratory studies quality requirements engineering practices are investigated. I confirm that some quality requirements fulfillment is not simply being implemented or not, rather evaluated on a scale. Furthermore, some quality requirements are cross-functional. Also, the product lifecycle phase seems to influence both the prevalence and acceptance of quality requirements in the scope decision process. Lastly, relying on external stakeholders and upfront analysis seems to lead to long lead-times and an insufficient quality requirements scope. QREME is a conceptual quality requirements engineering model with a lifecycle perspective. It is built upon a construct with a strategic and tactical level, a product and data dimension to include data in the scope decision process, and a forward- and a feedback-loop to enable a data-driven scope decision process. QREME is validated with five companies in a multi-case study. QREME was able to capture the companies' ways of working and provide relevant improvement recommendations. Also, the presence of the underlying constructs was confirmed. [Conclusions] Quality requirements engineering should be integrated with the overall requirements process. The awareness of quality requirements on a strategic level and catering for the product and portfolio lifecycle are important for success. I conclude that there is potential in sources such as usage data, customer service data, and continuous experimentation to complement stakeholder analysis, expert input, and focus groups. However, there is a need to better understand challenges and needs in practice, especially from a lifecycle perspective. Furthermore, longitudinal studies are needed to evaluate quality requirements solutions over time -- to understand the impact, costs, and benefits.
  •  
45.
  • Ouriques, Raquel, et al. (författare)
  • A Method to Evaluate Knowledge Resources in Agile Software Development
  • 2019
  • Ingår i: Proceeding of The ACM/IEEE International Symposium on Empirical Software Engineering and Measurement ESEM 2019. - : IEEE. - 9781728129686
  • Konferensbidrag (refereegranskat)abstract
    • 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.
  •  
46.
  • Ouriques, Raquel, et al. (författare)
  • Connecting the Dots of Knowledge in Agile Software Development
  • Annan publikation (övrigt vetenskapligt/konstnärligt)abstract
    • This article discusses the importance of managing knowledge as a resource due to its great potential to create economic value. We detail the types of knowledge resources, the challenges associated with their management, and potential solutions to maximise their utility. Our contribution is based on empirical studies performed in an industry context. 
  •  
47.
  • Ouriques, Raquel, et al. (författare)
  • Continuous Assimilation of Change in Agile Software Development : An empirical study on the role of the knowledge-based resources
  • Annan publikation (övrigt vetenskapligt/konstnärligt)abstract
    • As the software value chain is knowledge-based due to the high dependency on people, the lack of practice to manage knowledge as a resource might jeopardize its application in software development. The resource-based view of the firm provides a different perspective on the utilization of knowledge, assisting the identification of the Knowledge-Based Resources (KBRs) that allow a company to have a continuous readiness to quickly respond to the market changes. To understand how the KBRs support coordination in Agile Software Development (ASD), we applied a grounded theory approach, collecting data from 18 practitioners, coming from five companies. As results, we identified 44 KBRs that were grouped in the Continuous Assimilation Model (CHASM). They support coordination in ASD with continuous assimilation of change which is supported by people’s business analytic perspective and product systemic reasoning. The companies are able to utilize a certain level of their KBRs through social collaboration and team environment/settings. However, the inefficient utilization of these resources results in a significant knowledge loss. Furthermore, CHASM points out areas where practitioners can establish strategies based on the priorities that the companies give to the investigated KBRs, as well as a set of research opportunities for future investigation.
  •  
48.
  • Ouriques, Raquel, et al. (författare)
  • Preliminary Guideline for Creating Boundary Artefacts in Software Engineering
  • Annan publikation (övrigt vetenskapligt/konstnärligt)abstract
    • Context: Software development benefits from having Boundary Artefacts (BAs),as a single artefact can supply stakeholders with different boundaries, facilitatingcollaboration among social worlds. When those artefacts display inconsistencies,such as incorrect information, the practitioners have decreased trust in the BA. Astrust is an essential factor guiding the utilisation of BAs in software projects, it isnecessary to understand which principles should be observed when creating them.Objective: This study aimed at develop and validate a preliminary guidelinesupport the creation of trustworthy BAs.Method: We followed a multi-step approach. We developed our guideline througha literature review and previous results from our case study. Second, we submittedthe guideline for an expert evaluation via two workshops and a survey. At last, weadjusted our guideline by incorporating the feedback obtained during the workshops.Results: We grouped the principles collected from a literature review into threecategories. The first category (Scope) focuses on the scope, displaying principlesreferring to defining each boundary’s target audience, needs, and terminology. Thesecond category (Structure) relates to how the artefact’s content is structured tomeet stakeholders’ needs. The third (Management) refers to principles that canguide the establishment of practices to manage the artefact throughout time. Theexpert validation revealed that the principles contribute to creating trustworthy BAsat different levels. Also, the relevance of the guideline and its usefulness.Conclusions: The guideline strengthen BA traits such as shared understanding,plasticity and ability to transfer. Practitioners can utilise the guideline to guide thecreation or even evaluate current practices for existing BAs
  •  
49.
  • Ouriques, Raquel, et al. (författare)
  • The role of knowledge-based resources in Agile Software Development contexts
  • 2023
  • Ingår i: Journal of Systems and Software. - : Elsevier. - 0164-1212 .- 1873-1228. ; 197
  • Tidskriftsartikel (refereegranskat)abstract
    • 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
  •  
50.
  • Ouriques, Raquel, et al. (författare)
  • Thinking strategically about knowledge management in agile software development
  • 2018
  • Ingår i: Lecture Notes in Computer Science (including subseries Lecture Notes in Artificial Intelligence and Lecture Notes in Bioinformatics). - Cham : Springer Verlag. - 0302-9743 .- 1611-3349. - 9783030036720 ; 11271 LNCS, s. 389-395
  • Konferensbidrag (refereegranskat)abstract
    • Agile methodologies gave teams more autonomy regarding planning tasks and executing them. As a result, coordination gets more flexible, but much relevant knowledge remains undocumented and inside teams’ borders, due to informal communication and reduced development documentation. Since knowledge plays an essential role in software development, it is important to have effective knowledge management (KM) practices that contribute to a better knowledge resource allocation. Several KM practices have been reported in empirical studies in Agile Software Development (ASD). However, these practices are not evaluated regarding its effectiveness or how do they affect product quality. Besides, the studies do not demonstrate connections between the KM practices in the project level and the strategic level. The lack of connection between these levels can result in deviations from the company’s corporate strategy, wasted resources and irrelevant knowledge acquisition. This paper discusses how the strategic management can contribute to an integrated approach to KM in ASD; considering the organizational structure and the corporate strategy. Based on this discussion, we propose research areas that may help with planning KM strategies that can have their effectiveness measured and contribute to product quality. © Springer Nature Switzerland AG 2018.
  •  
Skapa referenser, mejla, bekava och länka
  • Resultat 1-50 av 89
Typ av publikation
tidskriftsartikel (41)
konferensbidrag (26)
annan publikation (11)
forskningsöversikt (4)
doktorsavhandling (3)
bokkapitel (2)
visa fler...
rapport (1)
licentiatavhandling (1)
visa färre...
Typ av innehåll
refereegranskat (74)
övrigt vetenskapligt/konstnärligt (14)
Författare/redaktör
Gorschek, Tony, 1972 ... (81)
Wnuk, Krzysztof, 198 ... (21)
Unterkalmsteiner, Mi ... (15)
Chatzipetrou, Panagi ... (10)
Mendez, Daniel (9)
Feldt, Robert, 1972 (9)
visa fler...
Alégroth, Emil, 1984 ... (8)
Vilela, Jéssyka (8)
Berntsson Svensson, ... (7)
Gorschek, Tony, 1973 (7)
Gonzalez-Huerta, Jav ... (7)
Ouriques, Raquel (7)
Klotins, Eriks (7)
Klotins, Eriks, 1985 ... (7)
Prikladnicki, Rafael (6)
Petersen, Kai (6)
Papatheocharous, Efi (6)
Borg, Markus (6)
Tripathi, Nirnaya (6)
Alégroth, Emil (5)
Martins, Luiz Eduard ... (5)
Badampudi, Deepika, ... (5)
Pompermaier, Leandro ... (5)
Cicchetti, Antonio (4)
Wohlin, Claes (4)
Fagerholm, Fabian (4)
Yu, Liang, 1986- (4)
Peixoto, Mariana (4)
Silva, Carla (4)
Olsson, Thomas (3)
Franch, Xavier (3)
Torkar, Richard, 197 ... (3)
Šmite, Darja (3)
Axelsson, Jakob (3)
Sentilles, Séverine, ... (3)
Regnell, Björn (3)
Palomares, Cristina (3)
Zabardast, Ehsan, 19 ... (3)
Araújo, João (3)
Afzal, Wasif (2)
Mattsson, Michael (2)
Frattini, Julian, 19 ... (2)
Shahrokni, Ali, 1982 (2)
Chatzipetrou, Panagi ... (2)
Quer, Carme (2)
Wilson, Magnus (2)
Chatzipetrou, Panagi ... (2)
Ferreira, Dayse (2)
Cavalcanti, Mateus (2)
Floren, D. (2)
visa färre...
Lärosäte
Blekinge Tekniska Högskola (87)
Chalmers tekniska högskola (12)
Örebro universitet (11)
RISE (8)
Göteborgs universitet (6)
Mälardalens universitet (5)
visa fler...
Lunds universitet (2)
Malmö universitet (1)
visa färre...
Språk
Engelska (89)
Forskningsämne (UKÄ/SCB)
Naturvetenskap (86)
Teknik (11)
Samhällsvetenskap (4)

År

Kungliga biblioteket hanterar dina personuppgifter i enlighet med EU:s dataskyddsförordning (2018), GDPR. Läs mer om hur det funkar här.
Så här hanterar KB dina uppgifter vid användning av denna tjänst.

 
pil uppåt Stäng

Kopiera och spara länken för att återkomma till aktuell vy