Thesis (M. Phil.)--University of Hong Kong, 1994. / Includes bibliographical references (leaves 99-102).

Thesis (Ph. D.)--University of Washington, 1999. / Vita. Includes bibliographical references (leaves 90-92).

Thesis (M.S.)--Virginia Polytechnic Institute and State University, 1993. / Vita. Abstract. Includes bibliographical references (leaves 100-102). Also available via the Internet.

Thesis (M.S. in Operations Research) Naval Postgraduate School, June 1997. / Thesis advisor, Arnold Buss. Includes bibliographical references (p. 115). Also available online.

Thesis (Ph. D.)--University of Wisconsin--Madison, 1994. / Typescript. Includes bibliographical references (leaves 133-141).

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

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 thesis describes the design and implementation of an interprocess communication (IPC) mechanism within a real-time distributed operating system kernel (RT-DOS) which is designed for a transputer-based network. The requirements of real-time operating systems are examined and existing design and implementation strategies are described. Particular attention is paid to one of the object-oriented techniques although it is concluded that these techniques are not feasible for the chosen implementation platform. Studies of a number of existing operating systems are reported. The choices for various aspects of operating system design and their influence on the IPC mechanism to be used are elucidated. The actual design choices are related to the real-time requirements and the implementation that has been adopted is described.

The aggregation hierarchy is one of the most significant data abstraction mechanisms that emerged as a result to semantic extensions to traditional systems analysis and design methods. The way inheritance works in this hierarchy is studied in this thesis. Special emphasis is placed on the behaviour of objects which are related via an aggregation hierarchy. A framework is introduced for capturing the behaviour of a system from the respective behaviour(s) of its components. This framework is based on a 3-level behaviour modelling hierarchy. One of the most significant contributions of this framework is the ability to apply inter-object interactions when building a behaviour model of a system. These interactions are significant in that they can yield totally distinct models of the systems functionality. Some of the notions that are supported by the behaviour modelling framework include unreachable and transient states, transition chains (cascades) and concurrency. The framework also enables the creation of behaviour model (semantic) hierarchies, wherein certain facets of the systems behaviour or functionality can be hidden (abstracted out) in a gradual fashion that suits the requirements of the problem domain. This creates what is effectively, distinct views of the behaviour or functionality of the system. The notions and concepts that are introduced here are verified and presented in a comprehensive case study that shows what can be achieved using these ideas. Suggestions are also made for future work which can help overcome some of the limitations introduced throughout this research.

Object-Oriented frameworks, OO frameworks, have been discussed over a long period of time, that when introducing Object-Oriented frameworks, the defect-density will decrease and the quality of software will increase. Capgemini had developed a framework that had been in the organization for nine years. Since then, the framework has been reengineered several times to meet the continuously changing requirements of the software systems the framework supports. My work was to develop a new framework to make the maintainability and evolution of the framework easier while not compromising the quality of the framework or the applications built on it. The new framework that I developed was called the Capgemini Development Framework, CDF. Results from the case study, conducted to test the differences between these two frameworks, showed that the CDF framework preserved the maintainability of the applications built on the framework. The architecture of the CDF framework made it also easier to handle any future updates to the core functionality of the framework.