Over the last few years a large number of security patterns have been proposed. However, this large number of patterns has created a problem in selecting patterns that are appropriate for different security requirements. In this paper, we present a selection approach for security patterns, which allows us to understand in depth the trade-offs involved in the patterns and the implications of a pattern to various security requirements. Moreover, our approach supports the search for a combination of security patterns that will meet given security requirements.
{"title":"Selecting Security Patterns that Fulfill Security Requirements","authors":"M. Weiss, H. Mouratidis","doi":"10.1109/RE.2008.32","DOIUrl":"https://doi.org/10.1109/RE.2008.32","url":null,"abstract":"Over the last few years a large number of security patterns have been proposed. However, this large number of patterns has created a problem in selecting patterns that are appropriate for different security requirements. In this paper, we present a selection approach for security patterns, which allows us to understand in depth the trade-offs involved in the patterns and the implications of a pattern to various security requirements. Moreover, our approach supports the search for a combination of security patterns that will meet given security requirements.","PeriodicalId":340621,"journal":{"name":"2008 16th IEEE International Requirements Engineering Conference","volume":"2 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2008-09-08","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"128100500","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}
H. Kaindl, L. Constantine, Ó. Pastor, A. Sutcliffe, D. Zowghi
In this panel, we propose to figure out how requirements engineering and interaction design can be usefully combined. In particular, some people argue that scenarios/ use cases should be concrete, as in story-telling. Others argue for use of "essential" use cases as a methodological approach to interaction and user-interface design. Somewhat in the middle, it is argued that use cases should help acquiring the requirements in the first place. What should the practitioner believe and, in particular, do, in order to develop useful and usable software and systems? Software development and interaction design require different skills and different methods and are typically done by different people. Still, scenario-based design is proposed for several activities relevant for both tasks, such as requirements elicitation, software design, and interaction design. Symbolic modeling in this spirit is actually common to various fields. However, scenario-based approaches vary, especially with regard to their use, e.g., employing abstract use cases or integrating scenarios with functions and goals in a systematic design process. So, the key issue to be raised at the panel is how to combine different approaches, e.g., in scenario-based development, so that the interaction design as well as the development of the user interface and of the software internally result in an overall useful and useable system.
{"title":"How to Combine Requirements Engineering and Interaction Design?","authors":"H. Kaindl, L. Constantine, Ó. Pastor, A. Sutcliffe, D. Zowghi","doi":"10.1109/RE.2008.59","DOIUrl":"https://doi.org/10.1109/RE.2008.59","url":null,"abstract":"In this panel, we propose to figure out how requirements engineering and interaction design can be usefully combined. In particular, some people argue that scenarios/ use cases should be concrete, as in story-telling. Others argue for use of \"essential\" use cases as a methodological approach to interaction and user-interface design. Somewhat in the middle, it is argued that use cases should help acquiring the requirements in the first place. What should the practitioner believe and, in particular, do, in order to develop useful and usable software and systems? Software development and interaction design require different skills and different methods and are typically done by different people. Still, scenario-based design is proposed for several activities relevant for both tasks, such as requirements elicitation, software design, and interaction design. Symbolic modeling in this spirit is actually common to various fields. However, scenario-based approaches vary, especially with regard to their use, e.g., employing abstract use cases or integrating scenarios with functions and goals in a systematic design process. So, the key issue to be raised at the panel is how to combine different approaches, e.g., in scenario-based development, so that the interaction design as well as the development of the user interface and of the software internally result in an overall useful and useable system.","PeriodicalId":340621,"journal":{"name":"2008 16th IEEE International Requirements Engineering Conference","volume":"124 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2008-09-08","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"114709979","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}
We propose an approach to runtime feature composition and conflict resolution that combines arbitration and contingencies. By arbitration we mean the resolution of conflicts between features using priorities. Contingency means having several specifications per feature, satisfying the same requirement, depending on the current state of the shared resource. Evaluation of our approach shows that combining arbitration and contingencies ensures that in the event of a conflict, requirements of the conflicting features are eventually satisfied.
{"title":"Building Contingencies into Specifications","authors":"A. Nhlabatsi, R. Laney, B. Nuseibeh","doi":"10.1109/RE.2008.65","DOIUrl":"https://doi.org/10.1109/RE.2008.65","url":null,"abstract":"We propose an approach to runtime feature composition and conflict resolution that combines arbitration and contingencies. By arbitration we mean the resolution of conflicts between features using priorities. Contingency means having several specifications per feature, satisfying the same requirement, depending on the current state of the shared resource. Evaluation of our approach shows that combining arbitration and contingencies ensures that in the event of a conflict, requirements of the conflicting features are eventually satisfied.","PeriodicalId":340621,"journal":{"name":"2008 16th IEEE International Requirements Engineering Conference","volume":"36 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2008-09-08","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"114402023","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. Finkelstein, M. Harman, S. Mansouri, Jian Ren, Yuanyuan Zhang
Requirements engineering for multiple customers, each of whom have competing and often conflicting priorities, raises issues of negotiation, mediation and conflict resolution. This paper uses a multi-objective optimisation approach to support investigation of the trade-offs in various notions of fairness between multiple customers. Results are presented to validate the approach using two real-world data sets and also using data sets created specifically to stress test the approach. Simple graphical techniques are used to visualize the solution space.
{"title":"“Fairness Analysis” in Requirements Assignments","authors":"A. Finkelstein, M. Harman, S. Mansouri, Jian Ren, Yuanyuan Zhang","doi":"10.1109/RE.2008.61","DOIUrl":"https://doi.org/10.1109/RE.2008.61","url":null,"abstract":"Requirements engineering for multiple customers, each of whom have competing and often conflicting priorities, raises issues of negotiation, mediation and conflict resolution. This paper uses a multi-objective optimisation approach to support investigation of the trade-offs in various notions of fairness between multiple customers. Results are presented to validate the approach using two real-world data sets and also using data sets created specifically to stress test the approach. Simple graphical techniques are used to visualize the solution space.","PeriodicalId":340621,"journal":{"name":"2008 16th IEEE International Requirements Engineering Conference","volume":"222 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2008-09-08","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"131590090","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}
Requirements reuse has become one of the most challenging topics in the Requirements Engineering (RE) field over the last years. Tangible solutions are needed to address the practicalities. This paper aims to show how such a solution can be integrated into a well-known RE tool. An add-in was created to ensure the coherency of reused specifications within the product family (PF) and to allow their evolution in future programs of the PF. This paper also presents the experience gained in the creation of PF specifications in military aircraft on-board systems for tactical missions. This kind of system typically reuses components associated with a standard set of sensors capturing real-time battlefield information. A reuse model and genuine data regarding savings are provided to illustrate the economic benefits derived from the systematic reuse of requirements. Inferred potential additional savings from the reuse of testing procedures and design elements are also outlined.
{"title":"A Practical Approach to Requirements Reuse in Product Families of On-Board Systems","authors":"Antonio Monzón","doi":"10.1109/RE.2008.19","DOIUrl":"https://doi.org/10.1109/RE.2008.19","url":null,"abstract":"Requirements reuse has become one of the most challenging topics in the Requirements Engineering (RE) field over the last years. Tangible solutions are needed to address the practicalities. This paper aims to show how such a solution can be integrated into a well-known RE tool. An add-in was created to ensure the coherency of reused specifications within the product family (PF) and to allow their evolution in future programs of the PF. This paper also presents the experience gained in the creation of PF specifications in military aircraft on-board systems for tactical missions. This kind of system typically reuses components associated with a standard set of sensors capturing real-time battlefield information. A reuse model and genuine data regarding savings are provided to illustrate the economic benefits derived from the systematic reuse of requirements. Inferred potential additional savings from the reuse of testing procedures and design elements are also outlined.","PeriodicalId":340621,"journal":{"name":"2008 16th IEEE International Requirements Engineering Conference","volume":"13 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2008-09-08","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"116841159","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}
Without distinguishing unstable from stable features and anticipating likely new features, building evolvability into software systems can be time-consuming and, above all, ineffective. This paper introduces a method based on a software evolution model whose goal is to help requirements engineers and product managers identify the unstable features of an embedded system and anticipate its potential adaptation needs in the future, with the aim of planning for changes beforehand. The core characteristic of this method is its support for systematic reasoning on requirements volatility and planning for changes. An application of the method in the domain of assisted living is described as a proof-of-concept, providing both a preliminary validation of the proposed solution and a useful example of its use.
{"title":"Proactively Managing the Evolution of Embedded System Requirements","authors":"Karina Villela, Jörg Dörr, Anne Gross","doi":"10.1109/RE.2008.57","DOIUrl":"https://doi.org/10.1109/RE.2008.57","url":null,"abstract":"Without distinguishing unstable from stable features and anticipating likely new features, building evolvability into software systems can be time-consuming and, above all, ineffective. This paper introduces a method based on a software evolution model whose goal is to help requirements engineers and product managers identify the unstable features of an embedded system and anticipate its potential adaptation needs in the future, with the aim of planning for changes beforehand. The core characteristic of this method is its support for systematic reasoning on requirements volatility and planning for changes. An application of the method in the domain of assisted living is described as a proof-of-concept, providing both a preliminary validation of the proposed solution and a useful example of its use.","PeriodicalId":340621,"journal":{"name":"2008 16th IEEE International Requirements Engineering Conference","volume":"17 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2008-09-08","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"126800162","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 requirements engineering (RE) field recognizes that many practitioners need help attaining the complex set of skills required to perform quality RE work. RE training courses offer a range of opportunities to acquire those skills, however most courses follow a traditional lecture-based approach. Research from other fields has demonstrated that the use of games can be an effective tool to improve student learning. The goal of this paper is to report the authorspsila initial experiences with using games to enhance RE training. This paper introduces existing research on the use of games in training and explains how it was reviewed and applied to RE training. A case study describes the specific experiences with and examples of games created for a requirements visualization training course. Future work is suggested which builds upon these early experiences in using such games.
{"title":"Games-Based Requirements Engineering Training: An Initial Experience Report","authors":"J. Beatty, M. Alexander","doi":"10.1109/RE.2008.15","DOIUrl":"https://doi.org/10.1109/RE.2008.15","url":null,"abstract":"The requirements engineering (RE) field recognizes that many practitioners need help attaining the complex set of skills required to perform quality RE work. RE training courses offer a range of opportunities to acquire those skills, however most courses follow a traditional lecture-based approach. Research from other fields has demonstrated that the use of games can be an effective tool to improve student learning. The goal of this paper is to report the authorspsila initial experiences with using games to enhance RE training. This paper introduces existing research on the use of games in training and explains how it was reviewed and applied to RE training. A case study describes the specific experiences with and examples of games created for a requirements visualization training course. Future work is suggested which builds upon these early experiences in using such games.","PeriodicalId":340621,"journal":{"name":"2008 16th IEEE International Requirements Engineering Conference","volume":"647 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2008-09-08","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"122700750","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}
Service-centric software systems offer new opportunities for requirements processes. This paper reports a new tool designed to increase the completeness of system requirements using information about designs and implementations of web services. It presents an algorithm for retrieving web services in domains that are analogical to a current requirements problem, to support creative thinking about requirements for that problem. It describes how the algorithm parses and analogically matches natural language descriptions of system requirements and web service descriptions. The paper also reports 2 evaluations of the tool that demonstrate improvements to specifications of requirements for a system in the automotive domain.
{"title":"Inventing Requirements from Software: An Empirical Investigation with Web Services","authors":"K. Zachos, N. Maiden","doi":"10.1109/RE.2008.39","DOIUrl":"https://doi.org/10.1109/RE.2008.39","url":null,"abstract":"Service-centric software systems offer new opportunities for requirements processes. This paper reports a new tool designed to increase the completeness of system requirements using information about designs and implementations of web services. It presents an algorithm for retrieving web services in domains that are analogical to a current requirements problem, to support creative thinking about requirements for that problem. It describes how the algorithm parses and analogically matches natural language descriptions of system requirements and web service descriptions. The paper also reports 2 evaluations of the tool that demonstrate improvements to specifications of requirements for a system in the automotive domain.","PeriodicalId":340621,"journal":{"name":"2008 16th IEEE International Requirements Engineering Conference","volume":"5 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2008-09-08","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"130390505","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}
Katharina Wolter, M. Smialek, Daniel Bildhauer, H. Kaindl
In order to make requirements comprehensible to humans and as unambiguous as possible, a glossary and/or domain model is needed for defining the terminology used. Unless these are available from related projects, however,they are hard to create. Therefore, we propose to reuse terminology and its definition for requirements specifications from the semantic lexicon WordNet. For making this useful, however, we had to deal with the issue of disambiguation of the general terminology there for a given domain of a requirements specification.
{"title":"Reusing Terminology for Requirements Specifications from WordNet","authors":"Katharina Wolter, M. Smialek, Daniel Bildhauer, H. Kaindl","doi":"10.1109/RE.2008.56","DOIUrl":"https://doi.org/10.1109/RE.2008.56","url":null,"abstract":"In order to make requirements comprehensible to humans and as unambiguous as possible, a glossary and/or domain model is needed for defining the terminology used. Unless these are available from related projects, however,they are hard to create. Therefore, we propose to reuse terminology and its definition for requirements specifications from the semantic lexicon WordNet. For making this useful, however, we had to deal with the issue of disambiguation of the general terminology there for a given domain of a requirements specification.","PeriodicalId":340621,"journal":{"name":"2008 16th IEEE International Requirements Engineering Conference","volume":"1 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2008-09-08","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"130476759","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}
D. Schmitz, H. Nissen, M. Jarke, T. Rose, P. Drews, Frank J. Heßeler, Michael Reke
Since nowadays more and more control systems are realised within software on electronic control units, a conceptual integration of control systems engineering and software engineering must be aimed at. Within this work, we build on a proposal to use the software requirements formalism i* to enable a combined investigation of control systems' and software requirements. While i*'s modelling means have turned out to be sufficiently expressive, two characteristics of control systems still need to be addressed: firstly, how to incorporate domain knowledge especially about the system to be controlled in the requirements development process and secondly, how to specifically support small and medium-sized companies (SMEs) that are the main driver for innovations in this domain. Due to their innovativeness and flexibility, the SMEs usually follow a project-oriented customer-specific development approach. To be nonetheless cost-effective, especially during the offer development phase, we develop a mechanism and a tool to compare a current requirements model with requirements models of control systems from earlier projects. Altogether this reduces time and increases reliability in regard to the identification of reusable software artefacts.
{"title":"Requirements Engineering for Control Systems Development in Small and Medium-Sized Enterprises","authors":"D. Schmitz, H. Nissen, M. Jarke, T. Rose, P. Drews, Frank J. Heßeler, Michael Reke","doi":"10.1109/RE.2008.27","DOIUrl":"https://doi.org/10.1109/RE.2008.27","url":null,"abstract":"Since nowadays more and more control systems are realised within software on electronic control units, a conceptual integration of control systems engineering and software engineering must be aimed at. Within this work, we build on a proposal to use the software requirements formalism i* to enable a combined investigation of control systems' and software requirements. While i*'s modelling means have turned out to be sufficiently expressive, two characteristics of control systems still need to be addressed: firstly, how to incorporate domain knowledge especially about the system to be controlled in the requirements development process and secondly, how to specifically support small and medium-sized companies (SMEs) that are the main driver for innovations in this domain. Due to their innovativeness and flexibility, the SMEs usually follow a project-oriented customer-specific development approach. To be nonetheless cost-effective, especially during the offer development phase, we develop a mechanism and a tool to compare a current requirements model with requirements models of control systems from earlier projects. Altogether this reduces time and increases reliability in regard to the identification of reusable software artefacts.","PeriodicalId":340621,"journal":{"name":"2008 16th IEEE International Requirements Engineering Conference","volume":"9 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2008-09-08","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"134342911","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
扫码关注我们
求助内容：
应助结果提醒方式：