# [1993] Proceedings of the IEEE International Symposium on Requirements Engineering

## Filter Results

Displaying Results 1 - 25 of 42
• ### Proceedings of IEEE International Symposium on Requirements Engineering (Cat. No.92TH0491-1)

Publication Year: 1993
| PDF (67 KB)
• ### CARD: a software requirements definition environment

Publication Year: 1993, Page(s):90 - 93
Cited by:  Papers (4)
| | PDF (288 KB)

Computer-aided requirements definition methods/environment are presented. A composite requirements model (requirements frame) is proposed, and several supporting methods of software requirements definition based on the model are developed. They are: analysis of requirements; describing requirements; verification of an SRS (software requirements specification); SRS execution; and software prelimina... View full abstract»

• ### READS: a requirements engineering tool

Publication Year: 1993, Page(s):94 - 97
Cited by:  Papers (2)  |  Patents (1)
| | PDF (368 KB)

A hypertext system, READS, designed to support the key requirements engineering activities of requirements discovery, analysis, decomposition, allocation, traceability and reporting is discussed. READS facilitates the construction, browsing, and maintenance of a typed hypertext network mapped onto a high-speed relational database server through a user interface designed specifically for the system... View full abstract»

• ### Theories underlying requirements engineering: an overview of NATURE at Genesis

Publication Year: 1993, Page(s):19 - 31
Cited by:  Papers (17)
| | PDF (1396 KB)

NATURE is a collaborative basic research project on theories underlying requirements engineering funded by the ESPRIT III program of the European communities. Its goals are to develop a theory of knowledge representation that embraces subject, usage and development worlds surrounding the system, including expressive freedoms; a theory of domain engineering that facilitates the identification, acqu... View full abstract»

• ### Requirement analysis by the KJ editor

Publication Year: 1993, Page(s):98 - 101
Cited by:  Papers (4)
| | PDF (292 KB)

The KJ method, a technique for obtaining a panoramic view of entire index card arrangements on a computer display, is described. The KJ editor simulates the activity of arranging index cards on a desk. Such activity is essential for carrying out the so-called KJ method, which is used in Japanese business. The editor is used for requirements analysis. It is found that the editor can be used for rec... View full abstract»

• ### Requirements reconnoitring at the juncture of domain and instance

Publication Year: 1993, Page(s):73 - 76
Cited by:  Papers (4)
| | PDF (360 KB)

The ability to rapidly reconnoitre requirements, i.e., construct, critique, contrast and complete a system's requirements, necessitates dealing with the inherent nature of requirements (their incompleteness, inconsistency, ambiguity, etc.). It is shown how such explorations can be sustained by linking a network of domain requirements with instantiations of those requirements for a particular insta... View full abstract»

• ### Issues in the development of a requirements traceability model

Publication Year: 1993, Page(s):256 - 259
Cited by:  Papers (14)
| | PDF (328 KB)

In the development of large-scale, real-time, complex computer intensive systems, it is essential to maintain traceability of requirements to various outputs to ensure that the system meets the current set of requirements. Based on an empirical study in a simulated systems development environment, several major issues that need to be considered in the development of a model of requirements traceab... View full abstract»

• ### Modeling organizations for information systems requirements engineering

Publication Year: 1993, Page(s):34 - 41
Cited by:  Papers (23)  |  Patents (1)
| | PDF (692 KB)

In attempting to understand information system environments during requirements engineering, it is often helpful to have an understanding of the whys' as well as the whats' about the environment. A natural way to answer why questions is by tracing them to goals. In an organizational environment, however, the whys do not originate from a single set of given goals. Organizational agents depend on ... View full abstract»

• ### Description of specification developments

Publication Year: 1993, Page(s):216 - 223
Cited by:  Papers (4)
| | PDF (540 KB)

A framework allowing the expression of both the incremental construction of a specification and the development process behind the construction (decisions and their rationale) is proposed. A data structure composed of a workplan and the product is introduced and used to model a specification development. The availability of development operators is a critical point of the specification development... View full abstract»

• ### Requirements engineering by example: an empirical study

Publication Year: 1993, Page(s):104 - 111
Cited by:  Papers (11)
| | PDF (676 KB)

Domain abstraction reuse during requirements engineering is evaluated as a paradigm during use of a research tool. Iterative fact acquisition and abstraction retrieval, supported by example-based explanation of abstractions, are implemented in a prototype known as AIR (adviser for intelligent reuse). Observation of the use of AIRs by inexperienced software engineers reveal the effectiveness of thi... View full abstract»

• ### Representing knowledge in requirements engineering: an empirical study of what software engineers need to know

Publication Year: 1993, Page(s):273 - 276
Cited by:  Papers (4)
| | PDF (384 KB)

The selection and structuring of requirements engineering data necessitates an empirical prediction about the future utility of the selected data and of the retrieval paths available in the structure. In order to investigate these predictions, the questions asked by software engineers at software requirements and preliminary design meetings are analyzed. It is assumed that the kinds of information... View full abstract»

• ### Should we specify systems or domain?

Publication Year: 1993, Page(s):77 - 80
| | PDF (8 KB)

The question of specifying systems or domains is addressed. Among the issues discussed are: the requirements of first-class connectors for domain specifications; the use of application frameworks as domain specifications; the role of connectors in domain specifications; domain model specification; the question of what precisely is meant by a domain of the question of reuse; and the difficulty in p... View full abstract»

• ### Domain descriptions

Publication Year: 1993, Page(s):56 - 64
Cited by:  Papers (20)
| | PDF (836 KB)

