introduction - object-oriented design  object-oriented, a buzzword of the late 1980s, has evolved into an accepted technology that has recognized benefits for the software development process. in its progression from a purely procedural approach, software development reached a data-driven--- object-based---approach, and has grown beyond that to the object-oriented approach.  the impact of the object-oriented approach is not limited to the design portion of the software development life cycle---its effects are evident at every phase. one of the strengths of the object model is that it provides a unifying element that is common to every phase of the life cycle. this uniformity provides a smooth transition from one phase to the next.  the article by henderson-sellers and edwards presents a revision of the traditional life cycle based on the object-oriented approach. it discusses the unique view of the design process and describes how it works: the process takes a specified problem and decomposes it. the resulting product forms the framework for a computer-based solution to the problem. object-oriented techniques begin this decomposition process in the analysis phase and carry it on into the design phase. a modeling paradigm is used for the decomposition process: the top layer of an object-oriented system is a model of the real- life situation for which the software system is being created. the underlying layers provide the implementation of this model.  the "pieces" produced by object- oriented techniques are as unique as the design perspective. its obvious similarities to and subtle differences from abstract data type (adt) technology have led to much discussion of objects and classes in terms of adts. the unique coupling of data and behavior in the object-oriented components provides much more than a syntactic distinction from the usual adt. added to the modeling approach, it produces a recognizably different approach to systems development.  the term object-oriented is defined differently by different people. many professionals agree with the basics of wegner's definition1 that object- oriented includes three concepts: objects, classes, and class inheritance. some would add a variety of other requirements including such concepts as polymorphism, dynamic binding, encapsulation, etc. the article by korson and mcgregor provides an overview of these concepts, leaving room for the reader to decide which to include and which to exclude; it also provides an overview of the basic concepts of object-oriented design.  the production of software in an increasingly competitive environment is making reuse a priority of software professionals. the popularity of the object-oriented technique is due, in part, to its support for reuse. two important factors influence reuse: first, it is necessary to have a set of high-quality components that are worth reusing. second, the components must be well-defined, easy to integrate, and efficient. meyer's article presents some experiences in developing the classes for the eiffel library; it also discusses characteristics of the library. for components to be reused, the designer must have the means to locate a component which models an entity in the current problem. not only must the component be located, but often necessary supporting pieces must be found as well. the article by gibbs et al. provides information on the management of classes and the software components of the object-oriented paradigm.  tom demarco, in a recent interview,2 declared parallel computing to be the emerging new paradigm. according to demarco object-oriented techniques will be an integral partner in this emergence. demarco observed that designing with objects preserves the natural parallelism in a problem. agha addresses models for parallel objects, presenting an overview of the problem and focusing on the actor model as a possible solution. he presents examples of design issues when using the actor model. he also considers a basic reflective design architecture.  the importance of well-defined and well-managed abstractions in the software development process is discussed in the articles by meyer and by gibbs et al as they explore what has come to be called the software base, the set of software components from which future products will be built.  the unique components developed by object-oriented methods are characterized by an interface that is separate from the implementation of that behavior. the designer is free to concentrate on modeling the problem at hand either by developing specific classes or by locating and reusing existing classes that model some subset of the needed behavior. meyer focuses on what he quotes mcilroy as terming a "software components subindustry,"3 presenting a case study of the development of the eiffel libraries.  the final article in this special issue, by henderson-sellers and edwards discusses modifications to the traditional life cycle supported by the object- oriented approach. the modified life cycle recognizes the iterative nature of the development process and incorporates that characteristic into its model.  wirfs-brock and johnson present a sampling of current research into several aspects of object-oriented design. their survey includes efforts to improve reusability through design technique and paradigm-specific tools. the works are representative of the broad spectrum of research activity currently under way.  we would like to thank the authors in this special issue for their hours of work both in developing their own articles and for the time spent evaluating and commenting upon the other articles.  john d. mcgregor tim korson