This mini-tutorial highlights and conveys key practices in Requirements Engineering that can be applied in daily projects. It synthesizes the essence of six tutorials presented at the RE'13 Tutorial's sessions, and so promotes a great opportunity for a wider audience to learn from practice and have knowledge transfer. Besides that, this session is a great stimulus to increase the global synergy between industry and academia.
{"title":"Top tips you can apply immediately to projects: Highlights from the RE'13 tutorials","authors":"Maria Lencastre, J. Beatty","doi":"10.1109/RE.2013.6636752","DOIUrl":"https://doi.org/10.1109/RE.2013.6636752","url":null,"abstract":"This mini-tutorial highlights and conveys key practices in Requirements Engineering that can be applied in daily projects. It synthesizes the essence of six tutorials presented at the RE'13 Tutorial's sessions, and so promotes a great opportunity for a wider audience to learn from practice and have knowledge transfer. Besides that, this session is a great stimulus to increase the global synergy between industry and academia.","PeriodicalId":6342,"journal":{"name":"2013 21st IEEE International Requirements Engineering Conference (RE)","volume":null,"pages":null},"PeriodicalIF":0.0,"publicationDate":"2013-07-15","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"89921617","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}
The International IEEE Requirements Engineering conference (RE) is the premier international forum for requirements engineering. However, participant interaction mechanisms have not received significant recent attention and conference attendees have suggested that interaction support could be improved. The “RE Interactive” program is a first implementation step to increase the level and quality of interaction at RE. We present here a brief background to the initiative, describe in greater detail those initiatives being introduced this year and summarize possible initiatives for future years. We describe in greater detail the focal “RE Interactive” session: Creative Collisions. This session aims to explore the power of combinatorial creativity to create unexpected ideas for the RE community by promoting creative engagements between individuals, focusing on forging new relationships within the community.
{"title":"Creative collisions: Meet and create: And other “RE interactive” suggestions","authors":"Martin Mahaux, David Callele","doi":"10.1109/RE.2013.6636756","DOIUrl":"https://doi.org/10.1109/RE.2013.6636756","url":null,"abstract":"The International IEEE Requirements Engineering conference (RE) is the premier international forum for requirements engineering. However, participant interaction mechanisms have not received significant recent attention and conference attendees have suggested that interaction support could be improved. The “RE Interactive” program is a first implementation step to increase the level and quality of interaction at RE. We present here a brief background to the initiative, describe in greater detail those initiatives being introduced this year and summarize possible initiatives for future years. We describe in greater detail the focal “RE Interactive” session: Creative Collisions. This session aims to explore the power of combinatorial creativity to create unexpected ideas for the RE community by promoting creative engagements between individuals, focusing on forging new relationships within the community.","PeriodicalId":6342,"journal":{"name":"2013 21st IEEE International Requirements Engineering Conference (RE)","volume":null,"pages":null},"PeriodicalIF":0.0,"publicationDate":"2013-07-15","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"88073633","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}
This paper describes the workshops held in conjunction with RE'13 and its corresponding presentation of results during the main conference. This paper presents the contents, structure, and format of the “Results” event: A slide show is followed by a poster session. This paper concludes with a complete list of all collocated workshops and their descriptions. The audience members of this session can expect a highly dynamic, interactive discussion of what went on during the workshops. All the interesting, new, controversial, and pioneering ideas of these exciting preceding events can be absorbed in a memorable, enjoyable and fun way.
{"title":"Workshops and doctoral symposium at RE'13: The results: Presentation session of new ideas for researchers and practitioners who weren't there","authors":"Oliver Creighton, M. Borges","doi":"10.1109/RE.2013.6636757","DOIUrl":"https://doi.org/10.1109/RE.2013.6636757","url":null,"abstract":"This paper describes the workshops held in conjunction with RE'13 and its corresponding presentation of results during the main conference. This paper presents the contents, structure, and format of the “Results” event: A slide show is followed by a poster session. This paper concludes with a complete list of all collocated workshops and their descriptions. The audience members of this session can expect a highly dynamic, interactive discussion of what went on during the workshops. All the interesting, new, controversial, and pioneering ideas of these exciting preceding events can be absorbed in a memorable, enjoyable and fun way.","PeriodicalId":6342,"journal":{"name":"2013 21st IEEE International Requirements Engineering Conference (RE)","volume":null,"pages":null},"PeriodicalIF":0.0,"publicationDate":"2013-07-15","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"86584021","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}
Safety assurance and certification are amongst the most expensive and time-consuming activities in the development of safety-critical systems. Deeming a system to be safe involves gathering convincing evidence to argue the safe operation of the system, usually according to the requirements of some safety standard. To handle large collections of safety evidence effectively, practitioners need knowledge of how to classify different types of evidence, how to structure the evidence to show fulfilment of standards' requirements, and how to assess the evidence. However, the notion of evidence is vague and safety standards' requirements can be ambiguous and difficult to understand. Major problems also arise when a system evolves, as the body of safety evidence has to be adequately maintained in order to ensure system safety and allow its demonstration. In this context, this PhD aims to propose a framework for safety evidence management in evolutionary scenarios. The thesis work will concentrate on devising a model-based and customizable infrastructure for storage, manipulation, reuse, and analysis of evolving safety evidence. The infrastructure will be developed and evaluated in the scope of OPENCOSS a large-scale European research project.
{"title":"Evidence management for evolutionary safety assurance and certification","authors":"Sunil S. Nair","doi":"10.1109/RE.2013.6636761","DOIUrl":"https://doi.org/10.1109/RE.2013.6636761","url":null,"abstract":"Safety assurance and certification are amongst the most expensive and time-consuming activities in the development of safety-critical systems. Deeming a system to be safe involves gathering convincing evidence to argue the safe operation of the system, usually according to the requirements of some safety standard. To handle large collections of safety evidence effectively, practitioners need knowledge of how to classify different types of evidence, how to structure the evidence to show fulfilment of standards' requirements, and how to assess the evidence. However, the notion of evidence is vague and safety standards' requirements can be ambiguous and difficult to understand. Major problems also arise when a system evolves, as the body of safety evidence has to be adequately maintained in order to ensure system safety and allow its demonstration. In this context, this PhD aims to propose a framework for safety evidence management in evolutionary scenarios. The thesis work will concentrate on devising a model-based and customizable infrastructure for storage, manipulation, reuse, and analysis of evolving safety evidence. The infrastructure will be developed and evaluated in the scope of OPENCOSS a large-scale European research project.","PeriodicalId":6342,"journal":{"name":"2013 21st IEEE International Requirements Engineering Conference (RE)","volume":null,"pages":null},"PeriodicalIF":0.0,"publicationDate":"2013-07-15","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"90116949","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}
Requirement engineering is one of the most critical system engineering processes, particularly when it deals with the safety requirements which are non-functional requirements and are related to emergent system properties. In fact, safety requirements must be formulated at system level and then be derived at sub-system level. The main objective of this paper is to present a new tool, “SafetyLab”, which implements a method for safety treatment of complex systems. The method allows the definition of the system safety requirements following a risk and hazard analysis, and then their derivation according to a top-down approach. It is based on the famous Failure Mode, Effects, and Criticality Analysis (FMECA) and the use of Fault Trees.
{"title":"A safety requirement engineering method and tool","authors":"R. Guillerm, H. Demmou, N. Sadou","doi":"10.1109/RE.2013.6636739","DOIUrl":"https://doi.org/10.1109/RE.2013.6636739","url":null,"abstract":"Requirement engineering is one of the most critical system engineering processes, particularly when it deals with the safety requirements which are non-functional requirements and are related to emergent system properties. In fact, safety requirements must be formulated at system level and then be derived at sub-system level. The main objective of this paper is to present a new tool, “SafetyLab”, which implements a method for safety treatment of complex systems. The method allows the definition of the system safety requirements following a risk and hazard analysis, and then their derivation according to a top-down approach. It is based on the famous Failure Mode, Effects, and Criticality Analysis (FMECA) and the use of Fault Trees.","PeriodicalId":6342,"journal":{"name":"2013 21st IEEE International Requirements Engineering Conference (RE)","volume":null,"pages":null},"PeriodicalIF":0.0,"publicationDate":"2013-07-15","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"89301892","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}
Traceability between development artefacts and mainly from and to requirements plays a major role in system lifecycle, supporting activities such as system validation, change impact analysis, and regulation compliance. Many researchers have been working on this topic and have published their work throughout the editions of the Requirements Engineering Conference. This paper aims to analyse the research on traceability published in the past 20 years of this conference and to provide insights into its contribution to the traceability area. We have selected and reviewed 70 papers in the proceedings of the conference and summarised several aspects of traceability that have been addressed and by whom. The paper also discusses the evolution of the topic at the conference, compares the results with those reported in other publications, and proposes aspects on which further research should be conducted.
{"title":"A review of traceability research at the requirements engineering conferencere@21","authors":"Sunil S. Nair, J. Vara, S. Sen","doi":"10.1109/RE.2013.6636722","DOIUrl":"https://doi.org/10.1109/RE.2013.6636722","url":null,"abstract":"Traceability between development artefacts and mainly from and to requirements plays a major role in system lifecycle, supporting activities such as system validation, change impact analysis, and regulation compliance. Many researchers have been working on this topic and have published their work throughout the editions of the Requirements Engineering Conference. This paper aims to analyse the research on traceability published in the past 20 years of this conference and to provide insights into its contribution to the traceability area. We have selected and reviewed 70 papers in the proceedings of the conference and summarised several aspects of traceability that have been addressed and by whom. The paper also discusses the evolution of the topic at the conference, compares the results with those reported in other publications, and proposes aspects on which further research should be conducted.","PeriodicalId":6342,"journal":{"name":"2013 21st IEEE International Requirements Engineering Conference (RE)","volume":null,"pages":null},"PeriodicalIF":0.0,"publicationDate":"2013-07-15","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"88805069","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}
A. Golnam, Gil Regev, A. Wegmann, Sofia Kyriakopoulou
This paper reports on a pilot study of the integration between the Systemic Enterprise Architecture Method (SEAM) and the Analytic Hierarchy Process (AHP) in a requirements engineering project. The objective of the project, conducted in one of the major banks in Switzerland, was to select a common SOA tool that could satisfy the needs of two of the bank's main business units, investment and private banking. SEAM provided help in identifying stakeholders, eliciting their requirements, and analyzing these requirements. The resulting requirements were then grouped and translated into selection criteria for the alternative SOA tools. Based on these criteria, the stakeholders chose the tool to be purchased using AHP. We describe the project, the challenges we faced and the lessons learned. These relate to the nature and traceability of requirements, to the requirements elicitation process and to the relations between the bank's business units.
{"title":"The integration of an RE method and AHP: A pilot study in a large Swiss bank","authors":"A. Golnam, Gil Regev, A. Wegmann, Sofia Kyriakopoulou","doi":"10.1109/RE.2013.6636735","DOIUrl":"https://doi.org/10.1109/RE.2013.6636735","url":null,"abstract":"This paper reports on a pilot study of the integration between the Systemic Enterprise Architecture Method (SEAM) and the Analytic Hierarchy Process (AHP) in a requirements engineering project. The objective of the project, conducted in one of the major banks in Switzerland, was to select a common SOA tool that could satisfy the needs of two of the bank's main business units, investment and private banking. SEAM provided help in identifying stakeholders, eliciting their requirements, and analyzing these requirements. The resulting requirements were then grouped and translated into selection criteria for the alternative SOA tools. Based on these criteria, the stakeholders chose the tool to be purchased using AHP. We describe the project, the challenges we faced and the lessons learned. These relate to the nature and traceability of requirements, to the requirements elicitation process and to the relations between the bank's business units.","PeriodicalId":6342,"journal":{"name":"2013 21st IEEE International Requirements Engineering Conference (RE)","volume":null,"pages":null},"PeriodicalIF":0.0,"publicationDate":"2013-07-15","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"86159422","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}
C. Ghezzi, C. Menghi, Amir Molzam Sharifloo, P. Spoletini
Conventional formal verification techniques rely on the assumption that a system's specification is completely available so that the analysis can say whether or not a set of properties will be satisfied. On the contrary, modern development lifecycles call for agileincremental and iterativeapproaches to tame the boosting complexity of modern software systems and reduce development risks. We focus here on requirements verification performed in the early exploratory stages on high-level models and we discuss how this can be integrated into an agile approach. We present a new technique to model-check incomplete high-level specifications against formally specified requirements. We do this in the context of incomplete hierarchical Statecharts, verified against a variation of CTL properties. Our approach supports step-wise specification and refinement verification. Verification can be incremental, that is alternative refinements may be separately explored and verification is only replayed for the modified parts. The results are presented by introducing the formalisms, the model-checking algorithm, and the tool we have implemented.
{"title":"On requirements verification for model refinements","authors":"C. Ghezzi, C. Menghi, Amir Molzam Sharifloo, P. Spoletini","doi":"10.1109/RE.2013.6636706","DOIUrl":"https://doi.org/10.1109/RE.2013.6636706","url":null,"abstract":"Conventional formal verification techniques rely on the assumption that a system's specification is completely available so that the analysis can say whether or not a set of properties will be satisfied. On the contrary, modern development lifecycles call for agileincremental and iterativeapproaches to tame the boosting complexity of modern software systems and reduce development risks. We focus here on requirements verification performed in the early exploratory stages on high-level models and we discuss how this can be integrated into an agile approach. We present a new technique to model-check incomplete high-level specifications against formally specified requirements. We do this in the context of incomplete hierarchical Statecharts, verified against a variation of CTL properties. Our approach supports step-wise specification and refinement verification. Verification can be incremental, that is alternative refinements may be separately explored and verification is only replayed for the modified parts. The results are presented by introducing the formalisms, the model-checking algorithm, and the tool we have implemented.","PeriodicalId":6342,"journal":{"name":"2013 21st IEEE International Requirements Engineering Conference (RE)","volume":null,"pages":null},"PeriodicalIF":0.0,"publicationDate":"2013-07-15","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"75789627","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}
One of the factors that is supposed to have a significant effect on an individual's effectiveness during requirements engineering activities is knowledge of the problem being solved by the system to be built, i.e., domain knowledge. Nevertheless, domain knowledge is a double-edged sword. While in-depth domain knowledge facilitates understanding the details of the problem, in-depth domain knowledge can promote falling for tacit assumptions of the domain and overlooking the obvious. On the other hand, lack of domain knowledge can facilitate more innovative out-of-the-domain-box idea generation. This paper describes a case study carried out in industry of the idea generation part of a requirements idea brainstorming session conducted by a team deliberately constructed with four domain experts supplied by the company participating in the case study and with four domain ignorants supplied by the authors. The results support the conclusion that having a team consisting of a mix of domain experts and domain ignorants improves the effectiveness of the idea generation part of requirements idea brainstorming.
{"title":"An industrial case study of the impact of domain ignorance on the effectiveness of requirements idea generation during requirements elicitation","authors":"Ali Niknafs, D. Berry","doi":"10.1109/RE.2013.6636730","DOIUrl":"https://doi.org/10.1109/RE.2013.6636730","url":null,"abstract":"One of the factors that is supposed to have a significant effect on an individual's effectiveness during requirements engineering activities is knowledge of the problem being solved by the system to be built, i.e., domain knowledge. Nevertheless, domain knowledge is a double-edged sword. While in-depth domain knowledge facilitates understanding the details of the problem, in-depth domain knowledge can promote falling for tacit assumptions of the domain and overlooking the obvious. On the other hand, lack of domain knowledge can facilitate more innovative out-of-the-domain-box idea generation. This paper describes a case study carried out in industry of the idea generation part of a requirements idea brainstorming session conducted by a team deliberately constructed with four domain experts supplied by the company participating in the case study and with four domain ignorants supplied by the authors. The results support the conclusion that having a team consisting of a mix of domain experts and domain ignorants improves the effectiveness of the idea generation part of requirements idea brainstorming.","PeriodicalId":6342,"journal":{"name":"2013 21st IEEE International Requirements Engineering Conference (RE)","volume":null,"pages":null},"PeriodicalIF":0.0,"publicationDate":"2013-07-15","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"89843844","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}
Modern traceability tools employ information retrieval (IR) methods to generate candidate traceability links. These methods track textual signs embedded in the system to establish relationships between software artifacts. However, as software systems evolve, new and inconsistent terminology finds its way into the system's taxonomy, thus corrupting its lexical structure and distorting its traceability tracks. In this paper, we argue that the distorted lexical tracks of the system can be systematically re-established through refactoring, a set of behavior-preserving transformations for keeping the system quality under control during evolution. To test this novel hypothesis, we investigate the effect of integrating various types of refactoring on the performance of requirements-to-code automated tracing methods. In particular, we identify the problems of missing, misplaced, and duplicated signs in software artifacts, and then examine to what extent refactorings that restore, move, and remove textual information can overcome these problems respectively. We conduct our experimental analysis using three datasets from different application domains. Results show that restoring textual information in the system has a positive impact on tracing. In contrast, refactorings that remove redundant information impact tracing negatively. Refactorings that move information among the system modules are found to have no significant effect. Our findings address several issues related to code and requirements evolution, as well as refactoring as a mechanism to enhance the practicality of automated tracing tools.
{"title":"Supporting requirements traceability through refactoring","authors":"Anas Mahmoud, Nan Niu","doi":"10.1109/RE.2013.6636703","DOIUrl":"https://doi.org/10.1109/RE.2013.6636703","url":null,"abstract":"Modern traceability tools employ information retrieval (IR) methods to generate candidate traceability links. These methods track textual signs embedded in the system to establish relationships between software artifacts. However, as software systems evolve, new and inconsistent terminology finds its way into the system's taxonomy, thus corrupting its lexical structure and distorting its traceability tracks. In this paper, we argue that the distorted lexical tracks of the system can be systematically re-established through refactoring, a set of behavior-preserving transformations for keeping the system quality under control during evolution. To test this novel hypothesis, we investigate the effect of integrating various types of refactoring on the performance of requirements-to-code automated tracing methods. In particular, we identify the problems of missing, misplaced, and duplicated signs in software artifacts, and then examine to what extent refactorings that restore, move, and remove textual information can overcome these problems respectively. We conduct our experimental analysis using three datasets from different application domains. Results show that restoring textual information in the system has a positive impact on tracing. In contrast, refactorings that remove redundant information impact tracing negatively. Refactorings that move information among the system modules are found to have no significant effect. Our findings address several issues related to code and requirements evolution, as well as refactoring as a mechanism to enhance the practicality of automated tracing tools.","PeriodicalId":6342,"journal":{"name":"2013 21st IEEE International Requirements Engineering Conference (RE)","volume":null,"pages":null},"PeriodicalIF":0.0,"publicationDate":"2013-07-15","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"89903103","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}
京公网安备 11010802042870号
京ICP备2023020795号-1
扫码关注我们
求助内容：
应助结果提醒方式：