A.2 Second Example

32.1563GPPFixed Mobile Convergence (FMC) model repertoireRelease 17Telecommunication managementTS

This shows a <<ProxyClass>> named YyyFunction. It represents all IOCs listed in the attached (or associated) Note. All the listed IOCs, in the context of this example, have link (internal and external) relations.

This shows a <<ProxyClass>> InternalYyyFunction. It represents all IOCs listed in the attached (or associated) Note.

This shows a <<ProxyClass>> Link_a_z and ExternalLink_a_z. They represent all IOCs listed in the attached (or associated) Note.

Figure A.2-1: <<ProxyClass>> Notation Example A.2

Annex B (normative):
Attribute properties

Table B.1 shows the impact of the "isWritable", "defaultValue" and "multiplicity" attribute properties on the behavior of managers and agents upon object creation, and on attribute values directly after object creationTable B.1: Attribute properties

isWritable

defaultValue

multiplicity ≥ 1

Impact of attribute properties on the behaviour of agents and managers upon object creation, and on attribute values directly after object creation

The manager may provide a value.

If not provided, the agent shall set the value to the default value.

-> The attribute has the default value or some other value.

The manager may provide a value.

If not provided, the agent shall set the value to the default value.

-> The attribute has the default value, or some other value.

Note, if "isInvariant: True", the attribute never has no value, even though this is allowed.

The manager shall provide an attribute value.

-> The attribute has some value.

The manager may provide a value.

If not provided, the agent shall not provide a value.

-> The attribute has some value, or no value.

The manager shall not provide a value.

The agent shall set the value to the default value.

-> The attribute has the default value.

The manager shall not provide a value.

The agent shall set the value to the default value.

-> The attribute has the default value.

Note, if "isInvariant: True", the attribute never has no value, even though this is allowed

Not valid.

Reason:

The manager shall not provide a value.

The agent shall not provide a value.

-> The attribute has no value, which is an invalid state

The manager shall not provide a value.

The agent shall not provide a value.

-> The attribute has no value.

Note, if "isInvariant: True", the attribute has invariantly no value, which is a valid state but may not make sense.

Annex C (normative):
Design patterns