Downloads & Free Reading Options - Results

For many applications, traditional data base models and technologies have proven inadequate, and this has led to research and development of database technologies based on the object-oriented paradigm. In this report, some of the recent research and development in object-oriented databases are surveyed. The core concepts that are being considered in developing a unified object-oriented data model are discussed, followed by some of the architectural issues involved in developing object-oriented database management systems. Technical summaries of two prototype object-oriented database products, GEMSTONE AND ORION, are given. Also, some of the exciting future research directions are highlighted. (kr)

For many applications, traditional data base models and technologies have proven inadequate, and this has led to research and development of database technologies based on the object-oriented paradigm. In this report, some of the recent research and development in object-oriented databases are surveyed. The core concepts that are being considered in developing a unified object-oriented data model are discussed, followed by some of the architectural issues involved in developing object-oriented database management systems. Technical summaries of two prototype object-oriented database products, GEMSTONE AND ORION, are given. Also, some of the exciting future research directions are highlighted. (kr)

ix, 249 p. :

ix, 249 p. :

ix, 249 p. :

This document describes a suggested approach for an organization considering transitioning object- oriented techniques into its software development process. The process of introducing and transitioning object-oriented technology (OOT) is described in detail, and is based upon the experiences of other OOT adopters. The primary audience for this document is software development managers and developers within the DoD Central Design Activities (CDAs), in particular those CDAs responsible for in-house information system development and maintenance. Using a pilot project as the primary mechanism for introducing OOT into the organization, the OOT transition process consists of four steps with associated activities: Perform Planning (develop a detailed understanding of the resources, activities, and commitment that will be required to conduct an OOT pilot project), Conduct Training (establish a well-understood competency in OOT by all participants in the pilot project), Conduct Pilot Projects (use OOT on one or more small, non-critical pilot projects), and Transition OOT to the Organization (establish an OOT capability within the organization).

This document presents the findings and recommendations for managing the implementation of object-oriented technology (OOT) in the DoD within specific information technology areas. This document explores some of the technology transition issues related to OOT implementation and identifies alternative strategies for such a transition within the DoD. The approach to this task was to consider the implementation of OOT with regard to current and planned DoD policy, current and anticipated DoD needs as expressed by DoD representatives, and the general state of maturity of OOT theory and practice. A key premise of this effort is that OOT has matured to the state whereby it may be considered for use within the DoD information technology areas. OOT appears to offer significant advantages over process and datadriven software development approaches, such as increased maintainability and reusability. OOT also facilitates distributed computing. However, there still exists a diversity of concepts and notations for development methodologies and a variety of mechanisms for object oriented database technology. There appear to be relatively few, if any, impediments within DoD information system lifecycle management and software development standards to using OOT.

This document presents the findings and recommendations for managing the implementation of object-oriented technology (OOT) in the DoD within specific information technology areas. This document explores some of the technology transition issues related to OOT implementation and identifies alternative strategies for such a transition within the DoD. The approach to this task was to consider the implementation of OOT with regard to current and planned DoD policy, current and anticipated DoD needs as expressed by DoD representatives, and the general state of maturity of OOT theory and practice. A key premise of this effort is that OOT has matured to the state whereby it may be considered for use within the DoD information technology areas. OOT appears to offer significant advantages over process and datadriven software development approaches, such as increased maintainability and reusability. OOT also facilitates distributed computing. However, there still exists a diversity of concepts and notations for development methodologies and a variety of mechanisms for object oriented database technology. There appear to be relatively few, if any, impediments within DoD information system lifecycle management and software development standards to using OOT.

This document presents the findings and recommendations for managing the implementation of object-oriented technology (OOT) in the DoD within specific information technology areas. This document explores some of the technology transition issues related to OOT implementation and identifies alternative strategies for such a transition within the DoD. The approach to this task was to consider the implementation of OOT with regard to current and planned DoD policy, current and anticipated DoD needs as expressed by DoD representatives, and the general state of maturity of OOT theory and practice. A key premise of this effort is that OOT has matured to the state whereby it may be considered for use within the DoD information technology areas. OOT appears to offer significant advantages over process and datadriven software development approaches, such as increased maintainability and reusability. OOT also facilitates distributed computing. However, there still exists a diversity of concepts and notations for development methodologies and a variety of mechanisms for object oriented database technology. There appear to be relatively few, if any, impediments within DoD information system lifecycle management and software development standards to using OOT.

