Goal Modeling PDF

RE
Goal Modeling
© 2006-07 Betty H.C. Cheng. This presentation is available free for non-commercial use with attribution under a creative commons license.
1
RE We Will Cover
• What is a goal?
• Where do goals come from?
• What is a goal model?
• When to use goal models?
– How do goal models relate to UML models?
• Why use goal models?
• Capturing the goal model
2
RE What is a goal?
• A stakeholder objective for the system
– The system includes the software and its
environment
• Who are stakeholders?
– Anyone who has an interest in the system
– Customers, end users, system developers,
system maintainers...
• What is a goal model?
– A hierarchy of goals
– Relates the high-level goals to low-level system
requirements
RE Goal or Not a Goal?
• Goal Examples:
– Credit card information is kept private
– Credit card information is accurate
– Safe transportation
– Highly reliability
• Non-goal Examples:
– The system will be implemented in C++
– The paint colors for the cars will be yellow,
orange, and red
4
RE Goal Exercise
• Order the list of goals from high-level
concern to low-level concern
– User receives a request for a timetable from a

system
– Collect timetables by system
– Schedule meeting
– System collect timetables from user
– Collect timetables
RE Goal Exercise
• Order the list of goals from high-level
concern to low-level concern
– Schedule meeting
– Collect timetables
– Collect timetables by system
– System collect timetables from user
– User receives a request for a timetable
RE Types of Goals
• Functional (Hard)
– Describe functions the system will perform
– Well defined criteria for satisfaction
– E.g., System collects timetables from user
• Non-functional (Soft or fuzzy)
– Describe desired system qualities
– Hard to define; satisficed rather than satisfied
– Reliability
• E.g., System should be reliable
– Quality
• E.g., System should be high quality.
RE Where do goals come from?
• Conveyed by stakeholders
• Disclosed in requirements documents
• Analysis of similar or current system
• Elaborating other goals
RE Goal Exercise
• Identify goals in the following paragraph
An Adaptive Regional Forecasting Ecological Observatory (ARFEO) is proposed as
means to implement an operational, run-time configurable, and adaptable ecological
observatory to be used for regional ecological forecasting. ARFEO has three main
dimensions. First, using a holistic perspective of environment, we will use sensors
that are analogous to human and organism senses to monitor the environment and its
changes. As such, ARFEO can be configured to observe and answer ecological
questions specific to one class of sensory input or across multiple sensory inputs.
Second, ARFEO will use a cyberinfrastructure comprising smart, heterogeneous
sensor networks, small-scale and GRID-scale distributed computing [6]. ARFEO’s
architecture will be a distributed design which will enable users to perform small and
complex computations and transparent integration of data and analysis. ARFEO will
enable a user to adapt monitoring capabilities at run-time, thus allowing a user to
customize the configuration to specific needs and questions. Finally, ARFEO will
emphasize the reuse and synergistic integration of existing analysis and visualization
techniques to include in the computational toolkit for processing the sensor and
ancillary data, as well as metadata. A key part of ARFEO will be the development of
processes to make use of the toolkit element to support the analysis and visualization
capabilities.
RE When to use goal models
• Early requirements engineering
– Focus on identifying problems
– Exploring system solutions and alternatives
– Done before UML modeling
Early RE Late
RRE Design Code Test
Why? What? How?
RE Why use goal models?
• Give rationale for requirements
• Identify stable information
• Guide requirement elaboration
RE
The Goal Model
RE Running Example
• Meeting Scheduler
– Assists the initiator in scheduling a meeting
– Meeting should be convenient for participants
• Participants should be available
• Modeled using the i* goal notation
13
Example adapted from the RE06 keynote given by John Mylopoulos
Goal Model
RE
Schedule Goals are refined into
meeting subgoals that elaborate
how the goal is
achieved
Collect Choose
timetables schedule
By Manually Automatically
By
person system
Collect from Collect from

agents users
Send Receive
request request

AND Refinement
RE
Schedule All of the
meeting subgoals must be
AND AND achieved for the
Collect Choose goal to be
timetables schedule achieved
By
person system

agents users
AND
AND
Send Receive
request request
15
OR Refinement
RE
Schedule
At least one of the
meeting subgoals must be
AND
achieved for the
AND
Collect Choose
goal to be achieved
timetables schedule
OR OR
OR OR
By
person system
OR
OR

