Results 1 - 10
of
596
An Analysis of the Requirements Traceability Problem
, 1993
"... In this paper1, we investigate and discuss the underlying nature of the requirements traceability problem. Our work is based on empirical studies, involving over 100 practitioners, and an evaluation of current support. We introduce the distinction between pre-requirements specification (pre-RS) trac ..."
Abstract
-
Cited by 389 (19 self)
- Add to MetaCart
(Show Context)
In this paper1, we investigate and discuss the underlying nature of the requirements traceability problem. Our work is based on empirical studies, involving over 100 practitioners, and an evaluation of current support. We introduce the distinction between pre-requirements specification (pre-RS) traceability and post-requirements specification (post-RS) traceability, to demonstrate why an all-encompassing solution to the problem is unlikely, and to provide a framework through which to understand its multifaceted nature. We report how the majority of the problems attributed to poor requirements traceability are due to inadequate pre-RS traceability and show the fundamental need for improvements here. In the remainder of the paper, we present an analysis of the main barriers confronting such improvements in practice, identify relevant areas in which
Toward reference models for requirements traceability
- IEEE Trans. Softw. Eng. 2001
"... Requirements traceability is intended to ensure continued alignment between stakeholder requirements and system evolution. To be useful, traces must be organized according to some modeling framework. Indeed, several such frameworks have been proposed, mostly based on theoretical considerations or an ..."
Abstract
-
Cited by 272 (5 self)
- Add to MetaCart
(Show Context)
Requirements traceability is intended to ensure continued alignment between stakeholder requirements and system evolution. To be useful, traces must be organized according to some modeling framework. Indeed, several such frameworks have been proposed, mostly based on theoretical considerations or analysis of other literature. This paper, in contrast, follows an empirical approach. Focus groups and interviews conducted in 26 major software development organizations demonstrate a wide range of traceability practices with distinct low-end and high-end users of traceability. From these observations, reference models comprising the most important kinds of traceability links for various development tasks have been synthesized. The resulting models have been validated in case studies and are incorporated in a number of commercial traceability tools. The discussion of the link types and their usage in practice has implications for the design of next-generation traceability methods and tools.
Augmenting Organizational Memory: A Field Study of Answer Garden
- ACM TRANSACTIONS ON INFORMATION SYSTEMS
, 1994
"... ... This article presents Answer Garden, a system for growing organizational memory. The article describes the system and its underlying implementation. It then presents findings from a field study of Answer Garden. The article discusses the usage data and qualitative evaluations from the field stud ..."
Abstract
-
Cited by 255 (15 self)
- Add to MetaCart
... This article presents Answer Garden, a system for growing organizational memory. The article describes the system and its underlying implementation. It then presents findings from a field study of Answer Garden. The article discusses the usage data and qualitative evaluations from the field study, and then draws a set of lessons for next-generation organizational memory systems.
Walking away from the desktop computer: distributed collaboration and mobility in a product design team
- Proc. Computer-Supported Cooperative Work (CSCW
, 1996
"... A study of a spatially distributed product design team shows that most members are rarely at their individual desks. Mobility is essential for the use of shared resources and for communication. It facilitates informal interactions and awareness unavailable to colleagues at remote sites. Impli-cation ..."
Abstract
-
Cited by 250 (1 self)
- Add to MetaCart
A study of a spatially distributed product design team shows that most members are rarely at their individual desks. Mobility is essential for the use of shared resources and for communication. It facilitates informal interactions and awareness unavailable to colleagues at remote sites. Impli-cations for technology design include portable and distrib-uted computing resources, in particular, moving beyond individual workstation-centric CSCW applications.
Telos: Representing Knowledge About Information Systems
- ACM Transactions on Information Systems
, 1990
"... This paper describes a language that is intended to support software engineers in the development of information systems throughout the software lifecycle. This language is not a programming language. Following the example of a number of other software engineering projects, our work is based on the ..."
Abstract
-
Cited by 246 (44 self)
- Add to MetaCart
(Show Context)
This paper describes a language that is intended to support software engineers in the development of information systems throughout the software lifecycle. This language is not a programming language. Following the example of a number of other software engineering projects, our work is based on the premise that information system development is knowledge-intensive and that the primary responsibility of any language intended to support this task is to be able to formally represent the relevant knowledge.
The Intellectual Challenge of CSCW: The Gap Between Social Requirements and Technical Feasibility
- Human-Computer Interaction
, 2000
"... Over the last 10 years, Computer-Supported Cooperative Work (CSCW) has identified a base set of findings. These findings are taken almost as assumptions within the field. In summary, they argue that human activity is highly flexible, nuanced, and contextualized and that computational entities such a ..."
Abstract
-
Cited by 225 (12 self)
- Add to MetaCart
(Show Context)
Over the last 10 years, Computer-Supported Cooperative Work (CSCW) has identified a base set of findings. These findings are taken almost as assumptions within the field. In summary, they argue that human activity is highly flexible, nuanced, and contextualized and that computational entities such as information transfer, roles, and policies need to be similarly flexible, nuanced, and contextualized. However, current systems cannot fully support the social world uncovered by these findings. This paper argues that there is an inherent gap between the social requirements of CSCW and its technical mechanisms. The social-technical gap is the divide between what we know we must support socially and what we can support technically. Exploring, understanding, and hopefully ameliorating this social-technical gap is the central challenge for CSCW as a field and one of the central problems for HCI. Indeed, merely attesting the continued centrality of this gap could be one of the important intellectual contributions of CSCW. This paper also argues that the challenge of the social-technical gap creates an opportunity to refocus CSCW as a Simonian science of the artificial. To be published in Human-Computer Interaction Preprint- Ackerman- Challenge of CSCW 1 1.
What is coordination theory and how can it help design cooperative work systems?
, 1990
"... It is possible to design cooperative work tools based only on “common sense ” and good intuitions. But the history of technology is replete with examples of good theories greatly aiding the development of useful technology. Where, then, might we look for theories to help us design computer-supported ..."
Abstract
-
Cited by 221 (7 self)
- Add to MetaCart
It is possible to design cooperative work tools based only on “common sense ” and good intuitions. But the history of technology is replete with examples of good theories greatly aiding the development of useful technology. Where, then, might we look for theories to help us design computer-supported cooperative work tools? In this paper, we will describe one possible perspective-the interdisciplinary study of coordination-that focuses, in part, on how people work together now and how they might do so differently with new information technologies. In one sense, there is little that is new about the study of coordination. Many different disciplines-including computer science, sociology, political science, management science, systems theory, economics, linguistics, and psychology-have all dealt, in one way or another, with fundamental questions about coordination. Furthermore, several previous writers have suggested that theories about coordination are likely to be important for designing cooperative work tools (e.g., [Holt88], lWino861). We hope to suggest here, however, that the potential for fruitful interdisciplinary connections concerning coordination is much greater than has as yet been widely
Experiments with Oval: A Radically Tailorable Tool for Cooperative Work
, 1995
"... This article describes a series of tests of the generality of a “radically tailorable” tool for cooperative work. Users of this system can create applications by combining and modifying four kinds of building blocks: objects, uiezus, agents, and links. We found that user-level tailoring of these pri ..."
Abstract
-
Cited by 177 (4 self)
- Add to MetaCart
This article describes a series of tests of the generality of a “radically tailorable” tool for cooperative work. Users of this system can create applications by combining and modifying four kinds of building blocks: objects, uiezus, agents, and links. We found that user-level tailoring of these primitives can provide most of the functionality found in well-known cooperative work systems such as gIBIS, Coordinator, Lotus Notes, and Information Lens. These primitives, therefore, appear to provide an elementary “tailoring language” out of which a wide variety of integrated information management and collaboration applications can be constructed by end users.
A Usability Study of Awareness Widgets in a Shared Workspace Groupware System
- Proceedings of the Conference on Computer-Supported Cooperative Work (CSCW’96
, 1996
"... Workspace awareness is knowledge about others’ interaction with a shared workspace. Groupware systems provide only limited information about other participants, often compromising workspace awareness. This paper describes a usability study of several widgets designed to help maintain awareness in a ..."
Abstract
-
Cited by 167 (15 self)
- Add to MetaCart
Workspace awareness is knowledge about others’ interaction with a shared workspace. Groupware systems provide only limited information about other participants, often compromising workspace awareness. This paper describes a usability study of several widgets designed to help maintain awareness in a groupware workspace. These widgets include a miniature view, a radar view, a multiuser scrollbar, a glance function, and a “what you see is what I do ” view. The study examined the widgets’ information content, how easily people could interpret them, and whether they were useful or distracting. Observations, questionnaires, and interviews indicate that the miniature and radar displays are useful and valuable for tasks involving spatial manipulation of artifacts.