This thesis describes the design and implementation of a multiple domain capability for a domain-oriented application composition system, named Architect. The research goal was to show how object-oriented database management system (OODBMS) technology can be used to provide simultaneous access to multiple domain-oriented knowledge bases. Since the Architect system was originally designed using the object-oriented paradigm, insertion of OODBMS technology was relatively simple and many of the object-oriented concepts, such as inheritance and aggregation, proved beneficial. Inheritance was used to encapsulate domain knowledge by defining each domain as a subclass of Architect's software architecture. Aggregation was used to allow applications to cross domain boundaries by nesting components from multiple domains in an application. To validate this approach, domain extensions to two existing domain models were implemented to make the domains compatible in a multiple domain environment, and applications containing objects from both the logic circuits and digital signal processing domains were successfully developed. One of the primary benefits of this research is the potential for greater reuse of objects. To satisfy new requirements, domain engineers can now search for and access objects from other domains as an alternative to implementing them in their own domains.

The results of object-oriented software development projects in the DoD have been disappointing relative to the promise that OO technology seems to hold. STARS Task IAO9 was commissioned to explore the feasibility of combining object-oriented methods (well known for their focus on reusability) with Cleanroom software engineering (well known for its emphasis on reliability) to define a software process capable of producing results that are not only reusable, but predictable and of high quality. A generic software process was defined in terms of phases, activities, and work products. Three OO processes (Booch, Objectory, Shlaer-Mellor) and the Cleanroom process were outlined by phases, activities, and work products as well, using a documentation baseline given by the methodologists. The three OO methods and Cleanroom were compared to the generic process for thoroughness and coverage, and an integrated process was defined.

The results of object-oriented software development projects in the DoD have been disappointing relative to the promise that OO technology seems to hold. STARS Task IAO9 was commissioned to explore the feasibility of combining object-oriented methods (well known for their focus on reusability) with Cleanroom software engineering (well known for its emphasis on reliability) to define a software process capable of producing results that are not only reusable, but predictable and of high quality. A generic software process was defined in terms of phases, activities, and work products. Three OO processes (Booch, Objectory, Shlaer-Mellor) and the Cleanroom process were outlined by phases, activities, and work products as well, using a documentation baseline given by the methodologists. The three OO methods and Cleanroom were compared to the generic process for thoroughness and coverage, and an integrated process was defined.

Object-Oriented Technology. ECOOP 2003 Workshop Reader: ECOOP 2003 Workshops, Darmstadt, Germany, July 21-25, 2003. Final Reports Author: Frank Buschmann, Alejandro P. Buchmann, Mariano A. Cilia Published by Springer Berlin Heidelberg ISBN: 978-3-540-22405-1 DOI: 10.1007/b98806 Table of Contents: Exception Handling in Object Oriented Systems: Towards Emerging Application Areas and New Programming Paradigms Parallel Object-Oriented Scientific Computing Today Communication Abstractions for Distributed Systems .NET: The Programmer’s Perspective Component-Oriented Programming Workshop for PhD Students in Object Oriented Programming Formal Techniques for Java-Like Programs Object-Oriented Reengineering Mobile Object Systems: Resource-Aware Computation Quantitative Approaches in Object-Oriented Software Engineering Composition Languages Tools and Environments for Learning Object-Oriented Concepts Patterns in Teaching Software Development Object-Oriented Language Engineering for the Post-Java Era Analysis of Aspect-Oriented Software Modeling Variability for Object-Oriented Product Lines Object Orientation and Web Services Advancing the State of the Art in Run-Time Inspection Aliasing, Confinement, and Ownership in Object-Oriented Programming

Thesis advisor, C. Thomas Wu

Includes index

Argos is a prototype multimedia database developed as both a Battle Group Commander's assesment tool and a shipboard data management tool. The current prototype developed by using HyperCard/Macintosh demonstrates an effective utilization of off-the-shelf technology to solve real world problems commonly faced by the United States Navy. The ultimate goal of Argos is to provide database support for the \"Paperless Ship\".

