only on using
Plan on the
F IGURE 2.7
Roles and responsibilities centered around the Resolution Phase.
The Developer Role
We have seen that a piece of software is produced by an organization that often controls the
exploitation rights on it. To keep things simple, we have always referred to the Software
Producer as the vendor and marketer of the services offered by the software. Of course, this is
not always the case, and generally speaking, we have to introduce at least another role, that of
the Software Owner . Nevertheless, this is a technical software topic. We are interested with in
the engineering of the deployment event, not with marketing or social issues. So, rarely will
we refer to a Software Owner being separate from the Software Producer.
The Software Producer role could be played by an entire organization or just a few individu-
als—there are many possibilities. What is useful is to separate another specialization from this
role: that of the Deployment Engineer. A Deployment Engineer is a developer or a team of
developers specialized in software deployment. They will work together with their developer
colleagues and with the Distributor organization to deploy the software being constructed. We
will dedicate the whole second part of this topic to this role, so don't worry if we put it aside
for a while.
The Distributor Role
In addition to the Producer, there is also the Distributor , which is a central role in the overall
deployment challenge. It is worth spending some time discussing the role here.
The Distributor role could be played by many different subjects. It has been traditionally cov-
ered by Software Producers themselves, struggling to reach their consumers.