Find the standard you are looking for at Engineering360. Documents are available for purchase from the IHS Standards Store.

1 - 20 of 57 results

CRC - AUE6380 - SECURITY SOFTWARE DEVELOPMENT : ASSESSING AND MANAGING SECURITY RISKS Organization: CRC
Date: 2008-10-23
Description: Drawing from the author’s extensive experience as a developer, Secure Software Development: Assessing and Managing Security Risks illustrates how software application security can be best, and most cost-effectively, achieved when developers monitor and regulate risks early on, integrating assessment and management into the development life cycle.
SAE JA1003 - SOFTWARE RELIABILITY PROGRAM IMPLEMENTATION GUIDE Organization: SAE
Date: 2004-01-01
Description: Custom software is generally newly developed software or a significant rework/upgrade of existing software that is for use with a specific application. OTS software sources include commercial vendors, government, and industry. The guidance in this document is generally applicable throughout the complete life cycle, although specific approaches may be more effectively applied at specific life cycle points depending on the software source, application, and pedigree.
FAA - FO 1370.112 - FAA APPLICATION SECURITY POLICY Organization: FAA
Date: 2010-10-05
Description: the establishment of the minimum required SDLC activities that must be included in all FAA software system development efforts, regardless of the platform or the lines of business staff office's (LOB/SO) iterative or traditional life cycle process in use; and b. that the LOB/SOs, all program and project managers, and all software development teams adequately plan for security by properly identifying, assessing and mitigating risks; including security controls in the software system design; adhering to agency and Federal Information Technology (IT) policies and regulations, and continually monitoring and assessing security through system retirement.
DSF/ISO/IEC FCD 15026-3 - INFORMATION TECHNOLOGY - SYSTEM AND SOFTWARE INTEGRITY LEVELS Organization: DS
Description: This part of ISO/IEC 15026 is applicable to systems and software and is intended for use by: a) Definers of integrity levels such as industry and professional organizations, standards organizations, and government agencies. b) Users of integrity levels such as developers and maintainers, suppliers and acquirers, users, and assessors of systems or software and for the administrative and technical support of systems and/or software products.
DS/ISO/IEC 15026-3 - SYSTEMS AND SOFTWARE ENGINEERING - SYSTEMS AND SOFTWARE ASSURANCE - PART 3: SYSTEM INTEGRITY LEVELS Organization: DS
Date: 2015-12-03
Description: This part of ISO/IEC 15026 is applicable to systems and software and is intended for use by the following: a) definers of integrity levels such as industry and professional organizations, standards organizations, and government agencies; b) users of integrity levels such as developers and maintainers, suppliers and acquirers, system or software users, assessors of systems or software and administrative and technical support staff of systems and/or software products.
ISO/IEC 15026-3 - SYSTEMS AND SOFTWARE ENGINEERING - SYSTEMS AND SOFTWARE ASSURANCE - PART 3: SYSTEM INTEGRITY LEVELS - SECOND EDITION Organization: ISO
Date: 2015-12-01
Description: This part of ISO/IEC 15026 is applicable to systems and software and is intended for use by the following: a) definers of integrity levels such as industry and professional organizations, standards organizations, and government agencies; b) users of integrity levels such as developers and maintainers, suppliers and acquirers, system or software users, assessors of systems or software and administrative and technical support staff of systems and/or software products.
CSA ISO/IEC 15026-3 - SYSTEMS AND SOFTWARE ENGINEERING - SYSTEMS AND SOFTWARE ASSURANCE - PART 3: SYSTEM INTEGRITY LEVELS Organization: CSA
Date: 2016-01-01
Description: This part of ISO/IEC 15026 is applicable to systems and software and is intended for use by the following: a) definers of integrity levels such as industry and professional organizations, standards organizations, and government agencies; b) users of integrity levels such as developers and maintainers, suppliers and acquirers, system or software users, assessors of systems or software and administrative and technical support staff of systems and/or software products.
DSF/ISO/IEC DIS 15026-3 - SYSTEMS AND SOFTWARE ENGINEERING -- SYSTEMS AND SOFTWARE ASSURANCE-- PART 3: SYSTEM INTEGRITY LEVELS Organization: DS
Description: This part of ISO/IEC 15026 is applicable to systems and software and is intended for use by: a) definers of integrity levels such as industry and professional organizations, standards organizations, and government agencies; b) users of integrity levels such as developers and maintainers, suppliers and acquirers, users, and assessors of systems or software and for the administrative and technical support of systems and/or software products.
SNZ AS/NZS 15026.3 - SYSTEMS AND SOFTWARE ENGINEERING – SYSTEMS AND SOFTWARE ASSURANCE PART 3: SYSTEM INTEGRITY LEVELS Organization: SNZ
Date: 2013-05-24
Description: This part of ISO/IEC 15026 is applicable to systems and software and is intended for use by: a) definers of integrity levels such as industry and professional organizations, standards organizations, and government agencies; b) users of integrity levels such as developers and maintainers, suppliers and acquirers, users, and assessors of systems or software and for the administrative and technical support of systems and/or software products.
MODUK AQAP-2210 - NATO SUPPLEMENTARY SOFTWARE QUALITY ASSURANCE REQUIREMENTS TO AQAP 2110 - EDITION 1 Organization: MODUK
Date: 2006-11-01
Description: The provisions of this publication can also apply to Government Agencies performing software development or maintenance.
ISO/IEC TR 9126-3 - SOFTWARE ENGINEERING - PRODUCT QUALITY - PART 3: INTERNAL METRICS - FIRST EDITION Organization: ISO
Date: 2003-07-01
Description: An evaluator may, for example, be a testing laboratory, the quality department of a software development organization, a government organization or a user);— Developer (an individual or organization that performs development activities, including requirements analysis, design, and testing through acceptance during the software life cycle process);— Maintainer (an individual or organization that performs maintenance activities);— Supplier (an individual or organization that enters into a contract with the acquirer for the supply of a system, software product or software service under the terms of the contract) when validating software quality at qualification test;— User (an individual or organization that uses the software product to perform a specific function) when evaluating quality of software product at acceptance test;— Quality manager (an individual or organization that performs a systematic examination of the software product or software services) when evaluating software quality as part of quality assurance and quality control.
ISO/IEC TR 9126-2 - SOFTWARE ENGINEERING - PRODUCT QUALITY - PART 2: EXTERNAL METRICS - FIRST EDITION Organization: ISO
Date: 2003-07-01
Description: An evaluator may, for example, be a testing laboratory, the quality department of a software development organization, a government organization or a user); — Developer (an individual or organization that performs development activities, including requirements analysis, design, and testing through acceptance during the software life cycle process); — Maintainer (an individual or organization that performs maintenance activities); — Supplier (an individual or organization that enters into a contract with the acquirer for the supply of a system, software product or software service under the terms of the contract) when validating software quality at qualification test; — User (an individual or organization that uses the software product to perform a specific function) when evaluating quality of software product at acceptance test; — Quality manager (an individual or organization that performs a systematic examination of the software product or software services) when evaluating software quality as part of quality assurance and quality control.
CSA ISO/IEC TR 9126-2 - SOFTWARE ENGINEERING - PRODUCT QUALITY - PART 2: EXTERNAL METRICS Organization: CSA
Date: 2004-01-01
Description: An evaluator may, for example, be a testing laboratory, the quality department of a software development organization, a government organization or a user); — Developer (an individual or organization that performs development activities, including requirements analysis, design, and testing through acceptance during the software life cycle process); — Maintainer (an individual or organization that performs maintenance activities); — Supplier (an individual or organization that enters into a contract with the acquirer for the supply of a system, software product or software service under the terms of the contract) when validating software quality at qualification test; — User (an individual or organization that uses the software product to perform a specific function) when evaluating quality of software product at acceptance test; — Quality manager (an individual or organization that performs a systematic examination of the software product or software services) when evaluating software quality as part of quality assurance and quality control.
CSA ISO/IEC TR 9126-3 - SOFTWARE ENGINEERING - PRODUCT QUALITY - PART 3: INTERNAL METRICS Organization: CSA
Date: 2004-01-01
Description: An evaluator may, for example, be a testing laboratory, the quality department of a software development organization, a government organization or a user); — Developer (an individual or organization that performs development activities, including requirements analysis, design, and testing through acceptance during the software life cycle process); — Maintainer (an individual or organization that performs maintenance activities); — Supplier (an individual or organization that enters into a contract with the acquirer for the supply of a system, software product or software service under the terms of the contract) when validating software quality at qualification test; — User (an individual or organization that uses the software product to perform a specific function) when evaluating quality of software product at acceptance test; — Quality manager (an individual or organization that performs a systematic examination of the software product or software services) when evaluating software quality as part of quality assurance and quality control.
ISO/IEC TR 9126-4 - SOFTWARE ENGINEERING - PRODUCT QUALITY - PART 4: QUALITY IN USE METRICS - FIRST EDITION Organization: ISO
Date: 2004-04-01
Description: An evaluator may, for example, be a testing laboratory, the quality department of a software development organization, a government organization or user);• Developer (an individual or organization that performs development activities, including requirements analysis, design and testing through acceptance during the software life cycle process);• Maintainer (an individual or organization that performs maintenance activities);• Supplier (an individual or organization that enters into a contract with the acquirer for the supply of a system, software product or software service under the terms of the contract) when validating software quality at qualification test;• User (an individual or organization that uses the software product to perform a specific function) when evaluating quality of software product at acceptance test;• Quality manager (an individual or organization that performs a systematic examination of the software product or software services) when evaluating software quality as part of quality assurance and quality control.
CSA ISO/IEC TR 9126-4 - SOFTWARE ENGINEERING - PRODUCT QUALITY - PART 4: QUALITY IN USE METRICS Organization: CSA
Date: 2005-01-01
Description: An evaluator may, for example, be a testing laboratory, the quality department of a software development organization, a government organization or user); Developer (an individual or organization that performs development activities, including requirements analysis, design and testing through acceptance during the software life cycle process); Maintainer (an individual or organization that performs maintenance activities); Supplier (an individual or organization that enters into a contract with the acquirer for the supply of a system, software product or software service under the terms of the contract) when validating software quality at qualification test; User (an individual or organization that uses the software product to perform a specific function) when evaluating quality of software product at acceptance test; Quality manager (an individual or organization that performs a systematic examination of the software product or software services) when evaluating software quality as part of quality assurance and quality control.
IEEE P15026-3 DRAFT - DRAFT STANDARD FOR ADOPTION OF SYSTEMS AND SOFTWARE ENGINEERING-SYSTEMS AND SOFTWARE ASSURANCE-PART 3: SYSTEM INTEGRITY LEVELS - IEEE COMPUTER SOCIETY Organization: IEEE
Date: 2017-07-01
Description: This part of ISO/IEC 15026 is applicable to systems and software and is intended for use by the following: a)definers of integrity levels such as industry and professional organizations, standards organizations, and government agencies: b) users of integrity levels such as developers and maintainers, suppliers and acquirers, system or software users, assessors of systems or software and administrative and technical support staff of systems and/or software products.
IEEE 15026-3 - ADOPTION OF ISO/IEC 15026-3-SYSTEMS AND SOFTWARE ENGINEERING-SYSTEMS AND SOFTWARE ASSURANCE-PART 3: SYSTEM INTEGRITY LEVELS - IEEE COMPUTER SOCIETY Organization: IEEE
Date: 2013-06-14
Description: This part of ISO/IEC 15026 is applicable to systems and software and is intended for use by: a) definers of integrity levels such as industry and professional organizations, standards organizations, and government agencies; b) users of integrity levels such as developers and maintainers, suppliers and acquirers, users, and assessors of systems or software and for the administrative and technical support of systems and/or software products.
DS/ISO/IEC 21827 - INFORMATION TECHNOLOGY - SECURITY TECHNIQUES - SYSTEMS SECURITY ENGINEERING - CAPABILITY MATURITY MODEL® (SSE-CMM®) Organization: DS
Date: 2008-11-03
Description: On the contrary, the SSE-CMM® promotes integration, taking the view that security is pervasive across all engineering disciplines (e.g., systems, software and hardware) and defining components of the model to address such concerns.
CSA ISO/IEC 21827 - INFORMATION TECHNOLOGY - SECURITY TECHNIQUES - SYSTEMS SECURITY ENGINEERING - CAPABILITY MATURITY MODEL (SSE-CMM) Organization: CSA
Date: 2009-01-01
Description: On the contrary, the SSE-CMM® promotes integration, taking the view that security is pervasive across all engineering disciplines (e.g., systems, software and hardware) and defining components of the model to address such concerns.

1 - 20 of 57 results