IEEE 15026-2-2022

15026-2-2022 is an English-language standard focused on assurance case in computing and processing, presented here as a redline version of Part 2. It is intended to help structure and review claims, evidence, and argumentation so that a system’s trustworthiness can be assessed more consistently. For organizations working with software-intensive or digitally processed systems, 15026-2-2022 supports clearer documentation and more disciplined assurance activities.

15026-2-2022 overview

This standard addresses the technical framework for an assurance case, with Part 2 concentrating on how assurance arguments are represented and examined in practice. In a computing and processing context, that means defining how evidence supports claims about a system’s properties, behavior, or dependability. The redline format is useful when comparing revisions, because it highlights changes to the requirements and guidance in 15026-2-2022 while preserving the structure of the document.

Typical use cases

15026-2-2022 is commonly relevant during system assurance planning, safety or dependability reviews, and procurement activities where a structured case is needed to justify confidence in a digital system. It may be used for software platforms, control systems, embedded processing, or other computer-based environments where evidence must be organized and traced. The standard can also support internal review cycles, supplier evaluation, and change management when assurance arguments need to be updated clearly.

Why this standard matters

In practice, an assurance case helps reduce ambiguity by showing how claims are supported and where evidence is incomplete. That matters when teams must demonstrate consistency, manage risk, or compare alternatives during design and verification. By using 15026-2-2022, organizations can improve traceability between requirements, analysis, and supporting records, which can make compliance reviews and technical decision-making more reliable. The redline version is especially helpful when tracking edits across revisions.

• Assurance case structure
• Claims, arguments, and evidence
• Computing and processing systems
• Redline revision comparison
• Review and traceability support