SwePub
Sök i SwePub databas

  Utökad sökning

Träfflista för sökning "L773:0947 3602 OR L773:1432 010X "

Sökning: L773:0947 3602 OR L773:1432 010X

  • Resultat 1-50 av 50
Sortera/gruppera träfflistan
   
NumreringReferensOmslagsbildHitta
1.
  •  
2.
  • Abbas, Muhammad, et al. (författare)
  • On the relationship between similar requirements and similar software : A case study in the railway domain
  • 2023
  • Ingår i: Requirements Engineering. - : Springer Science and Business Media Deutschland GmbH. - 0947-3602 .- 1432-010X. ; 28, s. 23-47
  • Tidskriftsartikel (refereegranskat)abstract
    • Recommender systems for requirements are typically built on the assumption that similar requirements can be used as proxies to retrieve similar software. When a stakeholder proposes a new requirement, natural language processing (NLP)-based similarity metrics can be exploited to retrieve existing requirements, and in turn, identify previously developed code. Several NLP approaches for similarity computation between requirements are available. However, there is little empirical evidence on their effectiveness for code retrieval. This study compares different NLP approaches, from lexical ones to semantic, deep-learning techniques, and correlates the similarity among requirements with the similarity of their associated software. The evaluation is conducted on real-world requirements from two industrial projects from a railway company. Specifically, the most similar pairs of requirements across two industrial projects are automatically identified using six language models. Then, the trace links between requirements and software are used to identify the software pairs associated with each requirements pair. The software similarity between pairs is then automatically computed with JPLag. Finally, the correlation between requirements similarity and software similarity is evaluated to see which language model shows the highest correlation and is thus more appropriate for code retrieval. In addition, we perform a focus group with members of the company to collect qualitative data. Results show a moderately positive correlation between requirements similarity and software similarity, with the pre-trained deep learning-based BERT language model with preprocessing outperforming the other models. Practitioners confirm that requirements similarity is generally regarded as a proxy for software similarity. However, they also highlight that additional aspect comes into play when deciding software reuse, e.g., domain/project knowledge, information coming from test cases, and trace links. Our work is among the first ones to explore the relationship between requirements and software similarity from a quantitative and qualitative standpoint. This can be useful not only in recommender systems but also in other requirements engineering tasks in which similarity computation is relevant, such as tracing and change impact analysis.
  •  
3.
  • Abdeen, Waleed, et al. (författare)
  • An approach for performance requirements verification and test environments generation
  • 2023
  • Ingår i: Requirements Engineering. - : Springer. - 0947-3602 .- 1432-010X. ; 28:1, s. 117-144
  • Tidskriftsartikel (refereegranskat)abstract
    • Model-based testing (MBT) is a method that supports the design and execution of test cases by models that specify theintended behaviors of a system under test. While systematic literature reviews on MBT in general exist, the state of the arton modeling and testing performance requirements has seen much less attention. Therefore, we conducted a systematic map-ping study on model-based performance testing. Then, we studied natural language software requirements specificationsin order to understand which and how performance requirements are typically specified. Since none of the identified MBTtechniques supported a major benefit of modeling, namely identifying faults in requirements specifications, we developed thePerformance Requirements verificatiOn and Test EnvironmentS generaTion approach (PRO-TEST). Finally, we evaluatedPRO-TEST on 149 requirements specifications. We found and analyzed 57 primary studies from the systematic mappingstudy and extracted 50 performance requirements models. However, those models don’t achieve the goals of MBT, whichare validating requirements, ensuring their testability, and generating the minimum required test cases. We analyzed 77 Soft-ware Requirements Specification (SRS) documents, extracted 149 performance requirements from those SRS, and illustratethat with PRO-TEST we can model performance requirements, find issues in those requirements and detect missing ones.We detected three not-quantifiable requirements, 43 not-quantified requirements, and 180 underspecified parameters in the149 modeled performance requirements. Furthermore, we generated 96 test environments from those models. By modelingperformance requirements with PRO-TEST, we can identify issues in the requirements related to their ambiguity, measur-ability, and completeness. Additionally, it allows to generate parameters for test environments
  •  
4.
  • Alenljung, Beatrice, et al. (författare)
  • Portraying the practice of decision-making in requirements engineering : a case of large scale bespoke development
  • 2008
  • Ingår i: Requirements Engineering. - : Springer Science and Business Media LLC. - 0947-3602 .- 1432-010X. ; 13:4, s. 257-279
  • Tidskriftsartikel (refereegranskat)abstract
    •  Complex decision-making is a prominent aspect of requirements engineering (RE) and the need for improved decision support for RE decision-makers has been identified by a number of authors in the research literature. A first step toward better decision support in requirements engineering is to understand multifaceted decision situations of decision-makers. In this paper, the focus is on RE decision-making in large scale bespoke development. The decision situation of RE decision-makers on a subsystem level has been studied at a systems engineering company and is depicted in this paper. These situations are described in terms of, e.g., RE decision matters, RE decision-making activities, and RE decision processes. Factors that affect RE decision-makers are also identified. 
  •  
5.
  • Ambreen, T., et al. (författare)
  • Empirical research in requirements engineering : trends and opportunities
  • 2018
  • Ingår i: Requirements Engineering. - : Springer London. - 0947-3602 .- 1432-010X. ; 23:1, s. 63-95
  • Tidskriftsartikel (refereegranskat)abstract
    • Requirements engineering (RE) being a foundation of software development has gained a great recognition in the recent era of prevailing software industry. A number of journals and conferences have published a great amount of RE research in terms of various tools, techniques, methods, and frameworks, with a variety of processes applicable in different software development domains. The plethora of empirical RE research needs to be synthesized to identify trends and future research directions. To represent a state-of-the-art of requirements engineering, along with various trends and opportunities of empirical RE research, we conducted a systematic mapping study to synthesize the empirical work done in RE. We used four major databases IEEE, ScienceDirect, SpringerLink and ACM and Identified 270 primary studies till the year 2012. An analysis of the data extracted from primary studies shows that the empirical research work in RE is on the increase since the year 2000. The requirements elicitation with 22 % of the total studies, requirements analysis with 19 % and RE process with 17 % are the major focus areas of empirical RE research. Non-functional requirements were found to be the most researched emerging area. The empirical work in the sub-area of requirements validation and verification is little and has a decreasing trend. The majority of the studies (50 %) used a case study research method followed by experiments (28 %), whereas the experience reports are few (6 %). A common trend in almost all RE sub-areas is about proposing new interventions. The leading intervention types are guidelines, techniques and processes. The interest in RE empirical research is on the rise as whole. However, requirements validation and verification area, despite its recognized importance, lacks empirical research at present. Furthermore, requirements evolution and privacy requirements also have little empirical research. These RE sub-areas need the attention of researchers for more empirical research. At present, the focus of empirical RE research is more about proposing new interventions. In future, there is a need to replicate existing studies as well to evaluate the RE interventions in more real contexts and scenarios. The practitioners’ involvement in RE empirical research needs to be increased so that they share their experiences of using different RE interventions and also inform us about the current requirements-related challenges and issues that they face in their work. © 2016 Springer-Verlag London
  •  
6.
  • Berntsson Svensson, Richard, 1978, et al. (författare)
  • Is role playing in Requirements Engineering Education increasing learning outcome?
  • 2017
  • Ingår i: Requirements Engineering. - : Springer Science and Business Media LLC. - 0947-3602 .- 1432-010X. ; 22:4, s. 475-489
  • Tidskriftsartikel (refereegranskat)abstract
    • Requirements Engineering has attracted a great deal of attention from researchers and practitioners in recent years. This increasing interest requires academia to provide students with a solid foundation in the subject matter. In Requirements Engineering Education (REE), it is important to cover three fundamental topics: traditional analysis and modeling skills, interviewing skills for requirements elicitation, and writing skills for specifying requirements. REE papers report about using role playing as a pedagogical tool; however, there is a surprising lack of empirical evidence on its utility. In this paper we investigate whether a higher grade in a role playing project have an effect on students' score in an individual written exam in a Requirements Engineering course. Data are collected from 412 students between the years of 2007 and 2014 at Lund University and Chalmers | University of Gothenburg. The results show that students who received a higher grade in the role playing project scored statistically significant higher in the written exam compared to the students with a lower role playing project grade.
  •  
