Requirements and user interface specifications are often separated from each other and do not fit together. We integrate them in a newly defined requirements specification language (RSL). In particular, RSL allows explicit linking of requirements artefacts with elements of the user interface specification. Some of these elements are modality independent,while others can be viewed as a prototype of the ldquolookrdquo of the user interface. This integration along the representation dimension is supposed to facilitate combined work on requirements and user interfaces along the process dimension as well.
{"title":"An Integration of Requirements and User Interface Specifications","authors":"K. Mukasa, H. Kaindl","doi":"10.1109/RE.2008.55","DOIUrl":"https://doi.org/10.1109/RE.2008.55","url":null,"abstract":"Requirements and user interface specifications are often separated from each other and do not fit together. We integrate them in a newly defined requirements specification language (RSL). In particular, RSL allows explicit linking of requirements artefacts with elements of the user interface specification. Some of these elements are modality independent,while others can be viewed as a prototype of the ldquolookrdquo of the user interface. This integration along the representation dimension is supposed to facilitate combined work on requirements and user interfaces along the process dimension as well.","PeriodicalId":340621,"journal":{"name":"2008 16th IEEE International Requirements Engineering Conference","volume":"24 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":"122868622","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}
Aspect-oriented requirements engineering (AORE) techniques provide new composition mechanisms to specify and reason about dependencies that crosscut elements of a requirements specification. This paper introduces the basic concepts of aspect-oriented requirements engineering and its support for compositional reasoning--reasoning about dependencies and interactions--over a requirements specification. Typical applications of aspect-oriented requirements engineering techniques are also highlighted. The paper concludes with an annotated bibliography of key tools, techniques and application studies.
{"title":"Aspect-Oriented Requirements Engineering: An Introduction","authors":"A. Rashid","doi":"10.1109/RE.2008.58","DOIUrl":"https://doi.org/10.1109/RE.2008.58","url":null,"abstract":"Aspect-oriented requirements engineering (AORE) techniques provide new composition mechanisms to specify and reason about dependencies that crosscut elements of a requirements specification. This paper introduces the basic concepts of aspect-oriented requirements engineering and its support for compositional reasoning--reasoning about dependencies and interactions--over a requirements specification. Typical applications of aspect-oriented requirements engineering techniques are also highlighted. The paper concludes with an annotated bibliography of key tools, techniques and application studies.","PeriodicalId":340621,"journal":{"name":"2008 16th IEEE International Requirements Engineering Conference","volume":"45 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":"125573619","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 domain requirements specification (DRS) of a product line comprises the common and variable requirements of all products of the product line. Due to the variability defined for a product line, the DRS may contain contradicting requirements. For example, it may contain requirements A and not(A) which can be included in different products. Checking the consistency of DRS in product line engineering is thus not straightforward. Variability information has to be incorporated into the consistency checks to ensure that contradicting requirements do not become part of the same product requirements specification. In this paper, we present a consistency checking technique for dynamic properties of DRS based on model checking techniques. We present a proof of correctness for the technique, sketch our tool environment, and report on the application of the approach to an industrial example.
{"title":"Dynamic Consistency Checking of Domain Requirements in Product Line Engineering","authors":"Kim Lauenroth, K. Pohl","doi":"10.1109/RE.2008.21","DOIUrl":"https://doi.org/10.1109/RE.2008.21","url":null,"abstract":"The domain requirements specification (DRS) of a product line comprises the common and variable requirements of all products of the product line. Due to the variability defined for a product line, the DRS may contain contradicting requirements. For example, it may contain requirements A and not(A) which can be included in different products. Checking the consistency of DRS in product line engineering is thus not straightforward. Variability information has to be incorporated into the consistency checks to ensure that contradicting requirements do not become part of the same product requirements specification. In this paper, we present a consistency checking technique for dynamic properties of DRS based on model checking techniques. We present a proof of correctness for the technique, sketch our tool environment, and report on the application of the approach to an industrial example.","PeriodicalId":340621,"journal":{"name":"2008 16th IEEE International Requirements Engineering Conference","volume":"48 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":"131708607","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 goal of aspect-oriented requirements engineering (AORE) is to identify possible crosscutting concerns, and to develop composition specifications around those concerns. These compositions can be used to reason about potential conflicts in the requirements and to relate requirements to architecture in semantically meaningful ways. Recent work in AORE has moved from a syntactic approach to composition, which leads to fragile compositions and increased coupling between aspect and base concerns, to a semantic composition approach, based on semantics of the natural language itself. However, such compositions are at present only informally specified, and as such formal reasoning about the requirements and the subsequent derivations are difficult. We present a formal approach to these semantic-based compositions which facilitates this reasoning. We show that the approach especially lends itself to identifying conflicts between requirements and mapping compositions to a derived architecture.
{"title":"A Formal Approach to Semantic Composition of Aspect-Oriented Requirements","authors":"Nathan Weston, R. Chitchyan, A. Rashid","doi":"10.1109/RE.2008.42","DOIUrl":"https://doi.org/10.1109/RE.2008.42","url":null,"abstract":"The goal of aspect-oriented requirements engineering (AORE) is to identify possible crosscutting concerns, and to develop composition specifications around those concerns. These compositions can be used to reason about potential conflicts in the requirements and to relate requirements to architecture in semantically meaningful ways. Recent work in AORE has moved from a syntactic approach to composition, which leads to fragile compositions and increased coupling between aspect and base concerns, to a semantic composition approach, based on semantics of the natural language itself. However, such compositions are at present only informally specified, and as such formal reasoning about the requirements and the subsequent derivations are difficult. We present a formal approach to these semantic-based compositions which facilitates this reasoning. We show that the approach especially lends itself to identifying conflicts between requirements and mapping compositions to a derived architecture.","PeriodicalId":340621,"journal":{"name":"2008 16th IEEE International Requirements Engineering Conference","volume":"25 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":"131285754","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 engineering is recognized as one of the most critical parts of the software development life cycle. The goal of RE is to develop good-not perfect-requirements and to manage them during development with respect to risks and quality. RE is the discipline within systems and software engineering that bridges the entire life cycle and thus determines success or failure of a product or project. From a business perspective, it is what makes the difference between a winning product and a mere set of features. Good requirements engineering practices in industry are critical to succeed-and survive-in ever-changing markets. Current trends are making effective requirements practices even more important. First, the demand for high quality and reliable software is growing rapidly. Second, we see an increasing number of projects being developed with different suppliers having a multitude of stakeholders with different needs and ambitions that have to cooperate to achieve a shared objective. Last but not least, global delivery models rely on the ability to efficiently distribute the software life cycle across locations.
{"title":"Requirements Engineering – Industry Needs","authors":"C. Ebert, A. Hickey","doi":"10.1109/RE.2008.64","DOIUrl":"https://doi.org/10.1109/RE.2008.64","url":null,"abstract":"Requirements engineering is recognized as one of the most critical parts of the software development life cycle. The goal of RE is to develop good-not perfect-requirements and to manage them during development with respect to risks and quality. RE is the discipline within systems and software engineering that bridges the entire life cycle and thus determines success or failure of a product or project. From a business perspective, it is what makes the difference between a winning product and a mere set of features. Good requirements engineering practices in industry are critical to succeed-and survive-in ever-changing markets. Current trends are making effective requirements practices even more important. First, the demand for high quality and reliable software is growing rapidly. Second, we see an increasing number of projects being developed with different suppliers having a multitude of stakeholders with different needs and ambitions that have to cooperate to achieve a shared objective. Last but not least, global delivery models rely on the ability to efficiently distribute the software life cycle across locations.","PeriodicalId":340621,"journal":{"name":"2008 16th IEEE International Requirements Engineering Conference","volume":"41 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":"115488553","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}
Daisuke Tanabe, Kohei Uno, Kinji Akemine, Takashi Yoshikawa, H. Kaiya, M. Saeki
Requirements changes frequently occur at any time of a software development process and their management is a crucial issue to develop software of high quality. Meanwhile, recently goal-oriented analysis techniques are being put into practice to elicit requirements. In this situation, the change management of goal graphs and its support is necessary. This paper presents two topics related to change management of goal graphs; 1) version control of goal graphs and 2) impact analysis on a goal graph when its modifications occur. In our version control system, we extract the differences between successive versions of a goal graph by means of monitoring modification operations performed through a goal graph editor, and store them in a repository. Our impact analysis detects conflicts that arise when a new goal is added, and investigates the achievability of the other goals when the existing goal is deleted.
{"title":"Supporting Requirements Change Management in Goal Oriented Analysis","authors":"Daisuke Tanabe, Kohei Uno, Kinji Akemine, Takashi Yoshikawa, H. Kaiya, M. Saeki","doi":"10.1109/RE.2008.18","DOIUrl":"https://doi.org/10.1109/RE.2008.18","url":null,"abstract":"Requirements changes frequently occur at any time of a software development process and their management is a crucial issue to develop software of high quality. Meanwhile, recently goal-oriented analysis techniques are being put into practice to elicit requirements. In this situation, the change management of goal graphs and its support is necessary. This paper presents two topics related to change management of goal graphs; 1) version control of goal graphs and 2) impact analysis on a goal graph when its modifications occur. In our version control system, we extract the differences between successive versions of a goal graph by means of monitoring modification operations performed through a goal graph editor, and store them in a repository. Our impact analysis detects conflicts that arise when a new goal is added, and investigates the achievability of the other goals when the existing goal is deleted.","PeriodicalId":340621,"journal":{"name":"2008 16th IEEE International Requirements Engineering Conference","volume":"91 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":"114551790","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 engineers with many years of experience have a distinct perspective on the field. To sample this knowledge, we interviewed 34 requirements researchers and practitioners, each with up to 42 years of experience. We used open-ended, structured interviews in which we asked them to reflect on their experiences and professional development as requirements engineers over their careers. Several themes emerged: requirements engineers act as bridges between different worlds, good communication is key, good process can help but isn't everything, shorter requirements documents can be better, and good requirements are driven by customer value not technical elegance. All of these pertain to amethodical requirements engineering. Amethodical concepts are not rejections of method, but rather those concepts that are marginalized and left out of prescriptive methods for carrying out a procedure. We discuss these results and their implications.
{"title":"Marginal Notes on Amethodical Requirements Engineering: What Experts Learned from Experience","authors":"S. Sim, T. Alspaugh, B. Al-Ani","doi":"10.1109/RE.2008.52","DOIUrl":"https://doi.org/10.1109/RE.2008.52","url":null,"abstract":"Requirements engineers with many years of experience have a distinct perspective on the field. To sample this knowledge, we interviewed 34 requirements researchers and practitioners, each with up to 42 years of experience. We used open-ended, structured interviews in which we asked them to reflect on their experiences and professional development as requirements engineers over their careers. Several themes emerged: requirements engineers act as bridges between different worlds, good communication is key, good process can help but isn't everything, shorter requirements documents can be better, and good requirements are driven by customer value not technical elegance. All of these pertain to amethodical requirements engineering. Amethodical concepts are not rejections of method, but rather those concepts that are marginalized and left out of prescriptive methods for carrying out a procedure. We discuss these results and their implications.","PeriodicalId":340621,"journal":{"name":"2008 16th IEEE International Requirements Engineering Conference","volume":"12 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":"129598961","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}
Soft issues, such as politics and people's feelings, are often cited as problems in the RE process. A method aimed at improving elicitation and analysis of such 'soft' issues is described. The method consists of a taxonomy of users' values, motivations and emotions, with process guidance for eliciting and analysing these issues for the RE process.
{"title":"Investigating the Role of 'Soft Issues' in the RE Process","authors":"S. Thew, A. Sutcliffe","doi":"10.1109/RE.2008.35","DOIUrl":"https://doi.org/10.1109/RE.2008.35","url":null,"abstract":"Soft issues, such as politics and people's feelings, are often cited as problems in the RE process. A method aimed at improving elicitation and analysis of such 'soft' issues is described. The method consists of a taxonomy of users' values, motivations and emotions, with process guidance for eliciting and analysing these issues for the RE process.","PeriodicalId":340621,"journal":{"name":"2008 16th IEEE International Requirements Engineering Conference","volume":"63 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":"127243757","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 mini-tutorial introduces Web services and service-centric systems, identifies their impact on requirements engineering, and introduces new tools and techniques for engineer requirements for service-centric systems.
{"title":"Service-Centric Systems and Requirements Engineering","authors":"L. Baresi, N. Maiden, P. Sawyer","doi":"10.1109/RE.2008.60","DOIUrl":"https://doi.org/10.1109/RE.2008.60","url":null,"abstract":"This mini-tutorial introduces Web services and service-centric systems, identifies their impact on requirements engineering, and introduces new tools and techniques for engineer requirements for service-centric systems.","PeriodicalId":340621,"journal":{"name":"2008 16th IEEE International Requirements Engineering Conference","volume":"44 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":"130123247","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}
Crosscutting concerns usually affect large portions of requirements models, compromising their modularity and, consequently, their evolution. Models built using the Problem Frames (PF) approach are no exception. PF models can be better modularized by integrating aspect-oriented concepts, as these provide mechanisms to systematically deal with crosscutting model elements. This poster outlines a hybrid approach for integrating aspects and PF, supporting aspects representation through pattern, and modelling composition of aspects. This improves the definition of PF aspectual concepts, as well as their composition process.
{"title":"Aspects Composition in Problem Frames","authors":"Maria Lencastre, A. Moreira, J. Araújo, J. Castro","doi":"10.1109/RE.2008.20","DOIUrl":"https://doi.org/10.1109/RE.2008.20","url":null,"abstract":"Crosscutting concerns usually affect large portions of requirements models, compromising their modularity and, consequently, their evolution. Models built using the Problem Frames (PF) approach are no exception. PF models can be better modularized by integrating aspect-oriented concepts, as these provide mechanisms to systematically deal with crosscutting model elements. This poster outlines a hybrid approach for integrating aspects and PF, supporting aspects representation through pattern, and modelling composition of aspects. This improves the definition of PF aspectual concepts, as well as their composition process.","PeriodicalId":340621,"journal":{"name":"2008 16th IEEE International Requirements Engineering Conference","volume":"231 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":"122467410","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
扫码关注我们
求助内容：
应助结果提醒方式：