By Topic

Requirements Engineering Conference, 2003. Proceedings. 11th IEEE International

Date 8-12 Sept. 2003

Filter Results

Displaying Results 1 - 25 of 64
  • Monitoring Web service requirements

    Publication Year: 2003, Page(s):65 - 74
    Cited by:  Papers (47)
    Request permission for commercial reuse | Click to expandAbstract | PDF file iconPDF (653 KB) | HTML iconHTML

    Businesses that rely on Web services are vulnerable to the problems of those Web services. Service contracts and warranties can provide some assurances. However, they provide traditional recourse, rather than timely alerts of impending problems. While electronic commerce has increased the speed of online transactions, the technology of monitoring online transactions has lagged behind. To address t... View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • Evaluating the quality of a UML business model

    Publication Year: 2003
    Request permission for commercial reuse | Click to expandAbstract | PDF file iconPDF (187 KB) | HTML iconHTML

    Many Siemens operating companies build software products or products with a high software content (e.g. embedded software). Siemens Corporate Research has had the unique opportunity over the last few years to look at the analysis models from which the software products were derived, analyze them, and recommend changes. All the models investigated define commercial products that are or will be in t... View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • Requirements engineering for a pervasive health care system

    Publication Year: 2003, Page(s):55 - 64
    Cited by:  Papers (5)
    Request permission for commercial reuse | Click to expandAbstract | PDF file iconPDF (359 KB) | HTML iconHTML

    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 enabl... View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • The journey toward secure systems: achieving assurance

    Publication Year: 2003, Page(s): 5
    Request permission for commercial reuse | Click to expandAbstract | PDF file iconPDF (173 KB) | HTML iconHTML

    First Page of the Article
    View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • Relating practitioner needs to research activities

    Publication Year: 2003
    Cited by:  Papers (2)
    Request permission for commercial reuse | Click to expandAbstract | PDF file iconPDF (300 KB) | HTML iconHTML

    Many organizations look to research to yield new and improved products and practices. Connecting practitioners who have the need for research results to the researchers producing those results is important to guiding research and utilizing its results. Likewise, connecting researchers working on related topics to one another, and connecting practitioners with related needs to one another, is impor... View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • Customer requirements and user requirements: why the discrepancies?

    Publication Year: 2003
    Cited by:  Papers (1)
    Request permission for commercial reuse | Click to expandAbstract | PDF file iconPDF (189 KB) | HTML iconHTML

    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 th... View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • Lessons learnt from five years of experience in ERP requirements engineering

    Publication Year: 2003, Page(s):45 - 54
    Cited by:  Papers (4)
    Request permission for commercial reuse | Click to expandAbstract | PDF file iconPDF (268 KB) | HTML iconHTML

    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... View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • Requirements for the Internet

    Publication Year: 2003, Page(s):3 - 4
    Cited by:  Papers (1)
    Request permission for commercial reuse | Click to expandAbstract | PDF file iconPDF (181 KB) | HTML iconHTML

    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 ... View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • A benchmarking method for information systems

    Publication Year: 2003, Page(s):245 - 253
    Cited by:  Papers (1)
    Request permission for commercial reuse | Click to expandAbstract | PDF file iconPDF (655 KB) | HTML iconHTML

    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 execute... View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • Goal-oriented idea generation method for requirements elicitation

    Publication Year: 2003, Page(s):363 - 364
    Cited by:  Papers (9)
    Request permission for commercial reuse | Click to expandAbstract | PDF file iconPDF (346 KB) | HTML iconHTML

    We present an extended version of goal-oriented analysis methods where an idea generation method is combined to reinforce the support of the step for identifying subgoals by a team of stakeholders. To assess our method, experimental results are also discussed. View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • Introducing abuse frames for analysing security requirements

    Publication Year: 2003, Page(s):371 - 372
    Cited by:  Papers (16)
    Request permission for commercial reuse | Click to expandAbstract | PDF file iconPDF (199 KB) | HTML iconHTML

    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 i... View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • SMaRT - scenario management and requirements tool

    Publication Year: 2003
    Request permission for commercial reuse | Click to expandAbstract | PDF file iconPDF (175 KB) | HTML iconHTML

    We demonstrate the scenario management and requirements tool (SMaRT). It provides an intuitive Web-based interface that supports analysts as they input, manage, view, analyze, and work with scenarios and their associated episodes, requirements, goals, obstacles, and pre- and post-conditions. The tool also supports project management functions. It encompasses greater functionality through the imple... View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • In situ requirements analysis: a deeper examination of the relationship between requirements determination and project selection

    Publication Year: 2003, Page(s):11 - 22
    Cited by:  Papers (2)
    Request permission for commercial reuse | Click to expandAbstract | PDF file iconPDF (624 KB)

    There has been sparse study of how requirements analysis is performed in situ, i.e. by organizations building large, complex systems. We assert that a better understanding of in situ requirements practice is necessary to improve and ground current theories of requirements analysis. We performed an empirical field study to examine in detail the issues faced by practitioners in forming and stabilizi... View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • Evolutionary requirements analysis

    Publication Year: 2003, Page(s):264 - 273
    Cited by:  Papers (4)
    Request permission for commercial reuse | Click to expandAbstract | PDF file iconPDF (487 KB) | HTML iconHTML

    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 combina... View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • Resolving requirements discovery in testing and operations

    Publication Year: 2003, Page(s):33 - 41
    Cited by:  Papers (5)
    Request permission for commercial reuse | Click to expandAbstract | PDF file iconPDF (262 KB) | HTML iconHTML

    We describe the results of an investigation into requirements discovery during testing and operations. Requirements discovery includes both new requirements and new knowledge regarding existing requirements. Analysis of anomaly reports shows that many of the anomalies that occur during these phases involve requirements discovery. Previous work identified four common mechanisms for requirements dis... View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • Testing with partial traced requirements: a necessary step towards higher quality system level verification

    Publication Year: 2003
    Request permission for commercial reuse | Click to expandAbstract | PDF file iconPDF (175 KB) | HTML iconHTML

    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... View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • Practical lessons from 40 system integrating projects

    Publication Year: 2003
    Cited by:  Papers (3)
    Request permission for commercial reuse | Click to expandAbstract | PDF file iconPDF (198 KB) | HTML iconHTML

    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 evaluate... View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • Improving requirements tracing via information retrieval

    Publication Year: 2003, Page(s):138 - 147
    Cited by:  Papers (64)  |  Patents (2)
    Request permission for commercial reuse | Click to expandAbstract | PDF file iconPDF (278 KB) | HTML iconHTML

    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 adapte... View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • RE in flatness measurement and control systems development at ABB

    Publication Year: 2003
    Cited by:  Papers (1)
    Request permission for commercial reuse | Click to expandAbstract | PDF file iconPDF (182 KB) | HTML iconHTML

    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® (rational unified process®) tailored to fit the Stressometer department's development... View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • Teaching requirements engineering through role playing: lessons learnt

    Publication Year: 2003, Page(s):233 - 241
    Cited by:  Papers (20)
    Request permission for commercial reuse | Click to expandAbstract | PDF file iconPDF (292 KB)

    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 v... View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • Bringing usability to the early stages of software development

    Publication Year: 2003, Page(s):359 - 360
    Cited by:  Papers (3)
    Request permission for commercial reuse | Click to expandAbstract | PDF file iconPDF (195 KB) | HTML iconHTML

    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... View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • Integrating RE methods to support use case based requirements specification

    Publication Year: 2003, Page(s):369 - 370
    Cited by:  Papers (2)
    Request permission for commercial reuse | Click to expandAbstract | PDF file iconPDF (203 KB) | HTML iconHTML

    There has recently been a trend in requirements engineering towards combining techniques in order to complement the deficiencies of one with the strengths of another. RESCUE is a process that continues this tradition and combines human activity modelling and i* system goal modelling in a concurrent engineering approach to support the generation of more complete and correct use case models and desc... View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • FAUST: formal analysis using specification tools

    Publication Year: 2003
    Cited by:  Papers (1)
    Request permission for commercial reuse | Click to expandAbstract | PDF file iconPDF (183 KB) | HTML iconHTML

    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 par... View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • Requirements analysis for customizable software: a goals-skills-preferences framework

    Publication Year: 2003, Page(s):117 - 126
    Cited by:  Papers (14)
    Request permission for commercial reuse | Click to expandAbstract | PDF file iconPDF (641 KB) | HTML iconHTML

    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 in... View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • Measuring requirements traceability from multiple angles at multiple lifecycle entry points

    Publication Year: 2003
    Cited by:  Papers (2)
    Request permission for commercial reuse | Click to expandAbstract | PDF file iconPDF (175 KB) | HTML iconHTML

    Ideally, requirements traceability metrics are started at the beginning of a project. The initial statement of work or request for proposal form the root of the requirements tree and the traditional requirements metrics (requirements added, modified, deleted) are baselined from those documents. The collecting of requirements metrics at various stages of the lifecycle $from architecture to testing ... View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.