Feasibility study of an Integrated Program for Aerospace-vehicle Design (IPAD) system. Volume 6: Implementation schedule, development costs, operational costs, benefit assessment, impact on company organization, spin-off assessment, phase 1, tasks 3 to 8

A baseline implementation plan, including alternative implementation approaches for critical software elements and variants to the plan, was developed. The basic philosophy was aimed at: (1) a progressive release of capability for three major computing systems, (2) an end product that was a working tool, (3) giving participation to industry, government agencies, and universities, and (4) emphasizing the development of critical elements of the IPAD framework software. The results of these tasks indicate an IPAD first release capability 45 months after go-ahead, a five year total implementation schedule, and a total developmental cost of 2027 man-months and 1074 computer hours. Several areas of operational cost increases were identified mainly due to the impact of additional equipment needed and additional computer overhead. The benefits of an IPAD system were related mainly to potential savings in engineering man-hours, reduction of design-cycle calendar time, and indirect upgrading of product quality and performance

The cleanroom case study in the Software Engineering Laboratory: Project description and early analysis

This case study analyzes the application of the cleanroom software development methodology to the development of production software at the NASA/Goddard Space Flight Center. The cleanroom methodology emphasizes human discipline in program verification to produce reliable software products that are right the first time. Preliminary analysis of the cleanroom case study shows that the method can be applied successfully in the FDD environment and may increase staff productivity and product quality. Compared to typical Software Engineering Laboratory (SEL) activities, there is evidence of lower failure rates, a more complete and consistent set of inline code documentation, a different distribution of phase effort activity, and a different growth profile in terms of lines of code developed. The major goals of the study were to: (1) assess the process used in the SEL cleanroom model with respect to team structure, team activities, and effort distribution; (2) analyze the products of the SEL cleanroom model and determine the impact on measures of interest, including reliability, productivity, overall life-cycle cost, and software quality; and (3) analyze the residual products in the application of the SEL cleanroom model, such as fault distribution, error characteristics, system growth, and computer usage

Migrating a Large Scale Legacy Application to SOA: Challenges and Lessons Learned

Abstract—This paper presents the findings of a case study of a large scale legacy to service-oriented architecture migration process in the payments domain of a Dutch bank. The paper presents the business drivers that initiated the migration, and describes a 4-phase migration process. For each phase, the paper details benefits of using the techniques, best practices that contribute to the success, and possible challenges that are faced during migration. Based on these observations, the findings are discussed as lessons learned, including the implications of using reverse engineering techniques to facilitate the migration process, adopting a pragmatic migration realization approach, emphasizing the organizational and business perspectives, and harvesting knowledge of the system throughout the system’s life cycle. I

Validating year 2000 compliance

Validating year 2000 compliance involves the assessment of the correctness and quality of a year 2000 conversion. This entails inspecting both the quality of the conversion emph{process followed, and of the emph{result obtained, i.e., the converted system. This document provides an overview of the techniques that can be used to validate year 2000 compliance. It includes typical code fragments, and a discussion of existing technology, impact analysis, solution strategies, code correction, testing, and tools

An overview of decision table literature 1982-1995.

This report gives an overview of the literature on decision tables over the past 15 years. As much as possible, for each reference, an author supplied abstract, a number of keywords and a classification are provided. In some cases own comments are added. The purpose of these comments is to show where, how and why decision tables are used. The literature is classified according to application area, theoretical versus practical character, year of publication, country or origin (not necessarily country of publication) and the language of the document. After a description of the scope of the interview, classification results and the classification by topic are presented. The main body of the paper is the ordered list of publications with abstract, classification and comments.

The management of end user computing

Includes bibliographical references.John F. Rockart, Lauren S. Flannery

Implementation and testing of a Neighborhood Office Center (NOC) and integration of the NOC with an administrative correspondence management information system

The application of telecommunications and telecomputing was investigated as a means of reducing NASA's consumption of natural resources and the proliferation of paper copies of correspondence. The feasibility, operational advantages, and limitations of decentralized (remote) neighborhood offices (NOC) linked through an electronic network are demonstrated. These offices are joined to a management information system for correspondence tracking, and to an administrative office center service based on the use of magnetic medium word processing typewriters which handle the daily typing load. In connection with an augmented teleconference network, a uniform means is provided for creating, storing, and retrieving administrative documents, records, and data, while simultaneously permitting users of the system to track their status. Information will be transferred without using paper - merely through digital electronic communication and display, as a step toward the establishment of an agency-wide electronic mail system

Enterprise Resource Planning Systems and Their Impact on Development and Training: A Study of Instructional Methods in North America

One of the most important issues facing the modern world today is the Year 2000 problem. One of the greatest impacts of this problem is experienced by legacy computer systems. These are the database systems that run our businesses. Legacy systems are operated by segregated software packages that may or may not be able to communicate to each other. With the globalization of the economy, business computer systems need to be able to communicate with each other. This type of situation is what enterprise resource planning software is designed to solve. Enterprise Resource Planning (ERP) systems provide a common, consistent system to capture data organization-wide without redundancies. ERP is defined as a software management system that integrates all facets of the business, including planning, manufacturing, sales, and marketing. In addition to integrating the information across functions, also provides a set of tools for planning and monitoring the organizational functions and ensuring progress towards a common organizational goal (Sudhakar, 1998). As ERP methodology has become more popular, software applications have emerged to help business managers implement ERP. The purpose of this pilot study is to identify development times and delivery methods for high-level computer technology training. This has become an issue for Human Resource Development (HRD) because of the Year 2000 situation and its resulting issues, which have compelled businesses around North America to implement these ERP systems. After circulating a survey for almost seven month, the data collection period ended in March 1999. The response rate of 47 returned surveys from 63 requests calculates to 74.6%. A total of 34, or 72%, of respondents developed training programs for high-level computer technology

An Approach to Teaching Multiple Computer Languages

In the digital economy era, business information systems students need to be knowledgeable of multiple computer programming languages in order to meet the requirements of computer literacy. This paper outlines the pedagogy of an innovated course of multiple computer languages for business students in the major of information systems. It discusses the rationale of why the proposed pedagogy is different from and better than traditional ones, and describes the approach to teaching this course. Based on our experiences in the past three years, it is concluded that a single course of multiple computer languages is useful and feasible