agents users
AND
AND
Send Receive
request request
16
Interpretations of OR Refinements
RE Static systems -
Schedule
meeting
alternative solutions
Adaptive systems –
AND AND points of variation
Collect Choose
timetables schedule
OR OR
OR OR
By
person system
OR
OR

agents users
AND
AND
Send Receive
request request
17
RE Softgoals Good Quality
schedule
AND
Minimal AND
conflicts
Minimal
effort Good
AND participation
AND Matching
effort
Collection
effort Minimal
disturbances
Accurate
constraints

RE Modeling Softgoals
• Used to evaluate alternatives
• Helps (+)
• Makes (++)
• Hurts (-)
• Breaks (--)

RE Contributions to Softgoals
Good Quality
schedule
AND
Schedule Minimal AND
meeting conflicts
AND Good
− + participation
Choose
schedule
OR +
OR −
Manually Automatically

RE Construction Process Good Quality
schedule
Minimal
effort
AND AND
Minimal AND
AND Matching conflicts
effort
Good
participation
Collection
effort
1. Define
Minimal Softgoals
disturbances
Accurate
constraints
21
schedule
Minimal
effort
AND AND
AND Matching meeting conflicts
effort
AND AND Choose Good
schedule participation
Collection Collect
effort timetables OR
OR OR
OR
By
person system
OR
OR

agents users 2. Define
Minimal AND
AND Hardgoals
disturbances
Send Receive
Accurate
request request Steps 1 & 2
constraints may be
iterative
22
schedule
Minimal
effort
AND AND
AND Matching meeting conflicts
effort
AND AND Choose Good
− + participation
schedule
Collection Collect +
effort timetables − OR +
+
OR OR −
OR
−
By
person system
OR
OR

+
agents users 3. Evaluate
Minimal − − AND
AND hardgoal
disturbances
+ Send Receive contribution
Accurate
request request to softgoals
constraints
23
RE
Integrating Goals with Other

Models
24
RE Integrated Use of Goals
• KAOS
– Refining goals into requirements
– 4 models
• Goal
• Agent
• Operationalization
• Object
RE KAOS Goal Model
• Agent - active system component
• Object - inactive system component
• Operation - an action an agent takes to achieve a goal
• Requirement - a goal for which an automated component is responsible
• Expectation - a goal for which a human is responsible Safe Transportation
Maintain Knowledge of Other Train Locations
Manually Radio Other Train Conductors
Radio Automatically Sense Other Train Locations
Human
Radio Other Train
Software Train
Sensor
RE KAOS Goal Model
Human
Radio Other Train
Software Train
Sensor
RE KAOS Goal Model
Human
Radio Other Train
Software Train
Sensor
RE KAOS Goal Model
Human
Radio Other Train
Software Train
Sensor
RE KAOS Goal Model
Human
Radio Other Train
Software Train
Sensor
RE KAOS Goal Model
Human
Radio Other Train
Software Train
Sensor
RE KAOS Goal Model
Human
Radio Other Train
Software Train
Sensor
RE KAOS Goal Model
Human
Radio Other Train
Software Train
Sensor
RE KAOS Goal Model
Human
Radio Other Train
Software Train
Sensor
RE KAOS Goal Model
Human
Radio Other Train
Software Train
Sensor
RE KAOS Goal Model
Human
Radio Other Train
Software Train
Sensor
RE KAOS Agent Model
• Objective: depicts agent responsibilities
• Agent models can be inferred from goal models
Maintain Knowledge of Other Train Locations Software
Sensor
Automatically Sense Other Train Locations

Human
Human
Software
Sensor
Goal Model Agent Model

27
RE KAOS Agent Model
Sensor

Human
Human
Human
Software
Sensor

27
RE KAOS Agent Model
Sensor

Human
Human
Software
Sensor

27
RE KAOS Agent Model
Alert Passengers to Delays Software
Sensor
Human

Manually Slow the Train Human
Human
Software
Sensor

27
RE KAOS Agent Model
Sensor

Human
Human
Software
Sensor

27
RE KAOS Operationalization Model
• Objective: specifies the operations that agents must
perform to achieve the goals
Safe Transportation
Train Doors Closed While Moving
Close Door Request Train Begins to Move
Close Door
Door
28
RE KAOS Operationalization Model
• Objective: specifies the operations that agents must
perform to achieve the goals

