-A system cannot fulfill its purpose until it is - -2
-deployed. And deploying a system involves physically placing the - -3
-system's executable modules on the hardware devices on which - -4
-they are supposed to run. So when you do that, - -5
-you're basically mapping your components and connectors to specific - -6
-hardware elements. Here in this diagram, for instance, I'm - -7
-showing the same components that we saw in the - -8
-previous diagram, but we see them deployed on a laptop, - -9
-which is depicted here in this way, and on two - -10
-smartphones that are represented here, or PDAs, if you wish. - -11
-So why do we this, why do we create - -12
-a deployment perspective for our architecture? Well, because the deployment - -13
-view of an architecture can be critical in assessing whether - -14
-the system will be able to satisfy its requirement. Because - -15
-doing this mapping allows you to discover and assess other - -16
-characteristics of your system that you might not have considered - -17
-up to now. For instance, using a deployment view like this - -18
-one and knowing the characteristics of the hardware devices, one might - -19
-be able to assess the system in terms of available memory. - -20
-Is there going to be enough memory available to run the system, - -21
-for example, on this device? Power consumption. Is the power consumption - -22
-profile going to be larger than what the device can handle? - -23
-Or again the required network bandwidth. Does the system have enough - -24
-network bandwidth to enable the required interactions? And so on. So all - -25
-of these characteristics, all of these qualities, you can assess when - -26
-you do this final mapping of the components to the hardware elements. -- cgit 1.4.1