{"title":"Teaching requirements engineering through role playing: lessons learnt","authors":"D. Zowghi, S. Paryani","doi":"10.1109/ICRE.2003.1232754","DOIUrl":"https://doi.org/10.1109/ICRE.2003.1232754","url":null,"abstract":"Requirements engineering (RE) has attracted a great deal of attention from researchers and practitioners in recent years. This increasing interest demands academia to provide software engineering students with a solid foundation in the subject matter. RE is a multi disciplinary and communication rich activity in software development. The RE tools, methods and techniques to date have drawn upon a variety of disciplines, and the requirements engineers are increasingly expected to be well versed with these disciplines. In RE education, it is thus imperative to cover a wide range of topics and teach a variety of skills that one needs to know and acquire to be able to perform effective requirements engineering. We argue that in teaching RE, we must cover three fundamental topics: the traditional analysis and modelling skills, interviewing and groupware skills for requirements elicitation, and writing skills for specifying requirements. We report on our experiences gained in teaching such a requirements engineering subject for the first time to students at University of Technology, Sydney. We used role playing as a pedagogical tool to give students a greater appreciation of the range of issues and problems associated with requirements engineering in real settings. We believe that the lessons learnt from this exercise will be valuable for those interested in advancing requirements engineering education and training.","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":"125349341","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":"Ontology as a requirements engineering product","authors":"K. Breitman, Julio Cesar Sampaio do Prado Leite","doi":"10.1109/ICRE.2003.1232775","DOIUrl":"https://doi.org/10.1109/ICRE.2003.1232775","url":null,"abstract":"The \"semantic Web\" community poses a new nonfunctional requirement for Web applications. In order to secure interoperability and allow autonomous agent interaction, software for the Web will be required to provide machine processable ontologies. We understand that the responsibility, not only for making explicit this requirement, but also to implement the ontology, belongs to requirements engineers. As such, we see the ontology of a Web application as a sub-product of the requirements engineering activity. In this tutorial we survey the basic principles behind ontologies as they are being implemented and used by the semantic Web community today. Those include ontology languages, tools and construction methods. We focus on a process for ontology construction centered on the concept of application languages. This concept is rooted on a representation scheme called the language extended lexicon (LEL). We demonstrate our approach with examples in which we implement machine processable ontologies in the DAML+OIL language. We finalize with a discussion of today's research issues in ontology engineering, including ontology evolution, integration and validation.","PeriodicalId":243621,"journal":{"name":"Proceedings. 11th IEEE International Requirements Engineering Conference, 2003.","volume":"20 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":"116628863","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 based testing at HP OpenView","authors":"Gerald Heller, Peter Vollmer","doi":"10.1109/ICRE.2003.1232771","DOIUrl":"https://doi.org/10.1109/ICRE.2003.1232771","url":null,"abstract":"Releasing a new version of a software product seems often to be a trade-off between time-to-market and quality. Customers are waiting for the announced product but also expect high quality. Sales organizations are eager to sell new products. However, if quality is not good enough the customer is not satisfied and will intensively use the vendor's support organization. This increases post-release costs and reduces net-earnings. A requirements-based test process can deliver key information for a business-driven release decision and helps to reduce rework. We describe how we have established a solid requirements management process in our organization during the last 4 years. It presents adoption experiences with a standard requirements management tool and talk about our process improvements towards requirements based testing.","PeriodicalId":243621,"journal":{"name":"Proceedings. 11th IEEE International Requirements Engineering Conference, 2003.","volume":"128 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":"116247812","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. Kaiya, Kouta Sasaki, Yasunori Maebashi, K. Kaijiri
{"title":"Trade-off analysis between security policies for Java mobile codes and requirements for Java application","authors":"H. Kaiya, Kouta Sasaki, Yasunori Maebashi, K. Kaijiri","doi":"10.1109/ICRE.2003.1232785","DOIUrl":"https://doi.org/10.1109/ICRE.2003.1232785","url":null,"abstract":"We propose a method for analyzing trade-off between security policies for Java mobile codes and requirements for Java application. We assume that mobile codes are downloaded from different sites, they are used in an application on a site, and their functions are restricted by security policies on the site. We clarify which functions to be performed under the policies on the site using our tool [H. Kaiya et al., (2002)]. We also clarify which functions are needed so as to meet the requirements for the application by goal oriented requirements analysis (GORA). By comparing functions derived from the policies and functions from the requirements, we find conflicts between the policies and the requirements, and also find vagueness of the requirements.","PeriodicalId":243621,"journal":{"name":"Proceedings. 11th IEEE International Requirements Engineering Conference, 2003.","volume":"10 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":"125046335","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}
Luncheng Lin, B. Nuseibeh, D. Ince, M. Jackson, J. Moffett
{"title":"Introducing abuse frames for analysing security requirements","authors":"Luncheng Lin, B. Nuseibeh, D. Ince, M. Jackson, J. Moffett","doi":"10.1109/ICRE.2003.1232791","DOIUrl":"https://doi.org/10.1109/ICRE.2003.1232791","url":null,"abstract":"We are developing an approach using Jackson's Problem Frames to analyse security problems in order to determine security vulnerabilities. We introduce the notion of an anti-requirement as the requirement of a malicious user that can subvert an existing requirement. We incorporate anti-requirements into so-called abuse frames to represent the notion of a security threat imposed by malicious users in a particular problem context. We suggest how abuse frames can provide a means for bounding the scope of security problems in order to analyse security threats and derive security requirements.","PeriodicalId":243621,"journal":{"name":"Proceedings. 11th IEEE International Requirements Engineering Conference, 2003.","volume":"2 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":"122720923","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":"Market driven requirements elicitation via critical success chains","authors":"T. Tuunanen, M. Rossi","doi":"10.1109/ICRE.2003.1232789","DOIUrl":"https://doi.org/10.1109/ICRE.2003.1232789","url":null,"abstract":"Elicitation of requirements becomes more difficult as usually consumers do not explicitly know what they want and it is difficult for them to express their ideas. To support different views of product development, such as project management and design, the method should present requirements in a 'rich enough' way to avoid overloading management but in the same time giving designers the detailed information they need. Requirements engineering should be easy to integrate to the software development process. To this end we have constructed a support environment for the method within Metaedit+ Meta CASE tool to present and manage the requirements. We have developed a new method that tries answering the complexities of development process. We based our method on critical success chains (CSC) method, that includes a top-down approach of planning but also wide participation of IS customers to get rich information. CSC aggregates the results of many individual interviews into meaningful graphical models of what is important about a potential system. CSC is extended with customer segmentation and lead user concepts from marketing.","PeriodicalId":243621,"journal":{"name":"Proceedings. 11th IEEE International Requirements Engineering Conference, 2003.","volume":"31 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":"124136472","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":"Evolutionary requirements analysis","authors":"A. Sutcliffe, Wei-chun Chang, R. Neville","doi":"10.1109/ICRE.2003.1232758","DOIUrl":"https://doi.org/10.1109/ICRE.2003.1232758","url":null,"abstract":"The evolutionary requirements analyser (ERA) applies evolutionary computing techniques to automatically select optimal combinations of human and machine agents in a system model to match nonfunctional requirements (NFRs). The tool assesses the reliability, performance times and cost of different system models by executing many model variants, as evolving forms, with scenarios and different combinations of environmental variables. Better performing models are selected, to converge on an optimal solution. Use of the tool is illustrated with a case study of requirements analysis for component selection in a command and control system.","PeriodicalId":243621,"journal":{"name":"Proceedings. 11th IEEE International Requirements Engineering Conference, 2003.","volume":"21 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":"125320203","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 for the Internet","authors":"V. Cerf","doi":"10.1109/ICRE.2003.1232730","DOIUrl":"https://doi.org/10.1109/ICRE.2003.1232730","url":null,"abstract":"The requirements for the Internet emerged in part from the practical experiences drawn from the development, deployment and use of the ARPANET. Each distinct network would have to stand on its own and no internal changes could be required to any such network to connect it to the Internet. Communications would be on a best effort basis. If a packet didn't make it to the final destination, it would shortly be retransmitted from the source. Black boxes would be used to connect the networks; these would later be called gateways and routers. There would be no information retained by the gateways about the individual flows of packets passing through them, thereby keeping them simple and avoiding complicated adaptation and recovery from various failure modes. There would be no global control at the operations level.","PeriodicalId":243621,"journal":{"name":"Proceedings. 11th IEEE International Requirements Engineering Conference, 2003.","volume":"60 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":"130135795","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}
André Rifaut, Philippe Massonet, J. Molderez, C. Ponsard, Pierre Stadnik, A. V. Lamsweerde, Hung Tran Van
{"title":"FAUST: formal analysis using specification tools","authors":"André Rifaut, Philippe Massonet, J. Molderez, C. Ponsard, Pierre Stadnik, A. V. Lamsweerde, Hung Tran Van","doi":"10.1109/ICRE.2003.1232781","DOIUrl":"https://doi.org/10.1109/ICRE.2003.1232781","url":null,"abstract":"Developing high quality requirements specifications is a necessity for a number of critical industrial systems. An integrated toolset, called FAUST, is proposed to assist in the production of such specifications based on the KAOS goal-driven methodology. The tool suite is designed to naturally extend the existing semiformal modeling framework and to allow formalizing only the relevant critical parts. Two tools from the toolset are presented. The requirements checker performs KAOS goal-level checks using existing model checking technology. The requirements animator produces domain-level animations hiding formality even further.","PeriodicalId":243621,"journal":{"name":"Proceedings. 11th IEEE International Requirements Engineering Conference, 2003.","volume":"21 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":"116215111","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":"RE in flatness measurement and control systems development at ABB","authors":"N. Yilmazturk","doi":"10.1109/ICRE.2003.1232768","DOIUrl":"https://doi.org/10.1109/ICRE.2003.1232768","url":null,"abstract":"The Stressometer product line involves software intensive systems, which have been providing rolling mills with accurate online control of the flatness of cold rolled strips for more than 30 years. New generation Stressometer systems are implemented by using SUP (Stressometer unified process) that is RUP/spl reg/ (rational unified process/spl reg/) tailored to fit the Stressometer department's development projects' needs. It facilitates use-case driven, iterative development during which modeling is done via UML. We present the requirements engineering activities that are involved in the SUP, and discuss the problems faced during practice, thus putting forward issues for the attention of research.","PeriodicalId":243621,"journal":{"name":"Proceedings. 11th IEEE International Requirements Engineering Conference, 2003.","volume":"389 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":"120881197","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}