Safe Transportation
Train Begins to Move
Close Door Request Train Begins to Move
Close Door
Close Door
Door Door
28
RE KAOS Object Model
• Objective: further specifies objects used in the goal model
• The syntax is similar to a that of a UML class diagram
Following Track
On Track
Train On TrackSegment hasGate Gate

Speed SpeedLimit Loc
Loc Status
Switch
position
29
RE Integrated Use of Goals
• KAOS
– Refining goals into requirements
– 4 models
• Goal
• Agent
• Operationalization
• Object
• i*
– Relates goals to the organization context
– 2 models
• Actor (Strategic) Dependency Model
• Actor (Strategic) Rationale Model
RE i* Actor Dependency Model
• Dependencies between actors - An actor is a black box
Attends
Meeting(p,m) or impa
D D rations
MeetingBe
D In th
D Scheduled(m) Enter
D AvailDates vides a
Meeting Meeting (m) D Meeting
Initiator
D Enter
DateRange
D Scheduler D D Participant side” ac
Proposed
X
(m) Date(m) tentiona
D Agreement
D appear i
D (m,p)
ISA
Attends but also
D Meeting(ip,m)
ships an
D Important
Assured
(Attends
Participant in Figur
D
LEGEND
Depender Dependee
Meeting(ip,m)) meeting
D D Resource Dependency SD mod
D D Task Dependency
D D Goal Dependency For e

