Semantic Annotation for Process Models: - Department of Computer ...
Semantic Annotation for Process Models: - Department of Computer ...
Semantic Annotation for Process Models: - Department of Computer ...
Create successful ePaper yourself
Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.
50 CHAPTER 3. STATE OF THE ART<br />
relationships. Intentional elements appear in SR models not only as external dependencies,<br />
but also as internal elements arranged into (mostly hierarchical) structures <strong>of</strong><br />
means-ends, task-decompositions and contribution relationships [212]. The means-ends<br />
links provide understanding about why an actor would engage in some tasks, pursue a<br />
goal, need a resource, or want a s<strong>of</strong>t goal; the task-decomposition links provide a hierarchical<br />
description <strong>of</strong> intentional elements that make up a routine; the contribution<br />
links provide elaboration <strong>of</strong> the effects from intentional elements to s<strong>of</strong>tgoals.<br />
3.3.3 GBRAM (Goal-Based Requirements Analysis Method)<br />
GBRAM [56] addresses the critical nature <strong>of</strong> the discovery process in goal analysis.<br />
GBRAM can be used in goal analysis and goal refinement/evolution. It defines a<br />
top-down analysis method refining goals and attributing them to agents starting from<br />
inputs such as corporate mission statements, policy statements, interview transcripts<br />
etc. There<strong>for</strong>e operationalization process is provided <strong>for</strong> defining a goal with enough detail<br />
so that its subgoals have an operational definition. GBRAM distinguishes between<br />
achievement goals and maintenance goals. Achievement goals are objectives <strong>of</strong> functional<br />
processes. Maintenance goals are those goals that are satisfied while their target<br />
condition remains true. They tend to be operationalized as actions or constraints that<br />
prevent certain states from being reached. Achievement goals usually map to actions<br />
that occur in a system, while maintenance goals map to nonfunctional requirements.<br />
In GBRAM, agents are the entities or processes that seek to achieve goals within<br />
an organization or system based on the implicit responsibility that must assume <strong>for</strong> the<br />
achievement <strong>of</strong> certain goals; constraints place conditions on the achievement <strong>of</strong> a goal;<br />
goal obstacles are behaviors or other goals that prevent or block the achievement <strong>of</strong> a<br />
given goal. GBRAM supports goal decomposition to subdividing a set <strong>of</strong> goals into a<br />
logical subgrouping.<br />
3.3.4 Goal modeling in EEML<br />
Goals in an EEML model can be decomposed into sub-goals and goal connectors such<br />
as "and", "or", or "xor". Those connectors can be used to specify logical relationships<br />
between the goal and its sub-goals. Besides, EEML provides more connecting relation<br />
types to associate goals with the elements in an EEML process model. The connecting<br />
relationships in the EEML goal modeling are listed in Table 3.3.<br />
3.3.5 Goal specification in WSMO<br />
Goal models in WSMO [210] are descriptions <strong>of</strong> Web services that would potentially<br />
satisfy the user desires. They provide the user view in the Web service usage process.<br />
Goal is represented through the capability <strong>of</strong> the Web services the user would like to<br />
have, and the interface <strong>of</strong> the Web service the user would like to have and interact with.<br />
A set <strong>of</strong> properties strictly belonging to a goal are defined as non-functional properties<br />
<strong>of</strong> a WSMO goal. A goal may be defined by reusing one or several already-existing<br />
goals by using goal mediators.