So she/he sees market tendencies
and says ‘everybody today is working with VMWare; virtualization
is important, so we must increase virtualization
support’, then the person here [the solution architect] is going
to say ‘yes, this is true, there is a large number of clients who
demand it’ and we go in this direction. Then, the other person
[the software architect] refines the focus. This is the division
according to the scope: the enterprise architect is broader and
less specific, while the technical architect [the IASA software
architect] is the lower level and is focused on the specific product;
she/he is going to see how this product attend the directions
that the higher level person [the enterprise architect]
points. (. . .)