{"title":"Evaluation of a Stakeholder Satisfaction-oriented Method for Prioritising Change Requests","authors":"R. Schmid, Samuel Fricker","doi":"10.1109/RE51729.2021.00033","DOIUrl":"https://doi.org/10.1109/RE51729.2021.00033","url":null,"abstract":"The prioritisation of change requests for an evolving software is an important and complex activity in the continuous requirements engineering and release planning of an evolving product. We have explored such prioritisation with an organisation consisting of several business units appearing as stakeholders that compete for the same development resources. The challenge lay in taking objective factors like the cost-benefit ratio and technical dependencies of the requests into account while creating a high level of stakeholder satisfaction with the defined release scope. Together with the organisation, we have designed and implemented a tailored method that uses the stakeholders’ satisfaction as a structured means for validating the criteria-based prioritisation results. The paper extends prior work by taking the perspective of the organisational stakeholders and describing the method design from the organisation’s perspective, reports the use of the method in the organisation, and summarises the lessons learned from using the method in the organisation. The results are useful to increase the maturity of prioritisation in industrialpractice.","PeriodicalId":440285,"journal":{"name":"2021 IEEE 29th International Requirements Engineering Conference (RE)","volume":"110 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2021-09-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"125121015","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
Catarina Gralha, Rita de Cássia de Faria Pereira, M. Goulão, João Araújo
{"title":"On the impact of using different templates on creating and understanding user stories","authors":"Catarina Gralha, Rita de Cássia de Faria Pereira, M. Goulão, João Araújo","doi":"10.1109/RE51729.2021.00026","DOIUrl":"https://doi.org/10.1109/RE51729.2021.00026","url":null,"abstract":"Context: User stories are often used for elicitation and prioritisation of requirements. However, the lack of a widely adopted user story template, covering benefit and the usage (or not) of a persona, can affect user stories’ quality, leading to ambiguity, lack of completeness, or accidental complexity. Objectives: Our goal was to analyse the differences between 4 alternative user story templates when creating and understanding user stories. Methods: We conducted a quasi-experiment. We asked 41 participants to perform creation and understanding tasks with the user story templates. We measured their accuracy, using metrics of task success; their speed, with task duration; visual effort, collected with an eye-tracker; and participants’ perceived effort, evaluated with NASA-TLX. Results: Regarding the impact of the different templates in creating user stories, we observed statistically significant differences in some of the metrics for accuracy, speed and visual effort. For understanding user stories, we observed small differences in terms of visual effort. Conclusions: Although some templates outperformed others in a few metrics, no template obtained the best overall result. As such, we found no compelling evidence that one template is \"better\" than the others.","PeriodicalId":440285,"journal":{"name":"2021 IEEE 29th International Requirements Engineering Conference (RE)","volume":"40 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2021-09-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"129794306","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
{"title":"Perspectives on Regulatory Compliance in Software Engineering","authors":"Evelyn Kempe, Aaron K. Massey","doi":"10.1109/RE51729.2021.00012","DOIUrl":"https://doi.org/10.1109/RE51729.2021.00012","url":null,"abstract":"Compliance reviews within a software organization are internal attempts to verify regulatory and security requirements during product development before its release. However, these reviews are not enough to adequately assess and address regulatory and security requirements throughout a software's development lifecycle. We believe requirements engineers can benefit from an improved understanding of how software practitioners treat and perceive compliance requirements. This paper describes an interview study seeking to understand how regulatory and security standard requirements are addressed, how burdensome they may be for businesses, and how our participants perceived them in the software development lifecycle. We interviewed 15 software practitioners from 13 organizations with different roles in the software development process and working in various industry domains, including big tech, healthcare, data analysis, finance, and small businesses. Our findings suggest that, for our participants, the software release process is the ultimate focus for regulatory and security compliance reviews. Also, most participants suggested that having a defined process for addressing compliance requirements was freeing rather than burdensome. Finally, participants generally saw compliance requirements as an investment for both employees and customers. These findings may be unintuitive, and we discuss seven lessons this work may hold for requirements engineering.","PeriodicalId":440285,"journal":{"name":"2021 IEEE 29th International Requirements Engineering Conference (RE)","volume":"103 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2021-09-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"133160222","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
Denisse Muñante Arzapalo, A. Perini, Fitsum Meshesha Kifetew, A. Susi
{"title":"Combining risk and variability modelling for requirements analysis in SAS engineering","authors":"Denisse Muñante Arzapalo, A. Perini, Fitsum Meshesha Kifetew, A. Susi","doi":"10.1109/RE51729.2021.00044","DOIUrl":"https://doi.org/10.1109/RE51729.2021.00044","url":null,"abstract":"Research on self-adaptive systems (SASs) has proliferated in the last fifteen years. Approaches resting on models at run-time have been proposed (e.g., to model system variants), as well as methods that aim at giving requirements a key role in driving the adaptation process (e.g., to choose the most appropriate system variant). More recent research focuses on automating model-based decisions, such as requirements revision, by exploiting data generated at execution time.Uncertainty is considered a first-class citizen in SAS engineering. A well recognised technique for dealing with uncertainty is risk management. Several risk management methods exist, as well as visual modelling languages that aim at supporting risk analysis.Our objective is to investigate how complementing requirements modelling with risk modelling could support automating risk-driven requirements analysis. While risk could be identified and modelled at design-time using domain knowledge and data generated by previous system executions, their estimation will be done at run-time, and guide the selection of system behaviour that minimises the risk of the system not being compliant with requirements.In this paper, we introduce our research objective that concerns the definition of an engineering framework, called Risk4SAS, that enables risk-driven requirements analysis in SASs life-cycle and describe first steps towards its realisation, including a meta-model, which captures the dependency between risk and the characteristics of a SAS’s variants. We conclude by presenting our research road-map.","PeriodicalId":440285,"journal":{"name":"2021 IEEE 29th International Requirements Engineering Conference (RE)","volume":"102 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2021-09-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"115731282","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
{"title":"A comprehensive approach to identifying key stakeholders in complicated software ecosystems","authors":"Stephanie Lewellen","doi":"10.1109/RE51729.2021.00074","DOIUrl":"https://doi.org/10.1109/RE51729.2021.00074","url":null,"abstract":"Software stakeholders are critical to the success of software development projects, because they influence the strategic direction, the financial backing, and have specific knowledge – all of which sustains the software being developed. As the complexity of software environments increase, and expectations for cross-product integration heighten, there is more pressure on actors within software ecosystems (SECOs) to work in unison to produce reliably integrated software, efficiently. Recently collected empirical findings show that requirements managers working in SECO environments believe that all key stakeholders can be identified, but that it requires analysis, investigation and expert knowledge. Until now, the existing frameworks describing stakeholder identification do not take into account the level of dependencies that occur in SECOs nor the implications on SECO health. This research proposes that a structured comprehensive approach to identifying stakeholders in SECOs would provide practitioners the guidance they need to avoid the common pitfalls of poor stakeholder identification, including late requirements from critical stakeholders which can risk the software release schedule, software quality, and scope.","PeriodicalId":440285,"journal":{"name":"2021 IEEE 29th International Requirements Engineering Conference (RE)","volume":"124 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2021-09-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"116328490","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
{"title":"Towards a typology of questions for requirements elicitation interviews","authors":"Olesya Zaremba, S. Liaskos","doi":"10.1109/RE51729.2021.00042","DOIUrl":"https://doi.org/10.1109/RE51729.2021.00042","url":null,"abstract":"Interviewing is known to be one of the most common requirements elicitation techniques. Interviews are driven by a series of questions asked for the purpose of receiving responses that can help understanding the domain and the needs of stakeholders. However, what constitutes a successful choice and ordering of questions continues to be more of an art than a systematic process. We review literature from a broad range of disciplines in which interviewing is widely applied, in order to identify a set of categories for characterizing interview questions. The resulting typology aims at offering an initial coding language for qualitatively analyzing interview content. Such coding language can be further validated for its reliability to enable standardization and community-wide reuse. We offer examples of how such an instrument would help researchers develop and evaluate both descriptive and normative theories of interviewing.","PeriodicalId":440285,"journal":{"name":"2021 IEEE 29th International Requirements Engineering Conference (RE)","volume":"112 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2021-09-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"122118541","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
{"title":"Co-AI: A Colab-Based Tool for Abstraction Identification","authors":"Zedong Peng, Nan Niu","doi":"10.1109/RE51729.2021.00050","DOIUrl":"https://doi.org/10.1109/RE51729.2021.00050","url":null,"abstract":"Abstraction identification is aimed at discovering significant domain terms. Prior work, notably AbstFinder and RAI (relevance-driven abstraction identification), has introduced the core ideas, but offered only limited tool support. This paper presents our abstraction identification tool, Co-AI, built on the Google Colab environment allowing the users to run the tool within their web browsers, promoting tool adoption and extension. Co-AI integrates the Wikipedia pages as the domain corpus, and identifies the candidate abstractions with a set of natural language processing (NLP) patterns. Co-AI is available at: https://colab.research.google.com/drive/1ur5KILoi_n-3KY0_vJcMBQDtiSYgcYeP?usp=sharing and we welcome the community’s feedback of our tool.","PeriodicalId":440285,"journal":{"name":"2021 IEEE 29th International Requirements Engineering Conference (RE)","volume":"1 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2021-09-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"128484148","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
Rijul Saini, G. Mussbacher, Jin L. C. Guo, J. Kienzle
{"title":"DoMoBOT: A Modelling Bot for Automated and Traceable Domain Modelling","authors":"Rijul Saini, G. Mussbacher, Jin L. C. Guo, J. Kienzle","doi":"10.1109/RE51729.2021.00054","DOIUrl":"https://doi.org/10.1109/RE51729.2021.00054","url":null,"abstract":"In the initial phases of the software development cycle, domain modelling is typically performed to transform informal requirements expressed in natural language into concise and analyzable domain models. These models capture the key concepts of an application domain and their relationships in the form of class diagrams. Building domain models manually is often a time-consuming and labor-intensive task. The current approaches which aim to extract domain models automatically, are inadequate in providing insights into the modelling decisions taken by extractor systems. This inhibits modellers to quickly confirm the completeness and conciseness of extracted domain models. To address these challenges, we present DoMoBOT, a domain modelling bot that uses a traceability knowledge graph to enable traceability of modelling decisions from extracted domain model elements to requirements and vice-versa. In this tool demo paper, we showcase how the implementation and architecture of DoMoBOT facilitate modellers to extract domain models and gain insights into the modelling decisions taken by our bot.","PeriodicalId":440285,"journal":{"name":"2021 IEEE 29th International Requirements Engineering Conference (RE)","volume":"38 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2021-09-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"127639556","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
J. Wouters, R. Janssen, Bas van Hulst, J. Veenhuizen, F. Dalpiaz, S. Brinkkemper
{"title":"CrowdRE in a Governmental Setting: Lessons from Two Case Studies","authors":"J. Wouters, R. Janssen, Bas van Hulst, J. Veenhuizen, F. Dalpiaz, S. Brinkkemper","doi":"10.1109/RE51729.2021.00035","DOIUrl":"https://doi.org/10.1109/RE51729.2021.00035","url":null,"abstract":"Crowd-based Requirements Engineering, or CrowdRE, is a recent paradigm that promotes the active participation of a large number of stakeholders in RE. In CrowdRE, requirements elicitation can be crowdsourced by creating an online platform that allows stakeholders to formulate ideas regarding the specific product. Although some case studies on crowd-based elicitation exist, no conclusive evidence can be derived on the effectiveness of such techniques. In this paper, we study crowd-based elicitation within a large governmental organization. We conduct two case studies of CrowdRE within the Royal Netherlands Marechaussee. For this, we construct the KMar-Crowd method, which adapts CrowdRE ideas to the needs of governmental organizations. While one case compares the crowd-generated ideas with requirements elicited via interviews and similar techniques, the other measures the usefulness of the gathered ideas for a product for which no prior elicitation was conducted. The results of the case studies, which attracted larger crowds than in previous studies, indicate that CrowdRE can be successfully applied to engage the users of a software product in requirements elicitation. Contradicting earlier studies, the inclusion of gamification elements in the CrowdRE method did not increase the motivation to participate, possibly due to the nature of governmental organizations.","PeriodicalId":440285,"journal":{"name":"2021 IEEE 29th International Requirements Engineering Conference (RE)","volume":"62 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2021-09-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"132568054","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}