This document presents the findings and recommendations of an initial study regarding the potential implementation of object-oriented technology (OOT) in the DoD within specific information technology areas This document also explores some of the technology transition issues related to OOT implementation and identifies strategy options for such a transition within the DoD. The approach to this task was to consider the implementation of OOT with regard to current and planned DoD policy, current and anticipated DoD needs as expressed by DoD representatives, and the general state of maturity of OOT theory and practice. A key premise of this effort is that OOT has matured to the state whereby it may be considered for use within the Dot information technology areas. OOT appears to offer significant advantages over process and data-driver software development approaches, such as increased maintainability and reusability, and OOT can also facilitate distributed computing. However, there still exists a diversity of concepts and notations for development methodologies and a variety of mechanisms for object-oriented database technology. There appear to be relatively few, if any, impediments within DoD information system lifecycle management and software development standards to using OOT. (KAR) P. 3

The purpose of this project was to define requirements for, design, and prototype a computer-based support system for R&D program managers (PMs). We call this support system the Program Manager's Associate (PMA). We specify the initial PMA for ARPA with the longer range aim of commercializing PMA for PMs in various government, business, and academic settings. This project builds upon our work on computer-based "associates," particularly in the design domain, resulting in commercial software for strategic planning and technological design. This base is enriched by Georgia Tech's "technology opportunities analysis" software that draws upon electronic information searching to profile and forecast R&D activities and trends. The current project explored the nature of the ARPA PM's job to specify system functionality. This led to the identification of five main functions for the ARPA PMA: We then developed a prototype PMA using PowerBuilder. The prototype is a Windows application that interacts with conventional office applications, and demonstrates how the PM's five functions would be supported. The PMA would also facilitate cross-program coordination by providing access to ARPA program information in structured, consistent ways. In addition, it provides a vehicle to help prepare new PMs to work in the ARPA environment.

The purpose of this project was to define requirements for, design, and prototype a computer-based support system for R&D program managers (PMs). We call this support system the Program Manager's Associate (PMA). We specify the initial PMA for ARPA with the longer range aim of commercializing PMA for PMs in various government, business, and academic settings. This project builds upon our work on computer-based "associates," particularly in the design domain, resulting in commercial software for strategic planning and technological design. This base is enriched by Georgia Tech's "technology opportunities analysis" software that draws upon electronic information searching to profile and forecast R&D activities and trends. The current project explored the nature of the ARPA PM's job to specify system functionality. This led to the identification of five main functions for the ARPA PMA: We then developed a prototype PMA using PowerBuilder. The prototype is a Windows application that interacts with conventional office applications, and demonstrates how the PM's five functions would be supported. The PMA would also facilitate cross-program coordination by providing access to ARPA program information in structured, consistent ways. In addition, it provides a vehicle to help prepare new PMs to work in the ARPA environment.

Argos is a prototype multimedia database developed as both a Battle Group Commander's assessment tool and a shipboard data management tool. The current prototype developed by using HyperCard/Macintosh demonstrates an effective utilization of off-the-shelf technology to solve real world problems commonly faced by the United States Navy. The ultimate goal of Argos is to provide database support for the Paperless Ship. Keywords: HyperCard computer program, HyperTalk programming language, Implementation.

A typed and temporal object oriented paradigm has been developed. A declarative object oriented, temporal constraint language MyT, its type system, and a model of persistence have been designed. The results on the associated model theory based on order sorted algebras and the view of MyT classes as temporal theories have been established. A provably type safe technique called constrained matching has been developed for the integrated typed and temporal object oriented paradigm. The underlying implementation architecture has been developed based on a persistent extension of the Java Virtual Machine. Specific techniques for handling advanced typing techniques in a persistent Java environment, such as bounded and F bounded polymorphism, have been developed. Results on the object oriented flight simulator technology have been established.

An object-oriented basis for interdisciplinary compressor simulation can, in principle, overcome several barriers associated with the traditional structured (procedural) development approach. This paper presents the results of a research effort with the objective to explore the repercussions on design, analysis, and implementation of a compressor model in an object oriented (OO) language, and to examine the ability of the OO system design to accommodate computational fluid dynamics (CFD) code for compressor performance prediction. Three fundamental results are that: (1) the selection of the object oriented language is not the central issue; enhanced (interdisciplinary) analysis capability derives from a broader focus on object-oriented technology; (2) object-oriented designs will produce more effective and reusable computer programs when the technology is applied to issues involving complex system inter-relationships (more so than when addressing the complex physics of an isolated discipline); and (3) the concept of disposable prototypes is effective for exploratory research programs, but this requires organizations to have a commensurate long-term perspective. This work also suggests that interdisciplinary simulation can be effectively accomplished (over several levels of fidelity) with a mixed language treatment (i.e., FORTRAN-C++), reinforcing the notion the OO technology implementation into simulations is a 'journey' in which the syntax can, by design, continuously evolve.