7.
  • Berntsson Svensson, Richard, et al. (författare)
  • Setting quality targets for coming releases with QUPER - an industrial case study
  • 2012
  • Ingår i: Requirements Engineering. - : Springer Science and Business Media LLC. - 0947-3602 .- 1432-010X. ; 17:4, s. 283-298
  • Tidskriftsartikel (refereegranskat)abstract
    • Quality requirements play a critical role in driving architectural design and are an important issue in software development. Therefore, quality requirements need to be considered, specified, and quantified early during system analysis and not later in the development phase in an ad-hoc fashion. This paper presents the quality performance model that estimates quality targets in relation to market expectations as a basis for the architecting of quality requirements. The purpose of the model is to provide concepts for qualitative reasoning of quality levels in the decision-making of setting actual targets of quality requirements for coming releases of the product. The quality performance model is evaluated at one case company, using a market-driven development approach, in the electronic payment-processing domain. The results show that the model is useful for supporting early decisionmaking in, e.g., release planning of quality requirements
  •  
8.
  • Bjarnason, Elizabeth, et al. (författare)
  • The role of distances in requirements communication: a case study
  • 2017
  • Ingår i: Requirements Engineering. - : Springer Science and Business Media LLC. - 0947-3602 .- 1432-010X. ; 22, s. 1-26
  • Tidskriftsartikel (refereegranskat)abstract
    • Requirements communication plays a vital role in development projects in coordinating the customers, the business roles and the software engineers. Communication gaps represent a significant source of project failures and overruns. For example, misunderstood or uncommunicated requirements can lead to software that does not meet the customers’ requirements, and subsequent low number of sales or additional cost required to redo the implementation. We propose that requirements engineering (RE) distance measures are useful for locating gaps in requirements communication and for improving on development practice. In this paper, we present a case study of one software development project to evaluate this proposition. Thirteen RE distances were measured including geographical and cognitive distances between project members, and semantic distances between requirements and testing artefacts. The findings confirm that RE distances impact requirements communication and project coordination. Furthermore, the concept of distances was found to enable constructive group reflection on communication gaps and improvements to development practices. The insights reported in this paper can provide practitioners with an increased awareness of distances and their impact. Furthermore, the results provide a stepping stone for further research into RE distances and methods for improving on software development processes and practices.
  •  
9.
  • Carlshamre, Pär (författare)
  • Release Planning in Market-Driven Software Product Development : Provoking an Understanding
  • 2002
  • Ingår i: Requirements Engineering. - : Springer Science and Business Media LLC. - 0947-3602 .- 1432-010X. ; 7:3, s. 139-151
  • Tidskriftsartikel (refereegranskat)abstract
    • In market-driven software development, release planning is one of the most critical tasks. Selecting a subset of requirements for realisation in a certain release is as complex as it is important for the success of a software product. Despite this, the literature provides little information on how release planning is done in practice. We designed, implemented and evaluated a support tool for release planning as a means for provoking a rich understanding of the task of release planning. The tool utilises a selection algorithm which, based on value, resource estimate and interdependencies, presents a number of valid and good release suggestions. The initial attempt at supporting release planning proved to be based on an overly simplistic and structuralistic view. The results provide ample evidence that the task could be characterised as a wicked problem, which in turn has several implications for the support needed. Although the provotype could indeed support the planner, in its current version it has several serious shortcomings related to the degree of interactivity, underlying models, presentation of information and general appearance. A rich description of the task of release planning is provided. Based on these findings, a list of design implications is proposed, which is intended to guide the future design of a support tool for release planning.  
  •  
10.
  • Duboc, Leticia, et al. (författare)
  • Requirements engineering for sustainability: an awareness framework for designing software systems for a better tomorrow
  • 2020
  • Ingår i: Requirements Engineering. - : Springer Science and Business Media LLC. - 0947-3602 .- 1432-010X. ; 25:4, s. 469-492
  • Tidskriftsartikel (refereegranskat)abstract
    • Integrating novel software systems in our society, economy and environment can have far-reaching effects. As a result, software systems should be designed in such a way as to maintain or improve the sustainability of their intended socio-technical systems. However, a paradigm shift is required to raise awareness of software professionals on the potential sustainability effects of software systems. While Requirements Engineering is considered the key for driving this change, requirements engineers lack the knowledge, experience and methodological support for acting as facilitators for a broader discussion on sustainability effects. This paper presents a question-based framework for raising awareness of the potential effects of software systems on sustainability, as the first step towards enabling the required paradigm shift. An evaluation study of the framework was conducted with four groups of computer science students. The results of the study indicate that the framework is applicable to different types of systems and helps to facilitate discussions about the potential effects that software systems could have on sustainability.
  •  
11.
  • 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.
  •  
12.
  • Frattini, Julian, 1995-, et al. (författare)
  • Causality in requirements artifacts : prevalence, detection, and impact
  • 2023
  • Ingår i: Requirements Engineering. - : Springer Science+Business Media B.V.. - 0947-3602 .- 1432-010X. ; 28:1, s. 49-74
  • Tidskriftsartikel (refereegranskat)abstract
    • Causal relations in natural language (NL) requirements convey strong, semantic information. Automatically extracting such causal information enables multiple use cases, such as test case generation, but it also requires to reliably detect causal relations in the first place. Currently, this is still a cumbersome task as causality in NL requirements is still barely understood and, thus, barely detectable. In our empirically informed research, we aim at better understanding the notion of causality and supporting the automatic extraction of causal relations in NL requirements. In a first case study, we investigate 14.983 sentences from 53 requirements documents to understand the extent and form in which causality occurs. Second, we present and evaluate a tool-supported approach, called CiRA, for causality detection. We conclude with a second case study where we demonstrate the applicability of our tool and investigate the impact of causality on NL requirements. The first case study shows that causality constitutes around 28 % of all NL requirements sentences. We then demonstrate that our detection tool achieves a macro-F 1 score of 82 % on real-world data and that it outperforms related approaches with an average gain of 11.06 % in macro-Recall and 11.43 % in macro-Precision. Finally, our second case study corroborates the positive correlations of causality with features of NL requirements. The results strengthen our confidence in the eligibility of causal relations for downstream reuse, while our tool and publicly available data constitute a first step in the ongoing endeavors of utilizing causality in RE and beyond. © 2022, The Author(s).
  •  
13.
  • Frattini, Julian, 1995-, et al. (författare)
  • Requirements quality research : a harmonized theory, evaluation, and roadmap
  • 2023
  • Ingår i: Requirements Engineering. - : Springer Science+Business Media B.V.. - 0947-3602 .- 1432-010X. ; 28:4, s. 507-520
  • Tidskriftsartikel (refereegranskat)abstract
    • High-quality requirements minimize the risk of propagating defects to later stages of the software development life cycle. Achieving a sufficient level of quality is a major goal of requirements engineering. This requires a clear definition and understanding of requirements quality. Though recent publications make an effort at disentangling the complex concept of quality, the requirements quality research community lacks identity and clear structure which guides advances and puts new findings into an holistic perspective. In this research commentary, we contribute (1) a harmonized requirements quality theory organizing its core concepts, (2) an evaluation of the current state of requirements quality research, and (3) a research roadmap to guide advancements in the field. We show that requirements quality research focuses on normative rules and mostly fails to connect requirements quality to its impact on subsequent software development activities, impeding the relevance of the research. Adherence to the proposed requirements quality theory and following the outlined roadmap will be a step toward amending this gap. © 2023, The Author(s).
  •  
14.
  • Fricker, Samuel A., et al. (författare)
  • Workshop Videos for Requirements Communication
  • 2016
  • Ingår i: Requirements Engineering. - : Springer. - 0947-3602 .- 1432-010X. ; 21:4, s. 521-552
  • Tidskriftsartikel (refereegranskat)abstract
    • Shared understanding of requirements between stakeholders and the development team is a critical success factor for requirements engineering. Workshops are an effective means for achieving such shared understanding since stakeholders and team representatives can meet and discuss what a planned software system should be and how it should support achieving stakeholder goals. However, some important intended recipients of the requirements are often not present in such workshops: the developers. Thus, they cannot benefit from the in-depth understanding of the requirements and of the rationales for these requirements that develops during the workshops. The simple handover of a requirements specification hardly compensates the rich requirements understanding that is needed for the development of an acceptable system. To compensate the lack of presence in a requirements workshop, we propose to record that requirements workshop on video. If workshop participants agree to be recorded, a video is relatively simple to create and is able to capture much more aspects about requirements and rationales than a specification document. This paper presents the workshop video technique and a phenomenological evaluation of its use for requirements communication from the perspective of software developers. The results show how the technique was appreciated by observers of the video, present positive and negative feedbacks from the observers, and lead to recommendations for implementing the technique in practice.
  •  
