Overview
ISO/IEC 23531:2020 - Systems and software engineering - Capabilities of issue management tools - defines a structured, vendor-neutral framework for the capabilities of issue management tools. It provides an object model, use cases and a categorized capability catalog to help organizations evaluate and select issue management tools across development and operations lifecycles. The standard is independent of development methodology (e.g., Waterfall or Agile) and maps to lifecycle activities in ISO/IEC/IEEE 12207.
Key Topics
- Scope and purpose: Establishes what an issue management tool should support to manage issues, defects, incidents, work items and related relationships across the lifecycle (Scope, Clause 1).
- Object model and UML use cases: Defines an object model for issue management entities and use cases for work management, defect management and incident/IT service scenarios (Clause 4).
- Capability categories: Groups capabilities into Common, Work Management, Defect Management and IT Service Management (Clauses 4–6).
- Entities and relationships: Clarifies data entities that tools must create, update, refer to and archive (e.g., issue-ID, timestamps, artifact links) without including the artifacts themselves (Clause 4.3).
- Evaluation guidance: Designed to be used with ISO/IEC 20741, the guideline for evaluation and selection of software engineering tools (Annex A).
- Normative independence: No prescriptive methodology - applicable to development, testing and operations.
Practical applications and who uses it
ISO/IEC 23531:2020 is practical for organizations that must compare, procure or integrate issue management tools:
- Project managers and program leads use it to define selection criteria for tool procurement and deployment.
- Tool evaluators and QA/Testing teams apply the capability categories to compare defect tracking and test-issue workflows.
- Configuration and release engineers map issue entities and links to configuration management and build tools for traceability.
- IT service and operations teams assess incident and service-request handling capabilities.
- Vendors and integrators use the object model to design interoperable features and APIs.
Typical uses:
- Creating a requirements checklist for vendor comparisons
- Mapping tool features to lifecycle activities in ISO/IEC/IEEE 12207
- Ensuring traceability between issues and related artifacts (requirements, code, test results)
- Integrating issue tracking with CI/CD, CM and ITSM ecosystems
Related standards
- ISO/IEC 20741 - Guideline for the evaluation and selection of software engineering tools (integration for selection process)
- ISO/IEC/IEEE 12207 - Systems and software lifecycle processes (source of related tasks and activities)
- ISO/IEC 19505-2 (UML) - Notation used for model diagrams in the standard
Using ISO/IEC 23531:2020 helps organizations make objective, standards-based decisions when selecting and integrating issue management tools that support consistent issue, defect and incident handling across the software lifecycle.