From: bjz@sei.cmu.edu (Barbara Zayas)
Newsgroups: comp.doc.techreports
Subject: Software Engineering Institute reports (Part 4 of 5)
Date: Tue, 6 Oct 1992 13:05:24 GMT
Organization: Software Engineering Institute
NNTP-Posting-Host: oak.ucsc.edu
Originator: golding@oak



Software Engineering Institute
Information Management
Software Engineering Institute Documents



HOW TO ACCESS SEI REPORTS ELECTRONICALLY

The Software Engineering Institute (SEI) has begun electronic
distribution of some-not all-of its publications. The
procedure by which you can obtain electronic copies of SEI
reports is described on pages 1 and 2 of this document. Since
many SEI reports are yet unavailable in electronic form,
instructions for obtaining hardcopies of such reports appear
on page 5 of this document.

FTP File transfer protocol (FTP) is a facility that allows
files to be transferred to and from remote network sites.
Brief instructions for using FTP are provided below; if you
require additional information about FTP, contact your system
administrator.

SEI DIRECTORY NAME
The directories listed in /pub/documents contain files that
are accessible via anonymous FTP.


SEI MACHINE ADDRESS
The SEI machine address is:

		ftp.sei.cmu.edu
                      or 
		128.237.2.179


INSTRUCTIONS
If you are working at a UNIX machine connected to the Internet, use the 
following procedure to access SEI files.


TO CONNECT TO THE SEI FTP MACHINE
1	At your Unix prompt, type:

ftp ftp.sei.cmu.edu

2	At the login prompt, type:

anonymous

3	At the password prompt, 
type:

your electronic mail address 
(e.g., jones@cs.xsu.edu)

4	Change to the documents 
directory by typing:

cd /pub/documents

5	Get the READ.ME file by 
typing:

get READ.ME

You should now have a copy of the READ.ME file on your home 
machine.

Repeat Steps 1- 5 from the above procedure to obtain the
documents you want. Step 5 may be repeated as many times as
needed to obtain the desired documents; otherwise, terminate
the process, as is indicated below:

6	Terminate the FTP process 
by typing:

quit


COPYRIGHT NOTE
Some of the files may be temporarily read-protected pending the 
resolution of some copyright issues.
File format

The documents in /pub/documents are formatted as PostScript
files, and thus may be printed on a PostScript printer at
your site. All PostScript files have a .ps suffix.


FIGURES
Some of the files contain figures that have not yet been made
available electronically. Until this is resolved, such files
(ones containing figures markers) will print without figures.
Until the figures are made available electronically, feel
free to contact one of the distribution centers (listed
below) to obtain hardcopies of the documents.


PRINTER
Most of the documents use several of the following PostScript
fonts: Helvetica, Times, New Century Schoolbook, Courier, and
Symbol. Be certain to use a printer that can support these
fonts.  All files MUST be printed with the pages in the order
that they appear in the file. Some print spoolers attempt to
reverse the pages before printing so that the output page
stack will be in the proper order. This may cause the files
to fail to be printed. A common symptom of such a page order
error is having the file printed almost entirely in Courier
font.  Test print

You may want to test these procedures before downloading
large documents. For that purpose, a short test document
appears in the /pub/documents directory in file testTR.ps.
It is a three page excerpt from a technical report; the
second page should be blank.  Photocopying

Documents in PostScript form are intended to be reproduced as
two- sided documents. The left and right margins will be
different widths on odd- and even-numbered pages. If you
choose to make a two-sided document from the printed
original, you may wish to check the first few pages and
insert a blank page wherever needed (such as after the title
page on some documents) to ensure that the pagination is
correct.

THE ANNOTATED LISTING
Documents appearing in the annotated listing that are denoted
with the following icon are available via anonymous FTP:


QUESTIONS
If you cannot print a file, first verify that the print
failure is not due to a problem at your site. Next, reread
and retry the above instructions.  Lastly, if the problem
remains, send electronic mail to bjz@sei.cmu.edu describing
the hardware/operating system being used, the type of printer
on which you're attempting to print the document, and a
description of the problem.



HOW TO ORDER BOUND COPIES OF SEI REPORTS
Software Engineering Institute (SEI) technical reports are
available from Research Access, Inc. (RAI), National
Technical Information Service (NTIS), or the Defense
Technical Information Center (DTIC).  (Note: To order
documents from DTIC, you must provide the DTIC accession
number for the desired report. As an example, "ADA235641" is
the DTIC number for the SEI report Rate Monotonic Analysis
for Real-Time Systems.)

DISTRIBUTING CENTERS
If you wish to request a bound copy of an SEI report, please
contact RAI, NTIS, or DTIC directly. The addresses are
provided below. Several SEI reports have not yet been filed
with DTIC; therefore, they do not have DTIC accession
numbers.

RAI
Research Access Inc.
3400 Forbes Avenue
Suite 302
Pittsburgh, PA 15213
Telephone: 1800 685-6510
FAX: (412) 682-6530


DTIC
Defense Technical Information Center
ATTN: FDRA Cameron Station
Alexandria, VA 22304-6145
Telephone: (703) 274-7633

(Note that DTIC limits distribution to government contractors
who have established a DTIC account.).


NTIS
National Technical Information Service
U.S. Department of Commerce
Springfield, VA 22161-2103
Telephone: (703) 487-4600



		-----begin Part 4 (of 5) -----

Ada for Embedded Systems: Issues and Questions
CMU/SEI-87-TR-26, ADA191096
Weiderman, N., Borger, M., Cappellini, A., Dart, S., Klein, M., Landherr, S.

This report addresses issues and questions related to the use
of Ada for embedded systems applications; it contains some
preliminary recommendations for compilation system
implementors, application developers, program managers, and
Ada policy makers. The issues and questions provide the
context for the Real-Time Embedded Systems Testbed (REST)
Project at the SEI, where staff members are investigating
software development and performance issues for real-time
embedded systems.


Final Evaluation of MIPS M/500 Final Report for the RISC Insertion Project
CMU/SEI-87-TR-25, ADA200611
Klein, D., Firth, R. 

In response to a request from the DoD, an analysis of a
Reduced Instruction Set Computer (RISC) processor, the MIPS
M/500, was performed. All aspects of processor capabilities
and support software were evaluated, tested, and compared to
familiar Complex Instruction Set Computer (CISC)
architectures. In all cases, the RISC computer and its
support software performed better than a comparable CISC
computer. This report provides the general and specific
results of these analyses, along with the recommendation that
the DoD and other government agencies seriously consider this
or other RISC architectures as a highly viable and attractive
alternative to the more familiar but less efficient CISC
architectures.


Software Development Environments
CMU/SEI-87-TR-24, ADA200542
Dart, S., Ellison, B.

"Environment" refers to the collection of hardware and
software tools that a system developer uses to build software
systems. As technology improves and user expectations grow,
an environment's functionality tends to change. Over the last
20 years, the set of software tools available to developers
has expanded considerably. We can illustrate this change by
observing some distinctions in the terminology. "Programming
environment" and "software development environment" are often
used synonymously, but here we make a distinction between the
two.


Method for Assessing the Software Engineering Capability of Contractors, A
CMU/SEI-87-TR-23, ADA187230
Humphrey, W., Sweet, W. 

This document provides guidelines and procedures for
assessing the ability of potential DoD contractors to develop
software in accordance with modern software engineering
methods. It includes specific questions and a method for
evaluating the results.


Factors Causing Unexpected Variations in Ada Benchmarks
CMU/SEI-87-TR-22, ADA187231
Altman, N.

Benchmarks are often used to describe the performance of
computer systems. This report considers factors that may
cause Ada benchmarks to produce inaccurate results. Included
are examples from the ongoing benchmarking efforts of the Ada
Embedded Systems Testbed (AEST) Project using bare target
computers with several Ada compilers.


Timing Variation in Dual Loop Benchmarks
CMU/SEI-87-TR-21, ADA185697
Altman, N., Weiderman, N. 

Benchmarks that measure time values using a standard system
clock often employ a dual loop design. One of the important
assumptions of this design is that textually identical loop
statements will take the same amount of time to execute. This
assumption was tested on two bare computers with Ada test
programs and has been demonstrated to be inaccurate in these
specific test cases.


Teaching a Project-Intensive Introduction to Software Engineering
CMU/SEI-87-TR-20, ADA200603
Tomayko, J. 

This report is meant as a guide to the teacher of the
introductory course in software engineering. It contains a
case study of a course based on a large project. Other models
of course organization are also discussed. Additional
materials used in teaching the course and samples of
student-produced documentation are also available.


