Physical Address
304 North Cardinal St.
Dorchester Center, MA 02124
ISO/TR 25102 — Intelligent Transport Systems: Use Case Pro-Forma Template for System Architecture
Standardized Use Case Template for ITS Requirements Engineering
1. Introduction to ISO/TR 25102 and the Need for Use Case Standardization
ISO/TR 25102:2008, developed by ISO/TC 204 (Intelligent Transport Systems), provides a pro-forma template for “Use Cases” in the context of intelligent transport systems (ITS). The Technical Report emerged from the recognition that use case development across ITS standards was arbitrary and inconsistent, leading to confusion among stakeholders and reducing the effectiveness of requirements capture.
In complex software-intensive systems such as ITS, the unambiguous communication of functional requirements between domain experts, system architects, developers, and end users is paramount. Use cases serve as a bridge — they describe how external entities (actors) interact with a system to achieve specific goals, expressed in narrative text that is accessible to non-technical stakeholders. ISO/TR 25102 formalizes this process by providing a structured template that ensures completeness, consistency, and traceability across all use cases within a project.
Use cases focus on the what and why of system behaviour, not the how. This implementation-neutral perspective allows stakeholders to agree on requirements before committing to specific technologies or architectures.
2. Anatomy of the Use Case Template
The core contribution of ISO/TR 25102 is its detailed use case template, comprising over thirty distinct elements organized into static and dynamic sections. The static section captures identity and context, while the dynamic section describes behavioural scenarios.
2.1 Template Structure
Each use case defined in accordance with ISO/TR 25102 includes the following essential elements:
| Element | Description | Example (ITS Context) |
|---|---|---|
| Use Case Name | Short verb phrase identifying the use case | “Monitor Pedestrian Traffic” |
| Primary Actor | Entity that initiates the interaction | Traffic Management Centre |
| Scope | System boundary (whole system, subsystem, function) | Urban Traffic Control Subsystem |
| Level | Abstraction level (user goal, sub-function, business) | User goal |
| Pre-conditions | State that must hold before execution | Sensors are operational |
| Post-conditions | State that must hold after successful completion | Traffic data logged |
| Main Scenario | Sequence of steps (normal flow) | Step 1: Detect vehicle… Step 5: Update signal |
| Extensions | Alternative flows for error/exceptional conditions | Sensor failure → fallback timing |
| Business Rules | Policies constraining the use case | Priority must be given to emergency vehicles |
| Acceptance Criteria | Measurable conditions for validation | Detection latency < 2 seconds |
2.2 Scenarios and Step Decomposition
A use case may contain multiple scenarios, each representing a distinct thread of activity. Within each scenario, individual steps describe atomic actions. ISO/TR 25102 explicitly supports step extensions — branches triggered by specific conditions — enabling the complete specification of both happy-path and error-handling behaviour without cluttering the primary flow.
A common pitfall in use case modelling is over-engineering the UML diagram with stereotyped relationships while neglecting the textual descriptions. ISO/TR 25102 emphasizes that the text is the most important artefact — diagrams are merely a convenient pictorial index.
3. Engineering Design Insights and Practical Application
From an engineering perspective, ISO/TR 25102 offers several valuable insights for practitioners developing complex systems:
3.1 Traceability and Requirements Management
The template includes fields for requirements references, assumptions, technology restrictions, and verification approaches. This creates a closed-loop traceability chain from stakeholder needs through use case specification to test case definition. In large-scale ITS deployments (e.g., city-wide traffic management), maintaining this traceability is critical for managing change impact and regulatory compliance.
3.2 Stakeholder Communication
The narrative, non-technical nature of use cases makes them an effective communication tool between engineers and non-technical stakeholders (policy makers, transport authorities, end users). This reduces the risk of building a system that satisfies the specification but fails to meet actual user needs.
3.3 Reuse and Standardization
The standardized template enables use case libraries to be developed and shared across projects, promoting reuse of well-defined interaction patterns. For ITS standards developers, this consistency is particularly valuable when defining common services such as electronic fee collection, traveller information, or traffic management.
Adopting the ISO/TR 25102 template early in the development lifecycle helps identify missing requirements, clarifies system boundaries, and provides a solid foundation for project planning, cost estimation, and risk assessment.
4. Frequently Asked Questions
Q1: Does ISO/TR 25102 require the use of UML?
No. The template is tool-agnostic and can be implemented using simple text documents, spreadsheets, or dedicated requirements management tools. However, when used alongside UML, the template provides a textual counterpart that enriches diagrammatic use case models.
No. The template is tool-agnostic and can be implemented using simple text documents, spreadsheets, or dedicated requirements management tools. However, when used alongside UML, the template provides a textual counterpart that enriches diagrammatic use case models.
Q2: Must all 30+ template fields be populated?
No. The Technical Report explicitly states that elements may be augmented or omitted as applicable. Empty rows may be deleted. The template is a guide, not a prescription.
No. The Technical Report explicitly states that elements may be augmented or omitted as applicable. Empty rows may be deleted. The template is a guide, not a prescription.
Q3: Can this template be used outside the ITS domain?
Yes. Although developed within ISO/TC 204, the template is domain-independent and applicable to any software-intensive system where use case modelling is employed.
Yes. Although developed within ISO/TC 204, the template is domain-independent and applicable to any software-intensive system where use case modelling is employed.
Q4: How does this template support agile development?
The template’s modular structure allows use cases to be prioritized and elaborated incrementally. High-priority use cases can be fully detailed while lower-priority ones remain as placeholders, aligning well with iterative and agile methodologies.
The template’s modular structure allows use cases to be prioritized and elaborated incrementally. High-priority use cases can be fully detailed while lower-priority ones remain as placeholders, aligning well with iterative and agile methodologies.
📥 Standard Documents Download
No download files available yet