Content deleted Content added
Tag: section blanking |
|||
Line 62:
[[Image:GRL legend.gif|thumb|320px|GRL Notation]]
[[Goal-oriented Requirements Language]] (GRL) is a language that is designed to support [[goal-oriented]] modeling and reasoning about requirements, especially the non-functional requirements <ref>Lin Liu, Eric Yu, “Designing information systems in social context: a goal and scenario modelling approach”</ref> It allows to express conflict between goals and helps to make decisions that resolve conflicts. There are three main categories of concepts in GRL: intentional elements, intentional relationships and actors <ref>GRL web site, University of Toronto, http://www.cs.toronto.edu/km/GRL/</ref>. They are called for intentional because they are used in models that primarily concerned with answering "why" question of requirements (for ex. why certain choices for behavior or structure were made, what alternatives exist and what is the reason for choosing of certain alternative.
==Goal and process oriented modeling==
We can describe process model as models that comprise a set of activities and an activity can be decomposed into sub-activities<ref name=eeml1>
Yun Lin and Arne Sølvberg Goal Annotation of Process Models for Semantic Enrichment of Process Knowledge </ref>. These activities have relationship amongst themselves. A goal describes the expected state of operation in a business enterprise and it can be linked to whole process model or to a process model fragment with each level activity in a process model can be considered as a goal <ref name =eeml1 />.
Goals are related in a hierarchical format where you find some goals are dependent on other sub goals for them to be complete which means all the sub goals must be achieved for the main goal to be achieved. There is other goals where only one of the goals need to be fulfilled for the main goal to be achieved. In goal modeling, there is use of deontic operator which falls in between the context and achieved state<ref name=emml2>J. Krogstie (2005) EEML2005: EXTENDED ENTERPRISE MODELING LANGUAGE </ref>. Goals apply to tasks, milestones, resource roles and resources as well and can be considered as action rule for at task. EEML rules were also possible to although the goal modeling requires much more consultation in finding the connections between rules on the different levels<ref name=eeml3>John Krogstie (2008) Using EEML for Combined Goal and Process Oriented Modeling: A Case Study. IDI, NTNU,Trondheim, Norway. Proceedings of EMMSAD 2008.</ref>. Goal-oriented analysis focuses on the description and evaluation of alternatives and their relationship to the organizational objectives <ref name=eeml4> Mylopoulos, Chung, and Yu (1999) : “From Object-oriented to Goal-oriented Requirements Analysis”. Communications of the ACM, January</ref>.
==Resource modeling==
| |||