Downloads & Free Reading Options - Results

Available from National Technical Information Service, Springfield, Va

Available from National Technical Information Service, Springfield, Va

Available from National Technical Information Service, Springfield, Va

Available from National Technical Information Service, Springfield, Va

Available from National Technical Information Service, Springfield, Va

The Department of Defense (DoD) is plagued by severe cost overruns and delays in developing software systems. Existing software within DoD, some developed 15 to 20 years ago, require continual maintenance and modification. Major difficulties arise with maintaining older systems due to cryptic source code and a lack of adequate documentation. To remedy this situation, the DoD, is pursuing the integrated computer aided software engineering (I-CASE) procurement as a means to improve DoD's development and maintenance of software systems. This study focuses on the concepts and theory behind software re-engineering. In particular, it studies the current state of I-CASE technology, and the feasibility of re-engineering existing software systems for migration to an I- CASE environment.

The Department of Defense (DoD) is plagued by severe cost overruns and delays in developing software systems. Existing software within DoD, some developed 15 to 20 years ago, require continual maintenance and modification. Major difficulties arise with maintaining older systems due to cryptic source code and a lack of adequate documentation. To remedy this situation, the DoD, is pursuing the integrated computer aided software engineering (I-CASE) procurement as a means to improve DoD's development and maintenance of software systems. This study focuses on the concepts and theory behind software re-engineering. In particular, it studies the current state of I-CASE technology, and the feasibility of re-engineering existing software systems for migration to an I- CASE environment.

The rising percentage of system costs attributed to software development and maintenance have resulted in the research by industry and academia into ways to improve the productivity of sofware professionals in all phases of the software lifecycle. Computer Aided Software Engineering (CASE) environments are one solution being pursued. This thesis attempts to coalesce, from various efforts to date, some general principles for such environments in order to assist decision makers who must procure them. This work is in support of the Missile Software ranch, Naval Weapon Center, China Lake, California (MSB), and their investigation of CASE environments to improve productivity. Problems of CASE development and use are discussed in this context. A general problem solving approach through abstraction of resources is proposed with a focus on an individual programmer productivity subset of a CASE environment. (Theses). (Author)

Available from National Technical Information Service, Springfield, Va

This study investigated whether using CASE tools in the requirements analysis phase of software development reduced the software coding errors attributable to requirement analysis. A survey of the population gathered data as to the current practices and efforts in the use of CASE tools. The data was gathered in two groups: a control group and a sample group. The data was analyzed by group and in various combinations to obtain a greater understanding into population trends and tendencies. The results of the research indicate that the Air Force does not use CASE tools to any great extent. Also, error and cost data are not tracked in a meaningful way either. The conclusion drawn from this research shows that CASE tool use is still in its infancy and needs to begin rapid growth in order to speed up developments and reduce costs with the constantly shrinking budget. The major recommendations by the Author is to perform a more detailed study of the population to determine exactly where CASE tools are being used and where improvements need to be made.

A prediction was made that the terms expert systems and knowledge acquisition would begin to disappear over the next several years. This is not because they are falling into disuse; it is rather that practitioners are realizing that they are valuable adjuncts to software engineering, in terms of problem domains addressed, user acceptance, and in development methodologies. A specific problem was discussed, that of constructing an automated test analysis system for the Space Shuttle Main Engine. In this domain, knowledge acquisition was part of requirements systems analysis, and was performed with the aid of a powerful inductive ESBT in conjunction with a computer aided software engineering (CASE) tool. The original prediction is not a very risky one -- it has already been accomplished.

A prediction was made that the terms expert systems and knowledge acquisition would begin to disappear over the next several years. This is not because they are falling into disuse; it is rather that practitioners are realizing that they are valuable adjuncts to software engineering, in terms of problem domains addressed, user acceptance, and in development methodologies. A specific problem was discussed, that of constructing an automated test analysis system for the Space Shuttle Main Engine. In this domain, knowledge acquisition was part of requirements systems analysis, and was performed with the aid of a powerful inductive ESBT in conjunction with a computer aided software engineering (CASE) tool. The original prediction is not a very risky one -- it has already been accomplished.

