Downloads & Free Reading Options - Results

Includes index

123

This project seeks to address the development of software systems targeted for heterogeneous distributed systems. In particular, this work is aimed at the discovery and construction of software development methods, corresponding software tools (programs), and consistent infrastructure that improve the quality and productivity of object-oriented (00) software engineering. DIAMONDS is the core project of this effort. The two major goals of the DIAMONDS project are: (1) the specification and validation of a sound object-oriented software development methodology for heterogeneous distributed processing, and (2) the development and support of an object (software) composition model which permits a system to effectively exploit an application's inherent concurrence with efficient communication and management overhead. The overall goal of DIAMONDS is to produce a methodology and supporting infrastructure such that the mapping of an application to system resources dynamically reflects algorithmic parallelism, computational needs, and the current state of the system. These goals, when met, greatly enhance the ability of a software product to be effectively deployed in a wide variety of system settings.

This project seeks to address the development of software systems targeted for heterogeneous distributed systems. In particular, this work is aimed at the discovery and construction of software development methods, corresponding software tools (programs), and consistent infrastructure that improve the quality and productivity of object-oriented (00) software engineering. DIAMONDS is the core project of this effort. The two major goals of the DIAMONDS project are: (1) the specification and validation of a sound object-oriented software development methodology for heterogeneous distributed processing, and (2) the development and support of an object (software) composition model which permits a system to effectively exploit an application's inherent concurrence with efficient communication and management overhead. The overall goal of DIAMONDS is to produce a methodology and supporting infrastructure such that the mapping of an application to system resources dynamically reflects algorithmic parallelism, computational needs, and the current state of the system. These goals, when met, greatly enhance the ability of a software product to be effectively deployed in a wide variety of system settings.

This project seeks to address the development of software systems targeted for heterogeneous distributed systems. In particular, this work is aimed at the discovery and construction of software development methods, corresponding software tools (programs), and consistent infrastructure that improve the quality and productivity of object-oriented (00) software engineering. DIAMONDS is the core project of this effort. The two major goals of the DIAMONDS project are: (1) the specification and validation of a sound object-oriented software development methodology for heterogeneous distributed processing, and (2) the development and support of an object (software) composition model which permits a system to effectively exploit an application's inherent concurrence with efficient communication and management overhead. The overall goal of DIAMONDS is to produce a methodology and supporting infrastructure such that the mapping of an application to system resources dynamically reflects algorithmic parallelism, computational needs, and the current state of the system. These goals, when met, greatly enhance the ability of a software product to be effectively deployed in a wide variety of system settings.

This project seeks to address the development of software systems targeted for heterogeneous distributed systems. In particular, this work is aimed at the discovery and construction of software development methods, corresponding software tools (programs), and consistent infrastructure that improve the quality and productivity of object-oriented (00) software engineering. DIAMONDS is the core project of this effort. The two major goals of the DIAMONDS project are: (1) the specification and validation of a sound object-oriented software development methodology for heterogeneous distributed processing, and (2) the development and support of an object (software) composition model which permits a system to effectively exploit an application's inherent concurrence with efficient communication and management overhead. The overall goal of DIAMONDS is to produce a methodology and supporting infrastructure such that the mapping of an application to system resources dynamically reflects algorithmic parallelism, computational needs, and the current state of the system. These goals, when met, greatly enhance the ability of a software product to be effectively deployed in a wide variety of system settings.

The SSVTF (Space Station Verification and Training Facility) project is completing the Preliminary Design Review of a large software development using object-oriented methods and systematic reuse. An incremental developmental lifecycle was tailored to provide early feedback and guidance on methods and products, with repeated attention to reuse. Object oriented methods were formally taught and supported by realistic examples. Reuse was readily accepted and planned by the developers. Schedule and budget issues were handled by agreements and work sharing arranged by the developers.

123

The purpose of this research is to technically evaluate, refine, and expand two existing aircraft safety management information systems (one military and one civilian). The systems are used in the data collection, organization, query, analysis, and reporting of maintenance errors that contribute to aviation mishaps, equipment damage, and personnel injury. Both programs implement the Human Factors Analysis and Classification System (HFACS) taxonomy model developed by the Naval Safety Center (NSC) to capture aircrew errors in Naval Aviation mishaps. The goal of this taxonomy is to identify areas for potential intervention by fully describing factors that are precursors to aircraft accidents.

