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.

System for adding attributes to an object at run time in an object oriented computer environment

Abstract: The system uses an intermediary process in an object oriented computer environment to allow application objects to perform operations such as creation, deletion and accessing of other objects. Typically the other objects are database objects. The intermediary process allows associations to be made between add-on attributes and primary objects. The primary objects are objects that are designed to be used by an original application. A later application that wishes to use the same objects as the original application, but with additional attributes, can create, delete and access the additional attributes at run time so that extra functionality is provided to a user of the original application program in an efficient manner.

Codesign from cospecification

Abstract: Describes an object-oriented codesign specification approach designed to eliminate the bias introduced from using more commonplace software or hardware specification languages. The goal is to investigate automated partitioning of behavior into hardware and software. The design methodology allows gradual, continuous repartitioning of codesign operations during design. For instance, designers might start with an all-software implementation and check the implementation's functionality: they might then refine the implementation over time to a mixed hardware-software implementation. At the system level, the authors use an object-oriented approach to identify the basic objects and associated functions of a system. They divide them into three groups: hardware, software, and codesign . They represent the codesign group's objects and functions using a prototype codesign specification language, Object-Oriented Functional Specifications (OOFS), which lets one describe system state in objects and write object methods as pure functions. Thus, the authors can describe complex systems without biasing the implementation toward hardware or software. >

An Investigation into the Applicability and Validity ofObject-Oriented Design Metrics

Abstract: In this paper we consider empirical evidence in support of a set of object-oriented software metrics. In particular, we look at the object oriented design metrics of Chidamber and Kemerer, and their applicability in different application domains. We briefly describe the metrics, and present our empirical findings, arising from our analysis of systems taken from a number of different application domains. Our investigations have led us to conclude that a subset of the metrics can be of great value to software developers, maintainers and project managers.

On formal specification of design tasks

Abstract: In the development of a design system, a formal specification can play an important role providing a precise description of both the static and the dynamic aspects of the system. Static aspects not only include domain knowledge about properties of design objects and relations between these properties, but also domain knowledge about requirements of design objects and relations between these requirements. Dynamic aspects include strategic knowledge about steps undertaken in the design process. In this paper, a logical framework for design tasks is presented which incorporates the notion of a meta-level architecture to explicitly represent declarative knowledge on the dynamics of reasoning processes. Based on this logical framework a generic task model of design is presented, describing the essential structure of the design task, in which the dynamic modification of design object descriptions and requirements is explicitly defined.

Generic software state machine

Abstract: A generic software state machine (10) for implementing a software application in an object oriented environment includes a set of entity objects (20, 30) defined for software elements of the software application, a set of state objects (26, 34, 38, 40) defined for each entity object representative of states that the software element may enter, and a set of event objects (36, 42) defined for each state object representative of inputs that the software element may receive or actions the software element may encounter while in the state represented by the state object.