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.

An inductive method for discovering design patterns from object-oriented software systems

Abstract: Object-Oriented Design Patterns (OODPs) have been proposed as a technique to encapsulate design experience and aid in design reuse. However, so far, there is very little empirical evidence about what we can expect from this emergent technology. For instance, to date little research has focused on the development of techniques for discovering workable patterns that can be captured, formalized, packaged, and quantitatively evaluated. Our work is a step in this direction. In this paper we present an inductive method aimed at helping us discover OODPs in existing OO software systems. It encompasses a set of procedures rigorously defined in order to be repeatable and usable by practitioners who are not acquainted with reverse architecting processes. Guidelines are provided and a case study is shown that demonstrates the usefulness of the approach.

Content enhancement system and method and applications thereof

Abstract: A source content enhancement system is described. A method for disambiguation of content and localization of culturally sensitive content including parsing content of an object for cultural objects and components, gathering knowledge about the object, inferring knowledge about the object, checking if the object is culturally appropriate, checking if the object and section of an object conform to local standards, and creating an adapted rendering of the object.

Method and system for licensed design and use of software objects

Abstract: A componentizing object designer is used to define a componentization of visual forms and other object-oriented technologies. The componentized object designer includes a set of tightly integrated protocols enabling Component Object Model (COM) objects to replace standard built-in visual form and other objects. The componentized object designer allows the design-time object and the run-time object to differ in implementation. The componentized object designer allows class identifiers for the run-time objects which are different than design-time objects. With a different class identifier, the run-time object can be saved as an object which is radically different from the design-time object. This enables the run-time object to be stored in a different object library than the design-time object. The componentized object designer allows for different persistence formats to be saved for run-time objects. The persistence formats for the run-time objects can be significantly smaller in size compared to the original the design-time objects. This is important when the run-time object needs to be downloaded over a computer network like the Internet or an intranet. Licensing is aided by checking the object designer for licensing data, and embedding a licensing key into the run-time object.

Process-driven tool interface for an object management system

Abstract: A process-driven object management system for managing data and code modules is disclosed. The object management system includes a repository that stores objects, wherein ones of the objects referred to as “Asset elements” each describe a respective code or data module. The object management system includes a set of scripted tools for performing renovation, transformation, and code development tasks on the code and data modules. According to one aspect of the invention, the tool invocation constructs are stored as objects in the repository, such that some of the same object management tools and automated repository interface functions used to manage the Asset element can also be used to manage and veiw the tool objects.