IEEE P15026-2, Apr 2011

P15026-2, Apr 2011 is a technical standard for assurance case practice in computing and processing, giving a structured way to present claims, evidence, and reasoning about system dependability. As Part 2: Assurance case, it is relevant where organizations need a clear argument that a system, component, or process meets defined expectations. This can support design review, verification planning, and communication between engineers, assessors, and procurement teams.

P15026-2, Apr 2011 overview

This standard focuses on the assurance case method, which is commonly used to organize justification for a system’s safety, reliability, or other critical properties. P15026-2, Apr 2011 helps define how evidence is linked to claims and how the reasoning is structured so it can be understood and assessed. In computing and processing environments, that kind of formalization is important when technical decisions need to be traceable and defensible.

Typical use cases

P15026-2, Apr 2011 may be used when building assurance arguments for software-intensive systems, control platforms, or processing equipment where confidence must be demonstrated rather than assumed. It is relevant during specification, validation, and independent assessment activities, especially for projects that need clear documentation of how requirements are satisfied. The standard can also support supplier evaluations, internal assurance reviews, and evidence preparation for regulated or high-consequence applications.

Why this standard matters

Assurance case structures help teams reduce ambiguity by making the relationship between claims and supporting evidence explicit. For organizations working with computing and processing systems, that can improve consistency in design control, testing, and review activities. P15026-2, Apr 2011 is useful where decisions must be justified to stakeholders or auditors, because it supports a disciplined approach to showing that a system has been evaluated in a repeatable and reviewable way.

• Assurance case structure
• Claims and evidence linkage
• Computing and processing context
• Review and assessment support
• Traceable technical justification