Thesis (M.S.C.I.T.)--Regis University, Denver, Colo., 2006. / Title from PDF title page (viewed on Aug. 30, 2006). Includes bibliographical references.

The design of correct software remains difficult, especially when dealing with concurrency. The primary goal of the research presented here is to devise a pragmatic software development method which  aids the software designer in producing reliable software,  is scalable,  is understandable,  follows a unified approach towards software development (is applicable to different implementation architectures),  promotes reuse,  has seamless transitions between the software development phases,  guarantees general availability and minimises developmental resources. The two main characteristics of the proposed new development method are captured in its name, viz. Single Location Object-Oriented Programming (SLOOP) . It is an object-oriented method, but its computational model is that of a set of statements that execute infinitely often and in any order. A program with such a computational model is called a Single Location Program (SLP). A UNITY program can also be classified as a Single Location Program. In the UNITY theory of programming it was demonstrated how this computational model could simplify correctness reasoning, particularly for concurrent systems. It is this simplification, together with the structuring and reuse features of object-orientation, that is leveraged in the SLOOP method to produce a mechanism whereby ordinary software practitioners can take advantage of the benefits of a more rigorous approach towards software development without requiring an in-depth understanding of the underlying mathematics. The following features of the SLOOP method contribute towards achieving the above goals:  its computational model (it simplifies correctness reasoning, thereby promoting understandability and scalability, and also facilitates designs that are independent of the target implementation architectures),  its object-oriented nature (apart from promoting reuse of frameworks, design patterns and classes, the SLOOP method provides the necessary mechanisms to facilitate reuse of correctness properties, correctness arguments as well as mappings to implementation architectures),  its emphasis on correctness reasoning throughout the software development life cycle (its "constructive approach" aids reliability and seamlessness),  the unique way in which the correctness properties can be specified, reused and reasoned about (this contributes towards understandability and scalability),  the checklist of useful correctness properties that is provided (this promotes reliability),  the incorporation of existing notations into the SLOOP syntax (this guarantees general availability, minimises developmental resources and aids understandability). The main contribution of this thesis is that it presents a unique way of incorporating the SLP computational model into an object-oriented method with the specific aim of simplifying informal correctness reasoning and promoting reuse. The notation used for the specification of correctness properties facilitates reuse of correctness properties, ensures the integrity of these specifications and allows one to specify correctness properties at a higher level of abstraction. The SLOOP method offers a unique way of modelling concurrency in object-oriented systems (via its parallel methods), which takes full advantage of the encapsulation and inheritance features of object-orientation. The issues surrounding mappings to implementation architectures are addressed, showing how even mappings can be reused. Finally, the general applicability of the SLOOP method is demonstrated. / Thesis (PhD (Computer Science))--University of Pretoria, 2007. / Computer Science / unrestricted

D.Phil. (Computer Science) / Please refer to full text to view abstract

This research is concerned with inheritance as used in object-oriented database. More specifically, partial bi-directional inheritance among classes is examined. In partial inheritance, a class can inherit a proper subset of instance variables from another class. Two subclasses of the same superclass do not need to inherit the same proper subset of instance variables from their superclass. Bi-directional partial inheritance allows a class to inherit instance variables from its subclass. The prototype of an object-oriented database that supports both full and partial bi-directional inheritance among classes was developed on top of an existing relational database management system. The prototype was tested with two database applications. One database application needs full and partial inheritance. The second database application required bi-directional inheritance. The result of this testing suggests both advantages and disadvantages of partial bi-directional inheritance. Future areas of research are also suggested.

Thesis (Ph. D.)--University of Texas at Austin, 2008. / Vita. Includes bibliographical references.

Most common object models of distributed object systems have a limited set of object-oriented features, lacking the advanced features of `polymorphism' (an abstraction mechanism that represents a quality or state of being able to assume different forms) and `concurrency' (the ability to have more than one thread of execution in an object simultaneously). The lack of support for advanced features is a serious limitation because it restricts the development of new components and limits reuse of existing of components that use these advanced features. As a result, wrappers must be used that hide the advanced features or components must be re-implemented using only the features of the common object model. In this dissertation, a new direction of research centered on a subset of object-oriented languages, specifically statically typed languages, is considered. One of the major drawbacks of existing distributed object systems is that they cater to a broad domain of programming languages including both object-oriented as well as non object-oriented languages. Mapping an object model into a non object-oriented language is a complex task and it does not appear natural to a native language user. The interoperable common object model (ICOM) proposed in this dissertation is an attempt to elevate common object models (with the advanced features of polymorphism and concurrency) closer to the object models of statically typed object-oriented languages. Specific features of the ICOM object model include: remote inheritance, method overloading, parameterized types, and guard methods. The actor model and reflection techniques are used to develop a uniform implementation framework for the ICOM object model in C++ and Modula-3. Prototype applications were implemented to demonstrate the utility of the advanced features of the ICOM object model. The main contributions of this dissertation are: design and implementation of a powerful common object model, an architecture for distributed compilation, and an implementation of a distributed object model using the actor model. / Ph. D.