This research informally investigates the use of Computer Aided Software Engineering (CASE) tools by a small software development organization. These tools are heralded as being productivity enhancers for software development personnel. Most of the literature discusses the generic use of this new generation of software development tools. This research effort focuses on the appropriateness os using these tools by the small software development organizations consisting of less than seven personnel. Provided in this thesis is a brief presentation of the software engineering discipline and descriptions of the CASE family of tools along with a discussion of 33 specific tools. A small software development organization model is provided and its areas of concerns are discussed. This research also performed a survey of users of current CASE products and the results from the 76 respondents are presented.

The rising percentage of system costs attributed to software development and maintenance have resulted in the research by industry and academia into ways to improve the productivity of software professionals in all phases of the software lifecycle. Computer Aided Software Engineering (CASE) environments are one solution being pursued. This thesis attempts to coalesce, from various efforts to date, some general principles for such environments in order to assist decision makers who must procure them. This work is in support of the Missile Software Branch, Naval Weapon Center, China Lake, California (MSB), and their investigation of CASE environments to improve productivity. Problems of CASE development and use are discussed in this context. A general problem solving approach through abstraction of resources is proposed with a focus on an individual programmer productivity subset of a CASE environment.

The rising percentage of system costs attributed to software development and maintenance have resulted in the research by industry and academia into ways to improve the productivity of software professionals in all phases of the software lifecycle. Computer Aided Software Engineering (CASE) environments are one solution being pursued. This thesis attempts to coalesce, from various efforts to date, some general principles for such environments in order to assist decision makers who must procure them. This work is in support of the Missile Software Branch, Naval Weapon Center, China Lake, California (MSB), and their investigation of CASE environments to improve productivity. Problems of CASE development and use are discussed in this context. A general problem solving approach through abstraction of resources is proposed with a focus on an individual programmer productivity subset of a CASE environment.

This thesis identifies the software engineering environment (SEE) as it exists at the Air Force Institute of Technology (AFIT) School of Engineering. It also describes the software process model employed and the software development methods presented as part of the curriculum. Based on this information, criteria was established to evaluate computer aided software engineering (CASE) tools being considered for integration into the SEE. Each criterion was weighted to indicate its importance when selecting CASE tools. The criteria were further used to establish a methodology to be used to evaluate and select the CASE tools under consideration as well as future tool candidates.

This thesis identifies the software engineering environment (SEE) as it exists at the Air Force Institute of Technology (AFIT) School of Engineering. It also describes the software process model employed and the software development methods presented as part of the curriculum. Based on this information, criteria was established to evaluate computer aided software engineering (CASE) tools being considered for integration into the SEE. Each criterion was weighted to indicate its importance when selecting CASE tools. The criteria were further used to establish a methodology to be used to evaluate and select the CASE tools under consideration as well as future tool candidates.

The Naval Postgraduate School's final exam scheduling system serves as a test case with which to compare two commercially available Computer-Aided Software Engineering (CASE) tools. The tools, Nastec Corporation's Design Aid (Release 3.55) and Index Technology's Excelerator (Release 1.7), are used to create Section 4.1 of two Abbreviated Systems Decision Papers to determine if their output can satisfy and should replace some of the Life Cycle Management documentation requirements of the Department of Defense for the procurement of Information Systems having a total cost of 100,00 or less.

The Naval Postgraduate School's final exam scheduling system serves as a test case with which to compare two commercially available Computer-Aided Software Engineering (CASE) tools. The tools, Nastec Corporation's Design Aid (Release 3.55) and Index Technology's Excelerator (Release 1.7), are used to create Section 4.1 of two Abbreviated Systems Decision Papers to determine if their output can satisfy and should replace some of the Life Cycle Management documentation requirements of the Department of Defense for the procurement of Information Systems having a total cost of 100,00 or less.

