ACM Home Page
Please provide us with feedback. Feedback
View-based tool integration in database-centered environment
Full text PdfPdf (872 KB)
Source Symposium on Small Systems archive
Proceedings of the 1990 ACM SIGSMALL/PC symposium on Small systems table of contents
Crystal City, Virginia, United States
Pages: 53 - 60  
Year of Publication: 1990
ISBN:0-89791-347-7
Author
V. Venugopal  Motorola Inc., Phoenix, AZ and Department of Computer Science, The Ohio State University, 2036 Neil Avenue Mall, Columbus, Ohio
Sponsor
SIGICE: ACM Special Interest Group on Individual Computing Environment
Publisher
ACM  New York, NY, USA
Bibliometrics
Downloads (6 Weeks): 1,   Downloads (12 Months): 3,   Citation Count: 0
Additional Information:

abstract   references   index terms   collaborative colleagues   peer to peer  

Tools and Actions: Request Permissions Request Permissions    Review this Article  
DOI Bookmark: Use this link to bookmark this Article: http://doi.acm.org/10.1145/99412.99428
What is a DOI?

ABSTRACT

Database-centered environment architectures differ significantly from file-based architectures. Consequently they require a different set of primitives for tool support. This paper describes a form of tool composition called cotools which provides many of the benefits of UNIX pipes in terms of being able to reuse existing tools in tool composites, and allowing tools to operate concurrently ad incrementally on data. However, the tool language and the composition model is tailored to provide these benefits in a database-centered environment where tools do not directly communicate with each other. The effect of communication is achieved by allowing member tools in a cotool to access common data in a coordinated manner while allowing the changes made to data by one tool immediately visible to other tools in the cotool. Since database transactions normally maintain consistency in a database by disallowing interleaved data manipulation amongst separate applications, certain modifications to the concept of transactions are required. One of goals from a systemic point of view is to allow the benefits of tool cooperation without completely violating the transactions idea, which is a very clean mechanism for maintaining data consistency in a shared data store.


REFERENCES

Note: OCR errors may be found in this Reference List extracted from the full text article. ACM has opted to expose the complete List rather than only correct and linked references.

 
1
Lightweight Processes Manual:SunOS4.0.
2
3
 
4
5
 
6
 
7
 
8
S. Sarkar and }. Ramanathan. Data model and persistent language features for integrated project support environments. Technical Report OSU-CISRC- 6/89-TR22, The Ohio State University, 1989.
9
 
10
 
11
V. Venugopal. Active Tool Support for Software Development Environments. PhD thesis, The Ohio State University, 1989.
 
12
V. Venugopal and J. Ramanathan. Programmed views for object-oriented environments. Technical Report OSU-CISRC-6/89-TR21, The Ohio State University, 1989.
 
13
Vasudevan Venugopal and Soumitra Sarkar. A tool integration mechanism for database-centered CASE environments, Technical report, The Ohio State University, 1989.


Peer to Peer - Readers of this Article have also read: