Engineering topics

Tausworthe, R. C.

Publications and source records attributed to Tausworthe, R. C..

At least 19 records

NASA NTRS1992

Deep Space Network information system architecture study

The purpose of this article is to describe an architecture for the Deep Space Network (DSN) information system in the years 2000-2010 and to provide guidelines for its evolution during the 1990s. The study scope is defined to be from the front-end areas at the antennas to the end users (spacecraft teams, principal investigators, archival storage systems, and non-NASA partners). The architectural vision provides guidance for major DSN implementation efforts during the next decade. A strong motivation for the study is an expected dramatic improvement in information-systems technologies, such as the following: computer processing, automation technology (including knowledge-based systems), networking and data transport, software and hardware engineering, and human-interface technology. The proposed Ground Information System has the following major features: unified architecture from the front-end area to the end user; open-systems standards to achieve interoperability; DSN production of level 0 data; delivery of level 0 data from the Deep Space Communications Complex, if desired; dedicated telemetry processors for each receiver; security against unauthorized access and errors; and highly automated monitor and control.

Beswick, C. A.↗

NASA NTRS1990

Simplified Correlator For Ranging Codes

Improved correlating subsystem of pseudorandom-code ranging system made possible by advent of fast, custom-made, very-large-scale integrated circuits. Performs far fewer arithmetical operations, contains much less specialized analog and digital circuitry, and used with large number of different codes.

Tausworthe, R. C.↗

NASA NTRS1988

A communication channel model of the software process

Reported here is beginning research into a noisy communication channel analogy of software development process productivity, in order to establish quantifiable behavior and theoretical bounds. The analogy leads to a fundamental mathematical relationship between human productivity and the amount of information supplied by the developers, the capacity of the human channel for processing and transmitting information, the software product yield (object size), the work effort, requirements efficiency, tool and process efficiency, and programming environment advantage. Also derived is an upper bound to productivity that shows that software reuse is the only means than can lead to unbounded productivity growth; practical considerations of size and cost of reusable components may reduce this to a finite bound.

Tausworthe, R. C.↗

NASA NTRS1988

A simplified, general-purpose deep-space ranging correlator design

A much-simplified, yet more general-purpose multi-channel deep-space ranging system correlator design that was used in past JPL spacecraft ranging systems is described. The method applies to detection of both single-component and multiple-component ranging codes, in either sequential (mu) or composite (pi) transmitted forms, and using either pseudonoise or square-wave components. Using this design, the Phobos Probe ranging system correlator computational complexity was reduced by over three orders of magnitude in multiply-and-add circuits and 45,000 bits of accumulator storage.

Tausworthe, R. C.↗

NASA NTRS1987

Tau ranging revisited

It is shown that a ranging receiver with a sufficient and reasonable number of correlators is competitive with the current sequential component ranging system by some 1.5 to 2.5 dB. The optimum transmitter code, the optimum receiver, and a near-maximum-lilelihood range-estimation algorithm are presented.

Tausworthe, R. C.↗

NASA NTRS1985

Algorithms for Software Development

Management aid makes changes obvious. One key element in scheme for software development control is check summing. If check sum for given line in source file is different from previous version, it is evident change has been made. Subsequent editing of file creates new lines, deletes old ones, modifies characters, moves lines, or copies (reuse) existing lines. Combination of three elements of line code permits all transactions to be detected.

Tausworthe, R. C.↗

NASA NTRS1985

Concepts and Tools for the Software Life Cycle

The tools, techniques, and aids needed to engineer, manage, and administer a large software-intensive task are themselves parts of a large softwaare base, and are incurred only at great expense. The needs of the software life cycle in terms of such supporting tools and methodologies are highlighted. The concept of a distributed network for engineering, management, and administrative functions is outlined, and the key characteristics of localized subnets in high-communications-traffic areas of software activity are discussed. A formal, deliberate, structured, systems-engineering approach for the construction of a uniform, coordinated tool set is proposed as a means to reduce development and maintenance costs, foster adaptability, enhance reliability, and promote standardization.

Tausworthe, R. C.↗

NASA NTRS1985

Software Cost-Estimation Model

Software Cost Estimation Model SOFTCOST provides automated resource and schedule model for software development. Combines several cost models found in open literature into one comprehensive set of algorithms. Compensates for nearly fifty implementation factors relative to size of task, inherited baseline, organizational and system environment and difficulty of task.

Tausworthe, R. C.↗

NASA NTRS1985

Software Design Analyzer System

CRISP80 software design analyzer system a set of programs that supports top-down, hierarchic, modular structured design, and programing methodologies. CRISP80 allows for expression of design as picture of program.

Tausworthe, R. C.↗

NASA NTRS1985

Concepts and tools for the software life cycle

The tools, techniques, and aids needed to engineer, manage, and administer a large software-intensive task are themselves parts of a large software base, and are incurred only at great expense. The needs of the software life cycle in terms of such supporting tools and methodologies are highlighted. The concept of a distributed network for engineering, management, and administrative functions is outlined, and the key characteristics of localized subnets in high-communications-traffic areas of software actively are discussed. A formal, deliberate, structured, systems-engineering approach for the construction of a uniform, coordinated tool set is proposed as a means to reduce development and maintenance costs, foster adaptability, enhance reliability, and promote standardization.

Tausworthe, R. C.↗

