ГОСТ Р 54582—2011
Библиография
[1]ISO/IEC TR 9126-2
[2]ISO/IEC TR 9126-3
[3]ISO/IEC TR 9126-4
[4]ISO 13407
[5]ISO/IEC 14598-2
[6]ISO/IEC 14598-3
[7]ISO/IEC 14598-4
[8]ISO/IEC 14598-5
[9]ISO/IEC 14598-6
[10]ISO/IEC TR 15271
[11]ISO/IEC 17024
[12]ISO/IEC 17025
[13] ISO/IEC 17050-1
[14] ISO/IEC 17050-2
[15]ISO/IEC TR 19760
[16]ISO/IEC 25000
[18]ISO/IEC 25021
[19]ISO/IEC 25030
42
Software engineering — Product quality — Part 2: External metrics
Software engineering — Product quality — Part 3: Internal metrics
Software engineering — Product quality — Part 4: Quality in use metrics
Human-centred design processes for interactive systems
Software engineering — Product evaluation — Part 2: Planning and management
Software engineering — Product evaluation — Part 3: Process for developers
Software engineering — Product evaluation — Part 4: Process for acquirers
Information technology — Software product evaluation — Part 5: Process for evaluators
Software engineering — Product evaluation — Part 6: Documentation of evaluation modules
Information technology — Guide for ISO/IEC 12207
Conformity assessment — General requirements for bodies operating certifi cation of persons
General requirements for the competence of testing and calibration laboratories
Note: EN ISO 17025 is identical to CEN/CENELEC EN ISO 17025
Note: ISO/IEC 17025 replaces ISO Guide 25 and CEN/CENELEC EN 45001
Conformity assessment — Supplier’s declaration of conformity — Part 1: General requirements
Conformity assessment — Supplier’s declaration of conformity — Part 2: Supporting
documentation
Systems engineering — Guide for ISO/IEC 15288 (System Life Cycle Processes)
Software Engineering — Software Product Quality Requirements and Evaluation (SQuaRE)—
Guide to SquaRE (presently FCD)
[17]ISO/IEC 25020Software and System Engineering — Software quality requirements and evaluation
(SQuaRE) — Quality measurement — Measurement reference model and guide (presently
CD)
Software and System Engineering — Software Product Quality Requirements and Evaluation
(SQuaRE) — Measurement Primitives (presently CD)
Software engineering — Software quality requirements and evaluation (SQuaRE) — Quality
requirements (presently CD)
[20]SCT. Strict Conformance Testing
NPL Report, March 1997. (National Physical Laboratory, Teddington, Middlesex TW11 OLW, UK)
[21]A Systems Engineering Capability Maturity Model (SE-CMM Model), Version 1.1
(CMU/SEI-95-MM-003), November 1995. Software Engineering Institute, Carnegie Mellon University, Pittsburgh,
PA 15213-3890, USA.
Note: The model may be available as http://www.sei.cmu.edu/pub/documents/95.reports/pdf/mm003.95.rjdf
[22]A Description of the Systems Engineering Capability Maturity Model Appraisal Method (SE-CMM Method), Version 1.1 A
(CMU/SEI-96-HB-004), March 1996. Software Engineering Institute, Carnegie Mellon University, Pittsburgh, PA
15213-3890, USA
Note: The model may be available as http://www.sei.cmu.edu/pub/documents/96.reports/pdf/hb004.96.pdf
[23]Capability Maturity Model® for Software (SW-CMM®) v1.1
National Technical Information Service (NTIS), US Department of Commerce, Springfield, VA 22161, USA
[24]System Security Engineering Capability Maturity Model, Model Description (SSE-CMM Model), Version 2.0
April 1, 1999 ISSEA, 13873 Park Center Road, Suite 200, Herndon, VA 20171, USA.
Note: The latest version is available at http://www.sse-cmm.om/model/model.asp
[25]System Security Engineering Capability Maturity Model, Appraisal Methodology (SSE-CMM Method), Version 2.0
April 16, 1999. ISSEA, 13873 Park Center Road, Suite 200, Herndon, VA 20171, USA.
Note: The latest version is available at http://www.sse-cmm.org/org/org.asp
[26]Trusted Capability Maturity Model, Version 2.0
NSA, June 20, 1996 (unreleased US Government document)
[27]A Tailoring of the CMM for the Trusted Software Domain
Kitson, David H in Proceedings of the Seventh Annual Software Technology Conference. Salt Lake City, Utah,
April 9-14, 1995
[28]Trust Technology Assessment Program (TTAP)
Note: Information may be available at http://www.radium.ncsc.mil/tpep/ttap/index.html
[29]Trusted Software Methodology (volumes 1 and 2)
SDI-S-SD-91-000007, June 17, 1992. US Dept. of Defense, Strategic Defense Initiative Organization, Washington,
D.C.