{"title":"Lessons learnt from five years of experience in ERP requirements engineering","authors":"M. Daneva","doi":"10.1109/ICRE.2003.1232736","DOIUrl":"https://doi.org/10.1109/ICRE.2003.1232736","url":null,"abstract":"Generic off-the-shelf requirements engineering (RE) processes have been packaged by enterprise resource planning (ERP) vendors since 1997, and adopted by client organizations as the key strategy for getting the business requirements and the conceptual design for their complex solutions. We summarize one company's five years of experience in making a generic ERP RE model a live process. It rests on previously published ERP RE process assessment results and reports on what we learnt with particular focus on typical issues organizations face when adopting a standard model and solutions that can be used to avoid those issues in the future. Each of our lessons is described together with a RE practice, technical foundation for the practice and engineering techniques for the RE practitioner. The lessons were used to refine our corporate documentation model, a process-focused and template-based ERP-architecture framework.","PeriodicalId":243621,"journal":{"name":"Proceedings. 11th IEEE International Requirements Engineering Conference, 2003.","volume":"1 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2003-09-08","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"126996400","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}
{"title":"Requirements engineering for a pervasive health care system","authors":"Jens Bæk Jørgensen, Claus Bossen","doi":"10.1109/ICRE.2003.1232737","DOIUrl":"https://doi.org/10.1109/ICRE.2003.1232737","url":null,"abstract":"We describe requirements engineering for a new pervasive health care system for hospitals in Denmark. The chosen requirements engineering approach composes iterative prototyping and explicit environment description in terms of workflow modelling. New work processes and their proposed computer support are represented via a combination of prose, formal models, and animation. The representation enables various stakeholders to make interactive investigations of requirements for the system in the context of the envisioned work processes. We describe lessons learned from collaboration between users and system developers in engineering the requirements for the new system.","PeriodicalId":243621,"journal":{"name":"Proceedings. 11th IEEE International Requirements Engineering Conference, 2003.","volume":"3 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2003-09-08","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"127318409","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}
{"title":"Using convergent design processes to surface hidden ambiguity and conflict in requirements","authors":"R. Barnes","doi":"10.1109/ICRE.2003.1232761","DOIUrl":"https://doi.org/10.1109/ICRE.2003.1232761","url":null,"abstract":"In a volatile and politically-charged design environment such as healthcare information systems (IS), ambiguity and conflict play significant roles in the success or failure of development efforts. However, the relationship between ambiguity and conflict is complex. Resolving ambiguity during IS requirements analysis may not readily lead to conflict resolution, since even the most innocent and well-intentioned probes for hidden requirements ambiguity can surface a lot of conflict. For example, ambiguity may concern issues as deciding which user constituency will be specifically favored or disfavored, or who will bear ultimate responsibility for system features and functionality, each of which involve potential conflicts of power and control over the project. The conflict averseness of IS designers may also impede efforts to employ techniques to reduce ambiguity, techniques in which issues involve changing traditional and controversial power structures. Ambiguity may even remain deliberately unresolved to passively suppress conflict, and crucial debates over critical assumptions never materialize. We also discuss a strategy for improving the effectiveness of developers in identifying hidden ambiguity and conflict during IS requirements specification.","PeriodicalId":243621,"journal":{"name":"Proceedings. 11th IEEE International Requirements Engineering Conference, 2003.","volume":"40 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2003-09-08","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"127353466","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. Covvey, D. Zitner, D. Berry, D. Cowan, M. Shepherd
{"title":"Formal structure for specifying the content and quality of the electronic health record","authors":"H. Covvey, D. Zitner, D. Berry, D. Cowan, M. Shepherd","doi":"10.1109/ICRE.2003.1232747","DOIUrl":"https://doi.org/10.1109/ICRE.2003.1232747","url":null,"abstract":"We outline a systematic approach to defining, eliciting, and specifying the structure and the information content of the electronic health record (EHR). The paper presents a scheme for specifying a uniform, but extensible EHR and for eliciting both the structure and contents of this EHR. The next step will be to carry out the proposed process with health-care providers to begin to put some order into health records and to allow specifications of families of interacting HI applications.","PeriodicalId":243621,"journal":{"name":"Proceedings. 11th IEEE International Requirements Engineering Conference, 2003.","volume":"38 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2003-09-08","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"128013067","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}
{"title":"Bringing usability to the early stages of software development","authors":"L. M. Cysneiros, A. Kushniruk","doi":"10.1109/ICRE.2003.1232786","DOIUrl":"https://doi.org/10.1109/ICRE.2003.1232786","url":null,"abstract":"Usability has been increasingly recognized as an important factor in the acceptance of systems by end users. Usability requirements can be considered to be requirements that capture the usability goals and associated measures for a system under development. In order to ensure usable systems we must ensure identification of appropriate requirements regarding these critical aspects of systems. There is a basic need for systematic approaches to reason, model and analyze usability from the early stages of the software development. Furthermore, it is necessary to develop a usable ontology or classification of measurable aspects of usability that can be used to aid in the specification of usability requirements. These ontologies should be represented in a way that facilitates their use as guidelines for the requirements elicitation process. We build on review of literature in the area of human-computer interaction and of usability engineering in developing a catalog of aspects of usability that can be considered during requirements gathering. This catalogue is used to guide the requirements engineer through alternatives for achieving usability. The approach is based on the use of the i* framework, having usability modeled as a special type of goal.","PeriodicalId":243621,"journal":{"name":"Proceedings. 11th IEEE International Requirements Engineering Conference, 2003.","volume":"32 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2003-09-08","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"121361821","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}
{"title":"Testing with partial traced requirements: a necessary step towards higher quality system level verification","authors":"S. Catrava","doi":"10.1109/ICRE.2003.1232772","DOIUrl":"https://doi.org/10.1109/ICRE.2003.1232772","url":null,"abstract":"Summary form only given. We propose new approach called testing with partial traced requirements as an alternate solution to achieve quality system verification when sub-requirement tracing is unavailable. Partially traced requirements have already been used in a large two years project at Guidant Corporation. The project, called TMS, researched, built, and deployed a comprehensive test management system based on Guidant traceability graph. Partially traced requirements were successfully used: first to identify the issues related to sub-requirement tracing, and second to define a semi automated strategy to increase the quality system verification. In addition to presenting the methodology, we also report on the experiences and lessons learned during development and deployment of TMS.","PeriodicalId":243621,"journal":{"name":"Proceedings. 11th IEEE International Requirements Engineering Conference, 2003.","volume":"46 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2003-09-08","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"116270315","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}
{"title":"Customer requirements and user requirements: why the discrepancies?","authors":"Mary Deraitus, A. Miller","doi":"10.1109/ICRE.2003.1232759","DOIUrl":"https://doi.org/10.1109/ICRE.2003.1232759","url":null,"abstract":"Development teams often speak about the need to satisfy the customer and to meet their requirements. But exactly who is the customer, how do they determine their requirements, and how do these differ from user requirements? If the customer requirements don't realistically (or objectively) present user requirements, can the developers still build a usable product? And if not, who's to blame when the product meets the requirements of the customer, but not the user?.","PeriodicalId":243621,"journal":{"name":"Proceedings. 11th IEEE International Requirements Engineering Conference, 2003.","volume":"44 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2003-09-08","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"127530608","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}
{"title":"Contrasting use case, goal, and scenario analysis of the Euronet system","authors":"T. Alspaugh, A. Antón","doi":"10.1109/ICRE.2003.1232784","DOIUrl":"https://doi.org/10.1109/ICRE.2003.1232784","url":null,"abstract":"In this research, we compare three related requirements engineering efforts: an industrial effort based on use cases; a case study analyzing these use cases by means of goal analysis; and a case study analyzing the same use cases with an integrated scenario analysis approach.","PeriodicalId":243621,"journal":{"name":"Proceedings. 11th IEEE International Requirements Engineering Conference, 2003.","volume":"7 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2003-09-08","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"133162523","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}
{"title":"Improving requirements tracing via information retrieval","authors":"J. Hayes, Alex Dekhtyar, J. Osborne","doi":"10.1109/ICRE.2003.1232745","DOIUrl":"https://doi.org/10.1109/ICRE.2003.1232745","url":null,"abstract":"We present an approach for improving requirements tracing based on framing it as an information retrieval (IR) problem. Specifically, we focus on improving recall and precision in order to reduce the number of missed traceability links as well as to reduce the number of irrelevant potential links that an analyst has to examine when performing requirements tracing. Several IR algorithms were adapted and implemented to address this problem. We evaluated our algorithms by comparing their results and performance to those of a senior analyst who traced manually as well as with an existing requirements tracing tool. Initial results suggest that we can retrieve a significantly higher percentage of the links than analysts, even when using existing tools, and do so in much less time while achieving comparable signal-to-noise levels.","PeriodicalId":243621,"journal":{"name":"Proceedings. 11th IEEE International Requirements Engineering Conference, 2003.","volume":"18 4 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2003-09-08","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"126934096","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}
{"title":"QFD for customer-focused requirements engineering","authors":"G. Herzwurm, S. Schockert, W. Pietsch","doi":"10.1109/ICRE.2003.1232777","DOIUrl":"https://doi.org/10.1109/ICRE.2003.1232777","url":null,"abstract":"Here an overview of the state of the art of QFD in software development or also called software QFD is given. The differences between classic QFD in manufacturing industries and software QFD are described. Following certain software specific QFD models (Zultner, Shindo, Ohmori, Herzwurm and Schockert), which can be considered as the most appreciated ones in theory as well as in practice, are introduced. Experiences in practice with these software QFD models are presented as well. Finally, through explaining the main principles of a special QFD variant for e-commerce, called continuous QFD (CQFD), we will show that QFD is suitable for planning electronic business applications as well.","PeriodicalId":243621,"journal":{"name":"Proceedings. 11th IEEE International Requirements Engineering Conference, 2003.","volume":"85 ","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2003-09-08","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"113984096","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}