The Naval Postgraduate School's final exam scheduling system serves as a test case with which to compare two commercially available Computer-Aided Software Engineering (CASE) tools. The tools, Nastec Corporation's Design Aid (Release 3.55) and Index Technology's Excelerator (Release 1.7), are used to create Section 4.1 of two Abbreviated Systems Decision Papers to determine if their output can satisfy and should replace some of the Life Cycle Management documentation requirements of the Department of Defense for the procurement of Information Systems having a total cost of 100,00 or less.

The Department of Defense (DoD) is plagues with severe cost overruns and delays in developing software systems. Existing software within Dod, some developed 15-to 20 years ago, require continual maintenance and modification. Major difficulties arise with maintaining older systems due to cryptic source code and a lack of adequate documentation. To remedy this situation, the DoD, is pursuing the integrated computer aided software engineering (I-CASE) procurement as a means to improve DoD's development and maintenance of software systems. This study focuses on the concepts ad theory behind software re-engineering. In particular, it studies the current state of I-CASE technology, and the feasibility of reengineering existing software systems for migration to an I-CASE environment.

The use of Computer-Aided Software Engineering (CASE) tools has been viewed as a remedy for the software development crisis by achieving improved productivity and system quality via the automation of all or part of the software engineering process. The proliferation and tremendous variety of tools available have stretched the understanding of experienced practitioners and has had a profound impact on the software engineering process itself. To understand what a tool does and compare it to similar tools is a formidable task given the existing diversity of functionality. This thesis investigates what tools are available, proposes a general classification scheme to assist those investigating tools to decide where a tool falls within the software engineering process and identifies a tool's capabilities and limitations. This thesis also provides guidance for the evaluation of a tool and evaluates three commercially available tools.

The use of Computer-Aided Software Engineering (CASE) tools has been viewed as a remedy for the software development crisis by achieving improved productivity and system quality via the automation of all or part of the software engineering process. The proliferation and tremendous variety of tools available have stretched the understanding of experienced practitioners and has had a profound impact on the software engineering process itself. To understand what a tool does and compare it to similar tools is a formidable task given the existing diversity of functionality. This thesis investigates what tools are available, proposes a general classification scheme to assist those investigating tools to decide where a tool falls within the software engineering process and identifies a tool's capabilities and limitations. This thesis also provides guidance for the evaluation of a tool and evaluates three commercially available tools.

The Naval Postgraduate School's final exam scheduling system serves as a test case with which to compare two commercially available Computer-Aided Software Engineering (CASE) tools. The tools, Nastec Corporation's DesignAid (Release 3.55) and Index Technology's Excelerator (Release 1.7) are used to create Section 4.1 of two Abbreviated Systems Decision Papers to determine if their output can satisfy and should replace some of the Life Cycle Management documentation requirements of the Department of Defense for the procurement of Information Systems having at total cost of $100,000 or less.

The Naval Postgraduate School's final exam scheduling system serves as a test case with which to compare two commercially available Computer-Aided Software Engineering (CASE) tools. The tools, Nastec Corporation's DesignAid (Release 3.55) and Index Technology's Excelerator (Release 1.7) are used to create Section 4.1 of two Abbreviated Systems Decision Papers to determine if their output can satisfy and should replace some of the Life Cycle Management documentation requirements of the Department of Defense for the procurement of Information Systems having at total cost of $100,000 or less.

The Naval Postgraduate School's final exam scheduling system serves as a test case with which to compare two commercially available Computer-Aided Software Engineering (CASE) tools. The tools, Nastec Corporation's DesignAid (Release 3.55) and Index Technology's Excelerator (Release 1.7) are used to create Section 4.1 of two Abbreviated Systems Decision Papers to determine if their output can satisfy and should replace some of the Life Cycle Management documentation requirements of the Department of Defense for the procurement of Information Systems having at total cost of $100,000 or less.

Thesis advisor, Martin J. McCaffrey

