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

1 - 20 of 64 results

CRC - EMBEDDED SOFTWARE DEVELOP - EMBEDDED SOFTWARE DEVELOPMENT FOR SAFETY-CRITICAL SYSTEMS Organization: CRC
SAE/TP - 2009-01-3284 - CHALLENGES IN VALIDATING SAFETY-CRITICAL EMBEDDED SYSTEMS Organization: SAE/TP
Date: 2009-11-10
Description: The embedded software has played an increasing role in safety-critical systems. At the same time the current development process of "build, then integrate" has proven unaffordable for the Aerospace industry.
SAE/TP - 2007-01-3024 - DISTRIBUTED, EMBEDDED CONTROL FOR LIFE SUPPORT DEVELOPMENT Organization: SAE/TP
Date: 2007-07-09
Description: The hardware changes from large standing racks of VERSAModuleEurocard (VME) computers and I/O cards to a set of small, modular controllers embedded in the hardware of the controlled systems. Additionally, the paper describes the redesign of an existing intelligent control architecture, known as 3T, that since 1995 has provided autonomous 24/7 controls to several long-duration life-support systems in ground tests at JSC.
CEI EN 62304 - MEDICAL DEVICE SOFTWARE - SOFTWARE LIFE-CYCLE PROCESSES Organization: CEI
Date: 2015-08-01
Description: This standard applies to the development and maintenance of MEDICAL DEVICE SOFTWARE when software is itself a MEDICAL DEVICE or when software is an embedded or integral part of the final MEDICAL DEVICE.
CENELEC - EN 62304 - MEDICAL DEVICE SOFTWARE - SOFTWARE LIFE-CYCLE PROCESSES - INCORPORATING CORRIGENDUM NOVEMBER 2008; INCORPORATES AMENDMENT A1: 2015 Organization: CENELEC
Date: 2006-07-01
Description: Field of application This standard applies to the development and maintenance of MEDICAL DEVICE SOFTWARE when software is itself a MEDICAL DEVICE or when software is an embedded or integral part of the final MEDICAL DEVICE.
AAMI - 62304 - MEDICAL DEVICE SOFTWARE - SOFTWARE LIFE CYCLE PROCESSES Organization: AAMI
Date: 2006-01-01
Description: This standard applies to the development and maintenance of MEDICAL DEVICE SOFTWARE when software is itself a MEDICAL DEVICE or when software is an embedded or integral part of the final EDICAL DEVICE.
SAE J2746 - SOFTWARE ASSESSMENT REPOSITORY Organization: SAE
Date: 2009-04-01
Description: Since car manufacturers OEMs (Original Equipment Manufacturer) also develop embedded software, they should participate in the Software Assessment Repository in addition to the supply base.
SAE/TP - 2011-01-2551 - AN EMBEDDED PLATFORM-AGNOSTIC SOLUTION TO DEPLOY GRAPHICAL APPLICATIONS Organization: SAE/TP
Date: 2011-10-18
Description: One of the key benefits in working with a Port Kit is that it allows designers to select from different combinations of safety critical software and hardware for their Human- Machine Interface (HMI) development.
UL 1998 - UL STANDARD FOR SAFETY SOFTWARE IN PROGRAMMABLE COMPONENTS - THIRD EDITION Organization: UL
Date: 2013-12-18
Description: These requirements apply to non-networked embedded microprocessor software whose failure is capable of resulting in a risk of fire, electric shock, or injury to persons.
SAE/TP - 2007-01-3827 - MODEL-BASED DEVELOPMENT OF DISTRIBUTED EMBEDDED REAL-TIME SYSTEMS WITH THE DECOS TOOL-CHAIN Organization: SAE/TP
Date: 2007-09-17
Description: Therefore, in the project DECOS1, which aims at improving system architectures and development of distributed safety critical embedded systems, an integrated, model-driven tool-chain is established, accompanying the system development process from design to deployment.
SAE PT-161 - SOFTWARE-HARDWARE INTEGRATION IN AUTOMOTIVE PRODUCT DEVELOPMENT - TO PURCHASE CALL 1-800-854-7179 USA/CANADA OR 303-397-7956 WORLDWIDE Organization: SAE
Date: 2013-11-07
Description: The current state of the art is to integrate, verify, validate, and test automotive hardware and software with a complement of physical hardware and virtual software prototyping tools.
ISO DIS 26262-6 - ROAD VEHICLES - FUNCTIONAL SAFETY - PART 6: PRODUCT DEVELOPMENT AT THE SOFTWARE LEVEL Organization: ISO
Date: 2016-09-21
Description: This part of ISO 26262 specifies the requirements for product development at the software level for automotive applications, including the following: - general topics for product development at the software level;  - specification of the software safety requirements; - software architectural design; - software unit design and implementation - software unit verification; - software integration and verification; and - testing of the embedded software.  It also specifies requirements associated with the use of configurable software
DSF/ISO/IEC DIS 25051 - SOFTWARE ENGINEERING - SOFTWARE PRODUCT QUALITY REQUIREMENTS AND EVALUATION (SQUARE) - REQUIREMENTS FOR QUALITY OF COMMERCIAL OFF-THE-SHELF (COTS) SOFTWARE PRODUCT AND INSTRUCTIONS FOR TESTING Organization: DS
Description: NOTE Examples of COTS software products include but are not limited to text processors, spreadsheets, data base control software, graphics packages, software for technical, scientific or real-time embedded functions, , human resources management software, sales management, smartphone application, freeware and web software such as generators of web sites/pages.
DS/ISO/IEC 25051 - SOFTWARE ENGINEERING - SYSTEMS AND SOFTWARE QUALITY REQUIREMENTS AND EVALUATION (SQUARE) - REQUIREMENTS FOR QUALITY OF READY TO USE SOFTWARE PRODUCT (RUSP) AND INSTRUCTIONS FOR TESTING Organization: DS
Date: 2014-02-14
Description: NOTE Examples of COTS software products include but are not limited to text processors, spreadsheets, data base control software, graphics packages, software for technical, scientific or real-time embedded functions, , human resources management software, sales management, smartphone application, freeware and web software such as generators of web sites/pages.
BSI - BS IEC 61511-1 - FUNCTIONAL SAFETY - SAFETY INSTRUMENTED SYSTEMS FOR THE PROCESS INDUSTRY SECTOR - PART 1: FRAMEWORK, DEFINITIONS, SYSTEM, HARDWARE AND SOFTWARE REQUIREMENTS Organization: BSI
Date: 2003-03-12
Description: In particular, this standarda) specifies the requirements for achieving functional safety but does not specify who is responsible for implementing the requirements (for example, designers, suppliers, owner/operating company, contractor); this responsibility will be assigned to different parties according to safety planning and national regulations;b) applies when equipment that meets the requirements of IEC 61508, or of 11.5 of IEC 61511-1, is integrated into an overall system that is to be used for a process sector application but does not apply to manufacturers wishing to claim that devices are suitable for use in safety instrumented systems for the process sector (see IEC 61508-2 and IEC 61508-3);c) defines the relationship between IEC 61511 and IEC 61508 (Figures 2 and 3);d) applies when application software is developed for systems having limited variability or fixed programmes but does not apply to manufacturers, safety instrumented systems designers, integrators and users that develop embedded software (system software) or use full variability languages (see IEC 61508-3);e) applies to a wide variety of industries within the process sector including chemicals, oil refining, oil and gas production, pulp and paper, non-nuclear power generation;NOTE Within the process sector some applications, (for example, off-shore), may have additional requirements that have to be satisfied.
CENELEC - EN 61511-1 - FUNCTIONAL SAFETY SAFETY INSTRUMENTED SYSTEMS FOR THE PROCESS INDUSTRY SECTOR PART 1: FRAMEWORK, DEFINITIONS, SYSTEM, HARDWARE AND SOFTWARE REQUIREMENTS Organization: CENELEC
Date: 2004-12-01
Description: In particular, this standard a) specifies the requirements for achieving functional safety but does not specify who is responsible for implementing the requirements (for example, designers, suppliers, owner/operating company, contractor); this responsibility will be assigned to different parties according to safety planning and national regulations; b) applies when equipment that meets the requirements of IEC 61508, or of 11.5 of IEC 61511-1, is integrated into an overall system that is to be used for a process sector application but does not apply to manufacturers wishing to claim that devices are suitable for use in safety instrumented systems for the process sector (see IEC 61508-2 and IEC 61508-3); c) defines the relationship between IEC 61511 and IEC 61508 (Figures 2 and 3); d) applies when application software is developed for systems having limited variability or fixed programmes but does not apply to manufacturers, safety instrumented systems designers, integrators and users that develop embedded software (system software) or use full variability languages (see IEC 61508-3); e) applies to a wide variety of industries within the process sector including chemicals, oil refining, oil and gas production, pulp and paper, non-nuclear power generation; NOTE Within the process sector some applications, (for example, off-shore), may have additional requirements that have to be satisfied.
ISA 84.00.01 P1 - FUNCTIONAL SAFETY: SAFETY INSTRUMENTED SYSTEMS FOR THE PROCESS INDUSTRY SECTOR - PART 1: FRAMEWORK, DEFINITIONS, SYSTEM, HARDWARE AND SOFTWARE REQUIREMENTS Organization: ISA
Date: 2004-09-02
Description: In particular, this standard a) specifies the requirements for achieving functional safety but does not specify who is responsible for implementing the requirements (for example, designers, suppliers, owner/operating company, contractor); this responsibility will be assigned to different parties according to safety planning and national regulations; b) applies when equipment that meets the requirements of IEC 61508, or of 11.5 of ANSI/ISA-84.00.01-2004 Part 1 (IEC 61511-1 Mod), is integrated into an overall system that is to be used for a process sector application but does not apply to manufacturers wishing to claim that devices are suitable for use in safety instrumented systems for the process sector (see IEC 61508-2 and IEC 61508-3); c) defines the relationship between ANSI/ISA-84.00.01-2004 (IEC 61511Mod), and IEC 61508 (Figures 2 and 3); d) applies when application software is developed for systems having limited variability or fixed programmes but does not apply to manufacturers, safety instrumented systems designers, integrators and users that develop embedded software (system software) or use full variability languages (see IEC 61508-3); e) applies to a wide variety of industries within the process sector including chemicals, oil refining, oil and gas production, pulp and paper, non-nuclear power generation; NOTE Within the process sector some applications, (for example, off-shore), may have additional requirements that have to be satisfied.
ISO/IEC DIS 30754 - INFORMATION TECHNOLOGY - SOFTWARE TRUSTWORTHINESS - GOVERNANCE AND MANAGEMENT - SPECIFICATION Organization: ISO
Date: 2016-04-06
Description: This International Standard provides a specification for software trustworthiness, that is intended to be a widely applicable approach that can be customised for any organization, and to software in its many guises from embedded equipment through consumer devices to industrial control systems.
SEPT - UL 1998 CHECKLIST - SOFTWARE ENGINEERING PROCESS TECHNOLOGY-EVIDENCE PRODUCT CHECKLIST FOR ANSI/UL 1998-2004 STANDARD FOR SOFTWARE IN PROGRAMMABLE COMPONENTS - REVISION 1 - REVISION 1 Organization: SEPT
Date: 2012-01-10
Description: The ANSI/UL 1998 standard is focused toward application-specific, non-networked software in a programmable component embedded in a product for which a failure may result in injury to persons.
BSI - 12/30264224 DC - DRAFT BS EN 61511-1 ED.2 FUNCTIONAL SAFETY - SAFETY INSTRUMENTED SYSTEMS FOR THE PROCESSY ISNEDCUTOSRT R - NORMATIVE PART 1: FRAMEWORK, DEFINITIONS, SYSTEM, HARDWARE AND SOFTWARE REQUIREMENTS Organization: BSI
Date: 2012-05-22
Description: In particular, this standard a) specifies the requirements for achieving functional safety but does not specify who is responsible for implementing the requirements (for example, designers, suppliers, owner/operating company, contractor); this responsibility will be assigned to different parties according to safety planning and national regulations; b) applies when equipment that meets the requirements of IEC 61508, or of 11.5 of IEC 61511-1, is integrated into an overall system that is to be used for a process sector application but does not apply to manufacturers wishing to claim that devices are suitable for use in safety instrumented systems for the process sector (see IEC 61508-2 and IEC 61508-3); c) defines the relationship between IEC 61511 and IEC 61508 (Figures 2 and 3); d) applies when application software is developed for systems having limited variability or fixed programmes but does not apply to manufacturers, safety instrumented systems designers, integrators and users that develop embedded software (system software) or use full variability languages (see IEC 61508-3); e) applies to a wide variety of industries within the process sector including chemicals, oil refining, oil and gas production, pulp and paper, non-nuclear power generation; NOTE Within the process sector some applications, (for example, off-shore), may have additional requirements that have to be satisfied.

1 - 20 of 64 results