Analysis of Early Aspects in Requirements Goal Models: A Concept-Driven Approach - Transactions on Aspect-Oriented Software Development - page 45

Legend:

Customer

Customize

Actor

PasswordProte−

[language]

ction[account]

Boundary

FAQ[shop] Make

Help Usability Hurt

Security

EmailInformation
[product]

Goal

Make

Manage[account]

FaxInformation
[product]

Help Buy Media

Items

Softgoal

Hurt

Break

SecureForm/
HttpsForm
[order]

Task

Acquire Product
Information

Search
Product

Place
Order

Modifiability

Contribution

Hurt

KeywordSearch
[product]

HttpForm
[order]

Navigate[shop]

Link

Accessibility

Help

Means−ends
Link

Help

ToolBox[shopping] Respon−

siveness

Accuracy

Decompo−
sition
Link

Fig. 2. Strategic rationale (SR) model for media shop customer

Legend:

Actor

Developer

Boundary

Consistency Help

PageLayout
[GUI]

Confidentiality

Hurt

Performance

Goal

WildcardSearch
[product]

FAQ[shop]

Hurt

Template
[navigation]

Hurt Softgoal

InfoBox[font]

Security

Adaptability Hurt Usability

Help

HttpForm
[order]

Task

Template
[layout]

Help

Run Shop

Navigate[shop] Report[shop] Contribution

Cookie
[transaction]

Make

Hurt Hurt

SSL[protocol]

SecureForm/
HttpsForm
[order]

Link

Manage
Product

Maintain
Shop

PasswordProte−

Availability Means−ends

Link

ction[account]

Hurt

Manage[account]

Correctness Make Monitor[shop]

Make Decompo−

sition
Link

Maintainability

Fig. 3. Strategic rationale (SR) model for media shop developer

shown in Figs. 2 and 3, respectively. Goals are states of desires, such as customer
wants to “buy media items” (Fig. 2). Goals can be hierarchically decomposed to
subgoals, and can be achieved by various means-ends relations linking to tasks.