Correctness is paramount for safety-critical software control systems. Critical software failures in medical radiation treatment, communications, and defense are familiar to the public. The significant quantity of software malfunctions regularly reported to the software engineering community, the laws concerning liability, and a recent NRC Aeronautics and Space Engineering Board report additionally motivate the use of error-reducing and defect detection software development techniques. The benefits of formal methods in requirements driven software development ('forward engineering') is well documented. One advantage of rigorously engineering software is that formal notations are precise, verifiable, and facilitate automated processing. This paper describes the application of formal methods to reverse engineering, where formal specifications are developed for a portion of the shuttle on-orbit digital autopilot (DAP). Three objectives of the project were to: demonstrate the use of formal methods on a shuttle application, facilitate the incorporation and validation of new requirements for the system, and verify the safety-critical properties to be exhibited by the software.

Correctness is paramount for safety-critical software control systems. Critical software failures in medical radiation treatment, communications, and defense are familiar to the public. The significant quantity of software malfunctions regularly reported to the software engineering community, the laws concerning liability, and a recent NRC Aeronautics and Space Engineering Board report additionally motivate the use of error-reducing and defect detection software development techniques. The benefits of formal methods in requirements driven software development ('forward engineering') is well documented. One advantage of rigorously engineering software is that formal notations are precise, verifiable, and facilitate automated processing. This paper describes the application of formal methods to reverse engineering, where formal specifications are developed for a portion of the shuttle on-orbit digital autopilot (DAP). Three objectives of the project were to: demonstrate the use of formal methods on a shuttle application, facilitate the incorporation and validation of new requirements for the system, and verify the safety-critical properties to be exhibited by the software.

Correctness is paramount for safety-critical software control systems. Critical software failures in medical radiation treatment, communications, and defense are familiar to the public. The significant quantity of software malfunctions regularly reported to the software engineering community, the laws concerning liability, and a recent NRC Aeronautics and Space Engineering Board report additionally motivate the use of error-reducing and defect detection software development techniques. The benefits of formal methods in requirements driven software development ('forward engineering') is well documented. One advantage of rigorously engineering software is that formal notations are precise, verifiable, and facilitate automated processing. This paper describes the application of formal methods to reverse engineering, where formal specifications are developed for a portion of the shuttle on-orbit digital autopilot (DAP). Three objectives of the project were to: demonstrate the use of formal methods on a shuttle application, facilitate the incorporation and validation of new requirements for the system, and verify the safety-critical properties to be exhibited by the software.

Correctness is paramount for safety-critical software control systems. Critical software failures in medical radiation treatment, communications, and defense are familiar to the public. The significant quantity of software malfunctions regularly reported to the software engineering community, the laws concerning liability, and a recent NRC Aeronautics and Space Engineering Board report additionally motivate the use of error-reducing and defect detection software development techniques. The benefits of formal methods in requirements driven software development ('forward engineering') is well documented. One advantage of rigorously engineering software is that formal notations are precise, verifiable, and facilitate automated processing. This paper describes the application of formal methods to reverse engineering, where formal specifications are developed for a portion of the shuttle on-orbit digital autopilot (DAP). Three objectives of the project were to: demonstrate the use of formal methods on a shuttle application, facilitate the incorporation and validation of new requirements for the system, and verify the safety-critical properties to be exhibited by the software.

Correctness is paramount for safety-critical software control systems. Critical software failures in medical radiation treatment, communications, and defense are familiar to the public. The significant quantity of software malfunctions regularly reported to the software engineering community, the laws concerning liability, and a recent NRC Aeronautics and Space Engineering Board report additionally motivate the use of error-reducing and defect detection software development techniques. The benefits of formal methods in requirements driven software development ('forward engineering') is well documented. One advantage of rigorously engineering software is that formal notations are precise, verifiable, and facilitate automated processing. This paper describes the application of formal methods to reverse engineering, where formal specifications are developed for a portion of the shuttle on-orbit digital autopilot (DAP). Three objectives of the project were to: demonstrate the use of formal methods on a shuttle application, facilitate the incorporation and validation of new requirements for the system, and verify the safety-critical properties to be exhibited by the software.

sFCFD

sFCFD

azdg

Space Administration, require that the system utilize a Microsoft Access based implementation. This research focuses on meticulous software engineering to investigate the feasibility of adapting the current \"structured\" systems to Microsoft-based object oriented architectures ensuring future scalability and increased potential for code-reuse. Primary research questions investigated in this thesis include: 1) How can a Microsoft Access-based implementation provide multi-user access to the same database in a client-server environment while ensuring the ability to scale to a large number (potentially thousands) of users? 2) How can the linguistic discontinuity associated with object-oriented concepts and non-object oriented, flat relational databases be overcome when limited by the requirement for a Microsoft Access based solution? This problem is commonly called \"impedence Mismatch\". 3) The current military and civilian systems provide similar functionality, but use different database schema. How can object oriented methods be implemented to provide a common interface to both types of data? 4) How should database schema be changed to provide the best performance, scalability, and opportunity for code re-use? 5) In the past, Microsoft has deployed new versions of Microsoft Access and Visual Basic that were not (fully) backwards compatible with previous versions. This caused great discontent among users of applications designed to run under the older versions of these programs. How can our system(s) be designed to isolate them from problems associated with new versions of Microsoft products? Specifically, the pending release of Microsoft Office 2002, the new SQL Server 2000 database engine, and Microsoft Visual Basic.NET. This thesis describes our use of the Spiral Development Model to create a Microsoft Based solution for the Aviation Safety School requirements. We hypothesize that the prototype produced as a part of our research will greatly enhance current HFACS-capabilities and provide the means to weather further changes in requirements and application platforms.

