IEC 62559-2 – Use Case Methodology: Templates for Use Cases, Actor Lists and Requirements

Standardized templates for describing system behavior, actors, and functional requirements in complex engineering domains

In complex systems engineering, clear and consistent documentation of user requirements and system behavior is critical for project success. IEC 62559-2:2015, developed by Technical Committee 8 (Systems aspects for electrical energy supply), provides a standardized template structure for use cases, actor lists, and requirements lists. This standard is particularly influential in smart grid, energy automation, and industrial control system design.

📋 Purpose and Scope

IEC 62559-2 defines the formal template structure for describing use cases in a consistent manner across projects and organizations. The standard addresses a fundamental challenge in systems engineering: different teams and stakeholders often describe the same system behavior in incompatible ways, leading to miscommunication and design errors.

The standard provides three interconnected template types:

Use Case Template – Describes a sequence of interactions between actors and the system to achieve a specific goal
Actor List Template – Catalogues all entities (human users, external systems, devices) that interact with the system
Requirements List Template – Links functional and non-functional requirements to specific use cases

The IEC 62559-2 template structure is designed for interoperability with UML (Unified Modeling Language) and SysML (Systems Modeling Language) tools, enabling seamless integration with modern model-based systems engineering (MBSE) workflows.

🔧 Template Structure Details

Use Case Template Components

The use case template defined in the standard includes the following major sections:

Section	Description	Mandatory	Example Content
Use Case Name	Unique identifier and descriptive name	Yes	“Grid-connected EV Charging”
Version Management	Version number, date, author	Yes	v2.1 / 2024-03-15
Scope	Boundaries and context of the use case	Yes	“This use case covers…”
Level of Detail	Business, system, or component level	Yes	“System level”
Primary Actor	Entity initiating the interaction	Yes	“EV Driver”
Preconditions	Required state before execution	Recommended	“Vehicle is parked and connected”
Postconditions	Expected state after successful execution	Recommended	“Battery is charged to target level”
Main Flow	Step-by-step interaction sequence	Yes	“1. Driver authenticates…”
Alternative Flows	Variations and error handling	Recommended	“If authentication fails…”

Actor List and Requirements List

The actor list template categorizes all entities that interact with the system, including human roles, external systems, databases, hardware devices, and time-based triggers. Each actor entry includes a unique identifier, description, and type classification. The requirements list template enables traceability from high-level stakeholder requirements down to specific use case steps, supporting verification and validation activities throughout the system lifecycle.

A common mistake when using IEC 62559-2 is defining actors at inconsistent abstraction levels. For example, mixing “Database Server” (a physical component) with “Regulatory Authority” (an organizational entity) in the same actor list without proper type classification can lead to confusion during system design.

🏗️ Engineering Design Insights

Integration with Smart Grid Architecture

IEC 62559-2 is integral to the Smart Grid Architecture Model (SGAM) framework. Use cases documented in the standardized template can be mapped directly to SGAM layers (business, function, information, communication, component) and zones (process, station, operation, enterprise, market). This mapping enables systematic analysis of interoperability requirements and identification of standardization gaps.

The standard’s XML serialization format allows automated exchange of use case data between modeling tools, requirements management systems, and documentation platforms. This is particularly valuable in large-scale smart grid projects involving multiple stakeholders and system integrators.

Practical Implementation Guidance

When implementing IEC 62559-2 in real projects, engineering teams should consider the following best practices:

Establish a use case naming convention aligned with the project’s system breakdown structure
Define actors early and maintain a centralized actor registry to ensure consistency across all use cases
Use the requirements list to create a clear traceability matrix linking stakeholder needs to system functions
Version control every template element to support audit trails and impact analysis during changes

For complex projects with more than 50 use cases, consider implementing a use case management database rather than individual documents. The IEC 62559-2 XML schema is well-suited for database storage and enables powerful query capabilities (e.g., “find all use cases involving actor X” or “list requirements not yet covered by any use case”).

❓ Frequently Asked Questions

Q1: What is the relationship between IEC 62559-2 and UML use case diagrams?
A: IEC 62559-2 templates provide significantly more structured detail than standard UML use case diagrams. UML provides a graphical overview, while IEC 62559-2 adds precise textual descriptions of flows, preconditions, postconditions, and requirements tracing. The two are complementary in a complete MBSE approach.

Q2: Is IEC 62559-2 applicable only to smart grid projects?
A: No, while the standard originated from the energy domain (TC 8), the template structure is domain-agnostic and applicable to any system engineering project. It has been adopted in industrial automation, building management, electric vehicle charging infrastructure, and distributed energy resource management.

Q3: How does IEC 62559-2 relate to IEC 62559-1?
A: IEC 62559-1 provides the overall use case methodology framework and process, while IEC 62559-2 defines the specific template structures and XML serialization format. They are designed to be used together.

Q4: Can IEC 62559-2 templates be exported to requirements management tools?
A: Yes, the XML serialization format defined in the standard enables data exchange with tools such as IBM DOORS, Jama Connect, and Polarion. The requirements list template is specifically designed for this purpose.