Information Technology Reference
In-Depth Information
A.1
Enterprise Viewpoint Specifications
The enterprise language defines four key concepts: enterprise specifica-
tion, system , scope and field of application .
In our example, the system to be specified is a computerized system that
supports the operations of the PhoneMob company. The scope of this system
describes its expected behaviour, stating the way it is supposed to work and
interact with its environment in the business context. The scope of the system
is modelled in terms of the set of roles it fulfils (see section A.1.2).
The enterprise specification of the PhoneMob system is expressed by
one model, stereotyped
«
Enterprise Spec
»
, which contains the contracts of all
the communities that make up the specification, as shown in figure A.2. This
also shows the field of application of the specification, which describes
the properties that the environment of the ODP system must have for the
specification to be used. It is expressed by means of a tagged value of the
«
Enterprise Spec
»
model, giving the enterprise specification of the system.
«Enterprise_Spec»
PhoneMob (E_Spec)
«Enterprise_Spec»
EV_FieldOfApplication = "This
specification assumes a
business environment, and can
be applied to most franchise
businesses. In particular, this
requires..."
«EV_CommunityContract»
CustomerOrg
«EV_CommunityContract»
Phone Repair
«EV_CommunityContract»
Logistics Provision
FIGURE A.2: The structure of the PhoneMob enterprise specification.
A.1.1
Communities and Their Contracts
Figure A.2 shows that the enterprise specification of the PhoneMob system
is composed of the specifications of three communities: Phone Repair (shown in
figure A.3), CustomerOrg (shown in figure A.4) and Logistics Provision (shown
in figure A.5).
In general, all community contracts have the same structure: one objec-
tive (which in a real contract would be more specific and detailed) and four
main packages with the specification of the community roles, object types,
processes and policies.