15.
  • Gorschek, Tony, et al. (författare)
  • Industry Evaluation of the Requirements Abstraction Model
  • 2007
  • Ingår i: Requirements Engineering. - London : Springer. - 0947-3602 .- 1432-010X. ; 12:3, s. 163-190
  • Tidskriftsartikel (refereegranskat)abstract
    • Software requirements are often formulated on different levels and hence they are difficult to compare to each other. To address this issue, a model that allows for placing requirements on different levels has been developed. The model supports both abstraction and refinement of requirements, and hence requirements can both be compared with each other and to product strategies. Comparison between requirements will allow for prioritization of requirements, which in many cases is impossible if the requirements are described on different abstraction levels. Comparison to product strategies will enable early and systematic acceptance or dismissal of requirements, minimizing the risk for overloading. This paper presents an industrial evaluation of the model. It has been evaluated in two different companies, and the experiences and findings are presented. It is concluded that the requirements abstraction model provides helpful improvements to the industrial requirements engineering process.
  •  
16.
  • Gorschek, Tony, et al. (författare)
  • Industry evaluation of the Requirements Abstraction Model
  • 2008
  • Ingår i: Requirements Engineering Journal. - : Springer Science and Business Media LLC. - 0947-3602 .- 1432-010X. ; 12:3, s. 163-190
  • Tidskriftsartikel (refereegranskat)abstract
    • Software requirements are often formulated on different levels and hence they are difficult to compare to each other. To address this issue, a model that allows for placing requirements on different levels has been developed. The model supports both abstraction and refinement of requirements, and hence requirements can both be compared with each other and to product strategies. Comparison between requirements will allow for prioritization of requirements, which in many cases is impossible if the requirements are described on different abstraction levels. Comparison to product strategies will enable early and systematic acceptance or dismissal of requirements, minimizing the risk for overloading. This paper presents an industrial evaluation of the model. It has been evaluated in two different companies, and the experiences and findings are presented. It is concluded that the requirements abstraction model provides helpful improvements to the industrial requirements engineering process.
  •  
17.
  • Gorschek, Tony, et al. (författare)
  • Requirements Abstraction Model
  • 2006
  • Ingår i: Requirements Engineering. - London : Springer. - 0947-3602 .- 1432-010X. ; 11:1, s. 79-101
  • Tidskriftsartikel (refereegranskat)abstract
    • Software requirements arrive in different shapes and forms to development organizations. This is particularly the case in market-driven requirements engineering, where the requirements are on products rather than directed towards projects. This results in challenges related to making different requirements comparable. In particular, this situation was identified in a collaborative effort between academia and industry. A model, with four abstraction levels, was developed as a response to the industrial need. The model allows for placement of requirements on different levels and supports abstraction or break down of requirements to make them comparable to each other. The model was successfully validated in several steps at a company. The results from the industrial validation point to the usefulness of the model. The model will allow companies to ensure comparability between requirements, and hence it generates important input to activities such as prioritization and packaging of requirements before launching a development project.
  •  
18.
  • Gren, Lucas, 1984-, et al. (författare)
  • Is it possible to disregard obsolete requirements? a family of experiments in software effort estimation
  • 2021
  • Ingår i: Requirements Engineering. - : Springer Science and Business Media Deutschland GmbH. - 0947-3602 .- 1432-010X. ; :3, s. 459-480
  • Tidskriftsartikel (refereegranskat)abstract
    • Expert judgement is a common method for software effort estimations in practice today. Estimators are often shown extra obsolete requirements together with the real ones to be implemented. Only one previous study has been conducted on if such practices bias the estimations. We conducted six experiments with both students and practitioners to study, and quantify, the effects of obsolete requirements on software estimation. By conducting a family of six experiments using both students and practitioners as research subjects (N= 461), and by using a Bayesian Data Analysis approach, we investigated different aspects of this effect. We also argue for, and show an example of, how we by using a Bayesian approach can be more confident in our results and enable further studies with small sample sizes. We found that the presence of obsolete requirements triggered an overestimation in effort across all experiments. The effect, however, was smaller in a field setting compared to using students as subjects. Still, the over-estimations triggered by the obsolete requirements were systematically around twice the percentage of the included obsolete ones, but with a large 95% credible interval. The results have implications for both research and practice in that the found systematic error should be accounted for in both studies on software estimation and, maybe more importantly, in estimation practices to avoid over-estimations due to this systematic error. We partly explain this error to be stemming from the cognitive bias of anchoring-and-adjustment, i.e. the obsolete requirements anchored a much larger software. However, further studies are needed in order to accurately predict this effect. © 2021, The Author(s).
  •  
19.
  • Habibullah, Khan Mohammad, et al. (författare)
  • Non-functional requirements for machine learning: understanding current use and challenges among practitioners
  • 2023
  • Ingår i: Requirements Engineering. - : Springer Science and Business Media LLC. - 0947-3602 .- 1432-010X. ; 28, s. 283-316
  • Tidskriftsartikel (refereegranskat)abstract
    • Systems that rely on Machine Learning (ML systems) have differing demands on quality—known as non-functional requirements (NFRs)—from traditional systems. NFRs for ML systems may differ in their definition, measurement, scope, and comparative importance. Despite the importance of NFRs in ensuring the quality ML systems, our understanding of all of these aspects is lacking compared to our understanding of NFRs in traditional domains. We have conducted interviews and a survey to understand how NFRs for ML systems are perceived among practitioners from both industry and academia. We have identified the degree of importance that practitioners place on different NFRs, including cases where practitioners are in agreement or have differences of opinion. We explore how NFRs are defined and measured over different aspects of a ML system (i.e., model, data, or whole system). We also identify challenges associated with NFR definition and measurement. Finally, we explore differences in perspective between practitioners in industry, academia, or a blended context. This knowledge illustrates how NFRs for ML systems are treated in current practice, and helps to guide future RE for ML efforts.
  •  
20.
  • Habibullah, Khan Mohammad, et al. (författare)
  • Requirements and software engineering for automotive perception systems: an interview study
  • 2024
  • Ingår i: REQUIREMENTS ENGINEERING. - 0947-3602 .- 1432-010X. ; 29:1, s. 25-48
  • Tidskriftsartikel (refereegranskat)abstract
    • Driving automation systems, including autonomous driving and advanced driver assistance, are an important safety-critical domain. Such systems often incorporate perception systems that use machine learning to analyze the vehicle environment. We explore new or differing topics and challenges experienced by practitioners in this domain, which relate to requirements engineering (RE), quality, and systems and software engineering. We have conducted a semi-structured interview study with 19 participants across five companies and performed thematic analysis of the transcriptions. Practitioners have difficulty specifying upfront requirements and often rely on scenarios and operational design domains (ODDs) as RE artifacts. RE challenges relate to ODD detection and ODD exit detection, realistic scenarios, edge case specification, breaking down requirements, traceability, creating specifications for data and annotations, and quantifying quality requirements. Practitioners consider performance, reliability, robustness, user comfort, and-most importantly-safety as important quality attributes. Quality is assessed using statistical analysis of key metrics, and quality assurance is complicated by the addition of ML, simulation realism, and evolving standards. Systems are developed using a mix of methods, but these methods may not be sufficient for the needs of ML. Data quality methods must be a part of development methods. ML also requires a data-intensive verification and validation process, introducing data, analysis, and simulation challenges. Our findings contribute to understanding RE, safety engineering, and development methodologies for perception systems. This understanding and the collected challenges can drive future research for driving automation and other ML systems.
  •  
