A shared, segmented memory system for an object-oriented database
ACM Transactions on Information Systems (TOIS)
Inheritance and the development of encapsulated software systems
Research directions in object-oriented programming
The object-oriented classification paradigm
Research directions in object-oriented programming
801 storage: architecture and programming
ACM Transactions on Computer Systems (TOCS)
Concurrent programming using actors
Object-oriented concurrent programming
Orient84/K: an object-oriented concurrent programming language for knowledge representation
Object-oriented concurrent programming
Pool-T: a parallel object-oriented language
Object-oriented concurrent programming
A survey of object-oriented concepts
Object-oriented concepts, databases, and applications
Object-oriented concepts, databases, and applications
Trellis: turning designs into programs
Communications of the ACM
Design of the Mneme persistent object store
ACM Transactions on Information Systems (TOIS)
ACM Transactions on Information Systems (TOIS) - Special issue: selected papers from the conference on office information systems
The Iris Architecture and Implementation
IEEE Transactions on Knowledge and Data Engineering
Simula Begin
Hi-index | 0.00 |
This paper presents an object-oriented approach to modeling an office, including both its content and the activities that are carried out within it. This is a part of a larger research effort---the ITHACA Project (Integrated Toolkit for Highly Advanced Computer Applications). Its purpose is to provide software engineers and application programmers with a generic framework within which to develop large, distributed office support systems. The set of interrelated models contains: the active object, the passive object and the procedure models. The active object model represents persons (or actors), organizational structures and their linkages through roles. Office facilities (e.g., cabinets, tables, tops-of-desks, wastebaskets) and information (e.g., documents, letters) are captured by the passive object model. The relationships among the various objects are expressed by both specified relationship attributes and other attributes that can be derived from them. The procedure model consists of office operators (e.g., Move, Edit, Create, Send) that are used as basic building blocks for defining office procedures.The model is presently being used to develop software for the ITHACA Project. A prototype of the active office object model has been developed, written in CooL---Combined object-oriented Language. The prototype will be used as a basis for developing a more complete systems architecture, also described in the paper.