Downloads & Free Reading Options - Results

The DoD is transitioning from many outmoded and proprietary automated information systems to a few modernized and less costly systems. This transition involves the migration and reengineering of legacy systems as well as the development of new automated information systems (AISs), and raises a number of issues around the proposed use of object-oriented technology (OOT). This report provides an overview to OOT and an extensive survey and discussion of which OOT techniques and methods are better suited to the AIS needs of the DoD. The bulk of the report was developed by abstracting from existing OO methodologies and practices all the essential activities in OO development, ranging from requirements analysis to maintenance. In addition, constraints imposed by DoD policies, standards, and procedures were evaluated as to their effects on the use of OOT.

This research is aimed at developing a neiv and advanced simulation framework that will significantly improve the overall efficiency of aerospace systems design and development. This objective will be accomplished through an innovative integration of object-oriented and Web-based technologies ivith both new and proven simulation methodologies. The basic approach involves Ihree major areas of research: Aerospace system and component representation using a hierarchical object-oriented component model which enables the use of multimodels and enforces component interoperability. Collaborative software environment that streamlines the process of developing, sharing and integrating aerospace design and analysis models. . Development of a distributed infrastructure which enables Web-based exchange of models to simplify the collaborative design process, and to support computationally intensive aerospace design and analysis processes. Research for the first year dealt with the design of the basic architecture and supporting infrastructure, an initial implementation of that design, and a demonstration of its application to an example aircraft engine system simulation.

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.

http://uf.catalog.fcla.edu/uf.jsp?st=UF021975271&ix=pm&I=0&V=D&pm=1

Click here to view the University of Florida catalog record

Click here to view the University of Florida catalog record

Click here to view the University of Florida catalog record

Click here to view the University of Florida catalog record

http://uf.catalog.fcla.edu/uf.jsp?st=UF027817463&ix=pm&I=0&V=D&pm=1

A set of computer aided software engineering (CASE) tools for the software development framework for parallel processing systems based on the Parallel Object Oriented Functional computation model (PROOF) toward the automation of object oriented software development for parallel processing systems is presented. An object oriented analysis tool has been developed to identify and express parallelism in the problem statement. We have developed a communication estimation tool to estimate the communication among objects, and a clustering tool to partition the objects in groups so that the intergroup communication is reduced and concurrency with specified user requirements is realized. The parallelism analysis tool further explores potential parallelism by analyzing the invocation relations and data flow among objects. The PROOF/L back end translator is extended to support clustering and dynamic allocation features in order to achieve better performance on a workstation cluster. The software effort using our approach can be greatly reduced due to implicit synchronization and communication, the user friendly graphical interfaces of the CASE tools, the automated object oriented analysis and parallelism analysis. The performance of software developed using our approach can be improved due to the integration of the object clustering algorithm, the parallelism analysis tool and the extended back end translator.

Mesh generation has long been recognized as a bottleneck in the CFD process. While much research on automating the volume mesh generation process have been relatively successful,these methods rely on appropriate initial surface triangulation to work properly. Surface discretization has been one of the least automated steps in computational simulation due to its dependence on implicitly defined CAD surfaces and curves. Differences in CAD peometry engines manifest themselves in discrepancies in their interpretation of the same entities. This lack of "good" geometry causes significant problems for mesh generators, requiring users to "repair" the CAD geometry before mesh generation. The problem is exacerbated when CAD geometry is translated to other forms (e.g., IGES )which do not include important topological and construction information in addition to entity geometry. One technique to avoid these problems is to access the CAD geometry directly from the mesh generating software, rather than through files. By accessing the geometry model (not a discretized version) in its native environment, t h s a proach avoids translation to a format which can deplete the model of topological information. Our approach to enable models developed in the Denali software environment to directly access CAD geometry and functions is through an Application Programming Interface (API) known as CAPRI. CAPRI provides a layer of indirection through which CAD-specific data may be accessed by an application program using CAD-system neutral C and FORTRAN language function calls. CAPRI supports a general set of CAD operations such as truth testing, geometry construction and entity queries.

http://uf.catalog.fcla.edu/uf.jsp?st=UF021970951&ix=pm&I=0&=D&pm=1

The following reports are presented on this project:A first year progress report on: Development of a Dynamically Configurable,Object-Oriented Framework for Distributed, Multi-modal Computational Aerospace Systems Simulation; A second year progress report on: Development of a Dynamically Configurable, Object-Oriented Framework for Distributed, Multi-modal Computational Aerospace Systems Simulation; An Extensible, Interchangeable and Sharable Database Model for Improving Multidisciplinary Aircraft Design; Interactive, Secure Web-enabled Aircraft Engine Simulation Using XML Databinding Integration; and Improving the Aircraft Design Process Using Web-based Modeling and Simulation.