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

1 - 20 of 40 results

PACKT - EMBEDDED LINUX FOR DEVELO - EMBEDDED LINUX FOR DEVELOPERS Organization: PACKT
Date: 2016-09-27
Description: This learning path starts with the module Learning Embedded Linux Using the Yocto Project. It introduces embedded Linux software and hardware architecture and presents information about the bootloader.
PACKT - LINUX: EMBEDDED DEVELOPME - LINUX: EMBEDDED DEVELOPMENT Organization: PACKT
Date: 2016-09-27
Description: This learning path starts with the module Learning Embedded Linux Using the Yocto Project. It introduces embedded Linux software and hardware architecture and presents information about the bootloader.
ANSI - INCITS/ISO/IEC 29164 - INFORMATION TECHNOLOGY - BIOMETRICS - EMBEDDED BIOAPI Organization: ANSI
Date: 2011-01-01
Description: — A C-based function header description, for those manufacturers that want to provide a C-library for integration as a Software Development Kit for the overall embedded system. Regarding security, this International Standard defines two kinds of devices: — Type A: devices that, due to lack of processing capabilities, do not implement any kind of security mechanism.
ISO/IEC 29164 - INFORMATION TECHNOLOGY - BIOMETRICS - EMBEDDED BIOAPI - FIRST EDITION Organization: ISO
Date: 2011-10-01
Description: — A C-based function header description, for those manufacturers that want to provide a C-library for integration as a Software Development Kit for the overall embedded system. Regarding security, this International Standard defines two kinds of devices: — Type A: devices that, due to lack of processing capabilities, do not implement any kind of security mechanism.
SAE/TP - 2007-01-3024 - DISTRIBUTED, EMBEDDED CONTROL FOR LIFE SUPPORT DEVELOPMENT Organization: SAE/TP
Date: 2007-07-09
Description: Additional controllers allow for automatically migrating control codes when the original controllers fail. The resulting hardware and software architecture dramatically decreases the downtime of life support systems due to component failure, and improves safety and operational efficiency by supporting reconfiguration of the life support hardware or the control system with a minimum of deactivation or shutdown of the systems being controlled.
NASA NPD 2820.1 REV C - NASA SOFTWARE POLICY Organization: NASA
Date: 2005-08-31
Description: Definitions: Software - as used in this NPD means computer programs, procedures, rules, and associated documentation and data pertaining to the development and operation of a computer system. Software also includes COTS, GOTS, MOTS, embedded software, reuse, heritage, legacy, auto generated code, firmware (instructions, logic, or associated data loaded into programmable devices), and open source software components.
SAE/TP - 2011-01-2551 - AN EMBEDDED PLATFORM-AGNOSTIC SOLUTION TO DEPLOY GRAPHICAL APPLICATIONS Organization: SAE/TP
Date: 2011-10-18
Description: While both offer significant advantages throughout the development process, many resulting custom in-house solutions only support a narrow set of embedded platforms, do not meet the performance requirements for some embedded configurations, and may make it difficult to upgrade hardware in future.
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 reuse of mechanical and electronic hardware as well as software code, libraries, and models is a critical element of today's design and integration activities.
SAE AS9006 - DELIVERABLE AEROSPACE SOFTWARE SUPPLEMENT FOR AS9100A QUALITY MANAGEMENT SYSTEMS - AEROSPACE - REQUIREMENTS FOR SOFTWARE (BASED ON AS9100A) Organization: SAE
Date: 2013-07-01
Description: This supplement contains Quality System requirements for suppliers of products that contain deliverable embedded or load able airborne, spaceborne or ground support software components that are part of an aircraft Type Design, weapon system, missile or spacecraft operational software and/or support software that is used in the development and maintenance of deliverable software.
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.
ARINC 653P4 - AVIONICS APPLICATION SOFTWARE STANDARD INTERFACE PART 4 – SUBSET SERVICES Organization: ARINC
Date: 2012-06-28
Description: The majority of this document describes the runtime environment for embedded avionics software. This list of services identifies the minimum functionality provided to the application software and is, therefore, the industry standard interface.
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.
SAE/TP - 2009-01-2925 - INTEGRATION OF AUTOMATIC CODE GENERATION IN MODEL-BASED ALGORITHM DEVELOPMENT; PREREQUISITES, WORKFLOW AND THE HUMAN FACTOR Organization: SAE/TP
Date: 2009-10-06
Description: Automatic code generation is an established technology in automotive and aerospace industries that is also adopted in commercial vehicle embedded software development. Code generation brings the productivity gains of model-based algorithm design to the next stage of the process – production software development.
SAE AS5506/1 - (R) SAE ARCHITECTURE ANALYSIS AND DESIGN LANGUAGE (AADL) ANNEX VOLUME 1: ANNEX A: ARINC653 ANNEX, ANNEX C: CODE GENERATION ANNEX, ANNEX E: ERROR MODEL ANNEX Organization: SAE
Date: 2015-09-01
Description: Finally, this document contains guidelines that supplement the transition between AADL models and software source code.
SAE/TP - 2011-01-2578 - SCADE SOLUTIONS FOR THE EFFICIENT DEVELOPMENT OF ARINC 661 COCKPIT DISPLAY SYSTEMS AND USER APPLICATIONS Organization: SAE/TP
Date: 2011-10-18
Description: At a later stage of the project, this same integrated tool suite can be used to produce and certify the final embedded software code within the CDS and to generate the communication code between the CDS and the UAs.
IEEE 1362 - GUIDE FOR INFORMATION TECHNOLOGY - SYSTEM DEFINITION - CONCEPT OF OPERATIONS (CONOPS) DOCUMENT - IEEE COMPUTER SOCIETY DOCUMENT; INCORPORATES IEEE 1362A-1998 Organization: IEEE
Date: 1998-03-19
Description: This guide is applicable to systems that will be implemented in all forms of product media, including firmware, embedded systems code, programmable logic arrays, and software-in-silicon. This guide can be applied to any and all segments of a system life cycle.
MODUK - DEF STAN-00-22 - IDENTIFICATION AND MARKING OF PROGRAMMABLE ITEMS - ISSUE 2; 05.91 Organization: MODUK
Date: 1991-05-03
Description: This Standard, which is exclusively concerned with identification and marking, uses the term PI for devices, assemblies and other reprogrammable media including embedded non-volatile software. While this Standard has been drafted assuming the use of conventional drawings, documents and alpha-numeric labelling, the methods described are intended to be equally appropriate to manual and/or computer-based engineering data management and logistic systems.
DS/EN 62429 - RELIABILITY GROWTH - STRESS TESTING FOR EARLY FAILURES IN UNIQUE COMPLEX SYSTEMS Organization: DS
Date: 2008-05-08
Description: It does not cover software tested alone, but the methods can be used during testing of large embedded software programs in operational hardware, when simulated operating loads are used.
IEC 62429 - RELIABILITY GROWTH – STRESS TESTING FOR EARLY FAILURES IN UNIQUE COMPLEX SYSTEMS - EDITION 1.0 Organization: IEC
Date: 2007-11-01
Description: It does not cover software tested alone, but the methods can be used during testing of large embedded software programs in operational hardware, when simulated operating loads are used.
SAE/TP - 2007-01-3826 - MODEL-BASED DESIGN OF COMPLEX INTEGRATED SYSTEMS FOR SYNCHRONOUS ARCHITECTURES Organization: SAE/TP
Date: 2007-09-17
Description: Both are based on the synchronous paradigm; TTA for the communication infrastructure and distributed embedded computing, and SCADE for simulating and generating code for the application components.

1 - 20 of 40 results