Producing a Single SR Model

A Single SR Model

The third key stage is to produce a single SR model. You do this by
integrating all of the actor SR models using the dependency links from
the SD model, then adding further dependency links that emerge from
the richer SR models.
The slide shows how to connect elements of 2 SR models using
dependency links. We’ve taken the passenger actor model from the
previous slide, and expanded on the web-site actor through the
inclusion of new elements. The main task of the web-site is to sell
tickets (that the passenger buys), and to do this is verifies payments
and records purchases. Furthermore, we want verification to happen
quickly, hence the inclusion of a soft goal decomposing the verify
payment sub-task.
Of course, this begs the question what to do about the dependency link
from the previous slide. This link was attached to the web-site actor, but
not to specific elements that the actor should undertake. Therefore we
need to attach the dependency from buy ticket in the passenger actor to
the correct element in the web-site actor. I think that this element is sell
ticket, as shown in the slide. Furthermore, the inclusion of the sub-task
elements enables us to be more specific about important dependencies
– that for example the passenger completing the pay for ticket sub-task
depends on the web-site completing the verify payment sub-task.
Hence these new dependencies are added

Reference: Neil Maiden (2011) Requirements Engineering Lecture Notes

Advertisements
This entry was posted in i* SRM and tagged , . Bookmark the permalink.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s