You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
A DataCentre represents a private space containing a Cluster of physical servers on a wired LAN provided by a physical Router, through which the DataCentre may be connected to other networks including the Internet. The Cluster and the Router are 'resourcedBy' the Data Centre, which means they provide the means to host services or VMs that are managed by the Data Centre.
System modeller users can insert the Router, Servers and WiredLAN assets explicitly, but if they do not they are added by construction patterns.
Construction pattern DC-R+RW checks if there is a physical Router, and if not, it adds a router providing a WiredLAN to a DataCentre. In principle this is incorrect, because it is possible that a user may assert the presence of the WiredLAN but not the providing Router or vice versa.
In principle, the three assets should exist and be related as follows:
Router-resourcedBy-DataCentre
WiredLAN-providedBy-DataCentre
WiredLAN-providedBy-Router
The DataCentre cannot be inferred from the other two, as the WiredLAN and Router could exist in any Space, so it must be asserted. That leaves the following possibilities, which should be covered by separate construction patterns:
DataCentre has no related Router or WiredLAN, so both should be created along with all three relationships
DataCentre has a related Router but no WiredLAN, and the Router provides no WiredLAN, so the WiredLAN should be created with two relationships
DataCentre has a related Router providing a WiredLAN but one not related to the DataCentre, so the WiredLAN-providedBy-DataCentre relationship should be added
DataCentre has a related WiredLAN but no Router, and the WiredLAN is not provided by any Host, so the Router should be created with two relationships
DataCentre has a related WiredLAN provided by a Router but one not related to the DataCentre, so the Router-resourcedBy-DataCentre relationship should be added
DataCentre has a related WiredLAN and Router, but the WiredLAN is not provided by any Host, so the WiredLAN-providedBy-Router should be added
There is a potentially open question whether the Router must be a Router. If another Host provides a WiredLAN, this could in principle be used instead.
The text was updated successfully, but these errors were encountered:
A DataCentre represents a private space containing a Cluster of physical servers on a wired LAN provided by a physical Router, through which the DataCentre may be connected to other networks including the Internet. The Cluster and the Router are 'resourcedBy' the Data Centre, which means they provide the means to host services or VMs that are managed by the Data Centre.
System modeller users can insert the Router, Servers and WiredLAN assets explicitly, but if they do not they are added by construction patterns.
Construction pattern DC-R+RW checks if there is a physical Router, and if not, it adds a router providing a WiredLAN to a DataCentre. In principle this is incorrect, because it is possible that a user may assert the presence of the WiredLAN but not the providing Router or vice versa.
In principle, the three assets should exist and be related as follows:
The DataCentre cannot be inferred from the other two, as the WiredLAN and Router could exist in any Space, so it must be asserted. That leaves the following possibilities, which should be covered by separate construction patterns:
There is a potentially open question whether the Router must be a Router. If another Host provides a WiredLAN, this could in principle be used instead.
The text was updated successfully, but these errors were encountered: