skip to main content
OSTI.GOV title logo U.S. Department of Energy
Office of Scientific and Technical Information

Title: User systems guidelines for software projects

Abstract

This manual presents guidelines for software standards which were developed so that software project-development teams and management involved in approving the software could have a generalized view of all phases in the software production procedure and the steps involved in completing each phase. Guidelines are presented for six phases of software development: project definition, building a user interface, designing software, writing code, testing code, and preparing software documentation. The discussions for each phase include examples illustrating the recommended guidelines. 45 refs. (DWL)

Authors:
 [1]
  1. (ed.)
Publication Date:
Research Org.:
Lawrence Livermore National Lab., CA (USA)
OSTI Identifier:
5704829
Report Number(s):
UCID-20643
ON: DE86010490
DOE Contract Number:  
W-7405-ENG-48
Resource Type:
Technical Report
Resource Relation:
Other Information: Portions of this document are illegible in microfiche products. Original copy available until stock is exhausted
Country of Publication:
United States
Language:
English
Subject:
99 GENERAL AND MISCELLANEOUS//MATHEMATICS, COMPUTING, AND INFORMATION SCIENCE; COMPUTER CODES; DESIGN; DOCUMENTATION; MANAGEMENT; MANUALS; TESTING; PROGRAMMING; RECOMMENDATIONS; DOCUMENT TYPES; 990200* - Mathematics & Computers

Citation Formats

Abrahamson, L. User systems guidelines for software projects. United States: N. p., 1986. Web. doi:10.2172/5704829.
Abrahamson, L. User systems guidelines for software projects. United States. doi:10.2172/5704829.
Abrahamson, L. Tue . "User systems guidelines for software projects". United States. doi:10.2172/5704829. https://www.osti.gov/servlets/purl/5704829.
@article{osti_5704829,
title = {User systems guidelines for software projects},
author = {Abrahamson, L.},
abstractNote = {This manual presents guidelines for software standards which were developed so that software project-development teams and management involved in approving the software could have a generalized view of all phases in the software production procedure and the steps involved in completing each phase. Guidelines are presented for six phases of software development: project definition, building a user interface, designing software, writing code, testing code, and preparing software documentation. The discussions for each phase include examples illustrating the recommended guidelines. 45 refs. (DWL)},
doi = {10.2172/5704829},
journal = {},
number = ,
volume = ,
place = {United States},
year = {1986},
month = {4}
}