STARS Task IA09 was conceived to examine the potential complementary nature of the Cleanroom Engineering software and a representative set of the popular object-oriented methods being used to specify, design and develop software systems. Both methods of software development support the software concepts of abstraction, encapsulation, modularity and hierarchy. However, object-orientation as practiced over the past few years has produced mixed results, whereas Cleanroom has a significant track record of producting highly reliable systems, with extremely low after-delivery defect rates. The study was based on the assumptions that (1) object-oriented methods support domain-specific architecture-based reuse, (2) Cleanroom software development emphasizes process-driven software development, and (3) object-oriented and Cleanroom ideas are both complementary and compatible. The purpose of this paper is to (1) discuss why object-oriented and Cleanroom software engineering techniques should be integrated, (2) outline the generic process for object-oriented software development that was derived on STARS Task IAO9, and comment on relevant aspects of the mapping from the studied methods to each generic process activity, and (3) discuss the shared leveraging of Cleanroom and object-oriented techniques, and how the integration of these techniques might be leveraged to produce software of greater reliability and reusability.

STARS Task IA09 was conceived to examine the potential complementary nature of the Cleanroom Engineering software and a representative set of the popular object-oriented methods being used to specify, design and develop software systems. Both methods of software development support the software concepts of abstraction, encapsulation, modularity and hierarchy. However, object-orientation as practiced over the past few years has produced mixed results, whereas Cleanroom has a significant track record of producting highly reliable systems, with extremely low after-delivery defect rates. The study was based on the assumptions that (1) object-oriented methods support domain-specific architecture-based reuse, (2) Cleanroom software development emphasizes process-driven software development, and (3) object-oriented and Cleanroom ideas are both complementary and compatible. The purpose of this paper is to (1) discuss why object-oriented and Cleanroom software engineering techniques should be integrated, (2) outline the generic process for object-oriented software development that was derived on STARS Task IAO9, and comment on relevant aspects of the mapping from the studied methods to each generic process activity, and (3) discuss the shared leveraging of Cleanroom and object-oriented techniques, and how the integration of these techniques might be leveraged to produce software of greater reliability and reusability.

STARS Task IA09 was conceived to examine the potential complementary nature of the Cleanroom Engineering software and a representative set of the popular object-oriented methods being used to specify, design and develop software systems. Both methods of software development support the software concepts of abstraction, encapsulation, modularity and hierarchy. However, object-orientation as practiced over the past few years has produced mixed results, whereas Cleanroom has a significant track record of producting highly reliable systems, with extremely low after-delivery defect rates. The study was based on the assumptions that (1) object-oriented methods support domain-specific architecture-based reuse, (2) Cleanroom software development emphasizes process-driven software development, and (3) object-oriented and Cleanroom ideas are both complementary and compatible. The purpose of this paper is to (1) discuss why object-oriented and Cleanroom software engineering techniques should be integrated, (2) outline the generic process for object-oriented software development that was derived on STARS Task IAO9, and comment on relevant aspects of the mapping from the studied methods to each generic process activity, and (3) discuss the shared leveraging of Cleanroom and object-oriented techniques, and how the integration of these techniques might be leveraged to produce software of greater reliability and reusability.

STARS Task IA09 was conceived to examine the potential complementary nature of the Cleanroom Engineering software and a representative set of the popular object-oriented methods being used to specify, design and develop software systems. Both methods of software development support the software concepts of abstraction, encapsulation, modularity and hierarchy. However, object-orientation as practiced over the past few years has produced mixed results, whereas Cleanroom has a significant track record of producting highly reliable systems, with extremely low after-delivery defect rates. The study was based on the assumptions that (1) object-oriented methods support domain-specific architecture-based reuse, (2) Cleanroom software development emphasizes process-driven software development, and (3) object-oriented and Cleanroom ideas are both complementary and compatible. The purpose of this paper is to (1) discuss why object-oriented and Cleanroom software engineering techniques should be integrated, (2) outline the generic process for object-oriented software development that was derived on STARS Task IAO9, and comment on relevant aspects of the mapping from the studied methods to each generic process activity, and (3) discuss the shared leveraging of Cleanroom and object-oriented techniques, and how the integration of these techniques might be leveraged to produce software of greater reliability and reusability.

