UL 1998
Standard for Software in Programmable Components

Edition Number:3SCC Approved:--
Edition Date:2013-12-18DOD Approved: --
Price Code:AANSI Approved: 2018-09-21


    1 Scope

    1.1 These requirements apply to non-networked embedded software residing in programmable components performing safety-related functions whose failure is capable of resulting in a risk of fire, electric shock, or injury to persons.

    1.2 This is a reference standard in which the requirements are to be applied when specifically referenced by other standards or product safety requirements.

    1.3 These requirements address the risks unique to product hardware controlled by software in programmable components.

    1.4 These requirements are intended to supplement applicable product or component standards and requirements, and are not intended to serve as the sole basis for investigating the risk of fire, electric shock, or injury to persons.

    1.5 These requirements are intended to address risks that occur in the software or in the process used to develop and maintain the software, such as the following:

    a)    Requirements conversion faults that cause differences between the specification for the programmable component and the software design;

    b)    Design faults such as incorrect software algorithms or interfaces;

    c)    Coding faults, including syntax, incorrect signs, endless loops, and other coding faults;

    d)    Timing faults that cause program execution to occur prematurely or late;

    e)    Microelectronic memory faults, such as memory failure, not enough memory, or memory overlap;

    f)    Induced faults caused by microelectronic hardware failure;

    g)    Latent, user, input/output, range, and other faults that are only detectable when a given state occurs; and

    h)    Failure of the programmable component to perform any function at all.

    1.6 Product standard requirements may amend or supersede the requirements in this standard, as appropriate.

    1.7 These requirements are not intended to address cybersecurity. Risks associated with unauthorized access or attack through a network shall be addressed in the product standard or other referenced standard such as the Standard for Software Cybersecurity for Network-Connectable Products, Part 1: General Requirements, UL 2900-1.

    Expand All

    • Cover
    • Transmittal
    • Table of Contents
    • UL Preface
      • Body
        • 1 Scope
        • 2 Definitions of Terms Used
        • 3 Risk Analysis
        • 4 Process Definition
        • 5 Qualification of Design, Implementation, and Verification Tools
        • 6 Software Design
        • 7 Critical and Supervisory Sections of Software
        • 8 Measures To Address Microelectronic Hardware Failure Modes
        • 9 Product Interface
        • 10 User Interfaces
        • 11 Software Analysis and Testing
          • 11.1 Software analysis
          • 11.2 Software testing
          • 11.3 Failure mode and stress testing
        • 12 Documentation
          • 12.1 User documentation
          • 12.2 Software plan
          • 12.3 Risk analysis approach and results
          • 12.4 Configuration management plan
          • 12.5 Programmable system architecture
          • 12.6 Programmable component and software requirements specification
          • 12.7 Software design documentation
          • 12.8 Analysis and test documentation
        • 13 Off-the-Shelf (OTS) Software
        • 14 Software Changes and Document Control
        • 15 Identification