21.
  • Heyn, Hans-Martin, 1987, et al. (författare)
  • An empirical investigation of challenges of specifying training data and runtime monitors for critical software with machine learning and their relation to architectural decisions
  • 2024
  • Ingår i: Requirements Engineering. - 0947-3602 .- 1432-010X. ; 29, s. 97-117
  • Tidskriftsartikel (refereegranskat)abstract
    • The development and operation of critical software that contains machine learning (ML) models requires diligence and established processes. Especially the training data used during the development of ML models have major influences on the later behaviour of the system. Runtime monitors are used to provide guarantees for that behaviour. Runtime monitors for example check that the data at runtime is compatible with the data used to train the model. In a first step towards identifying challenges when specifying requirements for training data and runtime monitors, we conducted and thematically analysed ten interviews with practitioners who develop ML models for critical applications in the automotive industry. We identified 17 themes describing the challenges and classified them in six challenge groups. In a second step, we found interconnection between the challenge themes through an additional semantic analysis of the interviews. We explored how the identified challenge themes and their interconnections can be mapped to different architecture views. This step involved identifying relevant architecture views such as data, context, hardware, AI model, and functional safety views that can address the identified challenges. The article presents a list of the identified underlying challenges, identified relations between the challenges and a mapping to architecture views. The intention of this work is to highlight once more that requirement specifications and system architecture are interlinked, even for AI-specific specification challenges such as specifying requirements for training data and runtime monitoring.
  •  
22.
  • Horkoff, Jennifer, 1980, et al. (författare)
  • Goal-oriented requirements engineering: an extended systematic mapping study
  • 2019
  • Ingår i: Requirements Engineering. - : Springer Science and Business Media LLC. - 0947-3602 .- 1432-010X. ; 24:2, s. 133-160
  • Tidskriftsartikel (refereegranskat)abstract
    • Over the last two decades, much attention has been paid to the area of goal-oriented requirements engineering (GORE), where goals are used as a useful conceptualization to elicit, model, and analyze requirements, capturing alternatives and conflicts. Goal modeling has been adapted and applied to many sub-topics within requirements engineering (RE) and beyond, such as agent orientation, aspect orientation, business intelligence, model-driven development, and security. Despite extensive efforts in this field, the RE community lacks a recent, general systematic literature review of the area. In this work, we present a systematic mapping study, covering the 246 top-cited GORE-related conference and journal papers, according to Scopus. Our literature map addresses several research questions: we classify the types of papers (e.g., proposals, formalizations, meta-studies), look at the presence of evaluation, the topics covered (e.g., security, agents, scenarios), frameworks used, venues, citations, author networks, and overall publication numbers. For most questions, we evaluate trends over time. Our findings show a proliferation of papers with new ideas and few citations, with a small number of authors and papers dominating citations; however, there is a slight rise in papers which build upon past work (implementations, integrations, and extensions). We see a rise in papers concerning adaptation/variability/evolution and a slight rise in case studies. Overall, interest in GORE has increased. We use our analysis results to make recommendations concerning future GORE research and make our data publicly available.
  •  
23.
  • Ivarsson, Martin, 1980, et al. (författare)
  • Technology Transfer Decision Support in Requirements Engineering Research : A Systematic Review of REj
  • 2009
  • Ingår i: Requirements Engineering Journal. - : Springer London. - 0947-3602 .- 1432-010X. ; 14:3, s. 155-175
  • Forskningsöversikt (refereegranskat)abstract
    • One of the main goals of an applied research field such as requirements engineering is the transfer of research results to industrial use. To promote industrial adoption of technologies developed in academia, researchers need to provide tangible evidence of the advantages of using them. This can be done through industry validation, enabling researchers to test and validate technologies in a real setting with real users and applications. The evidence obtained, together with detailed information on how the validation was conducted, offers rich decision support material for industrial practitioners seeking to adopt new technologies. This paper presents a comprehensive systematic literature review of all papers published in the Requirements Engineering journal containing any type of technology evaluation. The aim is to gauge the support for technology transfer, i.e., to what degree industrial practitioners can use the reporting of technology evaluations in the journal as decision support for adopting the technologies in industrial practice. Findings show that very few evaluations offer full technology transfer support, i.e., have a realistic scale, application or subjects. The major improvement potential concerning support for technology transfer is found to be the subjects used in the evaluations. Attaining company support, including support for using practitioners as subjects, is vital for technology transfer and for researchers seeking to validate technologies.
  •  
24.
  • Karakostas, Bill, et al. (författare)
  • Workflow requirements modelling using XML
  • 2002
  • Ingår i: Requirements Engineering. - : Springer-Verlag London Limited. - 0947-3602 .- 1432-010X. ; 7:3, s. 124-138
  • Tidskriftsartikel (refereegranskat)abstract
    • When modelling inter-organisational workflow it is important not to make assumptions such as with regard to the formats of the data exchanged between the workflow participants or the technical infrastructures and platforms, as they can restrict the range of possible workflow management implementations. The approach presented in this paper allows for the conceptual modelling of workflow processes using primitive constructs such as nodes, rules and business documents. The paper presents both a graphical notation for modelling workflows as well as a mapping of the workflow constructs to XML models that follows the Workflow Management Coalition interoperability standards. This allows the modelled workflow to be interpreted and executed by a variety of workflow engines.
  •  
25.
  • Knauss, Eric, 1977, et al. (författare)
  • Continuous Clarification and Emergent Requirements Flows in Open-Commercial Software Ecosystems
  • 2018
  • Ingår i: Requirements Engineering. - : Springer Science and Business Media LLC. - 0947-3602 .- 1432-010X. ; 23:1, s. 97-117
  • Tidskriftsartikel (refereegranskat)abstract
    • Software engineering practice has shifted from the development of products in closed environments towards more open and collaborative efforts. Software development has become significantly interdependent with other systems (e.g. services, apps) and typically takes place within large ecosystems of networked communities of stakeholder organizations. Such software ecosystems promise increased innovation power and support for consumer oriented software services at scale and are characterized by a certain openness of their information flows. While such openness supports project and reputation management, it also brings requirements engineering-related challenges within the ecosystem, such as managing dynamic, emergent contributions from the ecosystem stakeholders, as well as collecting their input while protecting their IP. In this paper we report from a study of requirements communication and management practices within IBM(R)'s Collaborative Lifecycle Management(R) product development ecosystem. Our research used multiple methods for data collection, including interviews within several ecosystem actors, on-site participatory observation, and analysis of online project repositories. We chart and describe the flow of product requirements information through the ecosystem, how the open communication paradigm in software ecosystems provides opportunities for 'just-in-time' RE - and which relies on emergent contributions from the ecosystem stakeholders-, as well as some of the challenges faced when traditional requirements engineering approaches are applied within such an ecosystem. More importantly, we discuss two tradeoffs brought about by the openness in software ecosystems: i) allowing open, transparent communication while keeping intellectual property confidential within the ecosystem, and ii) having the ability to act globally on a long-term strategy while empowering product teams to act locally to answer end-users' context specific needs in a timely manner. A sufficient level of openness facilitates contributions of emergent stakeholders. The ability to include important emergent contributors early in requirements elicitation appears to be a crucial asset in software ecosystems.
  •  
26.
  • Knauss, Eric, 1977, et al. (författare)
  • Patterns of Continuous Requirements Clarification
  • 2014
  • Ingår i: Requirements Engineering. - : Springer Science and Business Media LLC. - 0947-3602 .- 1432-010X. ; 20:4, s. 383-403
  • Tidskriftsartikel (refereegranskat)abstract
    • In software projects involving large and of- ten distributed teams, requirements evolve through the collaboration of many stakeholders, supported by online tools such as mailing lists, bug tracking systems, or online discussion forums. In this collaboration, requirements typically evolve from initial ideas, through clarification, to the implementation of a stable requirement. Deviations from this expected course might in- dicate requirements that are poorly understood, need further negotiation, or better alignment with project goals. If not addressed timely, such problems can surface late in the development cycle with negative consequences such as rework, missed schedules, or overrun budget. This paper presents an approach that provides project managers’ with timely awareness of such requirements-related risks, based on automatic analysis of stakeholders’ online requirements communication. We describe a clarification classifier that automatically analyzes requirements communication in a project and detects clarification events, a catalogue of clarification patterns, and a pattern matcher that suggests communication patterns based on our pattern catalogue. Our approach has been empirically constructed and evaluated in a case study in the IBM Rational Team Concert (RTC) project. We discuss the applicability of our approach in other projects as well as avenues for extending our pattern catalogue towards a theory of clarification patterns.
  •  
