Knowledge Base

Back

Interface Compliance Errors

In case of an interface compliance error, it can have typically two main causes: it can be a "trace error" or a "refusals error":

  1. When the interface compliance error is a trace error, this does not mean: "The interface tries to do something which is not allowed by the design". Instead, it means: "The design does something that is not allowed by the interface". The corresponding text in the sequence diagram is "Action not allowed".
  2. When the interface compliance error is a refusals error, this does not mean: "The interface tries to do something which is not allowed by the design". Instead, it means: "The design refuses to do something of which the interface says the design must be able to do". The corresponding text in the sequence diagram is "Missing action". Note that in this case, the last action in the sequence diagram of the interface is just one possible action that the interface model can do and which is refused by the design; it is very possible that other actions are also allowed and are also refused by the design. In one of the upcoming versions of the ASD:Suite we will show all possible actions that are allowed by the interface and that are refused by the design rather than just one possible counter example.