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 published on a yearly basis
Papers
More filters
01 Jan 1998
TL;DR: ACTs offer a powerful technique for addressing certain types of modelling problems, if applied with care, and should be applied for modelling real-world or design entities.
Abstract: communication types offer a number of advantages: o Expressive power: ACTs increase the expressive power of the model, as they allow for tailoring the semantics of message passing. o Complexity: ACTs can make the complexity of programs manageable by moving the interaction code to separate modules. This allows for reducing the number of inter-module relations and hiding communication details. ACTs can be applied to construct layered systems. o Separating functionaland interaction-code: ACTs promote the migration of interaction code to separate modules, thereby improving maintainability and reusability. o Reusability: Different types of classes may have common patterns of communication and synchronisation. Such commonalities can be abstracted using ACTs. Programmers may apply object-oriented techniques, such as inheritance and delegation, to achieve a more systematic reuse of ACTs, and thus of interaction code. o Enforcing invariant behaviour: It is easier to enforce the invariant behaviour among objects if there is a module explicitly representing this behaviour. However, ACTs should be applied with care: ACTs are only appropriate as a modelling tool, and should thus only be applied for modelling real-world or design entities. Carelessly shifting interaction code from participating objects to ACTs may violate the important object-oriented principle that every object is self-sufficient and independent. This would result in bad design characteristics. Nevertheless, if applied with care, ACTs offer a powerful technique for addressing certain types of modelling problems [Aksit 92b]. 5 Further Language Aspects This section briefly describes a number of language aspects that have not been covered yet in the previous sections. This includes type-checking, scope rules, an overview of the pseudo-variables, and 31 This is to avoid that multiple replies are created for a single message invocation.
34 citations
TL;DR: The role of objects in integrating ergonomic knowledge in engineering design processes is explored and recommendations for working with objects in design processes are included.
34 citations
Patent•
23 Dec 2003TL;DR: In this article, a method, system and apparatus for locating a testable object in a functional testing tool is described, which can include a record process configured to produce both a test script and an object mapping, and a playback process configurable to process the test script.
Abstract: A method, system and apparatus for locating a testable object in a functional testing tool is provided. The system can include a record process configured to produce both a test script and an object mapping, and a playback process configured to process the test script. An object manager can be coupled to the playback process and configured to locate among candidate objects in a GUI, a candidate object having a set of properties which partially matches another set of properties associated with a corresponding test object in the object mapping.
34 citations
Patent•
IBM1
TL;DR: In this article, the authors present a method and system which provides a prototypical object which can be copied to create a derived object, which can contain attribute values or it can hold a reference to its prototype object.
Abstract: A method and system which provides a prototypical object which can be copied to create a derived object. A derived object can contain attribute values or it can hold a reference to its prototypical object. If a required value is not held by the prototypical object, the present invention discloses a scheme by which the object searches up an object hierarchy to find the required attribute. In addition, each object can register an interest in a prototypical object that contains required attributes. If an attribute of a prototypical object changes, the prototypical object informs all registered objects of the change. At runtime, the prototypical object becomes a master object whose attribute values can be changed by the user, changes in master object attributes are propagated to all registered derived objects.
34 citations
TL;DR: This paper argues for the adoption of object‐oriented design and UML tools for nonsoftware designs, i.e., systems, hardware and algorithms: This is a controversial position and presents a case study, the design of a heating, ventilation, and air conditioning system, using U ML tools.
Abstract: This paper argues for the adoption of object-oriented design and UML tools for nonsoftware designs, i.e., systems, hardware and algorithms: This is a controversial position. It presents a case study, the design of a heating, ventilation, and air conditioning system, using UML tools. This case study also shows the incremental elaboration used to progress from the requirements model, to the analysis model, to the design model, etc. The paper finally discusses some difficulties that must be overcome in order to apply UML tools to system designs. © 2002 Wiley Periodicals, Inc. Syst Eng 6: 28–48, 2003.
34 citations