Use of Representation Clauses and Implementation-Dependent Features in Ada: IVA. Qualitative 
Results for Ada/M(44), The
CMU/SEI-87-TR-19, ADA188926
Meyers, C., Cappellini, A.

This report, one in a series, provides a qualitative
assessment of the support of representation clauses and
implementation-dependent features in Ada provided by the
Ada/M(44) compiler, Version 1.6. The evaluation questions
that were presented in a previous report of this series form
the basis of the qualitative assessment. A subjective
evaluation of the support provided for these features is also
presented.


Use of Representation Clauses and Implementation-Dependent Features in Ada: IIB. 
Experimental Procedures, The
CMU/SEI-87-TR-18, ADA200602
Meyers, C., Cappellini, A. 

This report is one in a series dealing with the use of
representation clauses and implementation-dependent features
in Ada. The purpose of this report is to discuss detailed
experimental procedures to assess compiler support. It is
readily acknowledged that the domain of possible
experimentation is large. To facilitate the experimentation,
a methodology is proposed that relies on program generators
and automated analysis tools.  An example of the methodology
is presented in some detail.


Use of Representation Clauses and Implementation-Dependent Features in Ada: IIIA. Qualitative 
Results for VAX Ada, The
CMU/SEI-87-TR-17, ADA188926
Meyers, C., Cappellini, A.

This report, one in a series, provides a qualitative
assessment of the support of representation clauses and
implementation-dependent features in Ada provided by the VAX
Ada compiler, Version 1.3. The evaluation questions that were
presented in a previous report of this series form the basis
of the qualitative assessment. A subjective evaluation of the
support provided for these features is also presented.


Preliminary Report on Conducting SEI-Assisted Assessments of Software Engineering
CMU/SEI-87-TR-16, ADA183429
Humphrey, W., Kitson, D. 

Characterizing the state of software engineering practice
within an organization is a necessary prerequisite to
orderly, meaningful, and sustainable improvement of the
organizations ability to produce or support cost-effective,
high quality software products.  The Software Engineering
Institute is developing a methodology for conducting
SEI-assisted assessments of software engineering capability.
The assessment methodology has five phases: 1. selecting the
candidate organization, 2. preparing for the assessment, 3.
conducting the assessment, 4. communicating final assessment
findings and action recommendations, and 5. post-assessment
follow-up activities. This report describes the methodology
in detail.


Use of Representation Clauses and Implementation-Dependent Features in Ada: IIA. Evaluation 
Questions, The
CMU/SEI-87-TR-15, ADA188925
Meyers, C., Cappellini, A. 

This report is the second in a series on the use of
representation clauses and implementation- dependent features
in Ada. It is the purpose of this document to specify a set
of questions relevant to the assessment of the support of
representation clauses and implementation- dependent features
provided by an Ada compiler. The questions identified are
categorized according to functionality and address both
qualitative and quantitative aspects.


Use of Representation Clauses and Implementation-Dependent Features in Ada: I. Overview, 
The
CMU/SEI-87-TR-14, ADA200601
Meyers, C., Cappellini, A.

This report, the first in a series, presents an overview of
the aspects of the Ada language relating to representation
clauses and implementation-dependent features. Particular
emphasis is given to the use of Ada for application to packed
data structures. This report is in part tutorial, and several
examples from real-time, mission-critical systems are
discussed in detail. A brief discussion of design guidelines
for the use of representation clauses and
implementation-dependent features is included.


Seeking the Balance Between Government and Industry Interests in Software Acquisition. Volume 
I. A Basis for Reconciling DoD and Industry Needs for Rights in Software
CMU/SEI-87-TR-13, ADA185742
Martin, A., Deasy, K.

The policy under which the Department of Defense (DoD)
acquires rights in software and technical data has, in the
past, been imbalanced in the direction of obtaining more
rights than necessary to meet its needs. As noted by the
Packard Commission, a more balanced policy is in the
interests of both the DoD and industry. The DoD has recently
adopted a new policy for acquiring rights in technical data,
and is developing a separate policy for acquiring rights in
software. This report offers several recommendations for
achieving a balanced policy as to government funded software,
privately funded software, and mixed funding software that
will meet the mission needs of the DoD while enabling
contractors to protect their proprietary interests, and
commercialize their software products.


