From: Pavan, P.S. (pavan@soi.city.ac.uk)
Date: Fri Feb 14 2003 - 21:33:28 EST
--------------9ABD5A7285A7F3A66D8F33AD Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit
Karl,
we did some work on this and you might find the paper written on it
relevant. We used I* to model the stakeholder requirements (goals / sub
goals) and then used AHP to prioritise.
http://panoramix.univ-paris1.fr/CRINFO/REFSQ/02/papers/Maiden.pdf
P Pavan
We’re having a debate about stakeholder requirements prioritization. The text books on requirements that I have seen usually describe the high, medium, low format aka “Must”, “Should”, “Nice”. In practice, many of the requirements might end up being high priority or “Must” have; therefore it would seem that a combination of H/M/L plus the numerical ranking of each group might be more useful.
Any feedback on what scheme has worked well for you, especially when soliciting this info from a number of stakeholders and having to aggregate the results in a meaningful way?
Cheers,
Karl.
--------------9ABD5A7285A7F3A66D8F33AD Content-Type: text/html; charset=iso-8859-1 Content-Transfer-Encoding: 8bit
<!doctype html public "-//w3c//dtd html 4.0 transitional//en">
<html>
<body link="#0000FF" vlink="#800080" lang="EN-US">
Karl,
<p>we did some work on this and you might find the paper written on it
relevant. We used I* to model the stakeholder requirements (goals / sub
goals) and then used AHP to prioritise.
<br><A HREF="http://panoramix.univ-paris1.fr/CRINFO/REFSQ/02/papers/Maiden.pdf">http://panoramix.univ-paris1.fr/CRINFO/REFSQ/02/papers/Maiden.pdf>
<p>P Pavan
<p>-------- Original Message --------
<table BORDER=0 CELLSPACING=0 CELLPADDING=0 >
<tr>
<th ALIGN=RIGHT VALIGN=BASELINE NOWRAP>Subject: </th>
<td>[re-online] Requirements prioritization</td>
</tr>
<tr>
<th ALIGN=RIGHT VALIGN=BASELINE NOWRAP>Date: </th>
<td>Wed, 12 Feb 2003 08:21:45 -0800</td>
</tr>
<tr>
<th ALIGN=RIGHT VALIGN=BASELINE NOWRAP>From: </th>
<td>"Karl Tolgu" <KarlTolgu@msn.com></td>
</tr>
<tr>
<th ALIGN=RIGHT VALIGN=BASELINE NOWRAP>To: </th>
<td><RE-online@it.uts.edu.au></td>
</tr>
</table>
<p><style>
<!--
/* Font Definitions */
@font-face
{font-family:"Trebuchet MS";
panose-1:2 11 6 3 2 2 2 2 2 4;}
@font-face
{font-family:"Franklin Gothic Book";
panose-1:2 11 5 3 2 1 2 2 2 4;}
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman";}
h1
{margin-top:.25in;
margin-right:0in;
margin-bottom:12.0pt;
margin-left:.3in;
text-indent:-.3in;
page-break-after:avoid;
punctuation-wrap:simple;
text-autospace:none;
border:none;
padding:0in;
font-size:16.0pt;
font-family:"Trebuchet MS";
font-weight:bold;}
h2
{margin-top:12.0pt;
margin-right:0in;
margin-bottom:3.0pt;
margin-left:.4in;
text-indent:-.4in;
page-break-after:avoid;
punctuation-wrap:simple;
text-autospace:none;
font-size:10.0pt;
font-family:"Trebuchet MS";
font-weight:bold;}
h5
{margin-top:12.0pt;
margin-right:0in;
margin-bottom:3.0pt;
margin-left:.7in;
text-indent:-.7in;
punctuation-wrap:simple;
text-autospace:none;
font-size:10.0pt;
font-family:"Trebuchet MS";
font-weight:normal;}
p.MsoBodyText, li.MsoBodyText, div.MsoBodyText
{margin-top:0in;
margin-right:0in;
margin-bottom:6.0pt;
margin-left:0in;
font-size:12.0pt;
font-family:"Times New Roman";}
a:link, span.MsoHyperlink
{color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{color:purple;
text-decoration:underline;}
p
{margin-right:0in;
margin-left:0in;
font-size:12.0pt;
font-family:"Times New Roman";}
span.EmailStyle18
{font-family:"Franklin Gothic Book";
color:windowtext;
font-weight:normal;
font-style:normal;
text-decoration:none none;}
@page Section1
{size:8.5in 11.0in;
margin:1.0in 1.25in 1.0in 1.25in;}
div.Section1
{page:Section1;}
{margin-bottom:0in;}
ul
{margin-bottom:0in;}
-->
</style>
<div class=Section1>
<div class="MsoNormal"><span
style='font-size:11.0pt;font-family:"Franklin Gothic Book"'><font face="Franklin Gothic Book"><font size=-1>We’re
having a debate about stakeholder requirements prioritization. The text
books on requirements that I have seen usually describe the high, medium,
low format aka “Must”, “Should”, “Nice”. In practice, many of the requirements
might end up being high priority or “Must” have; therefore it would seem
that a combination of H/M/L plus the numerical ranking of each group might
be more useful.</font></font></span></div>
<p class="MsoNormal"><span
style='font-size:11.0pt;font-family:"Franklin Gothic Book"'></span>
<p class="MsoNormal"><span
style='font-size:11.0pt;font-family:"Franklin Gothic Book"'><font face="Franklin Gothic Book"><font size=-1>Any
feedback on what scheme has worked well for you, especially when soliciting
this info from a number of stakeholders and having to aggregate the results
in a meaningful way?</font></font></span>
<p class="MsoNormal"><span
style='font-size:11.0pt;font-family:"Franklin Gothic Book"'></span>
<p class="MsoNormal"><span
style='font-size:11.0pt;font-family:"Franklin Gothic Book"'><font face="Franklin Gothic Book"><font size=-1>Cheers,</font></font></span>
<p class="MsoNormal"><span
style='font-size:11.0pt;font-family:"Franklin Gothic Book"'><font face="Franklin Gothic Book"><font size=-1>Karl</span><span style='font-size:11.0pt;font-family:
"Franklin Gothic Book"'>.</font></font></span></div>
</body>
</html>
--------------9ABD5A7285A7F3A66D8F33AD--
This archive was generated by hypermail 2.1.6 : Fri Feb 21 2003 - 11:31:31 EST