ISO/TR 25102:2008

TECHNICAL ISO/TR
REPORT 25102
First edition
2008-02-15
Intelligent transport systems — System
architecture — “Use Case” pro-forma
template
Systèmes intelligents de transport — Architecture des systèmes —
Gabarit pro forma de «cas d'usage»

Reference number
©
ISO 2008
PDF disclaimer
This PDF file may contain embedded typefaces. In accordance with Adobe's licensing policy, this file may be printed or viewed but
shall not be edited unless the typefaces which are embedded are licensed to and installed on the computer performing the editing. In
downloading this file, parties accept therein the responsibility of not infringing Adobe's licensing policy. The ISO Central Secretariat
accepts no liability in this area.
Adobe is a trademark of Adobe Systems Incorporated.
Details of the software products used to create this PDF file can be found in the General Info relative to the file; the PDF-creation
parameters were optimized for printing. Every care has been taken to ensure that the file is suitable for use by ISO member bodies. In
the unlikely event that a problem relating to it is found, please inform the Central Secretariat at the address given below.

©  ISO 2008
All rights reserved. Unless otherwise specified, no part of this publication may be reproduced or utilized in any form or by any means,
electronic or mechanical, including photocopying and microfilm, without permission in writing from either ISO at the address below or
ISO's member body in the country of the requester.
ISO copyright office
Case postale 56 • CH-1211 Geneva 20
Tel. + 41 22 749 01 11
Fax + 41 22 749 09 47
E-mail copyright@iso.org
Web www.iso.org
Published in Switzerland
ii © ISO 2008 – All rights reserved

Contents Page
Foreword. v
Introduction . vi
1 Scope . 1
2 Terms and definitions. 1
3 Abbreviated terms . 2
4 Background . 3
4.1 TC 204 Working Group WG 1. 3
4.2 Statement of requirements . 3
4.3 Use cases . 3
4.4 “Unified Modeling Language” (UML). 4
4.5 The bottom line value of “Use Cases”. 5
5 Use case elements. 6
5.1 General. 6
5.2 Normal use cases description. 6
5.3 “Use Case” template . 7
5.4 “Use Case” title name . 7
5.5 “Use Case” description. 7
5.6 “Use Case” scope. 7
5.7 “Use Case” level . 7
5.8 Target system release . 7
5.9 “Use Case” level of generality or abstraction .7
5.10 “Use Case” author/primary actor. 8
5.11 “Use Case” stakeholders/participants . 8
5.12 “Use Case” goal. 8
5.13 “Use Case” references to requirements. 8
5.14 “Use Case” assumptions. 8
5.15 “Use Case” technology restrictions . 8
5.16 Relationship to other “Use Cases”. 8
5.17 Actors associated with “Use Case”. 8
5.18 “Use Case” triggers. 9
5.19 “Use Case” pre-conditions . 9
5.20 “Use Case” scenarios . 9
5.21 “Use Case” expected outcomes . 9
5.22 “Use Case” acceptance criteria . 9
5.23 “Use Case” exceptions . 10
5.24 “Use Case” post-conditions . 10
5.25 “Use Case” extensions . 10
5.26 “Use Case” inclusions . 10
5.27 “Use Case” business rules. 10
5.28 “Use Case” verification approach. 10
5.29 “Use Case” test cases. 11
5.30 “Use Case” version . 11
5.31 “Use Case” modification history. 11
5.32 “Use Case” approvals . 11
5.33 “Use Case” application notes . 11
5.34 “Use Case” open issues . 11
6 Suggested “Use Case Template”. 11
6.1 “Use Case Template” rationale . 11
6.2 Form of “Use Case Template”. 11
6.3 Example “Use Case Template”. 11
Bibliography . 13

iv © ISO 2008 – All rights reserved

Foreword
ISO (the International Organization for Standardization) is a worldwide federation of national standards bodies
(ISO member bodies). The work of preparing International Standards is normally carried out through ISO
technical committees. Each member body interested in a subject for which a technical committee has been
established has the right to be represented on that committee. International organizations, governmental and
non-governmental, in liaison with ISO, also take part in the work. ISO collaborates closely with the
International Electrotechnical Commission (IEC) on all matters of electrotechnical standardization.
International Standards are drafted in accordance with the rules given in the ISO/IEC Directives, Part 2.
The main task of technical committees is to prepare International Standards. Draft International Standards
adopted by the technical committees are circulated to the member bodies for voting. Publication as an
International Standard requires approval by at least 75 % of the member bodies casting a vote.
In exceptional circumstances, when a technical committee has collected data of a different kind from that
which is normally published as an International Standard (“state of the art”, for example), it may decide by a
simple majority vote of its participating members to publish a Technical Report. A Technical Report is entirely
informative in nature and does not have to be reviewed until the data it provides are considered to be no
longer valid or useful.
Attention is drawn to the possibility that some of the elements of this document may be the subject of patent
rights. ISO shall not be held responsible for identifying any or all such patent rights.
ISO/TR 25102 was prepared by Technical Committee ISO/TC 204, Intelligent transport systems.
Introduction
The objective of this Technical Report is to propose a pro-forma template for “Use Cases” for intelligent
transport systems (ITS), and provide guidance on how the template should be used.
While this Technical Report provides a pro forma template, the elements may be augmented or omitted as
applicable. The Technical Report provides guidance to develop use cases and is a guide rather than a
prescription to be followed without variation.
A “Use Case Model” is simply a term to describe, and in many cases define, a user's view of interactions with
(and within) the system. Use cases show how entities interact, and are usually presented as structured text or
diagrammatically.
“Use Cases” are a means to define requirements for a system in terms of the primary users (known as actors)
that interact with the system and the scenarios or activities that are performed by the system in response to
stimuli from the actors or from other system entities. Each “Use Case” has a starting state and conditions, a
series of activity steps that together comprise a scenario, and a finishing state and conditions. There may be
more than one scenario in a “Use Case”. The “Use Case” should also include exceptional cases with alternate
outcomes.
In many situations, including some International Standards, there has been more attention paid to the
definition of “Actors”, “Use Cases” and the relationships between them, rather than the detail of each “Use
Case”, especially the explanatory text that goes with the “Use Case”.
The identification of “Use Cases” is most frequently associated with use case model diagrams using the
[4]
“Unified Modelling Language” (UML) . In this Technical Report, for consistency, this methodology is used
throughout. However, “Use Cases” can be elaborated and developed for any system methodology and are as
appropriate for process oriented methodology as object oriented methodology, and indeed there is no
requirement to use any technical architecture methodology at all. A “Use Case” can often be elaborated
simply with pen and paper.
The benefits of applying use cases to the development of ITS include the following:
⎯ Common, standardized approach available for the first segment of software system development, namely
requirements elicitation and definition;
⎯ Requirements are related to each other informally, thus providing some assurance of compatibility and
consistency.
vi © ISO 2008 – All rights reserved

TECHNICAL REPORT ISO/TR 25102:2008(E)

Intelligent transport systems — System architecture — “Use
Case” pro-forma template
1 Scope
This Technical Report discusses the application of “Use Cases” for requirements and related aspects of a
software-intensive system such as an intelligent transport system (ITS).
The scope of this Technical Report is to provide a pro-forma template for the consistent consideration and
development of “Use Cases” within ITS International Standards and associated deliverables.
NOTE This Technical Report provides a pro forma template; the elements may be augmented or omitted as
applicable. It provides guidance to develop use cases and is a guide rather
...