UAF 1.1 RTF Avatar
  1. OMG Issue

UAF11 — Inconsistency with Constraint [e] for Implements.supplier

Open Closed All
  • Key: UAF11-34
  • Status: closed  
  • Source: INCOSE ( Mr. Matthew Hause)
  • Summary:

    Page 43, under Figure 38: Constraint [e] for Implements.supplier says a ResourceConnector implements an OperationalConnector or ResourceConnector? Why? I understand Resource to Operational but why Resource to Resource? If it’s to show different levels of abstraction, then shouldn’t the same be available for Operational to Operational?
  • Reported: UAF 1.0 — Thu, 11 Jan 2018 06:30 GMT
  • Disposition: Closed; No Change — UAF 1.1
  • Disposition Summary:

    Needed to support DoDAF SV-2

    Resource Connector implementing another Resource Connector is needed to support DoDAF SV-2. Connectors in DoDAF SV-2 are considered to be physical. Connectors in SV-1 are considered to be logical. To show how physical connectors in the SV-2 realise logical connectors in the SV-1 implements relationship is used.
  • Updated: Tue, 8 Oct 2019 17:49 GMT