{"title":"Requirements stability assessment using scenarios","authors":"David Bush, A. Finkelstein","doi":"10.1109/ICRE.2003.1232734","DOIUrl":"https://doi.org/10.1109/ICRE.2003.1232734","url":null,"abstract":"We present a new approach to assessing requirements stability as a contribution to the building of more stable long lifetime systems. A goal-based model is used to analyze the requirements in a number of possible future worlds described by scenarios of the possible future environment of the system. The result is an assessment of possible instability of the requirements and the assumptions, which can be presented to system developers to inform alternative requirements definition and architectural choices supporting 'targeted design for change'. A process for carrying out the analysis is described and practical tool support outlined. Results from an industrial scale, live case study validating the approach, process and tool support is reported, and possible developments of the concept, process and tool are discussed.","PeriodicalId":243621,"journal":{"name":"Proceedings. 11th IEEE International Requirements Engineering Conference, 2003.","volume":"16 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":"123949787","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":"A benchmarking method for information systems","authors":"L. Hagge, J. Kreutzkamp","doi":"10.1109/ICRE.2003.1232756","DOIUrl":"https://doi.org/10.1109/ICRE.2003.1232756","url":null,"abstract":"Benchmark tests are used to evaluate the performance of information systems and to test their compliance with user requirements. In early project phases benchmark tests help to make build-or-buy decisions and to estimate the acceptance and performance an information system can achieve in a given environment. For a benchmark test, a team of future users visits candidate software vendors and executes pre-defined scenarios on their software systems using dedicated test data. Test scenarios and data are created using business-process modeling with UML. During the test, each team member observes and rates the system performance. For customers, benchmark results are powerful tools for project management, while vendors gain valuable insight into requirements and established practices of their target customers.","PeriodicalId":243621,"journal":{"name":"Proceedings. 11th IEEE International Requirements Engineering Conference, 2003.","volume":"412 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":"123542234","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 elicitation for the design of venue operations for the Athens 2004 Olympic games","authors":"P. Loucopoulos, K. Zografos, N. Prekas","doi":"10.1109/ICRE.2003.1232753","DOIUrl":"https://doi.org/10.1109/ICRE.2003.1232753","url":null,"abstract":"The design and implementation of systems for the support of venue operations for the Olympic games is a complex and multifaceted undertaking. Venue operations are designed to support the efficient functioning of every venue far every day for the duration of the games. We present the challenges faced and experiences gained during two years of requirements engineering projects for this high-profile and multifarious application. We describe the unique nature of the enterprise environment, briefly discuss and critique the approaches traditionally used, present the approach adopted in the venue operations planning of the Athens2004 Olympic games and discuss the issues that influenced the process of requirements elicitation. The purpose is to report on experiences from a particular type of requirements problems (very early, strategic requirements) and to draw lessons that may inform future practice and research.","PeriodicalId":243621,"journal":{"name":"Proceedings. 11th IEEE International Requirements Engineering Conference, 2003.","volume":"185 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":"128749901","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, configuration management and traceability for safety critical software","authors":"G. Romanski","doi":"10.1109/ICRE.2003.1232773","DOIUrl":"https://doi.org/10.1109/ICRE.2003.1232773","url":null,"abstract":"Software requirements are the focal point from which traceability to all related artifacts are established during the certification of safety critical software. For the certification of air-borne software, the guidance document DO-178B, requires that the link between requirements, design, code and tests be documented and verified. The DO-178B document does not describe how this should be done, but it permits the reengineering of information that is missing, to support the certification of commercial-off-the-shelf (COTS) products. Requirements were entered in a database and evolved through a sequence that enforced the states described in company process documents. The design descriptions, source code, tests, results and so on were maintained in a configuration management (CM) system. The final audit was successful and the CD-ROM delivery of a requirements based certification package was accepted and commended. The details of the approach and the lessons learned were presented.","PeriodicalId":243621,"journal":{"name":"Proceedings. 11th IEEE International Requirements Engineering Conference, 2003.","volume":"14 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":"127796729","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":"Practical lessons from 40 system integrating projects","authors":"Taichi Nakamura, S. Matsuda","doi":"10.1109/ICRE.2003.1232770","DOIUrl":"https://doi.org/10.1109/ICRE.2003.1232770","url":null,"abstract":"In developing an information system for a newly entered field of business, a customer cannot really finalize specifications, even if the specifications for the system have been decided and agreed on by both the customer and the system integrator (SI). To cope with this problem, the project manager (PM) of the SI evaluates each new request from a customer. The customer's requests should be evaluated in terms of their relevance to the six key project management points: price, cost, contract terms, specifications, team building and progress/quality. If the customer's request causes a change in the project's base line, such as a deadline, and it makes profitability less likely, this triggers a red card for the project. If the request may or may not adversely affect a plan, but nonetheless requires close attention, a yellow card is set. We describe the results of an analysis of the reports made by PMs of 40 projects for which negotiations with customers began from November 2001, and from which the accepted orders will be between 100 million yen (0.8 million dollars) and 12 billion yen. These reports made by PMs to the director show the degree of difficulty of system integration in a new market area and the lessons learned by PMs, which should form the basis for future actions.","PeriodicalId":243621,"journal":{"name":"Proceedings. 11th IEEE International Requirements Engineering Conference, 2003.","volume":"144 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":"116434998","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":"Daily challenges in requirements engineering","authors":"F. Salvatore, T. Alameda","doi":"10.1109/ICRE.2003.1232769","DOIUrl":"https://doi.org/10.1109/ICRE.2003.1232769","url":null,"abstract":"Summary form only given. Requirements engineering is becoming an increasingly more important aspect on every program. We present many challenges that we are faced with in a daily basis. Challenges such as requirements analysis, traceability, change management, system of systems interoperability, metrics, geographically dispersed engineering teams are just some of the many we must deal with. As requirements engineers we provide from a practitioners perspective real life examples of many of these challenges. We provide descriptions as to how we have personally solved some of these problems and provide examples when they are supportive of the ideas we are trying to express. Finally we wrap things up with a conclusion and some recommendations with the hopes of helping others face with similar problems.","PeriodicalId":243621,"journal":{"name":"Proceedings. 11th IEEE International Requirements Engineering Conference, 2003.","volume":"41 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":"126679562","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":"NIMBUS: a tool for specification centered development","authors":"M. Heimdahl, M. Whalen, J. Thompson","doi":"10.1109/ICRE.2003.1232780","DOIUrl":"https://doi.org/10.1109/ICRE.2003.1232780","url":null,"abstract":"Assurance that a formal specification (system specification or software specification) possesses desired properties can be achieved through (1) manual inspections, (2) formal verification of the desired properties, or (3) simulation and testing of the specification. To achieve the high level of confidence in the correctness required in a safety-critical system, all three approaches must be used in concert. We have developed an specification language, called RSML/sup -e/, and an environment, called NIMBUS, which provides support for all these activities. The three V&V techniques fill complementary roles within the validation and verification process. Manual inspections and visualization provide the specification team, customers, and regulatory representatives the means to informally verify that the behavior described formally matches the desired \"real world\" behavior of the system. RSML/sup -e/ is a fully formal, synchronous, data-flow language. NIMBUS supports large-scale, distributed simulation of specifications through communications over Microsoft's distributed COM or OMG's CORBA.","PeriodicalId":243621,"journal":{"name":"Proceedings. 11th IEEE International Requirements Engineering Conference, 2003.","volume":"39 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":"130719788","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":"From requirements to release criteria: specifying, monitoring, and demonstrating product quality","authors":"Erik Simmons","doi":"10.1109/ICRE.2003.1232763","DOIUrl":"https://doi.org/10.1109/ICRE.2003.1232763","url":null,"abstract":"Specifying quality requirements is an excellent first step to predictable, managed product quality, but it is just the beginning. Quality specification, quality planning, data generation, quality monitoring, and quality reporting all work together to ensure that quality levels are known throughout the project. Quality release criteria are a good way to ensure that product quality drives interim milestone releases and the final product release. Requirements and release criteria are mutually influential, and quantified requirements are an essential part of this process.","PeriodicalId":243621,"journal":{"name":"Proceedings. 11th IEEE International Requirements Engineering Conference, 2003.","volume":"43 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":"133078008","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 analysis for customizable software: a goals-skills-preferences framework","authors":"Bowen Hui, S. Liaskos, J. Mylopoulos","doi":"10.1109/ICRE.2003.1232743","DOIUrl":"https://doi.org/10.1109/ICRE.2003.1232743","url":null,"abstract":"Software customization has been argued to benefit both the productivity of software engineers and end users. However, most customization methods rely on specialists to manually tweak individual applications for a specific user group. Existing software development methods also fail to acknowledge the importance of different kinds of user skills and preferences and how these might be incorporated into a customizable software design. We propose a framework for performing requirements analysis on user goals, skills, and preferences in order to generate a customizable software design. We illustrate our methodology with an email system and review an on-going case study involving users with traumatic brain injury.","PeriodicalId":243621,"journal":{"name":"Proceedings. 11th IEEE International Requirements Engineering Conference, 2003.","volume":"22 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":"115051037","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}
M. Jarke, Oliver Fritzen, M. Miatidis, M. Schlüter
{"title":"Media-assisted product and process requirements traceability in supply chains","authors":"M. Jarke, Oliver Fritzen, M. Miatidis, M. Schlüter","doi":"10.1109/ICRE.2003.1232793","DOIUrl":"https://doi.org/10.1109/ICRE.2003.1232793","url":null,"abstract":"Requirements engineering for technical systems involves an intricate interplay of conceptual synthesis of alternative requirements and design configurations, preliminary impact analysis of these alternatives using complex simulations and multimedia visualizations, and human decision-making based on goal trade-offs. Requirements traceability in such settings must be both product- and process-oriented: it must enable an efficient media-based comparison of product alternatives from the current project or related experiences, and it must facilitate reuse of analysis process experiences to avoid unnecessary repetition of negative experiences. We study these problems in a large interdisciplinary project whose aim it is to optimize the innovation supply chains linking chemical engineering, plastics engineering, and application goals e.g. in the automotive industry.","PeriodicalId":243621,"journal":{"name":"Proceedings. 11th IEEE International Requirements Engineering Conference, 2003.","volume":"27 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":"115546706","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}