SIST ES 202 915-13 V1.1.1:2005

• Abstract:

  Specify the Policy Management aspects of the interface. PARLAY version 4.0.

• Status: Published
• Publication Date: 31-Dec-2004
• ICS: 33.040.01 - Telecommunication systems in general
• Technical Committee: SPN - Services and Protocols for Networks
• Current Stage: 6060 - National Implementation/Publication (Adopted Project)
• Start Date: 01-Jan-2005
• Due Date: 01-Jan-2005
• Completion Date: 01-Jan-2005
• Ref Project: ETSI ES 202 915-13 V1.1.1 (2003-01) - Open Service Access (OSA); Application Programming Interface (API); Part 13: Policy management SCF

SIST ES 202 915-13 V1.1.1:2005 is the Slovenian adoption of ETSI ES 202 915-13, published by SIST. It specifies the Policy Management Service Capability Feature (SCF) of the Open Service Access (OSA) Application Programming Interface (API) and shows how policy domains, repositories, rules, conditions, actions, and policy events are managed through the interface. The document is aimed at application developers, network operators, service providers, and policy administrators who need to create, view, subscribe to, or generate policy information.

What does SIST ES 202 915-13 V1.1.1:2005 specify?

SIST ES 202 915-13 V1.1.1:2005 specifies the Policy Management aspects of the OSA API, using PARLAY version 4.0. It defines the interface behavior, the object model, and the data types used to manage policy information and policy-enabled services.

The document is organized around the main technical views used in OSA specifications:

• scope and references
• definitions and abbreviations
• Policy Management SCF overview
• sequence diagrams
• class diagrams
• service interface specifications
• Policy Management interface classes
• state transition diagrams
• data definitions
• policy management exception classes

Annex	What it covers
Annex A	Normative OMG IDL description of the Policy Management SCF
Annex B	Informative contents of 3GPP OSA R5 Policy Management
Annex C	Informative record of changes, including interfaces, methods, data definitions, service properties, exceptions, and other items

In practice, this means the document is not just a high-level description. It also gives the interface structure and the formal elements needed to implement or integrate policy management consistently.

What are the key requirements of SIST ES 202 915-13 V1.1.1:2005?

SIST ES 202 915-13 V1.1.1:2005 defines a transaction-based policy management interface where clients create, modify, browse, and remove policy objects under authorization control. It also defines how policy rules are built from conditions and actions, how time validity and events work, and how applications receive event notifications.

Transaction control and authorization

Clause 8.1 defines IpPolicyManager as the main entry point for policy management. Clients use it to obtain references to domains and repositories, list their names, create new objects, and remove existing ones.

All policy management operations are subject to authorization checks, and the interface only returns data the client is allowed to see. In practice, this means access to policy structure is not global - the caller sees only the objects covered by its privileges. Clause 8.1 also defines startTransaction(), commitTransaction(), and abortTransaction(), and the exception classes state that transactions cannot be nested.

Policy hierarchy and reusable content

Clause 8.3 defines IpPolicyDomain as a generalized aggregation container for nested domains, groups, rules, event definitions, and variable sets. Clause 8.4 defines IpPolicyGroup as a container for groups and rules. Clause 8.5 defines IpPolicyRepository as the reusable container for policy conditions and actions.

This hierarchy matters because it separates structure from reuse. A repository is used for reusable policy objects, while a rule or domain can hold objects tied to a specific policy context. The sequence diagrams show both approaches: reusable conditions and actions can be created in a repository and then referenced from rules, or created directly inside a rule when they are local to that rule.

Policy rule logic

Clause 8.6 defines IpPolicyRule as the "If Condition then Action" object. It supports condition lists, action lists, and a validity-period condition. The document says a rule can use disjunctive normal form (DNF) or conjunctive normal form (CNF) through ConditionListType, and each condition list element can be grouped and negated.

The Mandatory attribute tells whether evaluation must be attempted. PolicyRoles carries role combinations, and SequencedActions controls whether action ordering is mandatory, recommended, or not significant. In practice, this is what a policy administrator uses to express whether a rule must run, who it applies to, and whether action order matters.

Conditions, actions, and expressions

Clause 8.7 defines IpPolicyCondition as the base condition type. Clause 8.8 defines IpPolicyTimePeriodCondition, which controls when a rule is active, and clause 8.9 defines IpPolicyAction as the base action type.

Clauses 8.12 and 8.14 define expression-based condition and action types. IpPolicyExpressionCondition evaluates an expression, and its grammar allows variables, comparison operators, and arithmetic operators. IpPolicyExpressionAction evaluates an expression as an action. In practice, this gives the policy model a way to express business logic directly, such as comparing values or calculating a new state.

Event definitions, event conditions, and notifications

Clause 8.10 defines IpPolicyEventDefinition as the template for events, with required and optional attributes. Clause 8.11 defines IpPolicyEventCondition, which is satisfied when a matching event is generated. Clause 8.13 defines IpPolicyEventAction, which generates an event instance.

Clause 8.3 also defines createNotification() and destroyNotification(), and clause 8.16 defines IpAppPolicyDomain with reportNotification(). In practice, this is the subscription path: a client registers the events it wants, receives a session identifier, and is then notified when matching events occur.

Iteration and discovery

Clause 8.15 defines IpPolicyIterator, which returns names in batches using getList(startIndex, numberRequested). Several interfaces also provide count and iterator methods for domains, repositories, groups, rules, event definitions, conditions, and actions.

This matters when a policy store is large or access-controlled. The client can page through authorized names rather than trying to retrieve everything at once.

Time-based validity

Clause 8.8 explains how IpPolicyTimePeriodCondition can limit a rule to specific periods. The attributes include TimePeriod, MonthOfYearMask, DayOfMonthMask, DayOfWeekMask, TimeOfDayMask, and LocalOrUtcTime.

These values are combined to define when the rule is active. In practice, this is how a policy administrator expresses schedules such as specific dates, recurring days, or time-of-day windows.

What terms does SIST ES 202 915-13 V1.1.1:2005 define?

• Open Service Access (OSA) - An architecture that lets application developers use network functionality through an open standardized interface.
• Application Programming Interface (API) - The interface layer defined here for accessing policy management functions.
• Service Capability Feature (SCF) - A functional part of the OSA API; this document covers the Policy Management SCF.
• Policy Repository - A container for reusable policy conditions and actions that can be referenced by one or more rules.
• PolicyRule - A policy object that expresses "if condition then action" behavior, with optional timing and action-order control.
• PolicyTimePeriodCondition - A condition type that controls when a rule is valid based on calendar or time-of-day criteria.
• Application Service Provider (ASP) - A third-party application provider that may use the policy management interface to host or consume policy-enabled services.

Who uses SIST ES 202 915-13 V1.1.1:2005?

SIST ES 202 915-13 V1.1.1:2005 is used by network operators, service providers, ASPs, and application developers who need to manage policy-controlled services. It is also relevant to policy administrators and engineers responsible for service logic, access control, event handling, and rule maintenance.

In practice, users apply it to tasks such as:

• creating and organizing policy domains and groups
• defining reusable conditions and actions in repositories
• building rules for charging, call control, load balancing, or similar services
• subscribing to and generating policy events
• managing time-based activation of rules
• checking authorized visibility of policy objects

The sequence examples show both operator-managed repositories and ASP-managed rules, so the document fits shared network-service scenarios where different parties contribute policy content.

Which standards are used with SIST ES 202 915-13 V1.1.1:2005?

The document relies on two companion parts of the same OSA API family:

• ETSI ES 202 915-1, Open Service Access (OSA); Application Programming Interface (API); Part 1: Overview - supplies the common terms, definitions, abbreviations, and reference framework used throughout the series.
• ETSI ES 202 915-2, Open Service Access (OSA); Application Programming Interface (API); Part 2: Common Data Definitions - supplies data types that are reused by the Policy Management part.

Clause 2 says the references listed in ES 202 915-1 apply as provisions when cited in this document. In practice, that means users should read the overview and common data definitions alongside this part to interpret the interface correctly.

What does the SIST ES 202 915-13 V1.1.1:2005 document contain?

SIST ES 202 915-13 V1.1.1:2005 contains sequence diagrams that show how policy repositories, domains, rules, conditions, actions, and notifications are used in practice. It includes examples for building rules from reusable repository objects, creating and modifying domains, generating and receiving policy events, and supporting prepaid subscriber services.

It also contains UML class diagrams for the policy object model, detailed interface specifications for methods and parameters, and data definitions for policy-specific types such as condition lists, action lists, keywords, and references. The policy model is illustrated with figures for nested domains, nested groups, and rule structure, and the expression and time-period sections explain the logic used in practical implementations.

Annex A provides the formal OMG IDL description. Annex B identifies the relation to 3GPP OSA R5 Policy Management. Annex C records listed changes to interfaces, methods, data definitions, service properties, exceptions, and other items.

SLOVENSKI STANDARD
01-januar-2005
Odprti dostop do storitve (OSA) – Vmesnik za aplikacijsko programiranje (API) –
13. del: Upravljanje politike SCF
Open Service Access (OSA); Application Programming Interface (API); Part 13: Policy
management SCF
Ta slovenski standard je istoveten z: ES 202 915-13 Version 1.1.1
ICS:
33.040.01 Telekomunikacijski sistemi Telecommunication systems
na splošno in general
2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.

ETSI Standard
Open Service Access (OSA);
Application Programming Interface (API);
Part 13: Policy management SCF

�
2 ETSI ES 202 915-13 V1.1.1 (2003-01)

Reference
DES/SPAN-120091-13
Keywords
API, IDL, OSA, UML
ETSI
650 Route des Lucioles
F-06921 Sophia Antipolis Cedex - FRANCE

Tel.: [phone]  Fax: [phone]

Siret N° 348 623 562 00017 - NAF 742 C
Association à but non lucratif enregistrée à la
Sous-Préfecture de Grasse (06) N° 7803/88

Important notice
Individual copies of the present document can be downloaded from:
http://www.etsi.org
The present document may be made available in more than one electronic version or in print. In any case of existing or
perceived difference in contents between such versions, the reference version is the Portable Document Format (PDF).
In case of dispute, the reference shall be the printing on ETSI printers of the PDF version kept on a specific network drive
within ETSI Secretariat.
Users of the present document should be aware that the document may be subject to revision or change of status.
Information on the current status of this and other ETSI documents is available at
http://portal.etsi.org/tb/status/status.asp
If you find errors in the present document, send your comment to:
[e-mail]
Copyright Notification
No part may be reproduced except as authorized by written permission.
The copyright and the foregoing restriction extend to reproduction in all media.

