Showing papers on "Object-oriented design published in 1984"

Object management system concepts

Abstract: An office database should be a “total” information resource in that it should be capable of storing data of many arbitrary types. Users of such a system should be able to store conveniently their documents and graphics objects in the same logical storage space as their more traditional records-oriented data.This paper presents a data model that can be used to describe more effectively the objects that occur naturally in the office environment. This model exploits some of the richer semantics of office objects such as the containment of one object within another (e.g., reports contain chapters) and the version histories of objects and their constituent parts. This model forms the basis for our experimental object management system which is used to support the creation of new office application programs.

3DPO's strategy for matching three-dimensional objects in range data

Abstract: A strategy for recognizing and locating three-dimensional objects in range data is presented. The strategy combines information derived from models of the objects and edges and surfaces detected in the data to efficiently match objects. Given a set of objects to be found, the set of object features are partitioned into subsets having similar intrinsic properties. An ordered tree of features to be considered is set up for each subset. These search trees are designed to maximize the use of the information as it is obtained and minimize the time required to recognize objects. A detailed example of this approach being used to recognize moderately complex castings in a jumble is presented.

The design of an object oriented architecture

Abstract: This paper proposes a new object model, called the distributed object model, wherein the model is unified as a protection unit, as a method of data abstraction, and as a computational unit, so as to realize reliable, maintainable, and secure systems. An object oriented architecture called ZOOM is designed based on this object model. A software simulator and cross assembler for this architecture have been implemented. The feasibility and performance of the architecture are discussed according to program sizes and estimated hardware size and execution speed.

Table: Object oriented editing of complex structures

Abstract: This research adopts the point of view that much of software development is a process of editing complex structures, structures that represent a tightly coupled integration of textual and graphical material. In the context of text and table objects, this research explores a Smalltalk-like, object oriented architecture for editors of such complex structures. Based on this experience, we propose certain design and operation principles for such editors.

An automated software design evaluator

Abstract: A prototype automated software design evaluator was implemented as part of a project whose long-term goal is the application of AI techniques to the tools in a software engineering environment. The purposes of undertaking this prototype were to: 1) identify the attributes of a software design that could be captured as design rules, 2) investigate machine-processable representations of a software design, and 3) build a proof-of-principle prototype that demonstrates that an automated design assistant can be built.

Object-oriented design and ballistics software

Abstract: The object-oriented design methodology is applied to the problem of designing ballistics software. This problem is sufficiently large and complex that the methodology must be iterated at successively lower levels of abstraction. The manner in which the design unfolds is illustrated.

An architecture for object management in OIS

Abstract: The design of a prototype for an application development environment in OIS (Office Information Systems), OPAL, is outlined. OPAL is based on an object management approach.The paper starts with a short discussion on object oriented systems and some important related concepts including Modularity, Instantiation, Property Inheritance and Subclassing, Active Objects and finally OIS-Modeling Tools.The authors' effort in this direction, OPAL, is based on the PACKET concept, which is the principal data and action structuring device. Programs, data including large data bases, meta-data as well as system defined components are all represented as objects which in turn are implemented as packets. Since all components in the system are considered as objects, it is possible to manage them all in a uniform way which in turn simplifies the system tremendously.