Proceedings of the Second International Conference on Requirements Engineering

15-18 April 1996

Filter Results

Displaying Results 1 - 25 of 31
  • Requirements elicitation with indirect knowledge elicitation techniques: comparison of three methods

    Publication Year: 1996, Page(s):4 - 11
    Cited by:  Papers (9)
    Request permission for commercial reuse | Click to expandAbstract | PDF file iconPDF (912 KB)

    In this paper we describe a case study comparing the effectiveness of three indirect knowledge elicitation techniques: repertory grid analysis, multi-dimensional scaling, and hierarchical clustering. These techniques are used in situations where it is difficult for the expert to articulate their knowledge in response to direct questions. The techniques were compared in terms of the number of attri... View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • Early elicitation and definition of requirements for an interactive multimedia information system

    Publication Year: 1996, Page(s):12 - 19
    Cited by:  Papers (2)
    Request permission for commercial reuse | Click to expandAbstract | PDF file iconPDF (921 KB)

    The literature on requirements engineering contains little in the way of either theoretical guidance or empirical case studies relating to the specification of requirements for interactive multimedia information systems. This paper describes some of the special difficulties currently encountered in the early stages of developing such systems. It then presents a description of the methods and tools... View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • Structuring utterance records of requirements elicitation meetings based on speech act theory

    Publication Year: 1996, Page(s):21 - 30
    Cited by:  Papers (3)
    Request permission for commercial reuse | Click to expandAbstract | PDF file iconPDF (993 KB)

    This paper discusses a technique to structure utterance records of the meetings for requirements elicitation based on speech act theory. To elicit requirements to the system to be developed, the customers and the developers often have a series of face-to-face meetings. Utterances in verbal conversation made during the meetings include not only declarative information but also speech acts such as "... View full abstract»

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

    Publication Year: 1996, Page(s):31 - 40
    Cited by:  Papers (4)
    Request permission for commercial reuse | Click to expandAbstract | PDF file iconPDF (1061 KB)

    We describe a model and system to support collaboration in requirements analysis with hypermedia technologies. The hypermedia support approaches the issues in communication, agreement, and traceability management, which are critical in the early phase in requirements analysis. Our approach consists of(l) an extension of the Inquiry Cycle model, a cyclic model of requirements analysis, for the coll... View full abstract»

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

    Publication Year: 1996, Page(s):44 - 51
    Cited by:  Papers (4)
    Request permission for commercial reuse | Click to expandAbstract | PDF file iconPDF (788 KB)

    The experience report describes the lessons learned from the use of software failure modes and effects analysis (SFMEA) for requirements analysis of critical spacecraft software. The SFMEA process was found to be successful in identifying some ambiguous, inconsistent, and missing requirements. More importantly, the SFMEA process, followed by a backward analysis somewhat similar to fault tree analy... View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • Integrating soft systems and object-oriented analysis

    Publication Year: 1996, Page(s):52 - 59
    Cited by:  Papers (11)  |  Patents (1)
    Request permission for commercial reuse | Click to expandAbstract | PDF file iconPDF (713 KB)

    The paper assumes that the establishment of requirements for software intensive systems is a two stage process: (i) a business analysis, to identify opportunities far business improvement; followed by (ii) a computing oriented analysis to identify and define where computing facilities might support that business improvement. With that assumption, the remainder of the paper is concerned with invest... View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • Capturing functional requirements through object interactions

    Publication Year: 1996, Page(s):60 - 67
    Cited by:  Papers (1)  |  Patents (1)
    Request permission for commercial reuse | Click to expandAbstract | PDF file iconPDF (769 KB)

    The author introduces transaction based analysis (TBA), an object-oriented analysis methodology that is a blend of use-case analysis and responsibility driven design. The author shows how a user's functional requirements can be captured in a hierarchy of transaction diagrams-this hierarchy is one of the primary models generated using TBA. Transaction diagrams show how responsibilities within the s... View full abstract»

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

    Publication Year: 1996, Page(s):69 - 75
    Request permission for commercial reuse | Click to expandAbstract | PDF file iconPDF (822 KB)

    Computer modelling is a viable method for aiding requirements elicitation of future systems as it provides a mechanism for understanding and consolidating ideas which people can readily relate to. However a major drawback with a computer model is the capturing of its requirements for future contractual use. We put forward a method by which requirement statements can be attributed within models tha... View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • PRO-ART: enabling requirements pre-traceability

    Publication Year: 1996, Page(s):76 - 84
    Cited by:  Papers (37)
    Request permission for commercial reuse | Click to expandAbstract | PDF file iconPDF (1023 KB)

    Requirements traceability is essential for developing software systems of high quality. Whereas the traceability of the refinement, deployment, and use of a requirement is called post-traceability, the traceability of a requirement back to its origin is named pre-traceability. We present a requirements engineering environment, called PRO-ART, which enables requirements pre-traceability, PRO-ART is... View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • Lessons learned from a trial application of requirements modeling using statecharts

    Publication Year: 1996, Page(s):86 - 93
    Cited by:  Papers (6)
    Request permission for commercial reuse | Click to expandAbstract | PDF file iconPDF (775 KB)

    A project is described in which statechart modeling is applied to the development and validation of system behavior in a state-of-the-practice organization. A group of systems engineers modeled the behavior of diverse airplane systems. The lessons learned by these engineers are described and categorized as lessons about statechart modeling and lessons about tool features that do a good job of supp... View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • A formal approach to requirements based testing in open systems standards

    Publication Year: 1996, Page(s):94 - 100
    Request permission for commercial reuse | Click to expandAbstract | PDF file iconPDF (587 KB)

    Experience with an innovative approach to requirements based testing in the IEEE POSIX arena is presented. The work described in this paper is based on a full scale conformance test suite development for the standard IEEE Std 10035-The Ada Language Binding to POSIX. The approach taken in this work is based on a formal description of test requirements which can be automatically translated into exec... View full abstract»

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

    Publication Year: 1996, Page(s):110 - 116
    Cited by:  Papers (59)
    Request permission for commercial reuse | Click to expandAbstract | PDF file iconPDF (758 KB)

    The importance of candidate software requirements can vary by orders of magnitude, yet most software providers do not have accurate and efficient means for selecting among them. The paper describes a case study at Ericsson Radio Systems AB of two techniques for software requirements prioritizing as a means for determining the importance of candidate requirements, a pairwise comparison technique an... View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • Quality requirements analysis in customer-centered software development

    Publication Year: 1996, Page(s):117 - 124
    Cited by:  Papers (3)
    Request permission for commercial reuse | Click to expandAbstract | PDF file iconPDF (844 KB)

    An approach to nonfunctional requirements analysis for software systems is discussed. The approach is designed to refine and analyse quality requirements, to manage change and to stress customer acceptance. Our work is driven by the aim to develop a technology to enable and support customer-centered (cooperative) approaches to software development. We view quality requirements analysis essentially... View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • User-centered system decomposition: Z-based requirements clustering

    Publication Year: 1996, Page(s):126 - 135
    Cited by:  Papers (1)
    Request permission for commercial reuse | Click to expandAbstract | PDF file iconPDF (886 KB)

    Requirements clustering (RC) provides a differed approach to system decomposition, by enabling a system to be partitioned into user-recognizable components, where each component can be used, almost independently, to satisfy part of the user's needs. Requirements clustering is essential for a software development approach called incremental delivery (ID). A successful clustering of system requireme... View full abstract»

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

    Publication Year: 1996, Page(s):136 - 144
    Cited by:  Papers (149)  |  Patents (3)
    Request permission for commercial reuse | Click to expandAbstract | PDF file iconPDF (1028 KB)

    Goals are a logical mechanism for identifying, organizing and justifying software requirements. Strategies are needed for the initial identification and construction of goals. We discuss goals from the perspective of two themes: goal analysis and goal evolution. We begin with an overview of the goal-based method we have developed and summarize our experiences in applying our method to a relatively... View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • A usability-oriented approach to requirements engineering

    Publication Year: 1996, Page(s):145 - 152
    Cited by:  Papers (4)
    Request permission for commercial reuse | Click to expandAbstract | PDF file iconPDF (815 KB)

    We describe and propose a usability-oriented approach to requirements engineering, the Delta method. We suggest that by focusing primarily on the tasks that the users are supposed to accomplish using a system, rather than the functionality of the system, functional requirements are elicited in a natural way and in their right context. The Delta method was developed in collaboration with a consulta... View full abstract»

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

    Publication Year: 1996, Page(s):157 - 164
    Cited by:  Papers (10)
    Request permission for commercial reuse | Click to expandAbstract | PDF file iconPDF (857 KB)

    The first argument presented is that if we have a clear understanding of the objectives of the requirements engineering (RE) process then we can identify what techniques we need. No single method or technique will be sufficient. The second argument is that a key objective of the RE process is to specify a system which will ultimately be successful. Three common types of failure are examined: proce... View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • Project Aurora: dawn of a new way

    Publication Year: 1996, Page(s):165 - 172
    Cited by:  Papers (1)
    Request permission for commercial reuse | Click to expandAbstract | PDF file iconPDF (766 KB)

    Project Aurora is an effort underway at Bellcore to reengineer its software development process to reduce lifecycle time and cost while increasing customer satisfaction. Our project began with a focus on the requirements engineering process, but this scope quickly expanded to include many aspects of software development. We are implementing recommendations in four general categories: customer inte... View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • Using generic method chunks to generate process models fragments

    Publication Year: 1996, Page(s):173 - 180
    Cited by:  Papers (9)
    Request permission for commercial reuse | Click to expandAbstract | PDF file iconPDF (1104 KB)

    The need for process models which are easy to construct, adapt and change is acknowledged by both the information system community and the software engineering community. Our contribution to this problem is the definition of a systematic way by which fragments of process models can be generated by reusing method knowledge acquired in previous projects. We propose a method for generating methods i.... View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • Collaboration during conceptual design

    Publication Year: 1996, Page(s):182 - 189
    Cited by:  Papers (5)
    Request permission for commercial reuse | Click to expandAbstract | PDF file iconPDF (935 KB)

    Conceptual design involves requirements analysis, functional specification, and architectural design. It remains informal and poorly understood. We studied the conceptual design activities of a representative industrial software project, Centauri, for three months with follow up observations and discussions over the following six months. Our goal was to understand how patterns of collaboration and... View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • A facilitator method for upstream design activities with diverse stakeholders

    Publication Year: 1996, Page(s):190 - 197
    Request permission for commercial reuse | Click to expandAbstract | PDF file iconPDF (857 KB)

    The paper presents a method that can be used for the elicitation and specification of requirements and high level design. It supports stakeholder based modeling, rapid feasibility feed back to marketing, and the interpersonal dynamics that are necessary to develop a product. The method centers on the role of the facilitator, an independent agent whose purpose is to build the Integrated System Mode... View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • Combined analysis of user interface and domain requirements

    Publication Year: 1996, Page(s):199 - 207
    Cited by:  Papers (2)
    Request permission for commercial reuse | Click to expandAbstract | PDF file iconPDF (866 KB)

    A requirements analysis method called FLUID is proposed which in contrast to conventional methods explicitly captures the requirements of direct manipulation user interfaces. The main concepts addressing the user interface requirements comprise a task model and a UIA model. The latter reveals the essential structure of the user interface and defines the basic dialog behavior, the presentation of d... View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • Exploiting an enterprise model during systems' requirements capture and analysis

    Publication Year: 1996, Page(s):208 - 215
    Request permission for commercial reuse | Click to expandAbstract | PDF file iconPDF (873 KB)

    The paper presents a framework for the inclusion of enterprise information in the development of a software requirements specification (SRS). An enterprise model is described which includes organisational, as well as business process components. The mission of an enterprise will determine a number of business objectives, which are translated into quantifiable goals under constraints imposed by the... View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • Requirements analysis from multiple perspectives: experiences with conceptual modeling technology

    Publication Year: 1996
    Cited by:  Papers (2)
    Request permission for commercial reuse | Click to expandAbstract | PDF file iconPDF (125 KB)

    The paper discusses experiences in several commercial requirements engineering (RE) projects in augmenting an informal, teamwork oriented method with formally based computer support for the analysis and interrelation of heterogeneous perspectives. For several years, the German consulting firm USU had been working with a methodology called PFR (Presence and Future Requirements analysis). PFR is tar... View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • Identifying quality-requirement conflicts

    Publication Year: 1996
    Cited by:  Papers (10)
    Request permission for commercial reuse | Click to expandAbstract | PDF file iconPDF (85 KB)

    One of the biggest risks in software requirements engineering is the risk of overemphasizing one quality attribute requirement (e.g., performance) at the expense of others at least as important (e.g., evolvability and portability). The paper describes an exploratory knowledge based tool for identifying potential conflicts among quality attributes early in the software/ system life cycle. The Quali... View full abstract»

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