© European Telecommunications Standards Institute 2003.
© The Parlay Group 2003.
All rights reserved.
TM TM TM
DECT , PLUGTESTS and UMTS are Trade Marks of ETSI registered for the benefit of its Members.
TM
TIPHON and the TIPHON logo are Trade Marks currently being registered by ETSI for the benefit of its Members.
TM
3GPP is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners.
ETSI
3 ETSI ES 202 915-13 V1.1.1 (2003-01)
Contents
Intellectual Property Rights.7
Foreword.7
1 Scope.8
2 References.8
3 Definitions and abbreviations.8
3.1 Definitions.8
3.2 Abbreviations.8
4 Policy Management SCF.9
5 Sequence Diagrams.9
5.1 Use of Policy Repository.9
5.2 Introduce condition and action into rule.11
5.3 Create and receive an event.13
5.4 Create and modify domain .15
5.5 ASP offering services to prepaid subscribers .17
6 Class Diagrams.20
7 The Service Interface Specifications.22
7.1 Interface Specification Format .22
7.1.1 Interface Class.22
7.1.2 Method descriptions.22
7.1.3 Parameter descriptions.22
7.1.4 State Model.22
7.2 Base Interface.22
7.2.1 Interface Class IpInterface .22
7.3 Service Interfaces.23
7.3.1 Overview.23
7.4 Generic Service Interface .23
7.4.1 Interface Class IpService .23
7.4.1.1 Method setCallback().23
7.4.1.2 Method setCallbackWithSessionID().23
8 Policy Management Interface Classes.24
8.1 Interface Class IpPolicyManager.24
8.1.1 Method createDomain().25
8.1.2 Method getDomain().26
8.1.3 Method removeDomain().26
8.1.4 Method getDomainCount().26
8.1.5 Method getDomainIterator().27
8.1.6 Method findMatchingDomains().27
8.1.7 Method createRepository().27
8.1.8 Method getRepository().28
8.1.9 Method removeRepository().28
8.1.10 Method getRepositoryCount().28
8.1.11 Method getRepositoryIterator().29
8.1.12 Method startTransaction().29
8.1.13 Method commitTransaction().30
8.1.14 Method abortTransaction().30
8.2 Interface Class IpPolicy.30
8.2.1 Attributes.31
8.2.2 Method getAttribute().32
8.2.3 Method setAttribute().32
8.2.4 Method getAttributes().32
8.2.5 Method setAttributes().33
ETSI
4 ETSI ES 202 915-13 V1.1.1 (2003-01)
8.3 Interface Class IpPolicyDomain.33
8.3.1 Attributes.35
8.3.2 Method getParentDomain().36
8.3.3 Method createDomain().36
8.3.4 Method getDomain().36
8.3.5 Method removeDomain().37
8.3.6 Method getDomainCount().37
8.3.7 Method getDomainIterator().37
8.3.8 Method createGroup().38
8.3.9 Method getGroup().38
8.3.10 Method removeGroup().39
8.3.11 Method getGroupCount().39
8.3.12 Method getGroupIterator().39
8.3.13 Method createRule().40
8.3.14 Method getRule().40
8.3.15 Method removeRule().40
8.3.16 Method getRuleCount().41
8.3.17 Method getRuleIterator().41
8.3.18 Method createEventDefinition().41
8.3.19 Method getEventDefinition().42
8.3.20 Method removeEventDefinition().42
8.3.21 Method getEventDefinitionCount().43
8.3.22 Method getEventDefinitionIterator().43
8.3.23 Method generateEvent().43
8.3.24 Method createNotification().44
8.3.25 Method destroyNotification().44
8.3.26 Method createVariableSet().45
8.3.27 Method getVariableSet().45
8.3.28 Method removeVariableSet().45
8.3.29 Method getVariableSetCount().46
8.3.30 Method getVariableSetIterator().46
8.3.31 Method setVariable().46
8.3.32 Method getVariable().47
8.4 Interface Class IpPolicyGroup .47
8.4.1 Attributes.48
8.4.2 Method getParentDomain().49
8.4.3 Method getParentGroup().49
8.4.4 Method createGroup().50
8.4.5 Method getGroup().50
8.4.6 Method removeGroup().50
8.4.7 Method getGroupCount().51
8.4.8 Method getGroupIterator().51
8.4.9 Method createRule().51
8.4.10 Method getRule().52
8.4.11 Method removeRule().52
8.4.12 Method getRuleCount().52
8.4.13 Method getRuleIterator().53
8.5 Interface Class IpPolicyRepository .53
8.5.1 Attributes.54
8.5.2 Method getParentRepository().55
8.5.3 Method createRepository().55
8.5.4 Method getRepository().55
8.5.5 Method removeRepository().56
8.5.6 Method getRepositoryCount().56
8.5.7 Method getRepositoryIterator().56
8.5.8 Method createCondition().57
8.5.9 Method getCondition().57
8.5.10 Method removeCondition().58
8.5.11 Method getConditionCount().58
8.5.12 Method getConditionIterator().58
8.5.13 Method createAction().59
8.5.14 Method getAction().59
ETSI
5 ETSI ES 202 915-13 V1.1.1 (2003-01)
8.5.15 Method removeAction().60
8.5.16 Method getActionCount().60
8.5.17 Method getActionIterator().60
8.6 Interface Class IpPolicyRule .61
8.6.1 Attributes.63
8.6.2 Method getParentGroup().64
8.6.3 Method getParentDomain().65
8.6.4 Method createCondition().65
8.6.5 Method getCondition().66
8.6.6 Method removeCondition().66
8.6.7 Method getConditionCount().66
8.6.8 Method getConditionIterator().67
8.6.9 Method createAction().67
8.6.10 Method getAction().68
8.6.11 Method removeAction().68
8.6.12 Method getActionCount().68
8.6.13 Method getActionIterator().69
8.6.14 Method setValidityPeriodConditionByName().69
8.6.15 Method setValidityPeriodCondition().69
8.6.16 Method getValidityPeriodCondition().70
8.6.17 Method unsetValidityPeriodCondition().70
8.6.18 Method setConditionList().70
8.6.19 Method getConditionList().71
8.6.20 Method setActionList().71
8.6.21 Method getActionList().71
8.7 Interface Class IpPolicyCondition.72
8.7.1 Attributes.73
8.7.2 Method getParentRepository().74
8.7.3 Method getParentRule().74
8.8 Interface Class IpPolicyTimePeriodCondition.74
8.8.1 Attributes.75
8.9 Interface Class IpPolicyAction.78
8.9.1 Attributes.79
8.9.2 Method getParentRepository().79
8.9.3 Method getParentRule().80
8.10 Interface Class IpPolicyEventDefinition.80
8.10.1 Attributes.80
8.10.2 Method setRequiredAttributes().81
8.10.3 Method setOptionalAttributes().81
8.10.4 Method getRequiredAttributes().82
8.10.5 Method getOptionalAttributes().82
8.10.6 Method getParentDomain().82
8.11 Interface Class IpPolicyEventCondition .83
8.11.1 Attributes.83
8.12 Interface Class IpPolicyExpressionCondition .84
8.12.1 Attributes.84
8.13 Interface Class IpPolicyEventAction.85
8.13.1 Attributes.85
8.14 Interface Class IpPolicyExpressionAction .86
8.14.1 Attributes.87
8.15 Interface Class IpPolicyIterator.88
8.15.1 Attributes.88
8.15.2 Method getList().89
8.16 Interface Class IpAppPolicyDomain .89
8.16.1 Method reportNotification().89
9 State Transition Diagrams.90
10 Data Definitions.90
10.1 Policy Management Data Definitions.90
10.1.1 TpPolicyConditionListType.90
10.1.2 TpPolicyConditionListElement.90
ETSI
6 ETSI ES 202 915-13 V1.1.1 (2003-01)
10.1.3 TpPolicyConditionList.90
10.1.4 TpPolicyConditionType.90
10.1.5 TpPolicyActionListElement.91
10.1.6 TpPolicyActionList.91
10.1.7 TpPolicyActionType.91
10.1.8 TpPolicyEvent.91
10.1.9 TpPolicyKeyword.91
10.1.10 TpPolicyKeywordSet.92
10.1.11 IpPolicyDomain.92
10.1.12 IpPolicyDomainRef.92
10.1.13 IpPolicyRepository.93
10.1.14 IpPolicyRepositoryRef.93
10.1.15 IpPolicyGroup.93
10.1.16 IpPolicyGroupRef.93
10.1.17 IpPolicyRule.93
10.1.18 IpPolicyRuleRef.93
10.1.19 IpPolicyEventDefinition.93
10.1.20 IpPolicyEventDefinitionRef.93
10.1.21 IpAppPolicyDomain.93
10.1.22 IpAppPolicyDomainRef.93
10.1.23 IpPolicyCondition.93
10.1.24 IpPolicyConditionRef.93
10.1.25 IpPolicyTimePeriodCondition.93
10.1.26 IpPolicyTimePeriodConditionRef.94
11 Policy Management Exception Classes.94
Annex A (normative): OMG IDL Description of Policy Management SCF.95
Annex B (informative): Contents of 3GPP OSA R5 Policy Management.96
Annex C (informative): Record of changes .97
C.1 Interfaces.97
C.1.1 New.97
C.1.2 Deprecated.97
C.1.3 Removed.97
C.2 Methods.97
C.2.1 New.97
C.2.2 Deprecated.97
C.2.3 Modified.98
C.2.4 Removed.98
C.3 Data Definitions.98
C.3.1 New.98
C.3.2 Modified.98
C.3.3 Removed.98
C.4 Service Properties.98
C.4.1 New.98
C.4.2 Deprecated.99
C.4.3 Modified.99
C.4.4 Removed.99
C.5 Exceptions.99
C.5.1 New.99
C.5.2 Modified.99
C.5.3 Removed.99
C.6 Others.99
History .100

