Java Reference
In-Depth Information
3.
AH-End-User Interaction Complexity
The perceived complexity when interacting with
the AH. Also for the AH management task, for those AHs that offer such a facility.
4.
Transfer time
Each resource that has to be installed, eventually including the AH itself.
5.
Awareness of the Involved System Processes
The layered boxes in Figure 2.8 express
this often-overlooked aspect. It's like opening up a Chinese box, only to find another one
inside and so on. This is something to be aware of at design time, especially for limited-
resource environments such as embedded devices.
Complexity here is intended to be thought of as that viewed by the End-User. Naturally, differ-
ent users may experience different levels of complexity for the same tasks; or, more impor-
tantly, experienced complexity may vary in time or with the working stress load.
N
OTE
The sequence and the timing between the various steps is essential to the End-User's
own experience of the deployment process. As an example, if not properly addressed
by the AH design, the On-The-Run Resources Installation Phase could be confusing for
users because of its unexpectedness during normal application execution.
The Overall Picture
We saw the roles involved in the model and the tools used to accomplish their tasks. It's time
to put all the pieces together and discuss the resulting scenario. Let's begin from Figure 2.9.
SW-Producer
Publication
Server
Software
Producer
Deployment
Servers
Software
Distributor
Client
Platforms
End-User
F
IGURE
2.9
The deployment model seen from the physical installations involved for each role.