27.
  • Koubarakis, Manolis, et al. (författare)
  • A retrospective on Telos as a metamodeling language for requirements engineering
  • 2021
  • Ingår i: Requirements Engineering. - : Springer. - 0947-3602 .- 1432-010X. ; 26, s. 1-23
  • Tidskriftsartikel (refereegranskat)abstract
    • Telos is a conceptual modeling language intended to capture software knowledge, such as software system requirements, domain knowledge, architectures, design decisions and more. To accomplish this, Telos was designed to be extensible in the sense that the concepts used to capture software knowledge can be defined in the language itself, instead of being built-in. This extensibility is accomplished through powerful metamodeling features, which proved very useful for interrelating heterogeneous models from requirements, model-driven software engineering, data integration, ontology engineering, cultural informatics and education. We trace the evolution of ideas and research results in the Telos project from its origins in the late eighties. Our account looks at the semantics of Telos, its various implementations and its applications. We also recount related research by other groups and the cross-influences of ideas thereof. We conclude with lessons learnt.
  •  
28.
  • Levy, Meira, et al. (författare)
  • Philanthropic conference-based requirements engineering in time of pandemic and beyond
  • 2023
  • Ingår i: Requirements Engineering. - : Springer Science and Business Media LLC. - 0947-3602 .- 1432-010X. ; 28, s. 213-227
  • Tidskriftsartikel (refereegranskat)abstract
    • As software engineering (SE) practitioners, we can help society by using our communities of experts to address a software need of a socially conscious organization. Doing so can benefit society in the locale of a SE conference and provide access to international experts for local organizations. Furthermore, established SE researchers as well as practitioners and students have the opportunity for a unique learning experience. While the SE community has already realized the importance of addressing human values and promoting social good objectives in software development, we are unaware of previous attempts to leverage SE conferences for this activity. Conferences present an opportunity to enjoy the assembly of SE practitioners, researchers, and students for the purpose of a philanthropic endeavor. Over the past four years of running a “Requirements Engineering for Social Good” event called RE Cares, co-located with the International Conference on Requirements Engineering, we worked with the stakeholders local to the conference venue. We selected stakeholders who would not necessarily have ready access to requirements engineering, software design, and development expertise otherwise, to build software targeting “good causes.” In the last two years, this event was altered to adapt to the constraints induced by COVID-19, moving to a hybrid mode and changing many of its practices accordingly. This paper summarizes and generalizes our experiences, discussing our lessons learned in the context of the pandemic and beyond and providing a framework for conducting similar social contribution in any SE conferences in general.
  •  
29.
  • Liebel, Grischa, 1987, et al. (författare)
  • Organisation and Communication Problems in Automotive Requirements Engineering
  • 2018
  • Ingår i: Requirements Engineering. - : Springer Science and Business Media LLC. - 0947-3602 .- 1432-010X. ; 23:1, s. 145-167
  • Tidskriftsartikel (refereegranskat)abstract
    • Project success in the automotive industry is highly influenced by Requirements Engineering (RE), for which communication and organisation structure play a major role, much due to the scale and distribution of these projects. However, empirical research is scarce on these aspects of automotive RE and warrants closer examination. Therefore, the purpose of this paper is to identify problems or challenges in automotive RE with respect to communication and organisation structure. Using a multiple-case study approach, we collected data via 14 semi-structured interviews at one car manufacturer and one supplier. We tested our findings from the case study with a questionnaire distributed to practitioners in the automotive industry. Our results indicate that it is difficult but increasingly important to establish communication channels outside the fixed organisation structure and that responsibilities are often unclear. Product knowledge during early requirements elicitation and context knowledge later on is lacking. Furthermore, abstraction gaps between requirements on different abstraction levels leads to inconsistencies. For academia, we formulate a concrete agenda for future research. Practitioners can use the findings to broaden their understanding of how the problems manifest and to improve their organisations.
  •  
30.
  • Linåker, Johan, et al. (författare)
  • A method for analyzing stakeholders’ influence on an open source software ecosystem’s requirements engineering process
  • 2020
  • Ingår i: Requirements Engineering. - : Springer Science and Business Media LLC. - 0947-3602 .- 1432-010X. ; 25:1, s. 115-130
  • Tidskriftsartikel (refereegranskat)abstract
    • For a firm in an open source software (OSS) ecosystem, the requirements engineering (RE) process is rather multifaceted. Apart from its typical RE process, there is a competing process, external to the firm and inherent to the firm’s ecosystem. When trying to impose an agenda in competition with other firms, and aiming to align internal product planning with the ecosystem’s RE process, firms need to consider who and how influential the other stakeholders are, and what their agendas are. The aim of the presented research is to help firms identify and analyze stakeholders in OSS ecosystems, in terms of their influence and interactions, to create awareness of their agendas, their collaborators, and how they invest their resources. To arrive at a solution artifact, we applied a design science research approach where we base artifact design on the literature and earlier work. A stakeholder influence analysis (SIA) method is proposed and demonstrated in terms of applicability and utility through a case study on the Apache Hadoop OSS ecosystem. SIA uses social network constructs to measure the stakeholders’ influence and interactions and considers the special characteristics of OSS RE to help firms structure their stakeholder analysis processes in relation to an OSS ecosystem. SIA adds a strategic aspect to the stakeholder analysis process by addressing the concepts of influence and interactions, which are important to consider while acting in collaborative and meritocratic RE cultures of OSS ecosystems.
  •  
31.
  • Maro, Salome, 1987, et al. (författare)
  • TracIMo: a traceability introduction methodology and its evaluation in an Agile development team
  • 2022
  • Ingår i: Requirements Engineering. - : Springer Science and Business Media LLC. - 0947-3602 .- 1432-010X. ; 27, s. 53-81
  • Tidskriftsartikel (refereegranskat)abstract
    • Software traceability, the ability to relate software development artifacts such as requirements, design models and code to each other, is an important aspect in software development. It yields a number of benefits such as facilitating impact analysis and tracking software changes. However, for companies to reap these benefits, a proper traceability strategy-a plan for how traceability should be managed-needs to be defined and implemented. Existing literature lacks concrete guidelines for practitioners to systematically define such a strategy. In this study, we address this gap by defining a Traceability Introduction Methodology (TracIMo), which is a methodology for systematically designing, implementing and evaluating software traceability in practice. We used design science research to design TracIMo and evaluated it in a case study with an agile development team of a company in the finance domain. Our results show that TracIMo is feasible as it allows incremental definition and evaluation of a traceability strategy that is aligned with the company's traceability goals and the existing development process. We also report practical challenges encountered when designing a traceability strategy such as defining the right level of granularity and the need for defining intermediate development artifacts.
  •  
32.
  • Montgomery, Lloyd, et al. (författare)
  • Empirical research on requirements quality : a systematic mapping study
  • 2022
  • Ingår i: Requirements Engineering. - : Springer. - 0947-3602 .- 1432-010X. ; 27:2, s. 183-209
  • Tidskriftsartikel (refereegranskat)abstract
    • Research has repeatedly shown that high-quality requirements are essential for the success of development projects. While the term “quality” is pervasive in the field of requirements engineering and while the body of research on requirements quality is large, there is no meta-study of the field that overviews and compares the concrete quality attributes addressed by the community. To fill this knowledge gap, we conducted a systematic mapping study of the scientific literature. We retrieved 6905 articles from six academic databases, which we filtered down to 105 relevant primary studies. The primary studies use empirical research to explicitly define, improve, or evaluate requirements quality. We found that empirical research on requirements quality focuses on improvement techniques, with very few primary studies addressing evidence-based definitions and evaluations of quality attributes. Among the 12 quality attributes identified, the most prominent in the field are ambiguity, completeness, consistency, and correctness. We identified 111 sub-types of quality attributes such as “template conformance” for consistency or “passive voice” for ambiguity. Ambiguity has the largest share of these sub-types. The artefacts being studied are mostly referred to in the broadest sense as “requirements”, while little research targets quality attributes in specific types of requirements such as use cases or user stories. Our findings highlight the need to conduct more empirically grounded research defining requirements quality, using more varied research methods, and addressing a more diverse set of requirements types. © 2022, The Author(s).
  •  