A dissertation submitted to the Faculty of Engineering, University of the Witwatersand Johannesburg, in fulfillment of the requirements of the degree of Master of Science in Engineering. Johannesburg April 16, 1990 / Automation is currently being used to an ever increasing degree in industrial plants. However most of these applications require only a few basic control concepts repeated for each piece of equipment. There is often a fair amount of interaction between pieces of equipment in terms of safety interlocking and sequencing. Despite this each piece of software remains an autonomous entity receiving the necessary external data it requires. The principles of OBJECT ORIENTED DESIGN are suited to the development of this type of software. This dissertation will demonstrate that object oriented development has distinct benefits over more classical design techniques. Generalized software for controlling a minerals processing plant will be conceptually designed, using techniques implemented in C++ to demonstrate the basic hypothesis. This will attempt to encompass all the available design techniques of object oriented design into an area that has traditionally developed its own software development paradigm.

No abstract provided.

by Wong, Shing-hung Lewis. / Thesis (M.Phil.)--Chinese University of Hong Kong, 1993. / Includes bibliographical references. / Acknowledgements / Abstract / Chapter Chapter 1 --- Introduction --- p.1-1 / Chapter 1.1 --- Background --- p.1-1 / Chapter 1.1.1 --- Technology Advancement --- p.1-1 / Chapter 1.1.2 --- Lack of Multiprocessor Standards --- p.1-1 / Chapter 1.1.3 --- Demand for Greater Processing Power --- p.1-3 / Chapter 1.1.4 --- Parallel Computing --- p.1-3 / Chapter 1.1.5 --- Research Support --- p.1-4 / Chapter 1.2 --- Related works --- p.1-4 / Chapter 1.3 --- "Expectations : OS dependent, but hardware independent" --- p.1-8 / Chapter 1.4 --- Summary --- p.1-8 / Chapter Chapter 2 --- Overall Design --- p.2-1 / Chapter 2.1 --- An Overview --- p.2-1 / Chapter 2.2 --- Common models --- p.2-3 / Chapter 2.2.1 --- The Master-Slave model --- p.2-3 / Chapter 2.2.2 --- Floating Executives Using Giant Locks --- p.2-4 / Chapter 2.2.3 --- Multithreaded Kernels (or Homogeneous Model) --- p.2-6 / Chapter 2.3 --- My model --- p.2-7 / Chapter 2.3.1 --- Multitaskers and my Object Scheduler --- p.2-8 / Chapter 2.3.2 --- Lower Layer: Object Scheduler & Message-box Handler --- p.2-10 / Chapter 2.3.3 --- "Upper Layer: ""C++*"" Language" --- p.2-12 / Chapter 2.4 --- Summary --- p.2-15 / Chapter Chapter 3 --- Design & Implementation Details --- p.3-1 / Chapter 3.1 --- Design Considerations --- p.3-1 / Chapter 3.1.1 --- Possible Scheduling Policies --- p.3-1 / Chapter 3.1.2 --- Interface to UNIX® OS --- p.3-5 / Chapter 3.2 --- Design and Implementation Details --- p.3-9 / Chapter 3.2.1 --- Lower Layer: Object Scheduler & Message-box Handler --- p.3-10 / Chapter 3.2.2 --- "Upper Layer: ""C++*""Language" --- p.3-17 / Chapter 3.3 --- Summary --- p.3-23 / Chapter Chapter 4 --- Simulation Results --- p.4-1 / Chapter 4.1 --- Execution of an application --- p.4-1 / Chapter 4.2 --- Design Simulation --- p.4-2 / Chapter 4.2.1 --- Simulation Experiment Design --- p.4-3 / Chapter 4.2.2 --- Simulation Results --- p.4-4 / Chapter 4.2.3 --- Discussion --- p.4-6 / Chapter 4.3 --- Summary --- p.4-7 / Chapter Chapter 5 --- Sample Applications --- p.5-1 / Chapter 5.1 --- A Distributed Object-Oriented Visualization Package --- p.5-1 / Chapter 5.1.1 --- Design Objectives --- p.5-1 / Chapter 5.1.2 --- Design Methodology --- p.5-2 / Chapter 5.1.3 --- Class Hierarchy Relation --- p.5-2 / Chapter 5.1.4 --- Object Hierarchy (Contain) Relation --- p.5-4 / Chapter 5.1.5 --- Class Specifications --- p.5-5 / Chapter 5.1.6 --- Parallel Algorithms --- p.5-7 / Chapter 5.1.7 --- Speed Up of Distributed Approach --- p.5-17 / Chapter 5.1.8 --- Grain Size Considerations --- p.5-19 / Chapter 5.1.9 --- Performance Evaluation --- p.5-19 / Chapter 5.2 --- Fractal Evaluation --- p.5-28 / Chapter 5.2.1 --- Unit Machine --- p.5-29 / Chapter 5.2.2 --- Speed Up --- p.5-29 / Chapter 5.2.3 --- Grain Size Considerations --- p.5-33 / Chapter 5.5 --- Summary --- p.5-35 / Chapter Chapter 6 --- Conclusion --- p.6-1 / Reference --- p.R-1 / "Appendix 1 User guide of ""C++*""" --- p.A-1 / Chapter 1 --- System Requirements --- p.A-1 / Chapter 2) --- Installation --- p.A-1 / Chapter 3) --- Usage --- p.A-1 / Chapter 4) --- Programming Interfaces --- p.A-2 / Chapter 5) --- Limitation --- p.A-2 / "Appendix 2 Coding of class "" Parallel""" --- p.A-4 / "Appendix 3 A Simple Sample Application of "" C++*""" --- p.A-17

