scispace - formally typeset
Search or ask a question

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


Journal ArticleDOI
TL;DR: This paper describes an object-oriented design methodology, using Ada as the implementation language, and indicates that the application of appropriate design methodolgies, embodied in a high-order language, is appropriate in combatting software depression.
Abstract: The current software depression is characterized by software that is late, erroneous, and costly. Experience indicates that the application of appropriate design methodolgies, embodied in a high-order language, is appropriate in combatting this depression. In particular, this paper describes an object-oriented design methodology, using Ada as the implementation language.

203 citations


Proceedings Article
18 Aug 1982
TL;DR: An attempt of analogical learning method by verbalism is shown in order to create a model for an identification of unknown objects that can augment or create new descriptions by making use of explicit verbal instructions.
Abstract: In this paper an attempt of analogical learning method by verbalism is shown in order to create a model for an identification of unknown objects. When we expect a computer to recognize objects, the models of them must be given to it, however there are cases where some objects may not be matched to the models or there is no model with which object is compared. At that time, this system can augment or create new descriptions by making use of explicit verbal instructions.

6 citations


Proceedings ArticleDOI
07 Jun 1982
TL;DR: Petri-nets and precedence graphs are presented as techniques for the modeling of a problem for implementation on a computer system and techniques using the Petri-net and precedence graph to decompose the problem model into subsets that may be executed on a distributed/multiprocessor system.
Abstract: Software design methodologies for distributed/multiprocessor systems are investigated. Parallelism and multitasking are considered as key issues in the design process. Petri-nets and precedence graphs are presented as techniques for the modeling of a problem for implementation on a computer system. Techniques using the Petri-net and precedence graph to decompose the problem model into subsets that may be executed on a distributed/multiprocessor system are presented. These techniques offer a systematic design methodology for the design of distributed/multiprocessor system software.

5 citations


Proceedings ArticleDOI
01 Jan 1982
TL;DR: This paper compares and contrasts, from an architectural point of view, eight major object oriented operating systems.
Abstract: Object oriented design of operating systems has evolved from pure protection considerations to a more general methodology of design as exemplified in Intel's iAPX-432 machine. This paper compares and contrasts, from an architectural point of view, eight major object oriented operating systems. Five different architectural aspects have been chosen as a basis for this analysis. These aspects include: uniformity of the object approach, object type extensibility, the process concept, the domain concept, and object implementation techniques.

5 citations


01 Jan 1982
TL;DR: A method for the design of distributed software systems and a model for their design representation and analysis are presented, based on a modified form of Petri net, that enables one to represent both the structure and the behavior of a distributed software system.
Abstract: A method for the design of distributed software systems and a model for their design representation and analysis are presented. This model is based on a modified form of Petri net, and enables one to represent both the structure and the behavior of a distributed software system. Both the control and data flows are included in a single graph, flowchart-like representation of the design. The representation technique emphasizes partially ordered software components, hierarchical component structure, abstract data types, data objects, local control, and distributed system state. Software components are externally described in terms of their input and output control state variables, abstract data types, data objects, and a set of control and data transfer specifications. Interconnection of software components is defined through the shared control state variables and through the shared data objects. A system component can internally be viewed as a collection of partially ordered subcomponents, local control states, local abstract data types and local data objects. The method generates a design representation at a certain design level of a distributed software system from a requirements specification by decomposition and/or synthesis of software components. The method is hierarchical in the sense that a software component can be designed independently from the other software components once its external specifications are determined. It is also insensitive to the granularity of concurrency in a software component and to the granularity of distribution of both data and software components. The design representation in the form of a modified Petri net can be checked for its structural properties and be analyzed to verify its behavioral properties after it is transformed into a Petri net. The application of the method and the representation technique to the design of a small distributed software system is also shown.

1 citations