leff@smu.UUCP (Laurence Leff) (08/15/89)
PART I 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
-------------------------------------------------------------------------------
Technical Reports
-------------------------------------------------------------------------------
CMU/SEI-86-TR-1, ADA169705
Samuelson
Toward a Reform of the Defense Department Software Acquisition Policy
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.
CMU/SEI-86-TR-2, ADA182093
Samuelson, Deasy, Martin, A.
Proposal for a New "Rights in Software" Clause for Software Acquisitions by
the Department of Defense
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.
CMU/SEI-86-TR-3, ADA178975
Barbacci
Durra: A Task-Level Description Language Preliminary Reference Manual
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.
CMU/SEI-86-TR-4, ADA178769
Barbacci, Wing
Specifying Functional and Timing Behavior for Real-Time Applications
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.
CMU/SEI-86-TR-5, ADA200085
Harvey
Summary of the SEI Workshop on Software Configuration Management
This report summarizes the discussion held during the Software Configuration
Management meeting at the Software Engineering Institute in Pittsburgh on 16
July 1986.
CMU/SEI-86-TR-6, ADA178771
Stockton
The Heterogeneous Machine Simulator
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.
CMU/SEI-87-TR-1, ADA180905
Weiderman, Habermann, Borger, Klein, M., Landherr, Smeaton, Altman,
D'Ippolito, Kochmar, Sun
Evaluation of Ada Environments
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.
CMU/SEI-87-TR-2, ADA178971
Martin, Deasy
The Effect of Software Support Needs on DoD Software Acquisition
Policy: Part 1: A Framework for Analyzing Legal Issues
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.
CMU/SEI-87-TR-4, ADA182982
Druffel, Wood, Pethia, Greenberger, Shuba
Software and System Warranty Issues
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.
CMU/SEI-87-TR-5
Cooper
Distributed Systems Technology Survey
ADA181853
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.
CMU/SEI-87-TR-6, ADA181852
Feiler
User Interface Technology Survey
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.
CMU/SEI-87-TR-7, ADA181156
Newcomer
Tool Interface Technology
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.
CMU/SEI-87-TR-8, ADA182003
Ford, Gibbs, Tomayko
Software Engineering Education: An Interim Report from the Software
Engineering Institute
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.
CMU/SEI-87-TR-9, ADA182023
Foreman, Goodenough
Ada Adoption Handbook
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.
CMU/SEI-87-TR-10
Firth, Mosley, Pethia, Roberts, Wood, W.
A Guide to the Classification and Assessment of Software Engineering Tools
ADA182895
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.
CMU/SEI-87-TR-11, ADA182895
Humphrey
Characterizing the Software Process: A Maturity Framework
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.
CMU/SEI-87-TR-12
Hansen, Kellner, Over, Przybylinski
The Analysis of the Technical Order Production Process at Ogden
Air Logistics Center and Recommendations for the Improvement of the Process
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 provement 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.
CMU/SEI-87-TR-13, ADA185742
A. Martin, Deasy
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
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 ADA185742
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.
CMU/SEI-87-TR-14, ADA200601
Meyers, Cappellini
The Use of Representation Clauses and Implementation-Dependent Features in
Ada: I. Overview
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.
CMU/SEI-87-TR-15, ADA188925
Meyers, Cappellini
The Use of Representation Clauses and Implementation-Dependent Features in
Ada: IIA. Evaluation Questions
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.
CMU/SEI-89-TR-16, ESD-TR-89-24
Graham, M.
Guidelines for the Use of the SAME
These guidelines describe the Structured Query Language (SQL) Ada Module
Extensions, or SAME, a method for the construction of Ada applications that
access database management systems whose data manipulation language is SQL. As
its name implies, the SAME extends the module language defined in the ANSI SQL
standard to fit the needs of Ada. The defining characteristic of the use of
the module language is that the SQL statements appear together, physically
separated from the Ada application, in an object called the module. The Ada
application accesses the module through procedure calls.
The primary audience for this document consists of application developers and
technicians creating Ada applications for SQL database management systems. The
document contains a complete description of the SAME, including its motivation.
CMU/SEI-87-TR-16, ADA183429
Humphrey, Kitson
Preliminary Report on Conducting SEI-Assisted Assessments of
Software Engineering
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 (SEI) 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.
--listing continued--listing continued--listing continued--listing continued--
--
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