Ideas about the meaning of descriptions, aimed at clarifying the relationship between a formal specification and the domain of the system to be specified, are introduced. Understanding of specifications must rest on explicit statements of what they are about and what they assert. The authors argue that current formal specification techniques are inadequate in this respect, and therefore cannot off... View full abstract»

• ### A strategy for conceptual model acquisition

Publication Year: 1993, Page(s):243 - 246
Cited by:  Papers (13)
| | PDF (336 KB)

A strategy for conceptual model acquisition is proposed. Knowledge acquisition is performed with a simple structure, i.e., the lexicon. Using the lexicon and an AI-based approach, a conceptual model is derived. The approach assists in the construction of a first cut version of the conceptual model, which should undergo a validation process. A prototype is built using an object-oriented AI shell. T... View full abstract»

• ### Requirements engineering using the SOS paradigm

Publication Year: 1993, Page(s):260 - 263
Cited by:  Papers (7)
| | PDF (416 KB)

Service-providing enterprises (SPEs) employ systems composed of people, computer hardware and software, and other mechanisms to perform service actions in the customer's environment as well as to carry out internal operations as part of the SPE infrastructure. These systems are termed service-oriented systems (SOSs). The authors address the question of how to reformulate and simplify the requireme... View full abstract»

• ### Dealing with performance requirements during the development of information systems

Publication Year: 1993, Page(s):42 - 49
Cited by:  Papers (5)
| | PDF (748 KB)

Performance goals for information systems are treated as a class of nonfunctional requirements (NFRs). A given model for representing NFRs is given to make provisions for: representing a variety of implementation alternatives; expressing performance goals (including responsiveness) in terms of performance and information system concepts; and organizing the process into layers corresponding to subs... View full abstract»

• ### The classification of requirements engineering methods

Publication Year: 1993, Page(s):182 - 186
Cited by:  Papers (8)
| | PDF (428 KB)

A classification of requirements engineering methods based on the social assumptions made about organizations is presented. The scheme, based on a taxonomy of social theories after J. Lyotard (1984), provides a set of categories corresponding to metanarratives used within requirements engineering. A short description of each metanarrative is provided in terms of the assumptions made about the natu... View full abstract»

• ### Social issues in requirements engineering

Publication Year: 1993, Page(s):194 - 195
Cited by:  Papers (8)
| | PDF (204 KB)

Social issues in requirements engineering are classified according to what groups are involved. Topics discussed include issues within the client organization, requirement team issues, issues between the client organization and the requirements team, and development team issues View full abstract»

• ### I never knew my requirements were object-oriented until I talked to my analyst

Publication Year: 1993, Page(s):226 - 230
Cited by:  Papers (1)
| | PDF (92 KB)

A discussion on object-oriented analysis (OOA) is summarized. Among the topics discussed are: whether objects facilitate understanding; whether autonomy facilitates understanding; whether OOA encourages premature design; whether OOA addresses requirements volatility; the Shlaer-Mellor method; the separation of problem domains; the translation of domains; the role of prototyping in requirements eng... View full abstract»

• ### Matching conceptual graphs as an aid to requirements re-use

Publication Year: 1993, Page(s):112 - 120
Cited by:  Papers (18)  |  Patents (5)
| | PDF (812 KB)

The types of knowledge used during requirements acquisition are identified and a tool to aid in this process, the ReqColl (requirements collector), is introduced. The tool uses conceptual graphs to represent domain concepts, and attempts to recognize new concepts through the use of a matching facility. The overall approach to requirements capture is described and the approach to matching is illust... View full abstract»

• ### The role of policy in requirements definition

Publication Year: 1993, Page(s):277 - 280
Cited by:  Papers (2)
| | PDF (372 KB)

Three significant challenges facing the discipline of software engineering are understanding how software designers reason about policy, understanding how they define requirements based on this reasoning, and providing machine-based intelligent tools that support reasoning about policy. The authors are developing the concept of a policy workbench: knowledge-based tools that support reasoning about... View full abstract»

• ### Using scenarios in deficiency-driven requirements engineering

Publication Year: 1993, Page(s):134 - 141
Cited by:  Papers (9)
| | PDF (672 KB)

A process is described for generating and validating specifications, together with an automated tool which supports this approach. The input to the process is a set of client objectives, expressed as transitions between states. These transitions fall into two classes: those which should be supported, and those which should be prevented. The output is a specification of a target artifact, expressed... View full abstract»

• ### An incremental integration tool between requirements engineering and programming in the large

Publication Year: 1993, Page(s):82 - 89
Cited by:  Papers (7)
| | PDF (688 KB)

In the IPSEN research project at Aachen University in Germany, integration tools that integrate documents of different working areas have been developed. They execute a transformation algorithm and check the consistency incrementally by installing and maintaining links between those documents. A framework is introduced that allows the efficient realization of new integration tools. The functionali... View full abstract»

• ### Requirements engineering technologies at Rome Laboratory

Publication Year: 1993, Page(s):15 - 18
Cited by:  Papers (1)
| | PDF (344 KB)

The program of research and development of requirements engineering technologies at Rome Laboratory since the early 1980s is described. Research is based on a process model of requirements engineering, and implementation of this model using conventional technologies. R&D activities have led to the enhancement of a requirements analysis tool and the development of two requirements validation to... View full abstract»

• ### Domain modelling with hierarchies of alternative viewpoints

Publication Year: 1993, Page(s):65 - 72
Cited by:  Papers (12)
| | PDF (728 KB)

It is shown how domain modelling can be used within requirements engineering to reveal the conceptual models used by the participants, and relate these to one another. Existing elicitation techniques used in AI adopt a purely cognitive stance, in that they model a single problem-cognitive stance, and ignore the social and organizational context. A framework for representing alternative, conflictin... View full abstract»