Information Technology Reference
In-Depth Information
centres delegate nancial concerns, like contact with a customer's bank, to
be handled centrally in headquarters. As a result, the community directly
involved in the repair process at a local centre, which we call the Branch
Repair Provision community, can be reduced to having the set of roles shown
in figure 2.4.
«EV_Community»
Branch Repair
Provision
has role
hidden
Bank
hidden
Customer
«EV_Role»
User
«EV_Role»
Logistics
Provider
«EV_Role»
Phone
Supplier
created by
refinement of the
Phone Repair
Provider role
hidden
HQ staff
«EV_Role»
HQ system
«EV_Role»
Branch
system
«EV_Role»
Branch
staff
FIGURE 2.4: The roles of the Branch Repair Provision community.
The whole sequence of developing the local repair process roles thus starts
with the abstract role set for the Phone Repair community, introduced in
figure 2.2. This is transformed to give the Detailed Phone Repair community,
in figure 2.3, by replacing the single repair service provider with the interaction
of headquarters and local branch roles and by differentiating between staff and
system participants. In a second step, just the roles concerned with the local
repair process in the branch are selected, yielding the Branch Repair Provision
community, with the role set shown in figure 2.4.
2.4
Roles and Role Filling
Roles are the glue that holds the enterprise specification together. There
is some similarity between the use of roles in a community and the software
concept of formal parameters for a procedure. Both enable reuse by providing
a local identity that can be referenced in the reusable part of the specification
