Issued in July 1977 as NBS Special Publication 500-11, this guide explains software project management and quality control for managers, technical staff, and executives, particularly in the Federal government. It covers the software life cycle, requirements definition, project organization, design and programming, testing, maintenance, production tools, and controls appropriate to different project sizes. It defines more than twenty quality control techniques and includes recommended milestones, organizational diagrams, and references.
Free preview text
The first 5 pages, shown as text so search engines and readers can find this document.
Page 1
A11103 08^523
NAFL INST OF STANDARDS & TECH R.I.C,
A1 1 1 03089223
Fife, Dennis W/Computer software managem
QC100 .U57 N0.500-, 11, 1977 C.I NBS-PUB
CE & TECHNOLOGY;
COMPUTER
SOFTWARE MANAGEME^
A PRIMER FOR
PROJECT MANAGEMENT
AND OUALITY CONTROL
500-11
7
NBS Special Publication 500-11
U.S. DEPARTMENT OF COMMERCE
National Bureau of Standards
Page 2
NATIONAL BUREAU OF STANDARDS
The National Bureau of Standards^ was established by an act of Congress March 3, 1901. The Bureau's overall goal is to
strengthen and advance the Nation's science and technology and facilitate their effective application for public benefit. To this
end, the Bureau conducts research and provides: (1) a basis for the Nation's physical measurement system, (2) scientific and
technological services for industry and government, (3) a technical basis for equity in trade, and (4) technical services to pro-
mote public safety. The Bureau consists of the Institute for Basic Standards, the Institute for Materials Research, the Institute
for Applied Technology, the Institute for Computer Sciences and Technology, the Office for Information Programs, and the
Office of Experimental Technology Incentives Program.
THE INSTITUTE FOR BASIC STANDARDS provides the central basis within the United States of a complete and consist-
ent system of physical measurement; coordinates that system with measurement systems of other nations; and furnishes essen-
tial services leading to accurate and uniform physical measurements throughout the Nation's scientific community, industry,
and commerce. The Institute consists of the Office of Measurement Services, and the following center and divisions:
Applied Mathematics — Electricity — Mechanics — Heat — Optical Physics — Center for Radiation Research — Lab-
oratory Astrophysics" — Cryogenics- — Electromagnetics - — Time and Frequency^.
THE INSTITUTE FOR MATERIALS RESEARCH conducts materials research leading to improved methods of measure-
ment, standards, and data on the properties of well-characterized materials needed by industry, commerce, educational insti-
tutions, and Government; provides advisory and research services to other Government agencies; and develops, produces, and
distributes standard reference materials. The Institute consists of the Office of Standard Reference Materials, the Office of Air
and Water Measurement, and the following divisions:
Analytical Chemistry — Polymers — Metallurgy — Inorganic Materials — Reactor Radiation — Physical Chemistry.
THE INSTITUTE FOR APPLIED TECHNOLOGY provides technical services developing and promoting the use of avail-
able technology; cooperates with public and private organizations in developing technological standards, codes, and test meth-
ods; and provides technical advice services, and information to Government agencies and the public. The Institute consists of
the following divisions and centers:
Standards Application and Analysis — Electronic Technology — Center for Consumer Product Technology: Product
Systems Analysis; Product Engineering — Center for Building Technology: Structures, Materials, and Safety; Building
Environment; Technical Evaluation and Application — Center for Fire Research: Fire Science; Fire Safety Engineering.
THE INSTITUTE FOR COMPUTER SCIENCES AND TECHNOLOGY conducts research and provides technical services
designed to aid Government agencies in improving cost effectiveness in the conduct of their programs through the selection,
acquisition, and effective utilization of automatic data processing equipment: and serves as the principal focus wthin the exec-
utive branch for the development of Federal standards for automatic data processing equipment, techniques, and computer
languages. The Institute consist of the following divisions:
Computer Services — Systems and Software — Computer Systems Engineering — Information Technology.
THE OFFICE OF EXPERIMENTAL TECHNOLOGY INCENTIVES PROGRAM seeks to affect public policy and process
to facilitate technological change in the private sector by examining and experimenting with Government policies and prac-
tices in order to identify and remove Government-related barriers and to correct inherent market imperfections that impede
the innovation process.
THE OFFICE FOR INFORMATION PROGRAMS promotes optimum dissemination and accessibility of scientific informa-
tion generated within NBS; promotes the development of the National Standard Reference Data System and a system of in-
formation analysis centers dealing with the broader aspects of the National Measurement System; provides appropriate services
to ensure that the NBS staff has optimum accessibility to the scientific information of the world. The Office consists of the
following organizational units:
Office of Standard Reference Data — Office of Information Activities — Office of Technical Publications — Library —
Office of International Standards — Office of International Relations.
1 Headquarters and Laboratories at Gaithersburg, Maryland, utiless otherwise noted; mailing address Washington, D.C. 20234.
' Located at Boulder, Colorado 80302.
Page 3
ANDAJRDS
1977
COMPUTER SCIENCE & TECHNOLOGY:
Computer Software Management: A Primer for
Project Management and Quality Control
Dennis W. Fife
Systems and Software Division
Institute for Computer Science and Technology
National Bureau of Standards
Washington, D.C. 20234
U.S. DEPARTMENT OF COMMERCE, Juanita M. Kreps, Secretary
Dr. Sidney Harman, Under Secretary
Jordan J. Baruch. Assistant Secretary for Science and Technology
i^liMATIONAL BUREAU OF STANDARDS. Ernest Ambler, Acting Director
Issued July 1977
Page 4
Reports on Computer Science and Technology
The National Bureau of Standards has a special responsibility within the Federal
Government for computer science and technology activities. The programs of the
NBS Institute for Computer Sciences and Technology are designed to provide ADP
standards, guidelines, and technical advisory services to improve the effectiveness of
computer utilization in the Federal sector, and to perform appropriate research and
development efforts as foundation for such activities and programs. This publication
series will report these NBS efforts to the Federal computer community as well as to
interested specialists in the academic and private sectors. Those wishing to receive
notices of publications in this series should complete and return the form at the end
of this publication.
National Bureau of Standards Special Publication 500-11
Nat. Bur. Stand. (U.S.), Spec. Publ. 500-11, 58 pages (July 1977)
CODEN: XNBSAV
Library of Congress Cataloging in Publication Data
Fife, Dennis W.
Computer software management.
(Computer science & technology) (NBS special publication ; 500-1 1)
Bibliography: p.
Supt. of Docs. No.: Ci3. 10:500-1
1. Electronic data processing—Management, 2. Programming
(Electronic computers)— Management. I. Title. II. Series. III. Series:
United States. National Bureau of Standards. Special publication ;
500-11.
QC100.U57 no. 500-11 [QA76.9.M3] 602Ms [658'.05'4042] 77-608127
U.S. GOVERNMENT PRINTING OFFICE
WASHINGTON: 1977
For sale by the Superintendent of Documents, U.S. Government Printing Office, Washington, D.C. 20402 - Price $2
Stock No. 003-<X)3-O1796-7
Page 5
PKEFACt.
Ttie National Bureau of Standards is tne
primary technical advisor on computers tor
government agencies (Brooks Act, Public Law
&9-3k)6) . NBb assists Federal agencies in specitic
projects, ana so obtains first-hand experience
with agency problems and competencies. This guide
was prepared drawing upon extensive contacts with
government computing personnel, and using the
published recommendations of authorities m
software management. A variety of executive
guides and primers in other fields were reviewed
in choosing the scope and approach to the material
covered here. uther staff members ot trie
Institute for Computer Sciences and Technology
assisted by reviewing the material as it was
developed. The author was helped particularly by
the constructive comments of I. Trotter Hardy ana
Theoaore Linden.
NOTICE TO READERS
This guide is intended to become a standard
reference for managing Federal government software
projects. Comments by the readers on its
completeness, clarity, etc. would be valuable in
making appropriate revisions for this purpose. A
postage-free reader evaluation form is included at
the back of the report, and you are encouraged to
complete and return it.
-iii-
Computer Software Management: A Primer for Project Management and Quality Control: summary, contents and background
This guide helps you understand the scope of Computer Software Management: A Primer for Project Management and Quality Control before or alongside reading the original document. It is based on the catalogue record, credited creator, source, classification and topics shown on this page. It does not replace the original work and does not invent claims about passages that Doxxly cannot verify.
Summary and overview
Computer Software Management: A Primer for Project Management and Quality Control is a 64-page documentcredited to Nadia G. Ingleby. Issued in July 1977 as NBS Special Publication 500-11, this guide explains software project management and quality control for managers, technical staff, and executives, particularly in the Federal government. It covers the software life cycle, requirements definition, project organization, design and programming, testing, maintenance, production tools, and controls appropriate to different project sizes. It defines more than twenty quality control techniques and includes recommended milestones, organizational diagrams, and references. It appears in the Technology & Security collection, which groups it with other material that readers may use for comparison and further study.
The item can be approached in several ways. A reader looking for a quick orientation can begin with the free five-page preview, inspect the page structure and use the metadata to judge relevance. Someone undertaking deeper research can work through the complete file, search its indexed text, record useful page references and compare its treatment of Software management, Project management, Software quality control, Software engineering, Software testing, Software maintenance, Federal government, NBS Special Publication, 1977 with the related resources linked below.
Rather than reducing the work to a single claim, this page treats it as a source that should be read in context. The title, creator, publication source, licence and format all help explain what kind of evidence it may offer. Readers should distinguish the original author's statements from Doxxly's catalogue description, and should cite the original edition when using the material in academic, professional or published work.
Key topics and reader takeaways
The catalogue connects this document with Software management, Project management, Software quality control, Software engineering, Software testing, Software maintenance, Federal government, NBS Special Publication, 1977. These terms offer practical entry points rather than a substitute for close reading. Start by identifying the definitions, examples, arguments, tables or visual explanations attached to each topic. Then note where the creator draws connections, makes distinctions or moves from background material to a conclusion, recommendation, calculation or narrative development.
A useful reading method is to separate description from interpretation. First record what the item actually presents: names, headings, figures, formulas, quotations or stated propositions. Next consider why those details matter within the whole work. Finally compare them with another source from the same subject area. This process helps turn a long digital file into evidence that can be evaluated rather than merely skimmed.
Table of contents and reading guide
The following is an editorial content guide based on the verified catalogue topics. It is not represented as the original author's formal table of contents. Use it to organise notes while moving through the 64 pages in the player.
Part 1
Software management
Use this section of the reading guide to identify how Software management appears in Computer Software Management: A Primer for Project Management and Quality Control, note important terms, and connect the subject to the wider purpose of the work.
Part 2
Project management
Use this section of the reading guide to identify how Project management appears in Computer Software Management: A Primer for Project Management and Quality Control, note important terms, and connect the subject to the wider purpose of the work.
Part 3
Software quality control
Use this section of the reading guide to identify how Software quality control appears in Computer Software Management: A Primer for Project Management and Quality Control, note important terms, and connect the subject to the wider purpose of the work.
Part 4
Software engineering
Use this section of the reading guide to identify how Software engineering appears in Computer Software Management: A Primer for Project Management and Quality Control, note important terms, and connect the subject to the wider purpose of the work.
Part 5
Software testing
Use this section of the reading guide to identify how Software testing appears in Computer Software Management: A Primer for Project Management and Quality Control, note important terms, and connect the subject to the wider purpose of the work.
Part 6
Software maintenance
Use this section of the reading guide to identify how Software maintenance appears in Computer Software Management: A Primer for Project Management and Quality Control, note important terms, and connect the subject to the wider purpose of the work.
Part 7
Federal government
Use this section of the reading guide to identify how Federal government appears in Computer Software Management: A Primer for Project Management and Quality Control, note important terms, and connect the subject to the wider purpose of the work.
Part 8
NBS Special Publication
Use this section of the reading guide to identify how NBS Special Publication appears in Computer Software Management: A Primer for Project Management and Quality Control, note important terms, and connect the subject to the wider purpose of the work.
When a heading in the original differs from this guide, follow the original heading in your citation. Page numbers can also vary between editions. Doxxly's direct page field is useful for navigation, but formal references should include the title, creator, source and edition details available in the file itself.
About Nadia G. Ingleby
Doxxly credits Nadia G. Ingleby as the author or creator of Computer Software Management: A Primer for Project Management and Quality Control. This page does not add an unverified biography, job title or institutional affiliation. The attribution is preserved so readers can distinguish the creator from the hosting library and follow the original record when an external author link is available.
Author context matters because a work reflects a particular purpose, audience and point of view. Before relying on the material, consider what the creator set out to explain, when the source was produced and whether later research or revised guidance should also be consulted. For literature and philosophy, compare translations and editions; for technical material, check whether a newer version has superseded the one shown here.
About the source organisation
The recorded source for this item is govinfo.gov. Doxxly provides access and discovery tools but does not claim to be the original publisher unless explicitly stated. Source links, creator attribution and the recorded Publicly available file collected for editorial review licence are displayed to help readers assess provenance and permitted use.
Provenance is especially important for reports, standards, presentations and working spreadsheets. Check the original source for amendments, supporting files and current policy. A trustworthy research workflow keeps the source URL with any notes or downloaded copy, verifies important figures against the original, and avoids treating an archived document as automatically current.
Begin with the title and opening pages, then use the guide above to decide whether to read sequentially or move to a particular topic. The Doxxly player provides previous and next navigation, a direct page field, zoom steps, fit-to-width and fit-to-page modes, rotation and fullscreen. These controls are useful when a page contains small type, a wide table, an image, a scanned layout or a dense sequence of notes.
The first five pages are open to every visitor. A plan unlocks the complete item and full-document search. Search is best used for distinctive names, technical terms or short phrases; broad words can produce too many possible contexts. When you find a useful passage, read the surrounding pages so that a sentence, chart or formula is not separated from its explanation.
If downloading is enabled, members can obtain the original PDF file. Keep the original format when formulas, slide sequencing, pagination or layout carries meaning. Respect the Publicly available file collected for editorial review terms displayed on this page, and use the rights-report link if you believe the attribution or availability needs review.
Research questions to consider
As you read Computer Software Management: A Primer for Project Management and Quality Control, ask which audience the creator addresses, what problem or idea organises the work, what evidence is presented, and which assumptions remain unstated. Note whether important terms are defined consistently and whether examples represent a broader pattern or a narrow case. For quantitative material, record units, time periods, formulas and data sources. For interpretive material, separate the creator's language from your own summary.
A second set of questions concerns relevance today. Which parts remain durable, which depend on their historical or institutional setting, and what would need confirmation from a newer source? Following the tags and the Technology & Security collection can reveal useful comparisons. Agreement between sources can strengthen confidence, while disagreement can point to changing definitions, methods, evidence or priorities.
Finally, decide what you need from the item: background knowledge, a quotation, a worked example, a model, a visual explanation or a starting bibliography. That purpose should guide the depth of reading and the notes you keep. Doxxly helps locate and navigate the source; careful interpretation remains the reader's responsibility.