Trust in Computer Systems and the Cloud

CHAPTER 5The Importance of Systems

Throughout this book, we have talked about computer systems. In Chapter 3, we offered a definition, of which the initial statement was:

A system is a set of components—for example, hardware, software, firmware, data, human users—which can be considered as a single entity for the purposes of one or more specific architectural views of abstractions.

This, and the broader issue of non-decomposability, will be useful when we consider the importance of trust relationships. However, in order to understand some of the problems around trust within systems made up of computers, or within the components of computers that are considered, when composed, as systems, we need to consider in more detail what computer systems look like.

System Design

While we have neither the space nor the need to perform a full examination of computer systems design—a whole field of research and endeavour of its own—there are nevertheless some core concepts and considerations that we need to consider and understand as they have—or can have—a direct bearing on the trust relationships between components and systems.

Those designing computer systems—typically known as architects of one type or another (systems architects, software architects, cloud architects, security architects, et al.)—tend to talk about layers when they discuss or describe the various components in which they are interested. Layers are important because it is well-nigh impossible for any one person to ...