HOME   Cart(0)   Quotation   About-Us Policy PDFs Standard-List
www.ChineseStandard.net Database: 189759 (19 Oct 2025)

GB/T 8567-2006 English PDF

GB/T 8567: Evolution and historical versions

Standard IDContents [version]USDSTEP2[PDF] delivered inStandard Title (Description)StatusPDF
GB/T 8567-2006EnglishRFQ ASK 3 days [Need to translate] Specification for computer software documentation Valid GB/T 8567-2006
GB/T 8567-1988EnglishRFQ ASK 11 days [Need to translate] Guidelines for computer software product development documentation Obsolete GB/T 8567-1988

PDF similar to GB/T 8567-2006


Standard similar to GB/T 8567-2006

GB/T 25000.51   GB/T 28172   GB/T 20918   GB/T 8566   GB/T 9386   GB/T 9385   

Basic data

Standard ID GB/T 8567-2006 (GB/T8567-2006)
Description (Translated English) Specification for computer software documentation
Sector / Industry National Standard (Recommended)
Classification of Chinese Standard L77
Classification of International Standard 35.080
Word Count Estimation 131,112
Date of Issue 2006-03-14
Date of Implementation 2006-07-01
Older Standard (superseded by this standard) GB/T 8567-1988
Quoted Standard GB/T 8566-2001; GB/T 11457-2006
Regulation (derived from) China Announcement of Newly Approved National Standards No. 4, 2006 (No. 91 overall)
Issuing agency(ies) General Administration of Quality Supervision, Inspection and Quarantine of the People's Republic of China, Standardization Administration of the People's Republic of China
Summary This standard specifies requirements for the software development process and management process should be prepared in the preparation of the main document and its content, format the basic requirements. In principle this standard applies to all types of software product development process and management process. Users can according to the actual situation on the appropriate standard trim (can cut the desired document type, but also on the content specifications for proper cropping). From the perspective of software documentation using software users can be divided into user documentation needs and developers in the development process using internal documents (development documentation) categories. The supplier shall provide documentation of the type and size of the software required by the recipient and the supplier in the contract.