This memorandum reports on a partially implemented interactive computer aided-design tool for software engineering. A distinguishing characteristic of this project is its concern for the evolutionary character of software systems. It draws a distinction between algorithms and systems, centering its attention on support for the system designer. Although verification has played a large role in recent research, this perspective suggests that the complexity and evolutionary nature of software systems require a number of additional techniques. Managing of complexity is a fundamental issue in all engineering disciplines. The authors identify three major techniques used in mature engineering fields which seem applicable to the engineering of software systems: incremental modelling; multiple and almost hierachical decomposition; and analysis by inspection. Along these lines they have (1) Constructed a plan library to aid in analysis by inspection (the analysis of a program based on identifying standard algorithms and methods in it); (2) Identified a small set of plan building methods which can be used to decompose a softwre system into loosely coupled subsystems; (3) Developed the technique of temporal abstraction which makes it possible to model a program from a viewpoint which clearly separates the actions of generations and consumers of data; and (4) Developed a dependency-based reasoning system uniquely suited to incremental and evolutionary program analysis. These methods are substantially language independent and have been applied to programs written in several commonly used languages.

Automating a software process both magnifies its strengths and accentuates its weaknesses. Automation can make an effective process more effective, but it can make a chaotic process even worse and at considerable expense. Anyone who buys expensive tools to solve an ill-defined problem is likely to be disappointed. Unless procurring such tools is part of a thoughtful software process improvement plan, the purchase could be an expensive mistake. This report discusses software process maturity and its relationship to planning and installing computer-aided software engineering (CASE) systems. While process is not a magic answer (there isn't one), the key issues are discussed from a process perspective, and guidelines are given for avoiding the most common pitfalls. Since CASE systems can involve significant investment, an economic justification may be necessary. The relevant financial considerations are therefore discussed, and some basic steps for producing such justifications are outlined. Finally, some key considerations for introducing and using CASE systems are discussed.

Automating a software process both magnifies its strengths and accentuates its weaknesses. Automation can make an effective process more effective, but it can make a chaotic process even worse and at considerable expense. Anyone who buys expensive tools to solve an ill-defined problem is likely to be disappointed. Unless procurring such tools is part of a thoughtful software process improvement plan, the purchase could be an expensive mistake. This report discusses software process maturity and its relationship to planning and installing computer-aided software engineering (CASE) systems. While process is not a magic answer (there isn't one), the key issues are discussed from a process perspective, and guidelines are given for avoiding the most common pitfalls. Since CASE systems can involve significant investment, an economic justification may be necessary. The relevant financial considerations are therefore discussed, and some basic steps for producing such justifications are outlined. Finally, some key considerations for introducing and using CASE systems are discussed.

A new software tool, Caesy, is described. This tool provides a strongly typed programming environment for research in the development of algorithms and software for computer-aided control system design. A description of the user language and its implementation as they currently stand are presented along with a description of work in progress and areas of future work.

20152__Computer Aided Softw__Bound __S__SDTE c1__L-19

The use of Computer-Aided Software Engineering (CASE) tools has been viewed as a remedy for the software development crisis by achieving improved productivity and system quality via the automation of all or part of the software engineering process. The proliferation and tremendous variety of tools available have stretched the understanding of experienced practitioners and has had a profound impact on the software engineering process itself. To understand what a tool does and compare it to similar tools is a formidable task given the existing diversity of functionality. This thesis investigates what tools are available, proposes a general classification scheme to assist those investigating tools to decide where a tool falls within the software engineering process and identifies a tool's capabilities and limitations. This thesis also provides guidance for the evaluation of a tool and evaluates three commercially available tools. Keywords: Project management, Rapid prototyping.

The NASA Engineering and Safety Center (NESC) was requested to perform an independent assessment of the mitigation of the Constellation Program (CxP) Risk 4421 through the use of computer-aided software engineering (CASE) tools. With the cancellation of the CxP, the assessment goals were modified to capture lessons learned and best practices in the use of CASE tools. The assessment goal was to prepare the next program for the use of these CASE tools. The outcome of the assessment is contained in this document.