Analysis of the Technical Order Production Process at Ogden Air Logistics Center and 
Recommendations for the Improvement of the Process, The
CMU/SEI-87-TR-12, ADA223960
Hansen, G.

This report details the process used by Ogden Air Logistics
Center to maintain Operational Flight Program Technical
Orders for the F-16 airplane. It is of general interest
because it makes recommendations for the improvement of the
process and also recommendations for technology insertion.
Since the Technical Order modification process is not
entirely different from documentation maintenance activities
in industry, this report is widely applicable.


Characterizing the Software Process: A Maturity Framework
CMU/SEI-87-TR-11, ADA182895
Humphrey, W.

Improvement in the performance of software development
organizations is an essential national need. The improvement
process has five basic elements: 1. an understanding of the
current status of the development process, 2. a vision of the
desired process, 3. a prioritized list of required
improvement actions, 4. a plan to accomplish these actions,
and 5. the resources and commitment to execute the plan. This
paper addresses the first three of these elements by
providing a model for software organizational improvement.
The structure of this model provides five maturity levels,
identifies the key improvements required at each level, and
establishes a priority order for implementation. This model
has been tested with a number of organizations and found to
reasonably represent the status and needs of actual software
development groups.


Guide to the Classification and Assessment of Software Engineering Tools, A
CMU/SEI-87-TR-10, ADA213968
Firth, R., Mosley, V., Pethia, R., Roberts Gold, L., Wood, W.

Software engineering tools are computer programs that assist
people in doing the work of software engineering. As
understanding of the software engineering process has
broadened and the need to solve problems has intensified,
there has been increasing interest in using software
engineering tools. Understanding what a tool does and
comparing it to similar tools are difficult tasks given the
diversity of functionality that exists. This report describes
a tool classification technique that helps those
investigating tools decide where a tool fits in the software
engineering process and identify what a tool does or doesn't
do. It also provides guidance to the tool evaluation process
and lists specific criteria that should be considered when
evaluating tools.


Ada Adoption Handbook
CMU/SEI-87-TR-9, ADA182023
Foreman, J., Goodenough, J. 

The Ada Adoption Handbook provides program managers with
information about how best to tap Ada's strengths and manage
this new software technology. Although the issues are
complex, they are not all unique to Ada. Indeed, many of
these issues must be addressed when using any language for
building sophisticated systems. The handbook addresses the
advantages and risks inherent in adopting Ada. Significant
emphasis has been placed on providing information and
suggesting methods that will help program and project
managers succeed in adopting Ada across a broad range of
application domains.

The handbook focuses on the following topics: program
management issues including costs and technical and program
control; Ada's goals and benefits; software tools with
emphasis on compiler validation and quality issues; the state
of Ada technology as it relates to system engineering; the
application of special purpose languages; issues related to
mixing Ada with other languages; possible productivity
benefits resulting from software reuse; and implications for
education and training.


Software Engineering Education: An Interim Report from the Software Engineering Institute
CMU/SEI-87-TR-8, ADA182003
Ford, G., Gibbs, N., Tomayko, J.

The goals and activities of the Software Engineering
Institute's Education Program are described. Two curriculum
recommendations are presented, one for a professional Master
of Software Engineering degree program, and the other for an
undergraduate project course in software engineering. Also
presented is an organizational structure for software
engineering curriculum content.


Tool Interface Technology
CMU/SEI-87-TR-7, ADA181156
Newcomer, J.

This report is one of a series of survey reports. It is not
intended to provide an exhaustive discussion of topics
pertinent to the area of user interface technology. Rather,
it is intended as an informative review of the technology
surveyed. These surveys were conducted in late 1985 and early
1986.


User Interface Technology Survey
CMU/SEI-87-TR-6, ADA181852
Feiler, P. 

This report is one of a series of survey reports. It is not
intended to provide an exhaustive discussion of topics
pertinent to the area of distributed systems technology.
Rather, it is intended as an informative review of the
technology surveyed. These surveys were conducted in late
1985 and early 1986.

One of the core technology areas in which project members
conducted a survey was user interface technology. This report
attempts to do two things: specify an understanding of user
interfaces by presenting a taxonomy that encompasses the
various aspects of user interfaces, and indicate the state of
the technology today by highlighting some of the major
issues.


