Correspondence Rules

Several correspondence rules guide the relationships between viewpoints. Generally speaking, elements in one view may be referenced in some fashion in at least one other view. Specific correspondence rules are:

1. Physical Objects are defined with scope such that they are under the control of a single Enterprise Object. Enterprise Objects have defined roles with Physical Objects.
2. Functional Objects provide functionality to Physical Objects, as defined by PSpecs.
3. Information Flows are characterized by Communications Characteristics, which imply various communications protocol standards.
4. Information Flows are further defined by Data Flows.
5. Information Flow and Data Flow definitions suggest ITS Application Layer standards.
6. Security characteristics characterize Information Flows and Physical Objects; these characteristics in turn suggest physical and cybersecurity standards.
7. Information Flows are always accompanied by a provision agreement relationship. Such relationships are formal if both participants are centers or field equipment. They are nearly always informal if between two mobile objects. If between mobile and fixed, the relationship may be formal if personalized or individually targeted information is exchanged.

8. Coordination relationships may imply Communications Characteristics:
   
   1. An expectation of guaranteed delivery drives non-repudiation of receipt.
   2. An expectation of information provision may drive regularity and periodicity.
   3. An expectation of personal information exchange drives a high confidentiality requirement.
9. Physical object context may constrain Communications Characteristics:
   
   1. Information flows between two mobile objects (vehicle or personal) are always restricted to wireless media.
   2. Communications involving one mobile object and one fixed object involve wireless media, but may also include fixed media backhaul.
   3. Communications between two vehicles always use short range wireless communications.