The purpose of this paper is to provide a description of NASA JPL Distributed Systems Technology (DST) Section's object-oriented component approach to open inter-operable systems software development and software reuse. It will address what is meant by the terminology object component software, give an overview of the component-based development approach and how it relates to infrastructure support of software architectures and promotes reuse, enumerate on the benefits of this approach, and give examples of application prototypes demonstrating its usage and advantages. Utilization of the object-oriented component technology approach for system development and software reuse will apply to several areas within JPL, and possibly across other NASA Centers.

The purpose of this paper is to provide a description of NASA JPL Distributed Systems Technology (DST) Section's object-oriented component approach to open inter-operable systems software development and software reuse. It will address what is meant by the terminology object component software, give an overview of the component-based development approach and how it relates to infrastructure support of software architectures and promotes reuse, enumerate on the benefits of this approach, and give examples of application prototypes demonstrating its usage and advantages. Utilization of the object-oriented component technology approach for system development and software reuse will apply to several areas within JPL, and possibly across other NASA Centers.

The purpose of this paper is to provide a description of NASA JPL Distributed Systems Technology (DST) Section's object-oriented component approach to open inter-operable systems software development and software reuse. It will address what is meant by the terminology object component software, give an overview of the component-based development approach and how it relates to infrastructure support of software architectures and promotes reuse, enumerate on the benefits of this approach, and give examples of application prototypes demonstrating its usage and advantages. Utilization of the object-oriented component technology approach for system development and software reuse will apply to several areas within JPL, and possibly across other NASA Centers.

The concern for reducing aviation safety risk is rising as the National Airspace System in the United States transforms to the Next Generation Air Transportation System (NextGen). The NASA Aviation Safety Program is committed to developing an effective aviation safety technology portfolio to meet the challenges of this transformation and to mitigate relevant safety risks. The paper focuses on the reasoning of selecting Object-Oriented Bayesian Networks (OOBN) as the technique and commercial software for the accident modeling and portfolio assessment. To illustrate the benefits of OOBN in a large and complex aviation accident model, the in-flight Loss-of-Control Accident Framework (LOCAF) constructed as an influence diagram is presented. An OOBN approach not only simplifies construction and maintenance of complex causal networks for the modelers, but also offers a well-organized hierarchical network that is easier for decision makers to exploit the model examining the effectiveness of risk mitigation strategies through technology insertions.

This report describes a set of strategies for performing software reengineering using object-oriented technology (OOT) for information systems in the DoD. The risks, problems, and issues associated with using OOT are identified. A reengineering example using OOT is given, the U.S. Air Force Base-Level System Modernization (BLSM) program, which has been designed to modernize base-level automated information systems at Air Force bases. One of BLSM's applications, the Air Force Operations Resource Management System, serves as an example of the program's approach to full-scale software reengineering using OOT. OOT reengineering guidelines are provided, covering the use of DoD-directed analysis techniques (IDEF0 and IDEF1X) and how to identify potential features for object-oriented modeling from the structured analysis models of legacy systems (when such models exist). The audience of this report includes DoD software development managers, technical leaders, and software engineers.

Few developers of commercial aviation software products are using object-oriented technology (OOT), despite its popularity in some other industries. Safety concerns about using OOT in critical applications, uncertainty about how to comply with regulatory requirements, and basic conservatism within the aviation community have been factors behind this caution. The Federal Aviation Administration (FAA) and the National Aeronautics and Space Administration (NASA) have sponsored research to investigate and workshops to discuss safety and certification concerns about OOT and to develop recommendations for safe use. Two Object Oriented Technology in Aviation (OOTiA) workshops have been held and numerous issues and comments about the effect of OOT features and languages have been collected. This paper gives a high level overview of the OOTiA project, and discusses selected specific results from the March 2003 workshop. In particular, results in the form of questions to consider before making the decision to use OOT are presented.