Distributed Systems Technology Survey
CMU/SEI-87-TR-5, ADA181853
Cooper, E. 

This report is one of a series of survey reports. It is not
intended to provide an exhaustive discussion of topics
pertinent to the area of distributed systems technology.
Rather, it is intended as an informative review of the
technology surveyed. These surveys were conducted in late
1985 and early 1986.

One of the core technology areas in which project members
were interested is distributed systems technology. This
report surveys the technical issues involved in designing
distributed systems, with particular emphasis on those
aspects that affect software engineering environments.


Software and System Warranty Issues 
CMU/SEI-87-TR-4, ADA182982
Druffel, L., Wood, W., Pethia, R.

This report addresses technical and administrative issues
associated with the system warranty process, and recommends a
straightforward, two-page generic system warranty clause that
covers software, not in isolation, but as part of a warranted
system. The report describes one approach to relieving
problems of system failure, and addresses legal, technical,
and administrative issues that support warranty enforcement.
The goal is to ease the government's burden of proving the
existence of a defect for which the warranty clause provides
a remedy. The key to satisfying that goal is to develop
technical tests and specifications that provide objective and
demonstrable standards against which a claim for breach of
warranty can be measured.


Effect of Software Support Needs on DoD Software Acquisition Policy: Part 1: A Framework 
for Analyzing Legal Issues, The
CMU/SEI-87-TR-2, ADA178971
Martin, A., Deasy, K. 

This report summarizes the significant technical and
managerial considerations that affect the maintenance and
enhancement of software. Prior work suggested that it is
often in the acquisition of intellectual property needed to
maintain and enhance software that data rights disputes arise
between DoD and the private sector. For this reason, an
understanding of DoD's maintenance and enhancement
requirements is a necessary predicate toward shaping a data
rights/software acquisition policy that achieves the proper
balance between the intellectual property needs of DoD and
the proprietary interests of private industry. A survey of
software engineering literature revealed no study that
addressed this important subject.  Accordingly, the Software
Licensing Project undertook to examine the issue itself.
Although this report discusses technical and managerial
issues, it is principally intended as a guide for lawyers and
policymakers who deal with, and have regulatory
responsibility for, software and data rights acquisition
issues.


Evaluation of Ada Environments
CMU/SEI-87-TR-1, ADA180905
Weiderman, N., Altman, N., Borger, M., Klein, M., Landherr, S., Smeaton, R., D'Ippolito, R., 
Kochmar, J., Sun, A.

The full report provides a detailed description of the
methodology and examples of its usage. Chapter 1 gives an
extended cross-environment analysis of the results of the
project.  For each of five experiment groups, it compares
three APSEs. The chapter provides an overview of the results
of all the experiments and is written for the technical
manager.  Chapter 2 describes in detail the methodology used
for evaluating the environments, along with some of the
background information and references to previous work in
environment evaluation. Chapters 3 through 8 provide detailed
descriptions of the six experiment groups.  Here one can find
the information on particular criteria, questions, and life
cycle activities that were tested for each experiment, as
well as test scripts, checklists, and resulting data that
were collected.


Heterogeneous Machine Simulator, The
CMU/SEI-86-TR-6, ADA178771
Stockton, R. 

The heterogeneous machine simulator is a program which
attempts to simulate the proposed hardware for the
heterogeneous machine at a high level, along with the low
level programming abstractions which have been proposed. This
will, hopefully, provide: 1) a reasonable basis for
programmers to evaluate application designs in the absence of
the actual machine; and 2) a testbed for designers to
experiment with various reconfigurations which might be
difficult to perform on the machine itself. This document
presents a basic description of the system, and an example of
how a simulation may be run.


Summary of the SEI Workshop on Software Configuration Management
CMU/SEI-86-TR-5, ADA200085
Harvey, K.E.

This report summarizes the discussion held during the
Software Configuration Management meeting at the Software
Engineering Institute in Pittsburgh on 16 July 1986.


Specifying Functional and Timing Behavior for Real-Time Applications
CMU/SEI-86-TR-4, ADA178769
Barbacci, M., Wing, J. 

We present a notation and a methodology for specifying the
functional and timing behavior of real-time applications for
a heterogeneous machine. In our methodology, we build upon
well-defined, though isolated, pieces of previous work: Larch
and Real-Time Logic. In our notation, we strive to keep
separate the functional specification from the timing
specification so that a task's functionality can be
understood independent of its timing behavior. We show that
while there is a clean separation of concerns between these
two specifications, the semantics of both pieces as well as
their combination are simple.