O
D D Softgoal Dependency
Open (uncommitted) X Critical
is that o
(represe
31 ings in
Diagram from Towards Modelling and Reasoning Support for Early-Phase Requirements Engineering by Eric Yu
(m) Da
X
D
RE i* Actor Dependency
D Model
Attends
D - An actorMeeting(ip,m)
• Dependencies between actors is a black box
Assured
Attends
or impa
Meeting(p,m)
D
(Attends
rations
D Meeting
LEGEND
Depender
MeetingBe Dependee In th
D Scheduled(m) D Enter
D D Resource
D
Dependency
AvailDates vides a
Initiator
D Enter D Scheduler Participant side” ac
DateRange D Task Dependency
D
Proposed
D
X
(m) D Date(m) tentiona
D Dependency
Goal Agreement
D appear i
D D D (m,p)
ISA
Attends but also
Meeting(ip,m)
D ships an
D Important
O
Assured
Open (uncommitted)
(Attends X Critical
D
LEGEND
Depender Dependee
D D Task Dependency

Figure 2: Strategic Dependenc
O
is that o
(represe
scheduling with computer-based s
31 ings in
RE i* Actor Dependency Model
• Dependencies between actors - An actor is a black box
Attends
Meeting(p,m) or impa
D D rations
MeetingBe
D In th
D Scheduled(m) Enter
D AvailDates vides a
Initiator
D Enter
DateRange
D Scheduler D D Participant side” ac
Proposed
X
(m) Date(m) tentiona
D Agreement
D appear i
D (m,p)
ISA
Attends but also
D Meeting(ip,m)
ships an
D Important
Assured
(Attends
D
LEGEND
Depender Dependee
D D Task Dependency

O
is that o
(represe
31 ings in
RE i* Actor Rationale Model
• Internal actor relationships - An actor is a white box
Meeting Meeting
Initiator Participant
Organize
Meeting D Attends Participate
Meeting InMeeting
D
Quick MeetingBe Low Attend
Scheduled Effort Arrange
Meeting Meeting
! + ! + Convenient
+ (Meeting,Date)
Schedule LetSceduler
Meeting Schedule Quality Low
Meeting D Meeting (ProposedDate) Effort
MeetingBe Scheduler Agreeable
Scheduled D + +
D (Meeting,Date)
Enter Richer User
LEGEND DateRange Medium + Friendly
D Schedule
Meeting ! ! +
Goal
FindAgreeable FindAgreeable
Task Obtain DateUsing DateByTalking
AvailDates Enter Scheduler ToInitiator
Resource
Obtain D AvailDates D
Soft!Goal Find Agreement
Task!Decompo!
Agreeable D
Proposed
Slot
D AgreeTo
sition link Date Date
Means!ends link
+ Contribution to Merge D Agreement D

! softgoals AvailDates
Actor
Actor Boundary
32
Figure 4: Strategic Rationale model for a computer-supported meeting scheduling configuration
ser
riendly Min
•Interruption
Internal actor relationships - An actor is a white box
! LEGEND
Meeting Meeting
Organize
D
Goal Participate
Meeting Attends
Meeting InMeeting
Task D
Meeting Meeting
! + ! + Resource Convenient
+ (Meeting,Date)
Meeting Schedule
D
Soft!Goal Quality Low
Meeting Meeting (ProposedDate) Effort
Scheduled D + +
D Task!Decompo! (Meeting,Date)
Enter
DateRange
sition link Richer
Medium +
User
LEGEND Friendly
Schedule Means!ends link
D
Meeting ! ! +
Goal
Task
+
! Obtain Contribution
Obtain
AvailDates
to
Enter
DateUsing
Scheduler
DateByTalking
ToInitiator
Resource
softgoals D AvailDates D
Soft!Goal Find AgreementActor
Task!Decompo!
Agreeable D
Proposed
Slot
D AgreeTo
Means!ends link
Merge
Actor Boundary
D
+
! Contribution to Agreement D
softgoals AvailDates
Actor
Actor Boundary
32
• Internal actor relationships - An actor is a white box
Meeting Meeting
Organize
Meeting D Attends Participate
Meeting InMeeting
D
Meeting Meeting
! + ! + Convenient
+ (Meeting,Date)
Meeting Schedule Quality Low
Meeting D Meeting (ProposedDate) Effort
Scheduled D + +
D (Meeting,Date)
Enter Richer User
LEGEND DateRange Medium + Friendly
D Schedule
Meeting ! ! +
Goal
Task Obtain DateUsing DateByTalking
AvailDates Enter Scheduler ToInitiator
Resource
Obtain D AvailDates D
Soft!Goal Find Agreement
Task!Decompo!
Agreeable D
Proposed
Slot
D AgreeTo
Means!ends link
+ Contribution to Merge D Agreement D

! softgoals AvailDates
Actor
Actor Boundary
32

Goal Modeling PDF

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Goal Modeling PDF

Uploaded by

Copyright:

Available Formats

RE

– User receives a request for a timetable from a

Why? What? How?

The Goal Model

• Modeled using the i* goal notation

Collect from Collect from

Example adapted from the RE06 keynote given by John Mylopoulos

Collect from Collect from

Collect from Collect from

Collect from Collect from

Example adapted from the RE06 keynote given by John Mylopoulos

Example adapted from the RE06 keynote given by John Mylopoulos

Example adapted from the RE06 keynote given by John Mylopoulos

Collect from Collect from

Collect from Collect from

Integrating Goals with Other

Maintain Knowledge of Other Train Locations

Manually Radio Other Train Conductors

Radio Automatically Sense Other Train Locations

Maintain Knowledge of Other Train Locations

Manually Radio Other Train Conductors

Radio Automatically Sense Other Train Locations

Maintain Knowledge of Other Train Locations

Manually Radio Other Train Conductors

Radio Automatically Sense Other Train Locations

Maintain Knowledge of Other Train Locations

Manually Radio Other Train Conductors

Radio Automatically Sense Other Train Locations

Maintain Knowledge of Other Train Locations

Manually Radio Other Train Conductors

Radio Automatically Sense Other Train Locations

Maintain Knowledge of Other Train Locations

Manually Radio Other Train Conductors

Radio Automatically Sense Other Train Locations

Maintain Knowledge of Other Train Locations

Manually Radio Other Train Conductors

Radio Automatically Sense Other Train Locations

Maintain Knowledge of Other Train Locations

Manually Radio Other Train Conductors

Radio Automatically Sense Other Train Locations

Maintain Knowledge of Other Train Locations

Manually Radio Other Train Conductors

Radio Automatically Sense Other Train Locations

Maintain Knowledge of Other Train Locations

Manually Radio Other Train Conductors

Radio Automatically Sense Other Train Locations

Maintain Knowledge of Other Train Locations

Manually Radio Other Train Conductors

Radio Automatically Sense Other Train Locations

Automatically Sense Other Train Locations

Automatically Sense Other Train Locations

Goal Model Agent Model

Manually Radio Other Train Conductors

Automatically Sense Other Train Locations

Goal Model Agent Model

Automatically Sense Other Train Locations

Automatically Sense Other Train Locations

Goal Model Agent Model

Automatically Sense Other Train Locations

Goal Model Agent Model

Automatically Sense Other Train Locations

Automatically Sense Other Train Locations

Goal Model Agent Model