NASA NTRS1983

Staffing implications of software productivity models

The attributes of software project staffing and productivity implied by equating the effects of two popular software models in a small neighborhood of a given effort-duration point are investigated. The first model presupposes that organizational productivity decreases as a function of the project staff size due to interfacing and intercommunication. The second, the so-called software equation, relates the product size to effort and duration through a power law tradeoff formula. The conclusions that may be reached by assuming that both of these describe project behavior, the former as a global phenomenon and the latter as a localized effect in a small neighborhood of a given effort duration point, are that (1) there is a calculable maximum effective staff level, which, if exceeded, reduces the project production rate, (2) there is a calculable maximum extent to which effort and time may be traded effectively, (3) it becomes ineffective in a practical sense to expend more than an additional 25 to 50% of resources in order to reduce delivery time, and (4) the team production efficiency can be computed directly from the staff level, the slope of the intercommunication loss function, and the ratio of exponents in the software equation.

Tausworthe, R. C.↗

NASA NTRS1983

Structural considerations for a software life cycle dynamic simulation model

This paper presents the results of a preliminary study into the prospects for simulating the software implementation and maintenance life cycle process, with the aim of producing a computerized tool for use by management and software engineering personnel in project planning, tradeoff studies involving product, environmental, situational, and technological factors, and training. The approach taken is the modular application of a 'flow of resource' concept to the systems dynamics simulation modeling technique. The software life cycle process is represented as a number of stochastic, time-varying, interacting work tasks that each achieves one of the project milestones. Each task is characterized by the item produced, the personnel applied, and the budgetary profile.

Tausworthe, R. C.↗

NASA NTRS1982

Algorithms for software development version control and change detection

Simple computer algorithms for processing source program and text data files in order to extract change detection, version control, version history, and current status information are described. These algorithms presuppose that it is possible to attach to each record of the source files a 6-character code, placed within delimiters that will cause the compiler, or other using program, to ignore this code field. The code contains a 2-character code for a character-by-character position-sensitive checksum of the record, another for the record number in the file, and a third for the data on which the encoding took place. Once the source file has been thus encoded, it is possible to detect the following transactions on the file since the most recent version coding; (1) addition of new records (having no version code), (2) modification of existing records, (3) deletion of a number of records, (4) movement and/or duplication of existing records, and (5) modification and duplication of records. In addition, it is possible to extract a version history of the number of records created or modified by date. A special file listing program is described which prints the file records without showing the version codes, but places a "change bar" at the right margin whenever a change is detected. The program also provides a list of changed pages and a version history.

Tausworthe, R. C.↗

NASA NTRS1981

Deep space network software cost estimation model

A parametric software cost estimation model prepared for Jet PRopulsion Laboratory (JPL) Deep Space Network (DSN) Data System implementation tasks is described. The resource estimation mdel modifies and combines a number of existing models. The model calibrates the task magnitude and difficulty, development environment, and software technology effects through prompted responses to a set of approximately 50 questions. Parameters in the model are adjusted to fit JPL software life-cycle statistics.

Tausworthe, R. C.↗

NASA NTRS1981

Deep space network software cost estimation model

A parametric software cost estimation model prepared for Deep Space Network (DSN) Data Systems implementation tasks is presented. The resource estimation model incorporates principles and data from a number of existing models. The model calibrates task magnitude and difficulty, development environment, and software technology effects through prompted responses to a set of approximately 50 questions. Parameters in the model are adjusted to fit DSN software life cycle statistics. The estimation model output scales a standard DSN Work Breakdown Structure skeleton, which is then input into a PERT/CPM system, producing a detailed schedule and resource budget for the project being planned.

Tausworthe, R. C.↗

NASA NTRS1980

The work breakdown structure in software project management

A work breakdown structure (WBS) is defined as an enumeration of all work activities in hierarchic refinement of detail which organizes work to be done into short manageable tasks with quantifiable inputs, outputs, schedules, and assigned responsibilities. Some of the characteristics and benefits of the WBS are reviewed, and ways in which these can be developed and applied in software implementation projects are discussed. Although the material is oriented principally toward new-software production tasks, many of the concepts are applicable to continuing maintenance and operations tasks.

Tausworthe, R. C.↗

NASA NTRS1979

Preparation guide for class B software specification documents

General conceptual requirements and specific application rules and procedures are provided for the production of software specification documents in conformance with deep space network software standards and class B standards. Class B documentation is identified as the appropriate level applicable to implementation, sustaining engineering, and operational uses by qualified personnel. Special characteristics of class B documents are defined.

Tausworthe, R. C.↗

NASA NTRS1979

Phase conjugation method and apparatus for an active retrodirective antenna array

An active retrodirective antenna array wherein a reference array element is used to generate a phase reference which is replicated at succeeding elements of the array. Each element of the array is associated with a phase regeneration circuit and the phase conjugation circuitry of an adjacent element. In one implementation, the phase reference circuit operates on the input signal at the reference element, a voltage controlled oscillator (VCO) output signal and the input pilot signal at the next array element received from a transmission line. By proper filtering and mixing, a phase component may be produced to which the VCO may be locked to produce the phase conjugate of the pilot signal at the next array element plus a transmission line delay. In another implementation, particularly suited for large arrays in space, two different input pilot frequencies are employed.

Tausworthe, R. C.↗