Information Technology Reference
In-Depth Information
ÆEV_CommunityContractÇ
Logistics Provision
ÆEV_ObjectiveOfÇ
Enterprise Objects
Types
Roles
ÆEV_CommunityÇ
Logistics Provision
ÆEV_ObjectiveÇ
Logistics Provision
Objective
Carrier
Green Transport
Customer
Manager
Person
Company
Goods Source
Cheap Transport
Goods Destination
Transport
ÆEV_ObjectiveÇ
description = "To provide delivery services to customers,
as securely, confidentially and efficiently as possible."
SecureTransport
Goods
Policies
Courier
Document
ÆEV_ProcessÇ
Logistics Provision Community Behaviour
FIGURE A.5: Community contract for the Logistics Provision community.
Enterprise Object Types
+employer
0..1
+staff
0..*
0..*
Company
«EV_ODPSystem»
PhoneMob
system
Handset
Person
+user
Document
1
+owner
1
Organization
Manufacturer
0..*
Paper
Document
PhoneMob
e−Document
Loan Handset
User Handset
FIGURE A.6: The enterprise objects in the Phone Repair community.
A.1.3
Behaviour
Behaviour can be modelled in the enterprise language in terms of pro-
cesses or, in a more fine-grained way, in terms of interactions. Processes are
expressed in UML4ODP as UML activities. Some of the processes for the
Phone Repair community were shown in figure 2.7, and one of them (Repair
Process) was further elaborated in figure 2.8, which showed the activity dia-
gram that expresses the steps of the process, and identified the roles involved
in each of these steps.
More detailed modelling of behaviour in terms of interactions between roles
in a community is appropriate when the modelling focus is placed primarily
on the roles and artefacts involved in the behaviour, and on the relationships
between them. Figure A.7 shows such an interaction in the CustomerOrg
community, in which the Employee and the Contract Manager agree to a repair
request.
