leff@smu.UUCP (Laurence Leff) (08/15/89)
Part III of V
Software Engineering Institute Carnegie Mellon University
Information Management
Pittsburgh, Pennsylvania 15213
1 January 1986 -- 4 August 1989 Annotated list of available documents.
Technical reports that have DTIC numbers are available from the Defense
Technical Information Center (DTIC) and the National Technical Information
Service (NTIS). (As an example, ADA169705 is the DTIC number for the SEI
report Toward a Reform of the Defense Department Software Acquisition Policy.)
If you wish to request a copy of one of the following reports, please contact
either DTIC or NTIS directly.
DTIC Defense Technical Information Center
ATTN: FDRA
Cameron Station
Alexandria VA 22304-6145
NTIS National Technical Information Service
U.S. Department of Commerce
Springfield, VA 22161
CMU/SEI-87-TR-30, ADA188932
Weiderman
Criteria for Constructing and Using an Ada Embedded System Testbed
The purpose of this report is to list some of the criteria used in five aspects
of the project: the hardware configuration, the software configuration, the
real-time application, the Ada real-time experiments, and the benchmarking and
instrumentation techniques. Each criterion will include a rationale. Each of
the criteria listed in this report will be categorized as either essential,
highly desirable, or desirable.
CMU/SEI-87-TR-31, ADA200609
Weiderman, Altman, Hefley, Klein, M., Landherr, Mumm, Slusarz, J.
Annual Technical Report for Ada Embedded Systems Testbed Project
The purpose of the Ada Embedded Systems Testbed Project (now called the
Real-Time Embedded Systems Project) is to investigate some of the critical
issues in using Ada for real-time embedded applications, particularly the
extent and quality of the runtime support facility provided by Ada
implementations. The project's objective has been to generate new information
about using Ada in real-time embedded systems. This information is in the form
of benchmark test results, higher level experiment results, and lessons learned
in designing and implementing real-time applications in Ada. This technical
report provides an overview of the results produced in the first year of the
project (through September 30, 1987). Details of these results are contained in
other referenced technical reports.
CMU/SEI-87-TR-32, ADA200612
Borger
VAXELN Experimentation: Programming a Real-Time Periodic Task Dispatcher
Using VAXELN Ada 1.1
The purpose of this paper is to provide the reader with some technical
information and observations, Ada source code, and measurement results based on
experimentation with respect to developing a real-time periodic task dispatcher
in Ada. In this context, a periodically scheduled task set implies that each
task in the set is executed at its own fixed frequency; a periodic task
dispatcher is a software component that schedules the individual tasks at their
implied runtime frequency. The results presented here are specific to a
MicroVAX-II/VAXELN 2.3 target system, the VAXELN 1.1 Ada compiler, and a
KWV11-C programmable real-time clock. Specifically, these results provide
answers to the question: How can one achieve the effect of scheduling a set of
periodic Ada tasks when the runtime frequency of some of the individual tasks
is less than the clock-cycle frequency supported by an Ada runtime
implementation?
CMU/SEI-87-TR-33, ADA200604
Landherr, Klein, M.
Inertial Navigation System Simulator: Behavioral Specification
The Real-Time Embedded Systems Testbed Project at the SEI is specifying and
developing a representative real-time application. This document augments an
original set of specifications written by a Navy affiliate. The purpose of this
behavioral specification is to clarify and augment the original.
CMU/SEI-87-TR-34, ADA200605
M. Klein, Landherr
Inertial Navigation System Simulator Program:
Top-Level Design
A real-time Ada application, an Inertial Navigation System (INS) simulator, is
being developed by the Real-Time Embedded Systems Testbed Project as a vehicle
to analyze issues regarding the use of Ada in the real-time embedded domain and
to provide a context for future experimentation. The technical philosophy
behind developing a real-time Ada artifact is to: (1) select a representative
(e.g., strict timing demands, multiple concurrent activities, low-level I/O,
error handling, interrupts, and periodic activities) real-time application; (2)
use Ada tasks as the unit of concurrency for the real-time design; and (3)
apply any relevant practical results being produced by the real-time scheduling
research community. In particular, the INS simulator must satisfy a set of
timing requirements that are similar to an INS with respect to data updating,
message transmission, and message reception. This document discusses the
top-level design of this application from three points of view: data flow
perspective, concurrency and control perspective, and the Ada module
perspective.
CMU/SEI-87-TR-35, ADA188928
Van Scoy
Prototype Real-Time Monitor: Executive Summary
This report summarizes the history, goals, and conclusions of the prototype
real-time monitor development effort. This effort was undertaken to address two
specific technical questions: 1) How can user tools find, access, and display
data hidden in the bodies of Ada applications? 2) How can user tools be layered
on top of Ada applications? The effort resulted in a generally usable
prototype, which is documented by four other SEI reports (CMU/SEI-87-TR-36
through CMU/SEI-87-TR-39).
CMU/SEI-87-TR-36, ADA188929
D'Ippolito, Lee, K., Plinta, Rissman, Van Scoy
Prototype Real-Time Monitor: Requirements
The requirements imposed by flight simulators and good software engineering
practice on Ada systems force software engineers to seek new solutions to the
problem of monitoring executing software. This report examines some of these
requirements and, based on these requirements, defines a subset for
implementation as a prototype real-time monitor (RTM).
CMU/SEI-87-TR-37, ADA188930
Van Scoy, Plinta, Coddington, T., D'Ippolito, Lee, K.
Prototype Real-Time Monitor: User's Manual
This report defines the user interface to the prototype real-time monitor
(RTM). It defines the concepts and commands needed by a software engineer to
use the RTM. In addition to defining the user interface, the report explains
the steps needed to tailor the RTM to work with the user's application.
CMU/SEI-87-TR-38, ADA188931
Van Scoy, Plinta, D'Ippolito, Lee, K., Rissman
Prototype Real-Time Monitor: Design
This report describes the software design used to implement the prototype
real-time monitor requirements. The design is presented at three levels:
system level, object level, and package architecture level. The report
concludes with a discussion of the key implementation obstacles that had to be
overcome to develop a working prototype: determining system addresses,
communicating with an executing application, accessing application memory,
converting data into human-readable form, and distributed CPU architectures.
CMU/SEI-87-TR-39, ADA191095
Van Scoy
Prototype Real-Time Monitor: Ada Code
This report documents the Ada code of the prototype real-time monitor (RTM).
CMU/SEI-87-TR-40, ADA200610
Donohoe
Ada Performance Benchmarks on the Motorola MC68020: Summary and Results
This report documents the results obtained from running the ACM SIGAda
Performance Issues Working Group (PIWG) and the University of Michigan Ada
performance benchmarks on a Motorola MC68020 microprocessor (MVME133 VMEmodule
Monoboard Microcomputer), using the Systems Designers Ada-Plus, the TeleSoft
TeleGen2, and the Verdix VAX/VMS hosted cross-compilers. A brief description of
the benchmarks and the test environment is followed by a discussion of some
problems encountered and lessons learned. Wherever possible, the output of each
benchmark program is also included.
CMU/SEI-87-TR-41, ADA200606
Firth, Wood, Pethia, Roberts, Methods Mosley, Dolce
A Classification Scheme for Software Development
Software development methods are used to assist with the process of designing
software for real-time systems. Many such methods have come into practice over
the last decade, and new methods are emerging. These new methods are more
powerful than the old ones, especially with regard to real-time aspects of the
software. This report describes a classification scheme for software
development methods, includes descriptions of the major characteristics of such
methods, and contains some words of advice on choosing and applying such
methods.
CMU/SEI-87-TR-42, ADA199877
Hefley
Issues in Software: A Blue Two Visit Feasibility Assessment
The SEI participated in a series of fact-finding meetings sponsored by the Air
Force Coordinating Office for Logistics Research to gather information
necessary to set the scope for and to implement one or more Blue Two Visits on
software. The purpose of a Blue Two Visit (BTV) is to introduce to industry's
top design engineers and program managers the day-to-day constraints Air Force
maintainers face on front-line operations bases. The participants experience
first-hand the effects of design on maintenance. This exposure has been
significant in bridging the gap between DoD and industry in understanding,
documenting, and supporting Air Force weapon system requirements to increase
combat supportability. This report documents discussions that attempt to
address the following questions for a software-oriented BTV: 1) Do software
maintainers and users have messages for software designers and programmers? 2)
What are these messages? 3) How can these messages be best communicated? 4) To
whom should these messages be targeted? 5) What should the BTV be called?
CMU/SEI-87-TR-43, ADA191097
Lee, Rissman, D'Ippolito, Plinta, Van Scoy
An OOD Paradigm for Flight Simulators
This report presents a paradigm for object-oriented implementations of flight
simulators. It is a result of work on the Ada Simulator Validation Program
(ASVP) carried out by members of the technical staff at the SEI.
CMU/SEI-87-TR-44, ADA188927
Ford, editor
Report on the SEI Workshop on Ada in Freshman Courses
The Undergraduate Software Engineering Education Project of the SEI Education
Program sponsored a workshop on Ada in Freshman Courses in June 1987. The
workshop brought together several educators to discuss how the software
engineering content of beginning programming and data structures courses might
be improved. This report describes the workshop and summarizes the discussions
and conclusions, and it also includes the position papers prepared by the
participants.
CMU/SEI-87-TR-45, ADA188923
Nestor
Views for Evolution in Programming Environments
Programming environments have become a focal point for much of the work
directed toward improving the practice of software engineering. Such
environments must provide mechanisms for recording and organizing the complex
set of persistent technical and management data associated with all parts of
the life cycle of large software systems. This paper focuses on one important
aspect of such persistent data: how to allow evolution when the existing
information must be preserved without change to maintain history. First, the
role of history in programming environments is discussed. Next, the additional
demands of evolution are considered and shown to lead to a set of problems.
View mechanisms are suggested as a solution to the problems. A simple example
involving file system directory structure is presented to illustrate these
problems. A simple view mechanism, called multidirectories, is introduced and
shown to solve the illustrated problems.
CMU/SEI-87-TR-46, ADA188924
Nestor
Evolving Persistent Objects in a Distributed Environment
This paper considers a class of objects, called incrementally mutable objects,
that are intermediate between mutable and immutable objects. Intuitively, the
only permitted modifications to an incrementally mutable object are those that
add new information to the object while preserving existing information.
Changes to incrementally mutable objects do not require central
synchronization. When a network becomes partitioned, the same incrementally
mutable object can be safely modified in each subnetwork. A mutable object can
be modeled by a set of immutable objects that represent each value of the
object over time and an incrementally mutable object that relates each
immutable object to its successor. Multiple successors are permitted to
represent parallel changes.
CMU/SEI-87-TR-47, ADA188922
Stone, Nestor
IDL: Background and Status
This paper presents an overview of the Interface Description Language (IDL).
We describe the language and its history. We also discuss the status of the IDL
community.
CMU/SEI-87-TR-48, ADA199634
Engle, Firth, Graham, Wood, B.
Interfacing Ada and SQL
The SEI was asked by the Ada Joint Program Office to investigate the problem of
interfacing programs written in Ada with database management systems
implementing the SQL database language. The authors decided to concentrate on a
description of the problems involved in producing an interface that would be
worthy of becoming a standard. This document is meant to assist the reader in
answering the question "What constitutes a good interface between Ada and SQL?"
The document should be useful both in the production of a standard and in the
analysis of any proposed standard.
CMU/SEI-88-TR-1, ADA200631
Summary of SEI Technical Operations: 1987
During 1987, the SEI had five programs in place: Ada-Based Software Engineering
Program, Education Program, Software Process Program, Pilot Projects Program,
and Technology Transition Program. These programs, their 1987 accomplishments,
and their planned work are described in this document. In addition, the SEI
affiliate functions, computing facilities, building, staff, and service
accomplishments are also described.
CMU/SEI-88-TR-3, ADA201345
Graham, Miller, D.
ISTAR Evaluation
ISTAR is an integrated project support environment produced by Imperial
Software Technology, Ltd. This evaluation of ISTAR is intended for software
technologists considering the adoption of an integrated project support
environment. Researchers and others interested in environments and evaluation
methods will also benefit from this report.
CMU/SEI-88-TR-4, ADA197136
Hansen, Over
Evaluation and Recommendations for Technology Insertion
into Technical Order Maintenance
As the need for mission-critical software systems increases, Post Deployment
Software Support (PDSS) activities will require increased priority in planning.
PDSS is "the sum of all activities required to ensure that, during the
production/deployment phase of a mission-critical computer system's life, the
implemented and fielded software/system continues to support its original
missions, and subsequent mission modifications and product improvements. PDSS,
therefore, includes not only software "maintenance" but also the activities
required for overall system support.
The SEI recognizes the importance of PDSS activities in the life cycle of
mission-critical systems. In March 1986, SEI personnel met with
representatives of the Air Force Logistics Command (AFLC) at Ogden Air
Logistics Center (OO-ALC), Hill Air Force Base, Utah, to determine if there
were areas in PDSS that the SEI could address. The AFLC representatives
described the activities performed at Air Logistics Centers and problems
encountered in those activities. As a result of this meeting, the SEI
authorized a feasibility study to determine how it might best interact with the
PDSS community. This report, written in August 1987, describes the evaluation
process and the ensuing recommendations for technology insertion into technical
order maintenance.
----listing continued in next post----
--
But who were they all in your sleep last night, first one then the next,
with their menace, wild sempahore, and lusts? I hardly know where you find
the strength come morning. August Kleinzahler