1986
DOI: 10.21236/ada182094
|View full text |Cite
|
Sign up to set email alerts
|

Intelligent Assistance without Artificial Intelligence

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
1
1

Citation Types

0
6
0

Year Published

1997
1997
2005
2005

Publication Types

Select...
5
2

Relationship

1
6

Authors

Journals

citations
Cited by 19 publications
(6 citation statements)
references
References 13 publications
0
6
0
Order By: Relevance
“…This is the first work the authors are aware of which attempts to marry virtual environment techniques with software development environments. A number of Software Development Environments (SDEs) have been created over the years in both research and industry (see [6], [7], [8], [9], [5] for example). These differ from our conceptual model in that they assume that all artifacts will be managed by the development environment itself (or through tools specially "wrapped" to be called from the environment).…”
Section: Related Workmentioning
confidence: 99%
See 1 more Smart Citation
“…This is the first work the authors are aware of which attempts to marry virtual environment techniques with software development environments. A number of Software Development Environments (SDEs) have been created over the years in both research and industry (see [6], [7], [8], [9], [5] for example). These differ from our conceptual model in that they assume that all artifacts will be managed by the development environment itself (or through tools specially "wrapped" to be called from the environment).…”
Section: Related Workmentioning
confidence: 99%
“…Central to the Groupspace concept is the idea that project artifacts continue to exist in their original form in their original repositories. This differs from traditional Software Development Environments (SDEs) (like Oz [5], SMILE [6], Desert [7], Sun NSE [8], Microsoft Visual C++ [9]), as well as most traditional Groupware systems (like eRoom[10], TeamWave [11], and Orbit [12]) in which artifacts are under the strict control of the environment. In these systems, users are expected to access artifacts only through the development environment's cadre of tools or via COTS tools specially "wrapped" to work with the environment.…”
mentioning
confidence: 99%
“…A fundamental problem is that di erent users working independently might c r e a t e t wo or more proposed updates that con ict with each other in some way. Some systems, such a s R CS, Smile (Kaiser and Feiler, 1987) or Infuse (Kaiser and Perry, 1987), provide mechanisms for the disciplined creation and modi cation of versions, so that con icts can be isolated and resolved before the base data is corrupted. However, the fundamental issue of e ciently identifying when a con ict has arisen is largely unexplored in the literature.…”
Section: Introductionmentioning
confidence: 99%
“…Our notion of an experimental database was initially introduced in Smile [11], a multiple-user programming environment for C developed as part of the Gandalf project [7] at Carnegie Mellon University. Infuse extends this notion to (1) a hierarchy, (2) automatic partitioning of the change set into EDBs, and (3) integration testing.…”
Section: Related Work and Future Directionsmentioning
confidence: 99%