by Lam Siu Hong. / Thesis (M.Phil.)--Chinese University of Hong Kong, 1991. / Includes bibliographical references. / Chapter Chapter1 --- Introduction --- p.1 / Chapter 1.1 --- Software Development Crisis of User Interface --- p.1 / Chapter 1.2 --- Objectives and Scope of Interests --- p.1 / Chapter 1.3 --- Overview of the Thesis --- p.2 / Chapter Chapter2 --- Background and Problems --- p.4 / Chapter 2.1 --- Categories of User Interfaces --- p.4 / Chapter 2.2 --- Trends of User Interfaces --- p.6 / Chapter 2.3 --- Some other Desirable Features and Problems of UI Development --- p.7 / Chapter 2.3.1 --- Separating UI from Application --- p.7 / Chapter 2.3.1.1 --- Benefits of Separable UIs and Applications --- p.7 / Chapter 2.3.1.2 --- Requirements of Complete Separation --- p.10 / Chapter 2.3.2 --- Instant Continuous Feedback --- p.12 / Chapter 2.3.2.1 --- Problems of Linguistic Model on World Model Type UIs --- p.12 / Chapter 2.3.3 --- Undo and Recovery --- p.15 / Chapter 2.3.4 --- Iterative Design through Rapid Protyping --- p.16 / Chapter Chapter3 --- An Object-Oriented Model for Model World User Interfaces Development --- p.18 / Chapter 3.1 --- Features of UIs to be supported by the Model --- p.18 / Chapter 3.2 --- A Linkage Model for Separating UI from Application --- p.19 / Chapter 3.2.1 --- Communication Messages Modeled using an Object Oriented Approach --- p.20 / Chapter 3.2.2 --- A Sample Message --- p.22 / Chapter 3.2.3 --- Linkage in a Distributed Heterogenous Environment --- p.24 / Chapter 3.2.4 --- Comparing the Linkage Model with the Application Interface Model in Seeheim's UI Model --- p.25 / Chapter 3.3 --- An Object-Oriented Model for Supporting Multiple Feedbacks and Multi-thread dialogue --- p.26 / Chapter 3.3.1 --- An Overview of the Model --- p.27 / Chapter 3.3.2 --- Objects on the Lexical Layer --- p.28 / Chapter 3.3.3 --- Roles of Presentation Objects --- p.29 / Chapter 3.3.4 --- Syntactic Objects --- p.31 / Chapter 3.3.5 --- Interaction Objects --- p.32 / Chapter 3.3.6 --- Interaction between objetcs and Linkage Component --- p.33 / Chapter 3.3.7 --- Multiple U-tubes Ladder for Supporting Multiple Feedbacks --- p.33 / Chapter 3.3.8 --- Recovery through a Generic UNDO stack --- p.35 / Chapter 3.3.9 --- Dialogue Control in an Object --- p.37 / Chapter 3.3.10 --- Interactive Objects --- p.39 / Chapter 3.3.11 --- An Architecture for Supporting Multi-thread Dialogue --- p.40 / Chapter 3.4 --- Basic Object Structure --- p.42 / Chapter 3.4.1 --- An Event Model for Dialogue Control --- p.43 / Chapter 3.4.2 --- Maintain Consistency through ε-rules --- p.45 / Chapter 3.4.3 --- An Example of an Inner Object Specification --- p.47 / Chapter 3.4.4 --- Pre and Post Condition of Action --- p.49 / Chapter 3.4.5 --- Automatic Message Routing --- p.49 / Chapter 3.5 --- Systematic Approach to UI Specification --- p.50 / Chapter Chapter4 --- User Interface Framework Design --- p.52 / Chapter 4.1 --- A Framework for UI Development --- p.52 / Chapter 4.1.1 --- Abstract Base Class for Each Object Type --- p.54 / Chapter 4.1.2 --- A Kernel for Message Routing --- p.60 / Chapter 4.1.3 --- Interaction Knowledge Base --- p.63 / Chapter 4.1.4 --- A Dynamic View of UI Objects --- p.64 / Chapter 4.1.5 --- Switch Box Mechanism for Dialogue Switching --- p.66 / Chapter 4.1.6 --- Software IC Construction --- p.68 / Chapter 4.2 --- Summaries of Object-Object UI Model and UI Framework --- p.70 / Chapter 4.2.1 --- A New Approach to User Interface Development 、 --- p.70 / Chapter 4.2.2 --- Feautures of UI Development provided by the Object-Object UI Model and UI Framework --- p.71 / Chapter Chapter5 --- Implementation --- p.73 / Chapter 5.1 --- Implementation of Framework in Microsoft Window Environment --- p.73 / Chapter 5.1.1 --- Implementation of automatic message routing through dynamic binding --- p.73 / Chapter 5.1.2 --- A generic message structure --- p.75 / Chapter 5.1.3 --- A meta class for object communication --- p.76 / Chapter 5.1.4 --- Software component of UI framework in Microsoft Window environment --- p.76 / Chapter 5.2 --- A Simple Stock Market Decision Support System (SSMDSS) --- p.77 / Chapter 5.2.1 --- UI Specification --- p.81 / Chapter 5.2.2 --- UI features supported by SSMDSS --- p.87 / Chapter Chapter6 --- Results --- p.89 / Chapter 6.1 --- Facts discovered --- p.89 / Chapter 6.1.1 --- Asynchronous and synchronous communication among objects --- p.89 / Chapter 6.1.2 --- Flexibility of the C+ + language --- p.90 / Chapter 6.2 --- Technical Problems Encountered --- p.91 / Chapter 6.2.1 --- Problems from Implementation Platform --- p.91 / Chapter 6.2.2 --- Problems due to Object Decomposition in an Interactive Object in SSMDSS --- p.92 / Chapter 6.3 --- Objectives accomplished by the Object-Oriented UI Model indicated by SSMDSS --- p.93 / Chapter Chapter7 --- Conclusion --- p.95 / Chapter 7.1 --- Thesis Summary --- p.95 / Chapter 7.2 --- Merits and Demerit of the Object-Oriented UI Model --- p.96 / Chapter 7.3 --- Cost of the Object-Oriented UI Model --- p.96 / Chapter 7.4 --- Future work --- p.97 / Appendix / Chapter A1 --- An Alogrithm for Converting Transition Network Diagram to Event Response Language --- p.A1 / Chapter A2 --- An Object-Oriented Software Development --- p.A4 / Chapter A2.1 --- Traditional Non Object-Oriented Software Development --- p.A4 / Chapter A2.2 --- An Object-Oriented Software Development --- p.A6 / Chapter A3 --- Vienna Development Method (VDM) --- p.A8 / Chapter A3.1 --- An Overview of VDM --- p.A8 / Chapter A3.2 --- Apply VDM to Object-Oriented UI model --- p.A10 / Chapter A4 --- Glossaries and Terms --- p.A12 / Reference