A Framework for Integrating ESL Tools - IRIT
A Framework for Integrating ESL Tools - IRIT
A Framework for Integrating ESL Tools - IRIT
Create successful ePaper yourself
Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.
All the a<strong>for</strong>e mentioned people (and many others) were added to the “CC<br />
list” of the bug, meaning that they get emailed whenever a change is made to<br />
the bug in BugZilla.<br />
4.3 Description Using CM_SPEM Concepts<br />
There are a number of actors involved:<br />
– Kai de Leeuw is a user<br />
– José Jeria, Gavin, and Madark are developers<br />
– Mike Beltzner and Dietrich Ayala are release drivers<br />
A number of actor specific tasks can be identified:<br />
– “Report Bug”, carried out by the user Kai de Leew. Note that in this particular<br />
case, the task is identified, then affected to someone who carries it<br />
out. The user just stumbles upon the bug during normal browser usage,<br />
and decides to report it. Thus, this actor specific task in the model merely<br />
records something that has been done. This demonstrates how some tasks<br />
in a project cannot explicitly appear in a process model which exclusively<br />
focuses on planning.<br />
– “Confirm bug”, carried out by developer José Jeria.<br />
– “Identify bug cause”, carried out by Gavin<br />
– “Fix bug”, which will be carried out by the developer assigned to the bug<br />
(as of today, no one has been assigned to this bug).<br />
– “Confirm fix” which will be carried out by a member of the QA (Quality<br />
Assurance) team. Note that this actor is not yet identified, as bugs are usually<br />
fixed be<strong>for</strong>e a QA team member (depending on his workload and his area of<br />
expertise) reviews it <strong>for</strong> fix confirmation.<br />
The conversation happening around the bug, depending on how it is recorded,<br />
can be considered as an artifact on its own. In the case of BugZilla, the conversation<br />
is stored in BugZilla’s database, outside of the actual repository. Thus,<br />
we focus only on the artifacts impacted by the bug:<br />
– The file 11 which tracks user preferences (URL encoding can be specified as<br />
a preference in Firefox).<br />
– The file which handles URL encoding in Firefox 12<br />
Each copy of these files in a developer directory is an actor specific artifact<br />
on its own, which can evolve independently of others. Typically, the copy in the<br />
repository of the developer assigned to the bug will evolve first, and the changes<br />
made will be sent to an integrator (not shown in the actor list <strong>for</strong> simplicity).<br />
Some CM_SPEM relations can be identified as well in this situation:<br />
11 seamonkey/source/modules/libpref/src/init/all.js<br />
12 docshell/base/nsDefaultURIFixup.cpp<br />
8
Change language