AS ISO 29481.1:2018 Building information models—Information delivery manual
A.2.2.3  Create exchange requirement
Exchange requirements should then be created. Wherever possible, they should re-use the resources of existing exchange requirements.
A.2.3  Information constraint customisation
A.2.3.1  Define information constraints
The set of information constraints that may need to be applied to further configure an existing (or newly defined) exchange requirement should be defined. These may be used to control properties to be asserted or values that can be assigned.
A.2.3.2  Information constraint localization
Information constraint localization assumes that an exchange requirement exists for the purpose required but that it does not meet the needs for use within a particular location. Location may be a place (country, region, etc.), a project or a framework of working agreed between members of a project team.
Information constraints are applied to individual units of information within the context of the exchange requirement to make it applicable at a particular location. Note that the same information unit may have different information constraints applied in the context of a different exchange requirement or for a different location.
A.2.4.1  General information
Reverse engineering assumes that software already exists that is capable of importing the information required to perform a target task, but the specific information items are not clearly documented. This process is not suitable for identifying the information requirement for export data because various information use cases of the export data may exist. Hence, the information requirement for export data should be specified from the receiving application perspective. The typical way of doing reverse engineering is to define each step in a software tool for achieving a target result and then work through the scenario to identify and specify individual data items that are required from upstream software applications.
A.2.4.2  Define scenario
Define each step to achieve the target result within a software application as a scenario. This scenario may be defined as a process map or as a detailed textual description that can be used as the overview description of an exchange requirement.
A.2.4.3  Identify required data
Work through the defined scenario within the software application and specify all the data required to achieve a target result. For each data item specified, check if it should be acquired from other software applications. If so, it should be included in an exchange requirement for import data.