ETSI
7 ETSI ES 202 915-13 V1.1.1 (2003-01)
Intellectual Property Rights
IPRs essential or potentially essential to the present document may have been declared to ETSI. The information
pertaining to these essential IPRs, if any, is publicly available for ETSI members and non-members, and can be found
in ETSI SR 000 314: "Intellectual Property Rights (IPRs); Essential, or potentially Essential, IPRs notified to ETSI in
respect of ETSI standards", which is available from the ETSI Secretariat. Latest updates are available on the ETSI Web
server (http://webapp.etsi.org/IPR/home.asp).
All published ETSI deliverables shall include information which directs the reader to the above source of information.
Foreword
This ETSI Standard (ES) has been produced by ETSI Technical Committee Services and Protocols for Advanced
Networks (SPAN).
The present document is part 13 of a multi-part deliverable covering Open Service Access (OSA); Application
Programming Interface (API), as identified below. The API specification (ES 202 915) is structured in the following
parts:
Part 1: "Overview";
Part 2: "Common Data Definitions";
Part 3: "Framework";
Part 4: "Call Control";
Part 5: "User Interaction SCF";
Part 6: "Mobility SCF";
Part 7: "Terminal Capabilities SCF";
Part 8: "Data Session Control SCF";
Part 9: "Generic Messaging SCF";
Part 10: "Connectivity Manager SCF";
Part 11: "Account Management SCF";
Part 12: "Charging SCF";
Part 13: "Policy Management SCF";
Part 14: "Presence and Availability Management SCF".
The present document has been defined jointly between ETSI, The Parlay Group (http://www.parlay.org) and the 3GPP,
in co-operation with a number of JAIN™ Community (http://www.java.sun.com/products/jain) member companies.
The present document forms part of the Parlay 4.0 set of specifications.
The present document is equivalent to 3GPP TS 29.198-13 V5.1.0 (Release 5).
ETSI
8 ETSI ES 202 915-13 V1.1.1 (2003-01)
1 Scope
The present document is part 13 of the Stage 3 specification for an Application Programming Interface (API) for Open
Service Access (OSA).
The OSA specifications define an architecture that enables application developers to make use of network functionality
through an open standardised interface, i.e. the OSA APIs.
The present document specifies the Policy Management Service Capability Feature (SCF) aspects of the interface. All
aspects of the Policy Management SCF are defined here, these being:
• Sequence Diagrams
• Class Diagrams
• Interface specification plus detailed method descriptions
• State Transition diagrams
• Data Definitions
• IDL Description of the interfaces
The process by which this task is accomplished is through the use of object modelling techniques described by the
Unified Modelling Language (UML).
2 References
The references listed in clause 2 of ES 202 915-1 contain provisions which, through reference in this text, constitute
provisions of the present document.
ETSI ES 202 915-1: "Open Service Access (OSA); Application Programming Interface (API); Part 1: Overview".
ETSI ES 202 915-2: "Open Service Access (OSA); Application Programming Interface (API); Part 2: Common Data
Definitions".
3 Definitions and abbreviations
3.1 Definitions
For the purposes of the present document, the terms and definitions given in ES 202 915-1 apply.
3.2 Abbreviations
For the purposes of the present document, the abbreviations defined in ES 202 915-1 apply.
ETSI
9 ETSI ES 202 915-13 V1.1.1 (2003-01)
4 Policy Management SCF
It is expected that more and more OSA services will use policies to express operational criteria. It is also expected that
rd
network providers will host policy-enabled services that have been written by 3 party application service providers. In
order to manage policy information and control access to it a policy management service is needed. Consistent with
this, a policy management service interface manager, IpPolicyManager, has been defined. All policy management
interfaces are accessible from IpPolicyManager.
A number of APIs have been defined to obtain services from a policy management service. These include APIs to
create, update or view policy information. Additionally APIs have been defined to facilitate interactions between clients
rd
(e.g. a 3 party application) and any policy enabled service. These include APIs to view policy events, to subscribe to
policy events and for the generation of events by clients. All APIs conform to an underlying policy information model.
Clients that perform administrative tasks, e.g. create, update or delete policy information must obtain access to
IpPolicyManager using the family of obtainInterface() methods supported by the IpAccess interface. Administrative
tasks may be performed through methods supported by IpPolicyManager.
Clients that need to interact with a specific policy enabled service (for non-administrative tasks) can obtain access to
that service's interface directly via the selectService() method supported by the IpAccess interface. It should be noted
that specific policy enabled services may support additional interfaces and methods that are not defined below.
Examples of policy enabled services include: A load balancing service that uses policies to manage application loads on
the network, a charging service that determines charging criteria based on policies, a call management service that uses
policies to direct end-user calls to appropriate call agents, etc.
The order is as follows:
• The Sequence diagrams give the reader a practical idea of how each of the
...