Durra: A Task-Level Description Language Preliminary Reference Manual
CMU/SEI-86-TR-3, ADA178975
Barbacci, M. 

Durra is a language designed to support the development of
large-grained parallel programming applications. This
document is a preliminary reference manual for the syntax and
semantics of the language.


Proposal for a New "Rights in Software" Clause for Software Acquisitions by the Department 
of Defense
CMU/SEI-86-TR-2, ADA182093
Samuelson, P., Deasy, K., Martin, A.

This report recommends three distinct regulatory strategies
for addressing difficulties the DoD has been experiencing
with respect to legal issues related to software
acquisitions.  First, the report reiterates the Software
Licensing Project's earlier recommendation that the DoD adopt
the proposed Federal Acquisition Regulation (FAR) data rights
provisions instead of the proposed revisions to the DoD
supplement to the FAR (DoD FAR SUPP).  Secondly, in the event
that the DoD chooses to adopt a data rights procurement
policy different from that found in the data rights
provisions of the proposed FAR, this report recommends that
the DoD adopt a separate "Rights in Software" clause for
software acquisitions, rather than continuing the present
practice of handling software procurements under the "Rights
in Technical Data" clause. Reasons in support of a separate
software acquisition policy, as well as a beginning model
"Rights in Software" clause are offered.  Finally, in the
event that the DoD elects to retain the procurement format
presently found in the DoD FAR SUPP provisions governing
software and technical data acquisitions, this report offers
several concrete recommendations for changes to those
regulations which should result in a procurement policy which
more effectively meets the mission needs of the Defense
Department.


Toward a Reform of the Defense Department Software Acquisition Policy
CMU/SEI-86-TR-1, ADA169705
Samuelson, P. 

A series of about 120 interviews were conducted with DoD
personnel and others recommended by them. This report is an
organized catalog of software acquisition problems reported,
along with some assessments of their seriousness.



SPECIAL REPORTS

A Reuse-Based Software Development Methodology
CMU/SEI-92-SR-4
Kang, K., Cohen, S., Holibaugh, R., Perry, J., Peterson, A.

Software has been reused in applications development ever
since programming started.  However, the reuse practices have
mostly been ad hoc, and the potential benefits of reuse have
never been fully realized. Most of the available software
development methodologies do not explicitly identify reuse
activities. The Application of Reusable Software Components
Project of the Software Engineering Institute is developing a
reuse-based software development methodology, and the current
direction and the progress of the methodology work are
discussed in this paper.

The methodology is based on the life cycle model in
DoD-STD-2167A with refinement of each phase to identify reuse
activities. The reuse activities that are common across the
life cycle phases are identified as: 1) studying the problem
and available solutions to the problem and developing a reuse
plan or strategy, 2) identifying a solution structure for the
problem following the reuse plan, 3) reconfiguring the
solution structure to improve reuse at the next phase, 4)
acquiring, instantiating, and/or modifying existing reusable
components, 5) integrating the reused and any newly developed
components into the products for the phase, and 6) evaluating
the products. These activities are used as the base model for
defining the specific activities at each phase of the life
cycle.

This methodology focuses more on identification and
application of reusable resources than on construction of
reusable resources, and some enhancements in the construction
aspect might be necessary to make it more complete.

This methodology has never been applied; it will be used in
an application redevelopment experiment and then will be
improved based on our experience.


Fault Tolerant Systems Practitioner's Workshop June 10-11, 1991
CMU/SEI-91-SR-13
Heimerdinger, W.L., Weinstock, C.B.

On June 10-11, 1991, a Fault Tolerant Systems Practitioner's
Workshop was held at the Software Engineering Institute. The
purpose of the workshop was to attempt to identify how fault
tolerance is being applied today, why fault tolerance is
under used, and what can be done to bring fault tolerant
practices into wider use. Attendance at the workshop was
limited to a small number of practitioners who had
successfully applied fault tolerance in a systems context.
This report summarizes the proceedings of the workshop which
included a discussion of barriers to the deployment of fault
tolerant systems, a summary of the state of the practice, and
a discussion of the technology needs of fault tolerance.  The
report concludes with a discussion of ways the Software
Engineering Institute may be able to help bring fault
tolerant practices into wider use.


