ГОСТ Р ИСО/МЭК 15026-1—2016
[98]ISO/1EC 25000:2005. Software Engineering — Software product QualityRequirements and Evaluation
(SQuaRE) — Guide to SQuaRE
[99] ISO/lEC 25010:2011. Systems and software engineering — Systems and software product Quality Requirements
and Evaluation (SQuaRE) — System and software quality models
[100] ISO/lEC 25012:2008. Software engineering — Software product QualityRequirements and Evaluation
(SQuaRE) — Data quality model
[101] ISO/lEC 25020:2007. Software engineering — Software product Quality Requirements and Evaluation (SQuaRE)—
Measurementreference model and guide
[102] ISO/lEC 25030:2007. Software engineering — Software product QualityRequirements and Evaluation
(SQuaRE) — Quality requirements
[103] ISO/lEC 25040:2011. Systems and software engineering — Systems and software Quality Requirements and
Evaluation (SQuaRE) — Evaluation process
[104] ISO/lEC 25051:2006. Software engineering — Software product Quality Requirements and Evaluation
(SQuaRE) — Requirements (or quality of Commercial Off-The-Shelf (COTS) software product and Instructions for
testing
[105] ISO/lEC 26702:2007. Systems engineering — Application and management of the systems engmeenng process
[106] ISO/lEC 27000:2012, Information technology — Security techniques — Information security management
systems — Overview and vocabulary
[107] ISO/lEC 27001:2013, Information technology— Security techniques — Information security management
systems — Requirements
[108] ISO/lEC 27002:2013, Information technology — Security techniques — Code of practice for information security
controls
[109] ISO/lEC27004:2009.Informationtechnology — Securitytechniques— Informationsecurity
management — Measurement
[110] ISO/lEC 27005.2011, Information technology — Security techniques — Information security risk management
[111] ISO/lEC 27006:2011. Information technology— Security techniques — Requirements for bodies providing audit
and certification ofinformation security management systems
[112] ISO/lEC 27011:2008, Information technology — Security techniques — Information secunty management
guidelines (ortelecommunications organizations based on ISO/lEC 27002
[113] ISO/1EC/IEEE 42010.2011. Systems and software engineering — Architecture Description
1114) ISO/lEC 90003:2004, Software engineering Guidelines for the application of ISO 9001:2000 to computer software
[115] ISO/lEC TR 15446:2009. Information technology — Security techniques — Guide for the production of Protection
Profiles and Security Targets
[116] ISO/lEC TR 19791:2010, Information technology — Security techniques — Secunfy assessment of operational
systems
[117] ISO/lEC TR 24748-1.2010, Systems and software engmeenng — Life cycle management — Part 1: Guide for life
cycle management
[118] ISO/TR 16982:2002. Ergonomics of human-system interaction — Usability methods supporting human-centred
design
[119] ISO/TR 18529:2000. Ergonomics — Ergonomics ofhuman-system interaction — Human-centred lifecycle process
descoptions
[120] ISO/TR 27809:2007, Health Informatics — Measures for ensuring patient safety of health software
[121] ISO/TS 25238:2007, Health informatics — Classification ofsafety risks from health software
[122] Kazman R., Asundi J.. Klein M. Making Architecture Design Decisions: An Economic Approach. SEI-2002-TR-035.
Software Engineering Institute, Carnegie Mellon University. 2002
[123] Kazman R „ Klein M.. Clements P. ATAM: Method for Architecture Evaluating the Quality Attributes of a Software
Architecture. Technical Report CMU/SEI-200-TR004. Software Engineering Institute. Carnegie Mellon University.
2000
[124] KellyT.Argu/ngSa/efy — A SystematicApproach to Managing Safety Cases. DoctonalThesis — UniversItyofYork.
Department of Computer Science. Sept 1998
[125] KellyT.Reviewing AssuranceArguments — A Step-by-Step Approach. Workshop on Assurance Cases for Security:
The Metrics Challenge. International Conference on Dependable Systems and Networks. 2007
[126] KellyT..&W eaverR. The GoalStructuring Notation — A Safe/yArgomenf/Vofa/forJ. Workshopon Assurance Cases:
Best Practices. Possible Obstacles, and Future Opportunities. Florence. Italy. July 2004