SEKE 2012 Proceedings - Knowledge Systems Institute

Figure 5.
Metamodel for contructing activity diagrams
V. EXAMPLE OF RESEARCH METHOD
An example of t he trouble ticket scenario is selec ted to
demonstrate how t o compose the underlying ADL script and
how to insert control nodes based on the ADL semantic model.
Fig.6 illustrates the target activity diagram [2] associated with
the example scenario.
15 then auditAndRecord,
16 communicateResult
17 endif
18 else
19 if 'not recorded' then terminate endif
20 endif
21 end
22
23 decision from reproduceProblem
24 if 'cannot reproduce problem'
25 then correctProblem
26 else
27 if 'can reproduce problem'
28 then idProblemAndResolution
29 endif
30 else
31 if 'duplication of another problem'
32 then verifyResolution
33 endif
34 else
35 if 'known problem and solution'
36 then auditAndRecord,
37 communicateResult
38 endif
39 endif
40 end
41
42 correctProblem -> auditAndRecord
43 correctProblem -> communicateResult
44
45 decision from verifyResolution
46 if 'problem not solved'
47 then idProblemAndResolution
48 else auditAndRecord,
49 communicateResult
50 endif
51 end
52 end
Fig. 7 illustrates all the actions and their object evidences as
implicit objects are used to create all action sequences here.
Record Problem A Reproduce Problem
B
Correct Problem
Verify Resolution
C
E
ID Problem and
Resolution
D
Audit and Record
G
Communicate Result
F
Figure 6. Target activity diagram of trouble ticket scenario [2]
The ADL script representing the trouble ticket scenario can
be written as follows:
01 diagram 'ticket trouble scenario'
02 action recordProblem end
03 action reproduceProblem end
04 action correctProblem end
05 action idProblemAndResolution end
06 action verifyResolution end
07 action auditAndRecord end
08 action communicateResult end
09
10 decision from recordProblem
11 if 'recorded'
12 then
13 reproduceProblem
14 if 'problem statement rectified'
Figure 7. Actions and their object evidences
Once all sequences of actions have been created, the start
point and the termination point are identified. Actions without
an input object and those without an output object are
candidates for connecting to th e initial node and the activity
final node, respectively. Therefore, recordProblem is connected
to the initial node, while auditAndRecord and
communicateResult are co nnected to the activity final node.
The directed connections can be expressed as follows:
initiate → INITIAL → recordProblem → A
auditAndRecord → G → terminate → TERMINATE
communicateResult → F → terminate → TERMINATE
Next, (5) is ap plied to build guard condition objects,
resulting in the directed connections as follows:
727