Method Engineering: A Service-Oriented Approach - Intentional Perspectives on Information Systems Engineering - page 341

Resource part

0..* 1

0..* 0..1

Is realized by

Resource Execution

graph

1 1

Resource Resource

0..1 process

process process

1..* 1..* 1..*

(Lprod)
Artefact

Domain
ontology

(Lprod)
Artefact

(Lprod)
Artefact

Domain
ontology

Domain
ontology

1 . 1 .

Node Node Node Edge Edge Edge

(Lgoal)
Goal

(Lgoal)
Goal

(Lgoal)
Goal

1 realize 1

(Lproc)
Elementary unit

(Lproc)
Control
construct

Variation
point

Decision
point

<< aid >>

Service

1..* 1..*

Legend :
Elements annoted with (Lgoal), (Lact), (Lproc), (Lprod) refer
respectively to the goal ontology, the actor ontology, the process
ontology and the product ontology

Input Output

0..* 0..*

0..* (Lprod)

Product
element

(Lprod)
Product
element

(Lprod)
Product
element

Elementof
processpart

Elementof
processpart

Element of
process part

could
correspond
to

Fig. 8 Resource part of a method service

In the execution graph given in Fig. 9, the variation point corresponds to the sim-
ple process “Identify conceptual classes” defined in the process part (cf. Fig. 7) .
At composition time, this variation point will be substitute with the execution
graph of the service chosen by the developer. This mechanism enables to generate
development methods tailored to developers' requirements.

- Artefact : UML language
- Domain ontology : -
- Execution graph :

« variation point »
Identify
conceptual classes

« activity »
Identify relationships
between classes

« output »:
Class diagram
[

partial]

«activity»
Complete the description of
classes by attributes

«output »:
Class diagram
[

« activity»
Complete the description of
classes by methods

finished]

Fig. 9 Resource part of the method service “construct a class diagram manually”