Pub Date : 1998-04-06DOI: 10.1109/ICRE.1998.667829
K. Weidenhaupt, K. Pohl, M. Jarke, P. Haumer
Summary form only given. Scenario-based approaches are attracting more and more interest in requirements engineering research and practice. The research literature offers an increasing number of scenario-related methods, models and notations which highlight the consideration of concrete system descriptions from a usage-oriented perspective, prior to abstract conceptual modelling of function, data and behavior. Scenario use is also becoming a pervasive phenomenon in industrial practice, but comprehensive and expressive studies on the practical relevance of the techniques proposed by research are still rare. The European ESPRIT project CREWS (Cooperative Requirements Engineering With Scenarios) aims at a deeper understanding of the diversity of scenarios, in order to help improve methodological and tool support for scenario-based requirements engineering. The authors consider the two-pronged strategy being followed to gain this understanding.
{"title":"Scenario usage in system development: a report on current practice","authors":"K. Weidenhaupt, K. Pohl, M. Jarke, P. Haumer","doi":"10.1109/ICRE.1998.667829","DOIUrl":"https://doi.org/10.1109/ICRE.1998.667829","url":null,"abstract":"Summary form only given. Scenario-based approaches are attracting more and more interest in requirements engineering research and practice. The research literature offers an increasing number of scenario-related methods, models and notations which highlight the consideration of concrete system descriptions from a usage-oriented perspective, prior to abstract conceptual modelling of function, data and behavior. Scenario use is also becoming a pervasive phenomenon in industrial practice, but comprehensive and expressive studies on the practical relevance of the techniques proposed by research are still rare. The European ESPRIT project CREWS (Cooperative Requirements Engineering With Scenarios) aims at a deeper understanding of the diversity of scenarios, in order to help improve methodological and tool support for scenario-based requirements engineering. The authors consider the two-pronged strategy being followed to gain this understanding.","PeriodicalId":207183,"journal":{"name":"Proceedings of IEEE International Symposium on Requirements Engineering: RE '98","volume":"25 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"1998-04-06","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"126576225","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}
Pub Date : 1998-04-06DOI: 10.1109/ICRE.1998.667827
N. Leveson
Software is a human product and specification languages are used to help humans perform the various problem solving activities involved in software development and evolution. This paper proposes an approach, called intent specifications, to designing system and software specifications based on research in systems theory, cognitive psychology, and human-machine interaction. The goal is to provide specifications that support software engineering activities by grounding specification design on psychological principles of how humans use specifications to solve problems as well as on basic system engineering principles.
{"title":"Intent specifications: an approach to building human-centered specifications","authors":"N. Leveson","doi":"10.1109/ICRE.1998.667827","DOIUrl":"https://doi.org/10.1109/ICRE.1998.667827","url":null,"abstract":"Software is a human product and specification languages are used to help humans perform the various problem solving activities involved in software development and evolution. This paper proposes an approach, called intent specifications, to designing system and software specifications based on research in systems theory, cognitive psychology, and human-machine interaction. The goal is to provide specifications that support software engineering activities by grounding specification design on psychological principles of how humans use specifications to solve problems as well as on basic system engineering principles.","PeriodicalId":207183,"journal":{"name":"Proceedings of IEEE International Symposium on Requirements Engineering: RE '98","volume":"1 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"1998-04-06","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"115933580","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}
Pub Date : 1998-04-06DOI: 10.1109/ICRE.1998.667816
R. Smith
This experience report chronicles the development and use of a Requirements Quality Model (RQM), an evaluation tool that can be used to generate process improvements and an organizational rating against ten categories of requirements development and management activities. The tool was developed considering experience gained from successes from the Cellular Switching Product's software quality program and employing key quality factors from software industry standards such as the SEI Capability Maturity Model and IEEE Standard 830. The RQM enables an evaluation of the four key dimensions of successful requirements engineering practice: people, process, software roofs, and the product. The experiences reported and lessons learned will help others who may wish to develop a similar software quality evaluation tool.
{"title":"Using a quality model framework to strengthen the requirements bridge","authors":"R. Smith","doi":"10.1109/ICRE.1998.667816","DOIUrl":"https://doi.org/10.1109/ICRE.1998.667816","url":null,"abstract":"This experience report chronicles the development and use of a Requirements Quality Model (RQM), an evaluation tool that can be used to generate process improvements and an organizational rating against ten categories of requirements development and management activities. The tool was developed considering experience gained from successes from the Cellular Switching Product's software quality program and employing key quality factors from software industry standards such as the SEI Capability Maturity Model and IEEE Standard 830. The RQM enables an evaluation of the four key dimensions of successful requirements engineering practice: people, process, software roofs, and the product. The experiences reported and lessons learned will help others who may wish to develop a similar software quality evaluation tool.","PeriodicalId":207183,"journal":{"name":"Proceedings of IEEE International Symposium on Requirements Engineering: RE '98","volume":"124 3","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"1998-04-06","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"120880049","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}
Pub Date : 1998-04-06DOI: 10.1109/ICRE.1998.667828
K. Breitman, Julio Cesar Sampaio do Prado Leite
We report on a framework for scenario evolution. We have studied, based on a laboratory case study, the evolution of scenarios from elicitation to coding, thus using the requirements baseline in a full cycle. Considering our observations of over a hundred and fifty scenarios we discovered a series of relationships and operations that occurred during the evolution. Our framework is a contribution to better understand scenario evolution and to help the tractability and identification of those actions belonging to the environment and those shared with the software.
{"title":"A framework for scenario evolution","authors":"K. Breitman, Julio Cesar Sampaio do Prado Leite","doi":"10.1109/ICRE.1998.667828","DOIUrl":"https://doi.org/10.1109/ICRE.1998.667828","url":null,"abstract":"We report on a framework for scenario evolution. We have studied, based on a laboratory case study, the evolution of scenarios from elicitation to coding, thus using the requirements baseline in a full cycle. Considering our observations of over a hundred and fifty scenarios we discovered a series of relationships and operations that occurred during the evolution. Our framework is a contribution to better understand scenario evolution and to help the tractability and identification of those actions belonging to the environment and those shared with the software.","PeriodicalId":207183,"journal":{"name":"Proceedings of IEEE International Symposium on Requirements Engineering: RE '98","volume":"27 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"1998-04-06","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"129170222","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}
Pub Date : 1998-04-06DOI: 10.1109/ICRE.1998.667810
N. Millard, Paula Lynch, K. Tracey
Tools and techniques for requirements elicitation are generally unsuitable for use with children and for innovative and futuristic developments. Using case studies, the paper explores practical methods to get requirements for future technologies from children. Techniques such as scenario building, role playing and storyboarding proved successful in involving children in the requirements process and stimulating innovation. The paper looks at how these methods can be adopted to take a more fundamental approach to requirements elicitation for adults. These techniques help requirements engineers face the difficult task of getting system requirements from users of whatever age, ability or background. They also enable requirements engineers to anticipate some of the future changes that might occur before or as a consequence of the installation of a new system. The lack of specialist notation was found to promote communication throughout the analysis and design process and gives the designers a context in which to design.
{"title":"Child's play: using techniques developed to elicit requirements from children with adults","authors":"N. Millard, Paula Lynch, K. Tracey","doi":"10.1109/ICRE.1998.667810","DOIUrl":"https://doi.org/10.1109/ICRE.1998.667810","url":null,"abstract":"Tools and techniques for requirements elicitation are generally unsuitable for use with children and for innovative and futuristic developments. Using case studies, the paper explores practical methods to get requirements for future technologies from children. Techniques such as scenario building, role playing and storyboarding proved successful in involving children in the requirements process and stimulating innovation. The paper looks at how these methods can be adopted to take a more fundamental approach to requirements elicitation for adults. These techniques help requirements engineers face the difficult task of getting system requirements from users of whatever age, ability or background. They also enable requirements engineers to anticipate some of the future changes that might occur before or as a consequence of the installation of a new system. The lack of specialist notation was found to promote communication throughout the analysis and design process and gives the designers a context in which to design.","PeriodicalId":207183,"journal":{"name":"Proceedings of IEEE International Symposium on Requirements Engineering: RE '98","volume":"82 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"1998-04-06","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"125453731","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}
Pub Date : 1998-04-06DOI: 10.1109/ICRE.1998.667831
W. Lam, S. Jones, C. Britton
Increasingly, software organisations are looking towards large-scale systematic reuse as a way of improving productivity, raising quality and reducing delivery timescales. We discuss technology transfer for reuse at the RE (requirements engineering) level. We first examine the state-of-the-art in terms of the approaches to RE reuse currently suggested in the literature. We then discuss factors in the reuse technology transfer process, and argue that most of the existing work focuses on one particular strand of technology transfer namely that of the technical reuse process. We highlight the need to address the reuse management process, and propose a generic process model for RE reuse called ORM (Operational Reuse Model). We also discuss evaluation issues related to reuse technology transfer, and conclude with lessons and observations on making reuse a normal part of RE practice.
{"title":"Technology transfer for reuse: a management model and process improvement framework","authors":"W. Lam, S. Jones, C. Britton","doi":"10.1109/ICRE.1998.667831","DOIUrl":"https://doi.org/10.1109/ICRE.1998.667831","url":null,"abstract":"Increasingly, software organisations are looking towards large-scale systematic reuse as a way of improving productivity, raising quality and reducing delivery timescales. We discuss technology transfer for reuse at the RE (requirements engineering) level. We first examine the state-of-the-art in terms of the approaches to RE reuse currently suggested in the literature. We then discuss factors in the reuse technology transfer process, and argue that most of the existing work focuses on one particular strand of technology transfer namely that of the technical reuse process. We highlight the need to address the reuse management process, and propose a generic process model for RE reuse called ORM (Operational Reuse Model). We also discuss evaluation issues related to reuse technology transfer, and conclude with lessons and observations on making reuse a normal part of RE practice.","PeriodicalId":207183,"journal":{"name":"Proceedings of IEEE International Symposium on Requirements Engineering: RE '98","volume":"23 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"1998-04-06","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"123268530","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}
Pub Date : 1998-04-06DOI: 10.1109/ICRE.1998.667812
W. N. Robinson, S. Pawlowski
Systems requirements errors are numerous, persistent, and expensive. To detect such errors, and focus on critical ones during the development of a requirements document, we have defined Root Requirements Analysis. This simple technique is based on: generalizing requirements to form root requirements, exhaustively comparing the root requirements, and applying simple metrics to the resultant comparison matrix. Root Requirements Analysis is effective. In the case study described, the technique finds that 36 percent of the case's root requirements interactions result in problems which require further analysis. Moreover, the technique provides a specific operational procedure to guide the efficient iterative resolution of identified requirements conflicts. The process of Root Requirements Analysis itself is not specific to a particular methodology. It can be applied directly to requirements in a variety of forms, as well as to the documentation of requirements development. We took this latter approach in the case study illustrating how Root Requirements Analysis can augment the Inquiry Cycle model of requirements development. Finally, the technique is amenable to support through collaborative CASE tools, as we demonstrate with our DEALSCRIBE prototype.
{"title":"Surfacing root requirements interactions from inquiry cycle requirements documents","authors":"W. N. Robinson, S. Pawlowski","doi":"10.1109/ICRE.1998.667812","DOIUrl":"https://doi.org/10.1109/ICRE.1998.667812","url":null,"abstract":"Systems requirements errors are numerous, persistent, and expensive. To detect such errors, and focus on critical ones during the development of a requirements document, we have defined Root Requirements Analysis. This simple technique is based on: generalizing requirements to form root requirements, exhaustively comparing the root requirements, and applying simple metrics to the resultant comparison matrix. Root Requirements Analysis is effective. In the case study described, the technique finds that 36 percent of the case's root requirements interactions result in problems which require further analysis. Moreover, the technique provides a specific operational procedure to guide the efficient iterative resolution of identified requirements conflicts. The process of Root Requirements Analysis itself is not specific to a particular methodology. It can be applied directly to requirements in a variety of forms, as well as to the documentation of requirements development. We took this latter approach in the case study illustrating how Root Requirements Analysis can augment the Inquiry Cycle model of requirements development. Finally, the technique is amenable to support through collaborative CASE tools, as we demonstrate with our DEALSCRIBE prototype.","PeriodicalId":207183,"journal":{"name":"Proceedings of IEEE International Symposium on Requirements Engineering: RE '98","volume":"131 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"1998-04-06","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"122534208","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}
Pub Date : 1998-04-06DOI: 10.1109/ICRE.1998.667825
Renaud Lecoeuche, C. Mellish, D. Robertson
We present our work on requirements elicitation. The elicitation process is a complex task which necessitates computer support. Elicitation systems should ideally help their users check the correctness of the specifications obtained but also actively guide them in the acquisition of the requirements. We consider systems that communicate in natural language. We describe a framework that tries to improve the quality of the guidance it provides to its users by taking into account natural language constraints. We discuss the need for a theory of natural language dialogue structure, and we show how we have integrated such a theory within an early prototype of an elicitation system.
{"title":"A framework for requirements elicitation through mixed-initiative dialogue","authors":"Renaud Lecoeuche, C. Mellish, D. Robertson","doi":"10.1109/ICRE.1998.667825","DOIUrl":"https://doi.org/10.1109/ICRE.1998.667825","url":null,"abstract":"We present our work on requirements elicitation. The elicitation process is a complex task which necessitates computer support. Elicitation systems should ideally help their users check the correctness of the specifications obtained but also actively guide them in the acquisition of the requirements. We consider systems that communicate in natural language. We describe a framework that tries to improve the quality of the guidance it provides to its users by taking into account natural language constraints. We discuss the need for a theory of natural language dialogue structure, and we show how we have integrated such a theory within an early prototype of an elicitation system.","PeriodicalId":207183,"journal":{"name":"Proceedings of IEEE International Symposium on Requirements Engineering: RE '98","volume":"30 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"1998-04-06","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"125756614","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}
Pub Date : 1998-04-06DOI: 10.1109/ICRE.1998.667819
P. Fowler, Anita D. Carleton, B. Merrin
We built a prototype "transition package" to determine if adoption of requirements management practices would be expedited by a suite of RM-specific materials for change agents. The transition package was a password-protected web site that included about 100 documents for use in both performing and introducing requirements management practices. These documents included examples, templates, checklists, and guidance materials. Three frameworks-document type, Software Capability Maturity Model Common Feature, and technology transition process model-helped users make use of the documents. This paper describes the prototype, summarizes the data gathered from an evaluation by reviewers and piloting organizations, and comments on what the data reflect about the need for and use of technology to support requirements management. Finally, the potential of this approach for improving software technology adoption and process improvement within organizations is assessed based on these experiences.
{"title":"Transition packages: an experiment in expediting the introduction of requirements management","authors":"P. Fowler, Anita D. Carleton, B. Merrin","doi":"10.1109/ICRE.1998.667819","DOIUrl":"https://doi.org/10.1109/ICRE.1998.667819","url":null,"abstract":"We built a prototype \"transition package\" to determine if adoption of requirements management practices would be expedited by a suite of RM-specific materials for change agents. The transition package was a password-protected web site that included about 100 documents for use in both performing and introducing requirements management practices. These documents included examples, templates, checklists, and guidance materials. Three frameworks-document type, Software Capability Maturity Model Common Feature, and technology transition process model-helped users make use of the documents. This paper describes the prototype, summarizes the data gathered from an evaluation by reviewers and piloting organizations, and comments on what the data reflect about the need for and use of technology to support requirements management. Finally, the potential of this approach for improving software technology adoption and process improvement within organizations is assessed based on these experiences.","PeriodicalId":207183,"journal":{"name":"Proceedings of IEEE International Symposium on Requirements Engineering: RE '98","volume":"94 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"1998-04-06","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"131369104","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}
Pub Date : 1998-04-06DOI: 10.1109/ICRE.1998.667815
M. Haglind, L. Johansson, Martin Rantzer
This paper presents a study that has been done in the area of business analysis (BA) in support of requirements engineering (RE). It is argued that the competitive nature of software procurement poses problems to the integration of BA and RE. To investigate this claim, eight procurement and development projects in which BA has been used are studied. The collected data are analyzed using a set of indicators for achieved integration level. The study shows that the projects encountered the proposed difficulties. This is most apparent in projects involving customers formulating requests for proposals (RFPs). To alleviate the integration problems, new approaches to system procurement in which customer organizations and vendors cooperate more closely seem necessary.
{"title":"Experiences integrating requirements engineering and business analysis. An empirical study of operations and management system procurement projects","authors":"M. Haglind, L. Johansson, Martin Rantzer","doi":"10.1109/ICRE.1998.667815","DOIUrl":"https://doi.org/10.1109/ICRE.1998.667815","url":null,"abstract":"This paper presents a study that has been done in the area of business analysis (BA) in support of requirements engineering (RE). It is argued that the competitive nature of software procurement poses problems to the integration of BA and RE. To investigate this claim, eight procurement and development projects in which BA has been used are studied. The collected data are analyzed using a set of indicators for achieved integration level. The study shows that the projects encountered the proposed difficulties. This is most apparent in projects involving customers formulating requests for proposals (RFPs). To alleviate the integration problems, new approaches to system procurement in which customer organizations and vendors cooperate more closely seem necessary.","PeriodicalId":207183,"journal":{"name":"Proceedings of IEEE International Symposium on Requirements Engineering: RE '98","volume":"21 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"1998-04-06","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"121303016","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
扫码关注我们
求助内容：
应助结果提醒方式：