Electronic service bundles such as Internet access and voice over IP become increasingly important for the economy. The requirements engineering problem is how to compose an e-service bundle such that consumer needs are met optimally, and the suppliers provide the services economically sustainable. We propose a technique to match a consumer need with a multi-supplier bundle of commercial e-services, which we illustrate by means of a telecommunication case study.
{"title":"Value-driven Service Matching","authors":"J. Gordijn, S. Kinderen, R. Wieringa","doi":"10.1109/RE.2008.10","DOIUrl":"https://doi.org/10.1109/RE.2008.10","url":null,"abstract":"Electronic service bundles such as Internet access and voice over IP become increasingly important for the economy. The requirements engineering problem is how to compose an e-service bundle such that consumer needs are met optimally, and the suppliers provide the services economically sustainable. We propose a technique to match a consumer need with a multi-supplier bundle of commercial e-services, which we illustrate by means of a telecommunication case study.","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":"117126370","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}
Octavio Glorio, Jesús Pardillo, J. Mazón, J. Trujillo
In this paper, we have extended the i* framework for data warehouses and we have combined it with our model driven architecture (MDA) framework for the development of data warehouses. Specifically, our framework establishes a set of formal transformations between a requirement model and a conceptual multidimensional model via the QVT (query/view/transformation) language. Such transformations assure the traceability between requirements and the necessary multidimensional elements, because the goal model conceptualizes why certain multidimensional elements are required by decision makers to satisfy their information needs. The main advantage is that the conceptual multidimensional model meets every goal and requirement defined in the requirement model. To support our approach, the profiling mechanism of the Unified Modeling Language (UML) has been used to adapt i* to the data warehouses domain. The proposed model-transformation architecture have been implemented in the Eclipse development platform.
{"title":"DaWaRA: An Eclipse Plugin for Using i* on Data Warehouse Requirement Analysis","authors":"Octavio Glorio, Jesús Pardillo, J. Mazón, J. Trujillo","doi":"10.1109/RE.2008.40","DOIUrl":"https://doi.org/10.1109/RE.2008.40","url":null,"abstract":"In this paper, we have extended the i* framework for data warehouses and we have combined it with our model driven architecture (MDA) framework for the development of data warehouses. Specifically, our framework establishes a set of formal transformations between a requirement model and a conceptual multidimensional model via the QVT (query/view/transformation) language. Such transformations assure the traceability between requirements and the necessary multidimensional elements, because the goal model conceptualizes why certain multidimensional elements are required by decision makers to satisfy their information needs. The main advantage is that the conceptual multidimensional model meets every goal and requirement defined in the requirement model. To support our approach, the profiling mechanism of the Unified Modeling Language (UML) has been used to adapt i* to the data warehouses domain. The proposed model-transformation architecture have been implemented in the Eclipse development platform.","PeriodicalId":340621,"journal":{"name":"2008 16th IEEE International Requirements Engineering Conference","volume":"203 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":"124158937","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}
Natural language is the main presentation means in industrial requirements documents. In such documents, system behavior is specified in the form of scenarios, with every scenario written as a sequence of sentences in natural language. To translate scenarios to executable models, message sequence charts (MSCs), we proposed an approach that analyzes textual scenarios by means of computational linguistics by L. Kof (2007). The presented paper shows that (1) a more differentiated treatment of certain sentence types than in our previous work results in better precision of the text-to-MSC translation and (2) it is possible to automate agent identification, performed semiautomatically in our previous work.
{"title":"From Textual Scenarios to Message Sequence Charts: Inclusion of Condition Generation and Actor Extraction","authors":"L. Kof","doi":"10.1109/RE.2008.12","DOIUrl":"https://doi.org/10.1109/RE.2008.12","url":null,"abstract":"Natural language is the main presentation means in industrial requirements documents. In such documents, system behavior is specified in the form of scenarios, with every scenario written as a sequence of sentences in natural language. To translate scenarios to executable models, message sequence charts (MSCs), we proposed an approach that analyzes textual scenarios by means of computational linguistics by L. Kof (2007). The presented paper shows that (1) a more differentiated treatment of certain sentence types than in our previous work results in better precision of the text-to-MSC translation and (2) it is possible to automate agent identification, performed semiautomatically in our previous work.","PeriodicalId":340621,"journal":{"name":"2008 16th IEEE International Requirements Engineering Conference","volume":"153 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":"122289456","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}
An accurate set of traceability relations between software development artifacts is desirable to support evolutionary development. However, even where an initial set of traceability relations has been established, their maintenance during subsequent development activities is time consuming and error prone, which results in traceability decay. This paper focuses solely on the problem of maintaining a set of traceability relations in the face of evolutionary change, irrespective of whether generated manually or via automated techniques, and it limits its scope to UML-driven development activities post-requirements specification. The paper proposes an approach for the automated update of existing traceability relations after changes have been made to UML analysis and design models. The update is based upon predefined rules that recognize elementary change events as constituent steps of broader development activities. A prototype traceMaintainer has been developed to demonstrate the approach. Currently, traceMaintainer can be used with two commercial software development tools to maintain their traceability relations. The prototype has been used in two experiments. The results are discussed and our ongoing work is summarized.
{"title":"Rule-Based Maintenance of Post-Requirements Traceability Relations","authors":"Patrick Mäder, O. Gotel, I. Philippow","doi":"10.1109/RE.2008.24","DOIUrl":"https://doi.org/10.1109/RE.2008.24","url":null,"abstract":"An accurate set of traceability relations between software development artifacts is desirable to support evolutionary development. However, even where an initial set of traceability relations has been established, their maintenance during subsequent development activities is time consuming and error prone, which results in traceability decay. This paper focuses solely on the problem of maintaining a set of traceability relations in the face of evolutionary change, irrespective of whether generated manually or via automated techniques, and it limits its scope to UML-driven development activities post-requirements specification. The paper proposes an approach for the automated update of existing traceability relations after changes have been made to UML analysis and design models. The update is based upon predefined rules that recognize elementary change events as constituent steps of broader development activities. A prototype traceMaintainer has been developed to demonstrate the approach. Currently, traceMaintainer can be used with two commercial software development tools to maintain their traceability relations. The prototype has been used in two experiments. The results are discussed and our ongoing work is summarized.","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":"133723449","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}
Takako Nakatani, Shouzo Hori, Naoyasu Ubayashi, Keiichi Katamine, Masaaki Hashimoto
Requirements changes sometimes cause a project to fail. A lot of projects now follow incremental development processes so that new requirements and requirements changes can be incorporated as soon as possible.These processes are called integrated requirements processes which integrate requirements processes with other development processes. We have investigated the requirements processes of a project from beginning to end, both quantitatively and qualitatively. Our focus is to clarify the types of requirements based on the components contained within a certain portion of the software architecture. Each type reveals its typical requirements processes through its rationale. The case studied is a system to manage the orders and services of a restaurant. In this paper, we introduce the case and describe the types of requirements processes. Then we discuss the reasons why we could not elicit all the requirements in the early development processes.
{"title":"A Case Study: Requirements Elicitation Processes throughout a Project","authors":"Takako Nakatani, Shouzo Hori, Naoyasu Ubayashi, Keiichi Katamine, Masaaki Hashimoto","doi":"10.1109/RE.2008.46","DOIUrl":"https://doi.org/10.1109/RE.2008.46","url":null,"abstract":"Requirements changes sometimes cause a project to fail. A lot of projects now follow incremental development processes so that new requirements and requirements changes can be incorporated as soon as possible.These processes are called integrated requirements processes which integrate requirements processes with other development processes. We have investigated the requirements processes of a project from beginning to end, both quantitatively and qualitatively. Our focus is to clarify the types of requirements based on the components contained within a certain portion of the software architecture. Each type reveals its typical requirements processes through its rationale. The case studied is a system to manage the orders and services of a restaurant. In this paper, we introduce the case and describe the types of requirements processes. Then we discuss the reasons why we could not elicit all the requirements in the early development processes.","PeriodicalId":340621,"journal":{"name":"2008 16th IEEE International Requirements Engineering Conference","volume":"4 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":"133972016","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}
S. Jones, P. Lynch, N. Maiden, Stefanie N. Lindstaedt
In this paper, we describe a creativity workshop that was used in a large research project, called APOSDLE, to generate creative ideas and requirements for a work-integrated learning system. We present an analysis of empirical data collected during and after the workshop. On the basis of this analysis, we conclude that the work-shop was an efficient way of generating ideas for future system development. These ideas, on average, were used at least as much as requirements from other sources in writing use cases, and 18 months after the workshop were seen to have a similar degree of influence on the project to other requirements. We make some observations about the use of more and less creative ideas, and about the techniques used to generate them. We end with suggestions for further work.
{"title":"Use and Influence of Creative Ideas and Requirements for a Work-Integrated Learning System","authors":"S. Jones, P. Lynch, N. Maiden, Stefanie N. Lindstaedt","doi":"10.1109/RE.2008.54","DOIUrl":"https://doi.org/10.1109/RE.2008.54","url":null,"abstract":"In this paper, we describe a creativity workshop that was used in a large research project, called APOSDLE, to generate creative ideas and requirements for a work-integrated learning system. We present an analysis of empirical data collected during and after the workshop. On the basis of this analysis, we conclude that the work-shop was an efficient way of generating ideas for future system development. These ideas, on average, were used at least as much as requirements from other sources in writing use cases, and 18 months after the workshop were seen to have a similar degree of influence on the project to other requirements. We make some observations about the use of more and less creative ideas, and about the techniques used to generate them. We end with suggestions for further work.","PeriodicalId":340621,"journal":{"name":"2008 16th IEEE International Requirements Engineering Conference","volume":"3 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":"115844176","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}
L. Duboc, Emmanuel Letier, David S. Rosenblum, Tony Wicks
Scalability is widely recognized as an important software quality, but it is a quality that historically has lacked a consistent and systematic treatment. To address this problem, we recently presented a framework for the characterization and analysis of software systems scalability. That initial work did not provide means to instantiate the variables and functions to be used in the analysis, which could compromise its results. This risk can be mitigated through a systematic exploration of system scalability goals in the application domain during requirements engineering. This paper describes our application of goal-oriented requirements engineering (GORE) for eliciting the scalability requirements of a large, real-world financial fraud detection system. The case study reveals both the suitability and the limitations of GORE as a technique for eliciting the information needed by stakeholders to specify scalability goals of a system. In the paper, we describe these findings in detail and chart a course for future research in extending goal-oriented techniques to scalability requirements.
{"title":"A Case Study in Eliciting Scalability Requirements","authors":"L. Duboc, Emmanuel Letier, David S. Rosenblum, Tony Wicks","doi":"10.1109/RE.2008.22","DOIUrl":"https://doi.org/10.1109/RE.2008.22","url":null,"abstract":"Scalability is widely recognized as an important software quality, but it is a quality that historically has lacked a consistent and systematic treatment. To address this problem, we recently presented a framework for the characterization and analysis of software systems scalability. That initial work did not provide means to instantiate the variables and functions to be used in the analysis, which could compromise its results. This risk can be mitigated through a systematic exploration of system scalability goals in the application domain during requirements engineering. This paper describes our application of goal-oriented requirements engineering (GORE) for eliciting the scalability requirements of a large, real-world financial fraud detection system. The case study reveals both the suitability and the limitations of GORE as a technique for eliciting the information needed by stakeholders to specify scalability goals of a system. In the paper, we describe these findings in detail and chart a course for future research in extending goal-oriented techniques to scalability requirements.","PeriodicalId":340621,"journal":{"name":"2008 16th IEEE International Requirements Engineering Conference","volume":"34 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":"124901912","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 proposes a method that integrates goals and scenarios modeling techniques into system project planning and scheduling. The increasing strategic importance of IT demands that system requirements need to be integrated with managerial methods, processes and tools to support their alignment with business objectives. Despite, both requirements engineering (RE) and project management (PM) lay emphasis on the importance of effort estimation, project planning, and scheduling, their applied methods and tools are imprecise and require significant manual efforts. A case study of its application and evaluation demonstrated that the method can significantly accelerate project scheduling production (>50%) and project realization (>10%) through automated schedule production.
{"title":"A Proposed Method for Automated Project Scheduling using Goals and Scenarios","authors":"Ákos Szoke","doi":"10.1109/RE.2008.23","DOIUrl":"https://doi.org/10.1109/RE.2008.23","url":null,"abstract":"This paper proposes a method that integrates goals and scenarios modeling techniques into system project planning and scheduling. The increasing strategic importance of IT demands that system requirements need to be integrated with managerial methods, processes and tools to support their alignment with business objectives. Despite, both requirements engineering (RE) and project management (PM) lay emphasis on the importance of effort estimation, project planning, and scheduling, their applied methods and tools are imprecise and require significant manual efforts. A case study of its application and evaluation demonstrated that the method can significantly accelerate project scheduling production (>50%) and project realization (>10%) through automated schedule production.","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":"128768609","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 panel presents and discusses effective techniques for teaching requirements engineering principles and practices, in ways which actively engage students in the learning process.
该小组介绍并讨论了教学需求工程原理和实践的有效技术，以积极参与学生学习过程的方式。
{"title":"Transforming the Requirements Engineering Classroom Experience","authors":"D. Zowghi, J. Cleland-Huang","doi":"10.1109/RE.2008.66","DOIUrl":"https://doi.org/10.1109/RE.2008.66","url":null,"abstract":"This panel presents and discusses effective techniques for teaching requirements engineering principles and practices, in ways which actively engage students in the learning process.","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":"128816283","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}
Patrick Mäder, O. Gotel, Tobias Kuschke, I. Philippow
traceMaintainer is a tool that maintains post-requirements traceability amongst the elements of structural UML models. The maintenance of traceability relations is based upon predefined rules. Each rule recognizes a development activity applied to a model element. traceMaintainer carries out associated traceability updates in the background after an activity has been completed, requiring minimal manual effort and limited interaction with the developer. Currently, traceMaintainer can be used with two commercial software development (CASE) tools to update the traceability relations stored within them, while the underlying approach extends further to maintaining traceability within a heterogeneous and distributed environment of tools.
{"title":"traceMaintainer - Automated Traceability Maintenance","authors":"Patrick Mäder, O. Gotel, Tobias Kuschke, I. Philippow","doi":"10.1109/RE.2008.25","DOIUrl":"https://doi.org/10.1109/RE.2008.25","url":null,"abstract":"traceMaintainer is a tool that maintains post-requirements traceability amongst the elements of structural UML models. The maintenance of traceability relations is based upon predefined rules. Each rule recognizes a development activity applied to a model element. traceMaintainer carries out associated traceability updates in the background after an activity has been completed, requiring minimal manual effort and limited interaction with the developer. Currently, traceMaintainer can be used with two commercial software development (CASE) tools to update the traceability relations stored within them, while the underlying approach extends further to maintaining traceability within a heterogeneous and distributed environment of tools.","PeriodicalId":340621,"journal":{"name":"2008 16th IEEE International Requirements Engineering Conference","volume":"42 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":"125026552","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
扫码关注我们
求助内容：
应助结果提醒方式：