Context Analysis of the Movement Control Domain for the Army Tactical Command and Control 
System (ATCCS), A
CMU/SEI-91-SR-3, ADA248117
Peterson, A.S., Cohen, S.G.

This report describes the results of the first phase of a
domain analysis performed by the SEI's Domain Analysis
Project. The report establishes the context and scope of the
movement control domain within command and control (C2)
systems and in particular, ATCCS. It discusses the purpose of
a domain analysis and presents an overview of the method
being used to perform the analysis. The report describes both
the Army's use of ATCCS in achieving the Army mission and the
ATCCS software development strategy. A brief description of
Army C2systems lays a foundation for defining movement
control and its context in the ATCCS structure. Within this
context, the report identifies the key areas within movement
control that will be explored during the remainder of the
domain analysis.  The report also describes the approach for
performing the analysis and includes appendices providing
additional information about ATCCS, relevant terms, and
acronyms.


Comparison of Ada 83 and C++, A
CMU/SEI-91-SR-4, ADA2535646
Weiderman, N.H.

The purpose of this report is to provide technical input to
the Deputy Assistant Secretary of the Air Force for
Communications, Computers, and Logistics to assist that
office in preparing a business case for using Ada or C++ to
develop Corporate Information Management (CIM) systems.  This
technical input has been gathered by using the comparison
methodology of a 1985 Federal Aviation Administration (FAA)
report as a model, as well as by conducting interviews with
experts in Ada and C++. The conclusion of this report is that
technically neither language is clearly better than the
other; for government use, however, there is clear
justification and rationale for using Ada rather than C++ for
large complex systems with long lifetimes.


National Software Capacity: Near-Term Study (Executive Summary)
CMU/SEI-90-SR-12, ADA227564
Siegel, J., Stewman, S., Kondra, S., Larkey, P., Wagner, W. Gary

This document is a summary of the results of the near-term
study. The complete results are published in
CMU/SEI-90-TR-12.


Understanding the Adoption of Ada: Results of an Industry Survey
CMU/SEI-90-SR-10, ADA226725
Carlson, M., Smith, G. 

In 1983, the U.S. Department of Defense (DoD) established a
policy requiring the use of a new programming language, Ada,
for the development of all new Mission-Critical Computer
Resource (MCCR) software that it purchases. Firms that supply
the DoD with these systems have shown considerable variation
in their decisions to incorporate this new technology into
their products and production processes. This survey is part
of a multi- stage research project that sought to understand
the variability in firms' adoption and use of new information
technologies. The present report is a follow-up and
elaboration on a case study of the adoption of Ada which is
described in CMU/SEI-89-TR-28, Understanding the Adoption of
Ada: A Field Study Report.

Participants in the survey were 123 business and technical
people from 69 business units that supply the DoD with MCCR
software systems and services. The survey explored factors
pertaining to respondents' technical and market environments
in an attempt to describe depth of adoption and to describe
the differences between the firms with active Ada contracts
and those without active contracts. For firms that have
adopted Ada the report describes aspects of the language and
tools that are considered most useful in different
application areas.  At present, 85% of the units have
proposed to use Ada as a primary implementation language, and
70% have been awarded a contract in which Ada is the primary
implementation language. Within the context of this study,
Ada contract awards have been in the following application
areas: aircraft engines, attack radar, display processors,
flight control, flight trainers, ground control vehicles,
night vision, radar warning receivers, missiles, space
command and control, and tactical command and control. Survey
participants reported that Ada is being used in 50% of the
new development contracts and is being proposed for use in
60% of the contracts in the proposal stage.


DARK Technology Transition Plan
CMU/SEI-90-SR-6, ADA226695
Bamberger, J.

The DARK Transition Project Plan is aimed at the transition
of the concepts, models, and prototype implementation
developed by the DARK development project over the past two
years. This document:

	1.  Presents the background, rationale, and
conceptual goals of the DARK Project.

	2.  Provides an overview of the phase approach to
Technology Transition used within 	the SEI and its
relationship to DARK Project activities.

	3.  Describes the goals and objectives of the DARK
Transition Project in the context of the phase approach.

	4.  Defines the tasks constituting the DARK
Transition Project.