33.
  • Natt och Dag, Johan, et al. (författare)
  • A Feasibility Study of Automated Support for Similarity Analysis of Natural Language Requirements in Market-Driven Development
  • 2002
  • Ingår i: Requirements Engineering. - : Springer Science and Business Media LLC. - 0947-3602 .- 1432-010X. ; 7:1, s. 20-33
  • Tidskriftsartikel (refereegranskat)abstract
    • In market-driven software development there is a strong need for support to handle congestion in the requirements engineering process, which may occur as the demand for short time-to-market is combined with a rapid arrival of new requirements from many different sources. Automated analysis of the continuous flow of incoming requirements provides an opportunity to increase the efficiency of the requirements engineering process. This paper presents empirical evaluations of the benefit of automated similarity analysis of textual requirements, where existing information retrieval techniques are used to statistically measure requirements similarity. The results show that automated analysis of similarity among textual requirements is a promising technique that may provide effective support in identifying relationships between requirements.
  •  
34.
  • Navarro, Israel, et al. (författare)
  • Semantic decoupling: reducing the impact of requirement changes
  • 2010
  • Ingår i: Requirements Engineering. - : Springer Science and Business Media LLC. - 0947-3602 .- 1432-010X. ; 15:4, s. 419-437
  • Tidskriftsartikel (refereegranskat)abstract
    • The continuous stream of requirements changes that often takes place during software development and can create major problems in the development process. This paper defines a concept we call semantic coupling that can be used during all the phases of a system specification and design to reduce the impact of changing requirements. Within the general framework of the intent specifications, traceability matrices representing the mappings between different abstraction levels are used to evaluate the sensitivity of a given design to requirement changes. The practicality of using the approach on real software is demonstrated using the specification of the control software for a NASA robot designed to service the heat-resistant tiles on the Space Shuttle.
  •  
35.
  • Oliinyk, Olesia, et al. (författare)
  • Structuring automotive product lines and feature models : an exploratory study at Opel
  • 2017
  • Ingår i: Requirements Engineering. - : Springer. - 0947-3602 .- 1432-010X. ; 22, s. 105-135
  • Tidskriftsartikel (refereegranskat)abstract
    • Automotive systems are highly complex and customized systems containing a vast amount of variability. Feature modeling plays a key role in customization. Empirical evidence through industry application, and in particular methodological guidance of how to structure automotive product lines and their feature models is needed. The overall aim of this work is to provide guidance to practitioners how to structure automotive product lines and their feature models, understanding strengths and weaknesses of alternative structures. The research was conducted in three phases. In the first phase, the context situation was understood using interviews and workshops. In the second phase, possible structures of product lines and feature models were evaluated based on industry feedback collected in workshops. In the third phase, the structures were implemented in the tool GEARS and practitioner feedback was collected. One key challenge was the unavailability of structuring guidelines, which was the focus of this research. The structures considered most suitable for the automotive product line were multiple product lines with modular decomposition. The structures most suitable for the feature model were functional decomposition, using context variability, models corresponding to assets, and feature categories. Other structures have been discarded, and the rationales have been presented. It was possible to support the most suitable structures with the commercial tool GEARS. The implementation in GEARS and the feedback from the practitioners provide early indications for the potential usefulness of the structures and the tool implementation.
  •  
36.
  • Olsson, Thomas, et al. (författare)
  • A systematic literature review of empirical research on quality requirements
  • 2022
  • Ingår i: Requirements Engineering. - : Springer Science and Business Media Deutschland GmbH. - 0947-3602 .- 1432-010X. ; 27:2, s. 249-271
  • Tidskriftsartikel (refereegranskat)abstract
    • Quality requirements deal with how well a product should perform the intended functionality, such as start-up time and learnability. Researchers argue they are important and at the same time studies indicate there are deficiencies in practice. Our goal is to review the state of evidence for quality requirements. We want to understand the empirical research on quality requirements topics as well as evaluations of quality requirements solutions. We used a hybrid method for our systematic literature review. We defined a start set based on two literature reviews combined with a keyword-based search from selected publication venues. We snowballed based on the start set. We screened 530 papers and included 84 papers in our review. Case study method is the most common (43), followed by surveys (15) and tests (13). We found no replication studies. The two most commonly studied themes are (1) differentiating characteristics of quality requirements compared to other types of requirements, (2) the importance and prevalence of quality requirements. Quality models, QUPER, and the NFR method are evaluated in several studies, with positive indications. Goal modeling is the only modeling approach evaluated. However, all studies are small scale and long-term costs and impact are not studied. We conclude that more research is needed as empirical research on quality requirements is not increasing at the same rate as software engineering research in general. We see a gap between research and practice. The solutions proposed are usually evaluated in an academic context and surveys on quality requirements in industry indicate unsystematic handling of quality requirements.
  •  
37.
  • Palomares, Cristina, et al. (författare)
  • The state-of-practice in requirements elicitation : an extended interview study at 12 companies
  • 2021
  • Ingår i: Requirements Engineering. - : Springer. - 0947-3602 .- 1432-010X. ; 26:2, s. 273-299
  • Tidskriftsartikel (refereegranskat)abstract
    • Requirements engineering remains a discipline that is faced with a large number of challenges, including the implementation of a requirements elicitation process in industry. Although several proposals have been suggested by researchers and academics, little is known of the practices that are actually followed in industry. Our objective is to investigate the state-of-practice with respect to requirements elicitation, by closely examining practitioners' current practices. To this aim, we focus on the techniques that are used in industry, the roles that requirements elicitation involves, and the challenges that the requirements elicitation process is faced with. As method, we conducted an interview-based survey study involving 24 practitioners from 12 different Swedish IT companies, and we recorded the interviews and analyzed these recordings by using quantitative and qualitative methods. Several results emerged from the studies. Group interaction techniques, including meetings and workshops, are the most popular type of elicitation techniques that are employed by the practitioners, except in the case of small projects. Additionally, practitioners tend to use a variety of elicitation techniques in each project. We noted that customers are frequently involved in the elicitation process, except in the case of market-driven organizations. Technical staff (for example, developers and architects) are more frequently involved in the elicitation process compared to the involvement of business or strategic staff. Finally, we identified a number of challenges with respect to stakeholders. These challenges include difficulties in understanding and prioritizing their needs. Further, it was noted that requirements instability (i.e., caused by changing needs or priorities) was a predominant challenge. These observations need to be interpreted in the context of the study. We conclude that the relevant observations regarding the survey participants' experiences should be of interest to the industry; experiences that should be analyzed in the practitioners' context. Researchers may find evidence for the use of academic results in practice, thereby inspiring future theoretical work, as well as further empirical studies in the same area.
  •  
38.
  • Peixoto, Mariana, et al. (författare)
  • A natural language-based method to specify privacy requirements : an evaluation with practitioners
  • 2024
  • Ingår i: Requirements Engineering. - : Springer Science+Business Media B.V.. - 0947-3602 .- 1432-010X.
  • Tidskriftsartikel (refereegranskat)abstract
    • Organisations are becoming concerned with effectively dealing with privacy-related requirements. Existing Requirements Engineering methods based on structured natural language suffer from several limitations both in eliciting and specifying privacy requirements. In our previous study, we proposed a structured natural-language approach called the “Privacy Criteria Method” (PCM), which demonstrates potential advantages over user stories. Our goal is to present a PCM evaluation that focused on the opinions of software practitioners from different companies on PCM’s ability to support the specification of privacy requirements and the quality of the privacy requirements specifications produced by these software practitioners. We conducted a multiple case study to evaluate PCM in four different industrial contexts. We gathered and analysed the opinions of 21 practitioners on PCM usage regarding Coverage, Applicability, Usefulness, and Scalability. Moreover, we assessed the syntactic and semantic quality of the PCM artifacts produced by these practitioners. PCM can aid developers in elaborating requirements specifications focused on privacy with good quality. The practitioners found PCM to be useful for their companies’ development processes. PCM is considered a promising method for specifying privacy requirements. Some slight extensions of PCM may be required to tailor the method to the characteristics of the company. © The Author(s), under exclusive licence to Springer-Verlag London Ltd., part of Springer Nature 2024.
  •  
