scispace - formally typeset
Search or ask a question
Topic

Object-oriented design

About: Object-oriented design is a research topic. Over the lifetime, 5136 publications have been published within this topic receiving 144108 citations.


Papers
More filters
Journal ArticleDOI
TL;DR: A theory of the algorithm design process based on observations of human design is described and a framework for automatic design is outlined, which helps understand human design better and the implementation process helps validate the framework.
Abstract: Algorithm design is a challenging intellectual activity that provides a rich source of observation and a test domain for a theory of problem-solving behavior. This paper describes a theory of the algorithm design process based on observations of human design and also outlines a framework for automatic design. The adaptation of the theory of human design to a framework for automation in the DESIGNER system helps us understand human design better, and the implementation process helps validate the framework. Issues discussed in this paper include the problem spaces used for design, the loci of knowledge and problem-solving power, and the relationship to other methods of algorithm design and to automatic programming as a whole.

90 citations

Proceedings ArticleDOI
01 May 1990
TL;DR: This paper presents OdeView, the graphical front end for Ode, an object-oriented database system and environment, and discusses its design and implementation.
Abstract: OdeView is the graphical front end for Ode, an object-oriented database system and environment. Ode's data model supports data encapsulation, type inheritance, and complex objects. OdeView provides facilities for examining the database schema (i.e., the object type or class hierarchy), examining class definitions, browsing objects, following chains of references starting from an object, synchronized browsing, displaying selected portions of objects (projection), and retrieving objects with specific characteristics (selection).OdeView does not need to know about the internals of Ode objects. Consequently, the internals of specific classes are not hardwired into OdeView and new classes can be added to the Ode database without requiring any changes to or recompilation of OdeView. Just as OdeView does not know about the object internals, class functions (methods) for displaying objects are written without knowing about the specifics of the windowing software used by OdeView or the graphical user interface provided by it.In this paper, we present OdeView, and discuss its design and implementation.

89 citations

Patent
10 Nov 1997
Abstract: A computer controlled object oriented programming system for interfacing a plurality of programming objects with each other to provide combination objects combining programming functions of the objects, each object including predetermined interface data defining a required common interface with the other programming objects in a framework of events, attributes and methods for manipulating the attributes. These objects may be combined with each other via their common interfaces to form combination objects and such combination objects may in turn be further combined with other objects and combination objects to form objects of increasing complexity which function as complete programs. There is provided a displayable output of documentation for the programming objects in which the basic documentation provided for an object oriented program by its developers may be added to or modified without the need to change the framework of the objects in the program. To accomplish this, the invention involves the combination of two documentation functions: 1) the basic documentation program which translates source code data within the object framework, and 2) an implementation translating a portion of the object source code data which is outside of the object framework.

89 citations

Book
01 Sep 1996
TL;DR: This course names many of good things that i ve done in code some patterns that i didn t even know how they are named how to implement them fully and also bad practices and anti patterns that I fall into sometimes, introduction to design patterns.
Abstract: uml 2 0 a major upgrade the available version of the uml 2 0 superstructure specification that is the version that has finished its first maintenance release and been built into vendor products has been completed and is available to everyone for free download, uml 2 0 a major upgrade the available version of the uml 2 0 superstructure specification that is the version that has finished its first maintenance release and been built into vendor products has been completed and is available to everyone for free download, introduction to design patterns hello this is david starr and in this module we re going to discuss the idea of design patterns and specifically how pluralsight means to present design patterns to you in our pluralsight design pattern library, last updated 14 oct 2017 added a new lecture guidelines for building quality class diagrams currently the course contains the use case diagram use case description activity diagram class diagram object diagram package diagram sequence diagram and state transition diagram, unified modeling language uml class diagram learning uml in simple and easy steps a beginner s tutorial containing complete knowledge of uml architecture diagrams notations examples with examples, applied database administration and design part time studies learn how to design operate and administer pc based relational database systems beginning with a foundation of systems analysis and design and dbms database management systems students learn relational database theory design data modeling sql programming and industry standards to provide it solutions, in software and systems engineering a use case is a list of actions or event steps typically defining the interactions between a role known in the unified modeling language uml as an actor and a system to achieve a goal the actor can be a human or other external system in systems engineering use cases are used at a higher level than within software engineering often representing, this course names many of good things that i ve done in code some patterns that i didn t even know how they are named how to implement them fully and also bad practices and anti patterns that i fall into sometimes, introduction to design patterns hello this is david starr and in this module we re going to discuss the idea of design patterns and specifically how pluralsight means to present design patterns to you in our pluralsight design pattern library, welcome to cay horstmanns home page cay horstmann com pgp key i grew up in

89 citations

Dissertation
01 Jan 2001
TL;DR: The Arch model is a revision of the Seeheim model aimed at providing a framework for understanding of the engineering tradeoffs, specifically, in what concerns evaluating candidate run-time architectures.
Abstract: ion Presentation Control PAC Aplication Conceptual Interface (ACI) Instantiation of a User Interface System Functional core Output Input User User Functional core Figure II.23 Conceptual Architectural Models for User-interface Objects In the late 1980s and early 1990s several approaches of implementation architectural models for interactive systems emerged. Unlike conceptual models, implementation models organize the interactive system as a set of software components and aim at practical software engineering considerations like reusability, maintainability, and performance. The Seeheim model [Bass, 1992] proposes a simple three-layer model (application, dialogue and presentation) of an interactive system, roughly coupling the semantic, syntactic and lexical functionality’s of the user interface. The application component models the domain-specific components, the dialogue component defines the structure of the dialogue between the user and the application and, finally, the presentation component is responsible for the external to internal mapping of basic symbols. The Seeheim model is considered a correct and useful model for specification of interactive systems [Duce et al., 1991]. However, its support for distribution, concurrency, resource management and performance is recognized to be insufficient. Background: A Brief Survey of Usability Engineering and Object Modeling 58 The Arch model [Pfaff and Haguen, 1985] is a revision of the Seeheim model aimed at providing a framework for understanding of the engineering tradeoffs, specifically, in what concerns evaluating candidate run-time architectures. The Arch model proposes a five-layer approach balanced around the dialogue component. The components of the Arch model are: • The interaction toolkit component implements the physical interaction with the end-user; • The presentation component provides a set of toolkit independent objects; • The dialogue component is responsible for task-level sequencing, providing multiple view consistency, and mapping the between domain specific and user interface specific formalisms; • The domain adapter component implements domain related tasks required but not available in the domain specific component; • The domain specific component controls, manipulates and retrieves domain data and performs other domain related functions. Application Dialogue Presentation Seeheim Model

89 citations


Network Information
Related Topics (5)
Software development
73.8K papers, 1.4M citations
91% related
Software system
50.7K papers, 935K citations
89% related
Software construction
36.2K papers, 743.8K citations
89% related
Web service
57.6K papers, 989K citations
86% related
Software
130.5K papers, 2M citations
86% related
Performance
Metrics
No. of papers in the topic in previous years
YearPapers
20231
20226
20215
20209
201915
201828