Domain Analysis Bibliography, A
CMU/SEI-90-SR-3, ADA248089
Hess, J., Cohen, S., Holibaugh, B., Kyang, K., Peterson, A., Novak, W., Carroll, P.

This document presents a bibliography of references on a
comparatively new discipline called domain analysis. This
discipline defines a process to identify and represent the
relevant information in a domain (a set of systems which
share common capabilities). The information is derived from:

The study of existing systems and their development histories

	1.  Knowledge captured from domain experts

	2.  Underlying theory

	3.  Emerging technology

The bibliography's purpose is to provide an historical
perspective on the field as well as a necessary background
for further work in the discipline.


Recommendations from the AIA/SEI Workshop on Research Advances Required for Real-Time 
Software Systems in the 1990s
CMU/SEI-89-SR-1
Sweet, W., Gagliardi, M., Klein, M., Little, R., Van Scoy, R., Veltre, R., Weinstock, C.

The Aerospace Industries Association (AIA) and the Software
Engineering Institute sponsored a workshop to facilitate
clear communication between the implementors of future
software-critical large systems and the professionals who
sponsor or perform software- related research. The workshop
was held at the SEI in Pittsburgh, Pennsylvania, on September
13-14, 1989. At the workshop, a representative group of
designers of major upcoming software systems discussed among
themselves and with representatives of the research community
the areas of software system technology that require research
advances to successfully implement these systems. The results
of the discussions are summarized in this report.

Conformance Criteria for the SAME Approach to Binding Ada Programs to SQL
SEI-89-SR-14
Moore, J. 

The structured query language (SQL) Ada Module Extensions
(SAME) form a method for the design and construction of Ada
database applications. The method is explained in a companion
document: "Guidelines for the Use of the SAME." In order to
enable the method to be referenced in requests for proposals
(RFPs) and development contracts, there must be some method
to determine if a given software design and implementation
conform to the SAME guidelines. Such conformance criteria are
contained in this report.


SAME Standard Package Installation Guide
SEI-89-SR-5
Graham, M.

This document outlines the procedures for installing the SQL
Ada Module Extensions (SAME) standard packages. It assumes
that the source of these packages has been off- loaded from
the distribution medium to a machine with the desired Ada
compiler.


Priority Ceiling Protocol: A Method for Minimizing the Blocking of High-Priority Ada Tasks, 
The
CMU/SEI-88-SR-4
Goodenough, J., Sha, L. 

The priority ceiling protocol is a new technique that
addresses the priority inversion problem, i.e., the
possibility that a high-priority task can be delayed by a
low-priority task.  Under the priority ceiling protocol, a
high priority task can be blocked at most once by a lower
priority task. This paper defines how to apply the protocol
to Ada. In particular, restrictions on the use of task
priorities in Ada are defined as well as restrictions on the
use of Ada tasking constructs. An extensive example
illustrating the behavior guaranteed by the protocol is
given.

This paper was presented at the 2nd International Workshop on
Real-Time Ada Issues in May 1988.


Practical Application of the Ceiling Protocol in a Real-Time System, A
CMU/SEI-88-SR-3, ADA206429
Goodenough, J., Locke, D. 

This paper briefly discusses some of the real-time design
issues that arise when using the priority ceiling protocol
for real-time systems. The paper shows a small real-time
system and shows how the code in the system could be
structured to satisfy the requirements of the ceiling
protocol.

This paper was presented at the 2nd International Workshop on
Real-Time Ada Issues in May 1988.


Conference Report: Overcoming the Disincentives to Modernization in the Defense Industry
CMU/SEI-88-SR-2
Hefley, B. 

The Procurement Committee of the National Security Industrial
Association held its annual winter meeting on 7-10 February
1988. This conference report documents the keynote address by
Thomas J. Murrin, Distinguished Service Professor in
Management and Technology, Carnegie Mellon University, along
with panel sessions on the topic of "Regulatory and Statutory
Direction of Acquisition" and "Financial Aspects of
Disincentives to Modernization".



		-----end Part 4 (of 5) -----

Barbara Zayas			Software Engineering Institute
(bjz@sei.cmu.edu)		(412) 268-6378
===========================================================================
Co-moderator:  Richard Golding, Computer & Information Sciences, UC Santa Cruz
	    compdoc-techreports-request@ftp.cse.ucsc.edu