39.
  • Peixoto, Mariana, et al. (författare)
  • Evaluating a privacy requirements specification method by using a mixed-method approach : results and lessons learned
  • 2023
  • Ingår i: Requirements Engineering. - : Springer Science+Business Media B.V.. - 0947-3602 .- 1432-010X. ; 28:2, s. 229-255
  • Tidskriftsartikel (refereegranskat)abstract
    • 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.
  •  
40.
  • Penzenstadler, Birgit, 1981, et al. (författare)
  • Editorial for the REFSQ’23 special issue
  • 2024
  • Ingår i: Requirements Engineering. - 0947-3602 .- 1432-010X. ; 29:1, s. 1-2
  • Tidskriftsartikel (övrigt vetenskapligt/konstnärligt)
  •  
41.
  • Regnell, Björn, et al. (författare)
  • An industrial case study on distributed prioritisation in market-driven requirements engineering for packaged software
  • 2001
  • Ingår i: Requirements Engineering. - : Springer Science and Business Media LLC. - 0947-3602 .- 1432-010X. ; 6:1, s. 51-62
  • Tidskriftsartikel (refereegranskat)abstract
    • When developing packaged software, which is sold `off-the-shelf' on a worldwide marketplace, it is essential to collect needs and opportunities from different market segments and use this information in the prioritisation of requirements for the next software release. The paper presents an industrial case study where a distributed prioritisation process is proposed, observed and evaluated. The stakeholders in the requirements prioritisation process include marketing offices distributed around the world. A major objective of the distributed prioritisation is to gather and highlight the differences and similarities in the requirement priorities of the different market segments. The evaluation through questionnaires shows that the stakeholders found the process useful. The paper also presents novel approaches to visualise the priority distribution among stakeholders, together with measures on disagreement and satisfaction. Product management found the proposed charts valuable as decision support when selecting requirements for the next release, as they revealed unforeseen differences among stakeholder priorities. Conclusions on stakeholder tactics are provided and issues of further research are identified, including ways of addressing identified challenges
  •  
42.
  •  
43.
  • Svahnberg, Mikael, et al. (författare)
  • Uni-REPM : Validated and Improved
  • 2013
  • Ingår i: Requirements Engineering. - : Springer. - 0947-3602 .- 1432-010X. ; 18:1, s. 85-103
  • Tidskriftsartikel (refereegranskat)abstract
    • Software products are usually developed for either a specific customer (bespoke) or a broader market (market-driven). Due to their characteristic, bespoke and market-driven development face different challenges, especially concerning requirements engineering. Many challenges are caused by an inadequate requirements engineering process, and hence there is a need for process improvement frameworks based on empirical research and industry needs. In a previous article we introduced Uni-REPM, a lightweight requirements engineering process assessment framework based on a review of empirically motivated practices in market-driven and bespoke requirements engineering literature. In this article, we validate this framework in academia as well as industry, in order to prepare Uni-REPM for widespread industry use. We conduct two validations; a static validation based on interviews with seven academic experts and a dynamic validation where Uni-REPM is applied in four industrial organisations. Uni-REPM is refined according to the feedback obtained in the validations. The study shows that Uni-REPM is a quick, simple, and cost-effective solution to assess the maturity level of the requirements engineering process of projects. Moreover, the assessment method using checklists is highly usable and applicable in various international development environments.
  •  
44.
  • Svahnberg, Mikael, et al. (författare)
  • Uni-REPM : a framework for requirements engineering process assessment
  • 2015
  • Ingår i: Requirements Engineering. - : Springer. - 0947-3602 .- 1432-010X. ; 20:1, s. 91-118
  • Tidskriftsartikel (refereegranskat)abstract
    • It has been shown that potential business benefits could be achieved by assessing and improving the requirements engineering (RE) process. However, process assessment models such as CMMI and ISO9000 only cover RE shallowly. Tailored models such as REGPG and REPM, on the other hand, do not cover market-driven requirements engineering. Other attempts such as MDREPM covers market-driven requirements engineering, but correspondingly neglects bespoke requirements engineering. Moreover, the area itself has evolved so practices that once were cutting edge are now commonplace. In this article, we develop and evaluate a unified requirements engineering process maturity model (Uni-REPM) that can be used in a market-driven as well as a bespoke context. This model is based on REPM, but has evolved to reflect contemporary requirements engineering practices. Uni-REPM is primarily created based on a systematic literature review of market-driven requirements engineering practices and a literature review of bespoke practices. Based on the results, Uni-REPM is formulated. The objective of Uni-REPM is twofold. Firstly, it is expected to be applicable for assessing the maturity of RE processes in various scenarios where an organisation would use different development approaches. Secondly, it instructs practitioners about which RE practices to perform and their expected benefits. As an assessment instrument, Uni-REPM provides a simple and low-cost solution for practitioners to identify the status of their RE process. As a guidance tool, Uni-REPM lessens the gap between theoretical and practical worlds by transferring the available RE technologies from research to industry practice.
  •  
45.
  • Villamizar, Hugo, et al. (författare)
  • An efficient approach for reviewing security-related aspects in agile requirements specifications of web applications
  • 2020
  • Ingår i: Requirements Engineering. - : Springer Science and Business Media Deutschland GmbH. - 0947-3602 .- 1432-010X. ; 25:4, s. 439-468
  • Tidskriftsartikel (refereegranskat)abstract
    • Defects in requirement specifications can have severe consequences during the software development life cycle. Some of them may result in poor product quality and/or time and budget overrun due to incorrect or missing quality characteristics, such as security. This characteristic requires special attention in web applications because they have become a target for manipulating sensible data. Several concerns make security difficult to deal with. For instance, security requirements are often misunderstood and improperly specified due to lack of security expertise and emphasis on security during early stages of software development. This often leads to unspecified or ill-defined security-related aspects. These concerns become even more challenging in agile contexts, where lightweight documentation is typically produced. To tackle this problem, we designed an approach for reviewing security-related aspects in agile requirements specifications of web applications. Our proposal considers user stories and security specifications as inputs and relates those user stories to security properties via natural language processing. Based on the related security properties, our approach identifies high-level security requirements from the Open Web Application Security Project (OWASP) to be verified and generates a reading technique to support reviewers in detecting defects. We evaluate our approach via three experimental trials conducted with 56 novice software engineers, measuring effectiveness, efficiency, usefulness and ease of use. We compare our approach against using: (1) the OWASP high-level security requirements and (2) a perspective-based approach as proposed in contemporary state of the art. The results strengthen our confidence that using our approach has a positive impact (with large effect size) on the performance of inspectors in terms of effectiveness and efficiency. © 2020, Springer-Verlag London Ltd., part of Springer Nature.
  •  
46.
  • Westman, Jonas, 1986-, et al. (författare)
  • Providing Tool Support for Specifying Safety-Critical Systems by Enforcing Syntactic Contract Conditions
  • 2019
  • Ingår i: Requirements Engineering. - London : Springer. - 0947-3602 .- 1432-010X. ; 24:2, s. 231-256
  • Tidskriftsartikel (refereegranskat)abstract
    • Functional safety standards such as IEC 61508 and ISO 26262 advocate a particularly stringent requirements engineering where safety requirements must be structured in a hierarchical manner and specified in accordance with the system architecture. In contrast to the stringent requirements engineering in functional safety standards, according to previous studies, requirements engineering in industry is in general of poor quality. Contracts theory has been previously shown to be suitable for supporting such a stringent requirements engineering effort; this support has also been implemented in tools. However, to use these contract-based tools, requirements must be formalized, which is a major challenge in industry. Therefore, to support current industrial requirements engineering practice and the stringent requirements engineering in functional safety standards, it is shown how tool support can be provided even when requirements, and also architectures, are not formalized. This is achieved by enforcing syntactic, yet formal, conditions in contracts theory. Despite the need for further validation, initial findings in an industrial case study indicate high potential in realizing the proposed support in an industrial setting.
  •  
47.
  • Wohlrab, Rebekka, 1991, et al. (författare)
  • Collaborative traceability management: a multiple case study from the perspectives of organization, process, and culture
  • 2020
  • Ingår i: Requirements Engineering. - : Springer Science and Business Media LLC. - 0947-3602 .- 1432-010X. ; 25:1, s. 21-45
  • Tidskriftsartikel (refereegranskat)abstract
    • Traceability is crucial for many activities in software and systems engineering including monitoring the development progress, and proving compliance with standards. In practice, the use and maintenance of trace links are challenging as artifacts undergo constant change, and development takes place in distributed scenarios with multiple collaborating stakeholders. Although traceability management in general has been addressed in previous studies, there is a need for empirical insights into the collaborative aspects of traceability management and how it is situated in existing development contexts. The study reported in this paper aims to close this gap by investigating the relation of collaboration and traceability management, based on an understanding of characteristics of the development effort. In our multiple exploratory case study, we conducted semi-structured interviews with 24 individuals from 15 industrial projects. We explored which challenges arise, how traceability management can support collaboration, how collaboration relates to traceability management approaches, and what characteristics of the development effort influence traceability management and collaboration. We found that practitioners struggle with the following challenges: (1) collaboration across team and tool boundaries, (2) conveying the benefits of traceability, and (3) traceability maintenance. If these challenges are addressed, we found that traceability can facilitate communication and knowledge management in distributed contexts. Moreover, there exist multiple approaches to traceability management with diverse collaboration approaches, i.e., requirements-centered, developer-driven, and mixed approaches. While traceability can be leveraged in software development with both agile and plan-driven paradigms, a certain level of rigor is needed to realize its benefits and overcome challenges. To support practitioners, we provide principles of collaborative traceability management. The main contribution of this paper is empirical evidence of how culture, processes, and organization impact traceability management and collaboration, and principles to support practitioners with collaborative traceability management. We show that collaboration and traceability management have the potential to be mutually beneficial—when investing in one, also the other one is positively affected.
  •  
48.
  • Zdravkovic, Jelena, et al. (författare)
  • Capturing consumer preferences as requirements for software product lines
  • 2015
  • Ingår i: Requirements Engineering. - : Springer Science and Business Media LLC. - 0947-3602 .- 1432-010X. ; 20:1, s. 71-90
  • Tidskriftsartikel (refereegranskat)abstract
    • Delivering great consumer experiences in competitive market conditions requires software vendors to move away from traditional modes of thinking to an outside- in perspective, one that shifts their business to becoming consumer-centric. Requirements engineers operating in these conditions thus need new means to both capture real preferences of consumers and then relate them to requirements for software customized in different ways to fit anyone. Additionally, because system development models require inputs that are more concrete than abstract, the indistinct values of consumers need to be classified and formalized. To address this challenge, this study aims to establish a conceptual link between preferences of consumers and system requirements, using software product line (SPL) as a means for systematically accommodating the variations within the preferences. The novelty of this study is a conceptual model of consumer preference, which integrates generic value frameworks from both psychology and marketing, and a method for its transformation to requirements for SPL using a goal-oriented RE framework as the mediator. The presented artifacts are grounded in an empirical study related to the development of a system for online education.
  •  
49.
  • Ågren, Magnus, 1984, et al. (författare)
  • The Impact of Requirements on Systems Development Speed: A Multiple-Case Study in Automotive
  • 2019
  • Ingår i: Requirements Engineering. - : Springer Science and Business Media LLC. - 0947-3602 .- 1432-010X. ; 24:3, s. 315-340
  • Tidskriftsartikel (refereegranskat)abstract
    • Automotive manufacturers have historically adopted rigid requirements engineering processes. This allowed them to meet safety-critical requirements when producing a highly complex and differentiated product out of the integration of thousands of physical and software components. Nowadays, few software-related domains are as rapidly changing as the automotive industry. In particular, the needs of improving development speed are increasingly pushing companies in this domain toward new ways of developing software. In this paper, we investigate how the goal to increase development speed impacts how requirements are managed in the automotive domain. We start from a manager perspective, which we then complement with a more general perspective. We used a qualitative multiple-case study, organized in two steps. In the first step, we had 20 semi-structured interviews, at two automotive manufacturers. Our sampling strategy focuses on manager roles, complemented with technical specialists. In the second step, we validated our results with 12 more interviews, covering nine additional respondents and three recurring from the first step. In addition to validating our qualitative model, the second step of interviews broadens our perspective with technical experts and change managers. Our respondents indicate and rank six aspects of the current requirements engineering approach that impact development speed. These aspects include the negative impact of a requirements style dominated by safety concerns as well as decomposition of requirements over many levels of abstraction. Furthermore, the use of requirements as part of legal contracts with suppliers is seen as hindering fast collaboration. Six additional suggestions for potential improvements include domain-specific tooling, model-based requirements, test automation, and a combination of lightweight upfront requirements engineering preceding development with precise specifications post-development. Out of these 12 aspects, seven can likely be addressed as part of an ongoing agile transformation. We offer an empirical account of expectations and needs for new requirements engineering approaches in the automotive domain, necessary to coordinate hundreds of collaborating organizations developing software-intensive and potentially safety-critical systems.
  •  
50.
  • Regnell, Björn, et al. (författare)
  • A Market-driven Requirements Engineering Process - Results from an Industrial Improvement Programme
  • 1998
  • Ingår i: Requirements Engineering. - 0947-3602. ; 3:2, s. 121-129
  • Tidskriftsartikel (refereegranskat)abstract
    • In market-driven software evolution, the objectives of a requirements engineering process include the envisioning and fostering of new requirements on existing packaged software products in a way that ensures competitiveness in the market place. This paper describes an industrial, market-driven requirements engineering process which incorporates continuous requirements elicitation and prioritisation together with expert cost estimation as a basis for release planning. The company has gained a measurable improvement in delivery precision and product quality of their packaged software. The described process will act as a baseline against which new promising techniques can be evaluated in the continuation of the improvement programme.
  •  
Skapa referenser, mejla, bekava och länka
  • Resultat 1-50 av 50
Typ av publikation
tidskriftsartikel (49)
forskningsöversikt (1)
Typ av innehåll
refereegranskat (48)
övrigt vetenskapligt/konstnärligt (2)
Författare/redaktör
Knauss, Eric, 1977 (7)
Mendez, Daniel (4)
Horkoff, Jennifer, 1 ... (4)
Gorschek, Tony, 1972 ... (4)
Ferrari, Alessio (3)
Unterkalmsteiner, Mi ... (3)
visa fler...
Fucci, Davide, 1985- (3)
Wohlin, Claes (3)
Abbas, Muhammad (2)
Enoiu, Eduard Paul, ... (2)
Sundmark, Daniel (2)
Shatnawi, Anas (2)
Penzenstadler, Birgi ... (2)
Franch, Xavier (2)
Steghöfer, Jan-Phili ... (2)
Berntsson Svensson, ... (2)
Gay, Gregory, 1987 (2)
Pelliccione, Patrizi ... (2)
Zdravkovic, Jelena (1)
Helms, Remko (1)
Olsson, Thomas (1)
Saadatmand, Mehrdad, ... (1)
Saadatmand, Mehrdad (1)
Abdeen, Waleed (1)
Chen, Xingru (1)
Wnuk, Krzysztof, 198 ... (1)
Höst, Martin (1)
Lundqvist, Kristina (1)
Andersson, M (1)
Chitchyan, Ruzanna (1)
Persson, Anne (1)
Jeusfeld, Manfred A. (1)
Karlsson, J. (1)
Leifler, Ola (1)
Usman, Muhammad (1)
Wohlrab, Rebekka, 19 ... (1)
Bjarnason, Elizabeth (1)
Tichy, Matthias, 197 ... (1)
Gren, Lucas, 1984 (1)
Linåker, Johan (1)
Petersen, Kai (1)
Alenljung, Beatrice (1)
Carlshamre, Pär (1)
Piras, Luca (1)
Ågren, Magnus, 1984 (1)
Ambreen, T. (1)
Ikram, N. (1)
Niazi, M. (1)
Muccini, H. (1)
Heldal, Rogardt, 196 ... (1)
visa färre...
Lärosäte
Blekinge Tekniska Högskola (19)
Göteborgs universitet (14)
Chalmers tekniska högskola (12)
Lunds universitet (9)
Mälardalens universitet (5)
Örebro universitet (2)
visa fler...
Linköpings universitet (2)
Högskolan i Skövde (2)
RISE (2)
Kungliga Tekniska Högskolan (1)
Uppsala universitet (1)
Stockholms universitet (1)
visa färre...
Språk
Engelska (50)
Forskningsämne (UKÄ/SCB)
Naturvetenskap (44)
Teknik (9)
Samhällsvetenskap (3)

Å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