Design Consideration. 6.1 All materials used by the DEVELOPER shall comply with the requirements of the relevant Specifications, Codes and Rules issued by the South African Bureau of Standards or by the British Standards Institution where the former do not exist. Only undamaged materials shall be used in the works. All work shall be executed in accordance with the manufacturer’s instructions.
Design Consideration. 2.1 The aesthetics of the new Control Cab need not conform with the established architectural style of the existing airport but should be harmonious and aesthetically pleasing. The structural, electrical, and mechanical components must be coordinated to achieve a facility that meets the operational criteria and requirements set forth by an established international standard for that facility. The interior and exterior design should be functional; all designs shall meet the requirements of the local authorities and the local regulatory body ASSI.
Design Consideration. One design goal of ServiceTrust is to help the service consumers evaluate the trustworthiness of the service providers. We believe that the evaluation of service providers’ reputation should be based on their long-term reputation. The reasons are twofold. First, long-term reputation can highlight service providers’ performance in the long term and smooth out fluctuations in the short term. Second, service providers’ expectation of long-term reputation creates an incentive for their good performance at present. Another design goal of ServiceTrust is to help protect the service consumers from threats in the open SOC environment. A widely recognised threat that the service consumers are exposed to in the open SOC environment is that malicious service providers manipulate service consumers to report incorrect feedbacks in order to boost their reputations or to ruin their competitors’ reputations [58]. It can also be done by malicious service providers to fake service consumers. Another major threat is QoS abuse, where service providers strategically alter their behaviour in QoS offering and then provide fraudulent service transactions in order to earn profit [101]. Due to the above issues, in service selection, approaches should be provided to help the service consumers evaluate the trustworthiness of the service providers, as suggested but not specified in [5, 54, 107]. However, sometimes it is difficult for a service consumer to determine how much it can trust a service provider due to the lack of sufficient experience and knowledge about the service provider. A direct approach to address this issue is to use a trust system which collects and processes feedbacks about service providers’ past behaviour [51, 88, 92, 104]. However, to the best of our knowledge, no trust system has been tailored for service selection in the open SOC environment and the threats described earlier have not been properly addressed. Furthermore, different from the peers in the peer-to-peer (P2P) environment, the service providers in the SOC environment usually have unique identifications in order for the service consumers to identify their services. Therefore, existing trust systems in the P2P environment, which usually put a lot of effort in maintaining peers’ anonymity property, are generally unsuitable to be directly applied in the SOC environment. To summarise, ServiceTrust should provide two functions:
Design Consideration
