Proceedings. IEEE International Requirements Engineering Conference最新文献

{"title":"RE for ERP: Requirements Management for the Development of Packaged Software Baan Company","authors":"S. Brinkkemper","doi":"10.1109/RE.1999.10003","DOIUrl":"https://doi.org/10.1109/RE.1999.10003","url":null,"abstract":"Requirements Engineering within packaged software companies is quite different from RE in custom software development projects. As Enterprise Resource Planning (ERP) software covers functionality for the complete spectrum of business functions in industrial organizations, the management of large volumes of requirements from customers, possibly all over the world, is a non-trivia1 task. Collecting and prioritizing requirements, maintaining complex dependency structures, cost/value assessments, base-lining and re-scoping techniques call for dedicated requirement management methods with corresponding tools. We will discuss the industrial practices of Requirements Engineering and Requirements Management, and illustrate these with the RM methods and tools for the development of the Baan ERP products. We will end with an overview of research opportunities in Requirements Engineering motivated from the industrial perspective.","PeriodicalId":90955,"journal":{"name":"Proceedings. IEEE International Requirements Engineering Conference","volume":"18 1","pages":"159-"},"PeriodicalIF":0.0,"publicationDate":"1999-06-07","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"75342510","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":"XML for Software Engineers","authors":"A. Zisman, A. Finkelstein","doi":"10.1109/RE.1999.10014","DOIUrl":"https://doi.org/10.1109/RE.1999.10014","url":null,"abstract":"","PeriodicalId":90955,"journal":{"name":"Proceedings. IEEE International Requirements Engineering Conference","volume":"1 1","pages":"193-"},"PeriodicalIF":0.0,"publicationDate":"1999-01-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"75979571","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":"How Multi-Disciplinary Is RE (really)?","authors":"S. Easterbrook, B. Nuseibeh","doi":"10.1109/RE.1999.10011","DOIUrl":"https://doi.org/10.1109/RE.1999.10011","url":null,"abstract":"","PeriodicalId":90955,"journal":{"name":"Proceedings. IEEE International Requirements Engineering Conference","volume":"1 1","pages":"33-"},"PeriodicalIF":0.0,"publicationDate":"1999-01-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"81802253","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 Traceability","authors":"Anthony Finkelstein, Richard Stevens","doi":"10.1109/RE.1997.10008","DOIUrl":"https://doi.org/10.1109/RE.1997.10008","url":null,"abstract":"","PeriodicalId":90955,"journal":{"name":"Proceedings. IEEE International Requirements Engineering Conference","volume":"82 1","pages":"265"},"PeriodicalIF":0.0,"publicationDate":"1997-01-05","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"89120715","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":"Software Requirements Specification and System Safety","authors":"M. Heimdahl, J. Reese","doi":"10.1109/RE.1997.10004","DOIUrl":"https://doi.org/10.1109/RE.1997.10004","url":null,"abstract":"Computer software is playing an increasingly important role in safety-critical embedded computer systems, where incorrect operation of the software could lead to loss of life, substantial material or environmental damage, or large monetary losses. Such diverse technologies as avionics, automobile drive trains, power plants, and medical equipment are relying more and more on the computer to control system parameters. Although software is a powerful and flexible tool for industry, these very advantages have contributed to a corresponding increase in system complexity. Traditional approaches to system development have not successfully handled the problems of increased system complexity. The fatal accidents caused by software in the Therac-25 radiation therapy machine, as well as other incidents, have brought public attention to these problems. Ironically, it is becoming clear that the powerful control logic that software can bring to a system can also impair the ability of the systems analyst to study and understand, and hence safely control, the system’s behavior. sion avoidance System II). Furthermore, using a formal requirements specification language, for example, RSML, enables several types of automated or semi automated analysis techniques that can be used to detect and eliminate potential safety problems from the specification. In this tutorial, we will discuss techniques for automatically detecting incomplete, inconsistent, and nondeterministic requirements, show how fault tree analysis can be used in the RSML framework, and demonstrate how a new analysis technique called deviation analysis can be used to evaluate the effects on the system if the inputs to the system deviates from expected value.","PeriodicalId":90955,"journal":{"name":"Proceedings. IEEE International Requirements Engineering Conference","volume":"29 1","pages":"264"},"PeriodicalIF":0.0,"publicationDate":"1997-01-05","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"74107014","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":"The SCR Approach to Requirements Specification and Analysis","authors":"S. Faulk, C. Heitmeyer","doi":"10.1109/RE.1997.10007","DOIUrl":"https://doi.org/10.1109/RE.1997.10007","url":null,"abstract":"The Software Cost Reduction (SCR) requirements method is a practical, industrial-strength approach to requirements that leads to precise, unambiguous, and testable requirements specifications. The method scales to large applications, producing specifications that are both easy to understand and easy to change. Effectiveness of the SCR approach has been demonstrated in a variety of industrial, safety-critical applications. These include software for military aircraft, commercial aircraft, and the shutdown system of a nuclear power plant. Recent work has extended the method to include mechanical support for creation, validation, and verification of formal requirements specifications. This support is based on a formal requirements model. Researchers have claimed that formal methods have the potential to address many of industry’s problems with requirements, including ambiguity, incompleteness, and imprecision. Nonetheless, industry has been slow to adopt formal techniques because they are perceived as impractical for large, complex applications. The SCR method was developed to provide the benefits of formal methods to industrial developers of large-scale real-time systems. It has been effective in meeting industry needs because the technical approach addresses constraints and concerns common to industrial software developers, including ease of use, scalability, and cost-effectiveness. This tutorial gives an overview of the SCR method, its rationale, and empirical results on its effectiveness. It includes the following topics:","PeriodicalId":90955,"journal":{"name":"Proceedings. IEEE International Requirements Engineering Conference","volume":"80 1","pages":"263"},"PeriodicalIF":0.0,"publicationDate":"1997-01-05","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"72877085","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":"Exploring Scenarios in Requirements Engineering","authors":"A. Sutcliffe","doi":"10.1109/RE.1997.10000","DOIUrl":"https://doi.org/10.1109/RE.1997.10000","url":null,"abstract":"","PeriodicalId":90955,"journal":{"name":"Proceedings. IEEE International Requirements Engineering Conference","volume":"37 1","pages":"180-"},"PeriodicalIF":0.0,"publicationDate":"1997-01-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"80618637","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":"Advanced Object-Oriented Requirements Specification Methods","authors":"R. Wieringa","doi":"10.1109/RE.1997.10006","DOIUrl":"https://doi.org/10.1109/RE.1997.10006","url":null,"abstract":"treatment is based upon published material as as information publicly accessible at WWW sites. The presentation thus excludes developments of these methods that are internal to the companies that market the technique or method. The techniques and methods are analysed in terms of a framework for requirements specifications that is derived from systems engineering. The framework defines several views on software products. First, it distinguishes externally observable software product behavior from internal software product decomposition. External behavior is often described by listing required system functions. Second, the internal decomposition is further divided into a conceptual decomposition, in which the components have a meaning in terms of the environment in which the software product will operate, and a physical decomposition that has a meaning in terms of the implementation on which the software will run. The tutorial is restricted to what the techniques and methods have to say about ways to specify external behavior and the conceptual decomposition, as well as the relationship between the two. The techniques used by the methods use to specify these different views of a software product are reviewed. Roughly, the 1996 version of the objectoriented methods treated in this tutorial specify external behavior by means of use cases and the conceptual decomposition as a collection of communicating objects. Communication may be synchronous or asynchronous, and each object may perform its behavior according to a life cycle. The 1993 version of the Yourdon Systems Method specifies external behavior by means of a list of events to which the software product must respond, the initiator of the events, the desired system response and the data entering and leaving the product during the event or its response. The conceptual components of the system are data processes, data stores, event stores and control processes. The tutorial goes into some detail to show exactly how external behavior and conceptual decomposition are specified in each of the methods. In particular, the elements in the notations of the methods are listed and compared to each other. In general, the object-oriented techniques and methods tend to be strong in defining a coherent, modular conceptual architecture for the software product, where the structured methods tend to be strong in the definition of functional requirements on external software behavior. An obvious possibility for combining parts of the two approaches is to use heuristics and techniques from structured analysis for the specification of external behavior requirements and objectoriented techniques for the specification of a conceptual decomposition of the system. It turns out that the structured techniques for specifying external behavior can readily be combined with use case specification, but that the techniques of structured and object-oriented conceptual decomposition are incompatible. If we compare the techniques f","PeriodicalId":90955,"journal":{"name":"Proceedings. IEEE International Requirements Engineering Conference","volume":"92 1","pages":"266"},"PeriodicalIF":0.0,"publicationDate":"1997-01-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"80497258","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":"How Can Requirements Engineering Research Become Requirements Engineering Practice?","authors":"Steve Miller","doi":"10.1109/RE.1997.10001","DOIUrl":"https://doi.org/10.1109/RE.1997.10001","url":null,"abstract":"The path from conceptualization of a good idea to its widespread use in industry is usually long, complicated, and fraught with peril. Too often, research justified as satisfying the needs of industry begins with a wrong or simplified understanding of industry’s problems. Even given a real solution to a real problem, successful transfer of that solution into practice depends on many other factors such as funding, the emergence of champions, availability of tools, education, integration with existing methods, and all too often, plain luck. This panel will explore how methods for requirements engineering for realtime and embedded systems can be moved into practice. Representatives from industry will discuss their needs and problems using existing methods, members of the research community will discuss current research trends, and tool vendors will discuss the difficulties of moving a good solution to a real problem into practice. Each speaker will be asked to briefly state, with respect to requirements engineering for real-time, embedded systems:","PeriodicalId":90955,"journal":{"name":"Proceedings. IEEE International Requirements Engineering Conference","volume":"1 1","pages":"260"},"PeriodicalIF":0.0,"publicationDate":"1997-01-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"76760568","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}