Certification System Operator --> Certification System:
certification operator input
Definitions
certification operator input (Information Flow): User input from certification personnel that support monitoring, management, and documentation of the certification process and results.
Certification System Operator (Source Physical Object): The 'Certification System Operator' represents the human operator who monitors and manages ITS device and application certification.
Certification System (Destination Physical Object): The 'Certification System' verifies that devices and applications meet standards for participation in the ITS environment. Particular requirements vary depending on the type of certification; applications may be certified for performance and adherence to standards or specifications; devices may be similarly certified, and will also typically be subject to security-related interrogation.
Included In
This Triple is in the following Service Packages:
This triple is associated with the following Functional Objects:
This Triple is described by the following Functional View Data Flows:
This Triple has the following triple relationships:
| Relationship | Source | Destination | Flow |
|---|---|---|---|
| Interactive | Certification System | Certification System Operator | certification operator presentation |
Communication Solutions
No communications solutions identified.Characteristics
| None defined |
| Interoperability | Description |
|---|---|
| Not Applicable | Interoperability ratings don't apply per se to some types of interfaces like human interfaces. These interfaces may still benefit from associated standards (e.g., ergonomic and human factors standards for human interfaces), but the primary motive for these standards is not interoperability. |
Security
| Information Flow Security | ||||
|---|---|---|---|---|
| Confidentiality | Integrity | Availability | ||
| Rating | High | High | High | |
| Basis | This value is derived from the specific flows satisfied by this super-flow. HIGH is set because some flows may require it. If the implementation includes flows with only a MODERATE or LOW confidentiality requirement, then this could be MODERATE or LOW, as appropriate. | This value is derived from the specific flows satisfied by this super-flow. HIGH is set because some flows may require it. If the implementation includes flows with only a MODERATE integrity requirement, then this could be MODERATE. | Any application testing or certification will fail without the ability to stimulate and receive responses. Thus unlike most super-flow characteristics, this is set HIGH as without availability there is no chance of success. | |