scan of unit An Introduction to Methods Unit 4 M255 Object-oriented programming with Java 2nd edition by The M255 Course Team [2008] {005.133--oclc}

scan of unit An Introduction to Methods Unit 4 M255 Object-oriented programming with Java 2nd edition by The M255 Course Team [2008] {005.133--oclc}

scan of unit An Introduction to Methods Unit 4 M255 Object-oriented programming with Java 2nd edition by The M255 Course Team [2008] {005.133--oclc}

The purpose of this research is to technically evaluate, refine, and expand two existing aircraft safety management information systems (one military and one civilian). The systems are used in the data collection, organization, query, analysis, and reporting of maintenance errors that contribute to Aviation mishaps, equipment damage, and personnel injury. Both programs implement the Human Factors Analysis and Classification System (HFACS) taxonomy model developed by the Naval Safety Center (NSC) to capture aircrew errors in Naval Aviation mishaps. The goal of this taxonomy is to identify areas for potential intervention by fully describing factors that are precursors to aircraft accidents. Requirements outlined by Dr. John K. Schmidt of the Naval Safety Center, in conjunction with funding by the National Aeronautics and Space Administration, require that the system utilize a Microsoft Access based implementation. This research focuses on meticulous software engineering to investigate the feasibility of adapting the current \"structured\" systems to Microsoft-based object oriented architectures ensuring future scalability and increased potential for code-reuse. Primary research questions investigated in this thesis include: 1) How can a Microsoft Access-based implementation provide multi-user access to the same database in a client-server environment while ensuring the ability to scale to a large number (potentially thousands) of users? 2) How can the linguistic discontinuity associated with object-oriented concepts and non-object oriented, flat relational databases be overcome when limited by the requirement for a Microsoft Access based solution? This problem is commonly called \"impedence Mismatch\". 3) The current military and civilian systems provide similar functionality, but use different database schema. How can object oriented methods be implemented to provide a common interface to both types of data? 4) How should database schema be changed to provide the best performance, scalability, and opportunity for code re-use? 5) In the past, Microsoft has deployed new versions of Microsoft Access and Visual Basic that were not (fully) backwards compatible with previous versions. This caused great discontent among users of applications designed to run under the older versions of these programs. How can our system(s) be designed to isolate them from problems associated with new versions of Microsoft products? Specifically, the pending release of Microsoft Office 2002, the new SQL Server 2000 database engine, and Microsoft Visual Basic.NET. This thesis describes our use of the Spiral Development Model to create a Microsoft Based solution for the Aviation Safety School requirements. We hypothesize that the prototype produced as a part of our research will greatly enhance current HFACS-capabilities and provide the means to weather further changes in requirements and application platforms.

This document presents a methodology for developing an organizational process model which is based on the principles of object oriented design and formal software engineering methods. The methodology begins with the development of an object oriented Rumbaugh model (27). The Rumbaugh model is then formally specified in Z (Zed) schemas. Finally, the Z specifications are translated into an executable model in the Software Refinery Environment(TM). This model is described based on the AF wing domain and developed in this domain. The proposed methodology is then shown to produce a very general model which is extendable across almost any domain. The proposed methodology is also shown to be very general and tailorable for specific domain applications.

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.

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.

User interfaces in interactive simulations convey the dynamic behavior of the modeled system and allow the analyst to interact with the executing simulation. Traditionally, the software to display the system behavior and to facilitate user interaction has been embedded in the simulation model. Such tight integrations make it difficult to maintain large simulations and impose unnecessary limitations on the development of interfaces to a simulation model. This report presents a portable, object-based architecture, called JADIS (Java-based Architecture for Developing Interactive Simulations), for developing interactive simulations. The architecture is implemented in Java and applied the Model View-Controller paradigm to the development of interactive simulations. In JADIS, the simulation model and its user interfaces are distinct processes that execute concurrently. JADIS integrates concepts from object-oriented programming, concurrent, distributed processing, and human factors interface design in developing interactive simulations. This report describes the JADIS architecture and presents its application to an aircraft repair time analysis problem in the domain of airbase logistics.