From: Abd-El-Kader Sahraoui (kader@laas.fr)
Date: Fri May 21 2004 - 19:19:50 EST
effectivelly, business goals determine the process of prirtisation; Andrew
too stressed out the implicit link requirements and costs.
we come the basic :
- difficulty in setting req but not impossible
- we all make priorities whenever we take an action/decision even though
it wasever set explicitly
- so priotisation is dynamic ; might not be set only at the elicitation
and may change as an atributed of a req (requirements evolution)
- stakeholder dependant : hierarchy,
- requirement link : if R1 is dependab=nt on R2, then R1 and R2 priroty
are related
- analysis of requirement priority : whar does it mean higher priority ?
to implement first, to affect a validation process more strict (safety
Req),
I advise the attached paper, I used often in practical small project only reference : published at INCOSE symposium 1998 at Vancouver best regards
Kader
Professor at LAAS-CNRS and Toulouse University France
> I believe that prioritisation is very difficult to do realising that the
> whole prioritisation process occurs in a very political and biased
> organisational setting.
>
> In my PhD work I highlight the importance of finding cliques of
> stakeholders who are setting their priorities based on their own agendas
> and not based on what is most beneficial for the organisation.
>
> Social Network Analysis helps in detecting anomalies in priorities and
> possible cliques.
>
> I also believe prioritisation should be goal-based. Business goals are a
> good means to validate the priorities produced by any prioritisation
> process. The requirements that affect the most important goals should
> (theoretically) have a high priority.
>
> Objective techniques could also help set priorities. For instance,
> investigating the number of other requirements that depend on a
> particular requirement being satisfied, the number of objects and
> stakeholders that interact with a requirement, and the importance of
> those objects and stakeholders to the system.
>
> Most of the prioritisation techniques are very subjective in nature, and
> disregard the value of understanding why a stakeholder has set his/her
> priorities.
>
> Kind Regards
> Frank Moisiadis
>
> Dept Computing
> Macquarie University
> Marsfield NSW 2109
> Australia
>
> fmoisiad@ics.mq.edu.au
>
>
>
>
>
>
> ----- Original Message -----
> From: "Donald Firesmith" <donald_firesmith@hotmail.com>
> To: <re-online@it.uts.edu.au>
> Sent: Sunday, May 16, 2004 9:04 AM
> Subject: [re-online] Prioritizing Requirements
>
>
>> Everyone,
>> My next column on Requirements Engineering for the Journal of Object
>> Technology will be about prioritizing requirements. What does the
>> group think is the most important issues to address with regard to
>> prioritizing requirements? What are the biggest risks and
>> misunderstandings? Does anyone have any specific questions they would
>> like to see addressed? What are your favorite techniques for
>> categorizing requirement priorities? You get the idea. What would
>> you like to see addressed? I thought that since
> I
>> have several weeks before the column is due, I would get the group's
> inputs
>> to make sure that I didn't let anything significant fall through the
> cracks.
>> Thanks.
>>
>> Donald Firesmith
>> Senior Member of the Technical Staff
>> Acquisition Support Program
>> Software Engineering Institute (SEI)
>> Carnegie Mellon University (CMU)
>> Pittsburgh, PA 15213-3890
>> (412) 268-6874
>> dgf@sei.cmu.edu
>> http://www.donald-firesmith.com
>>
>> _________________________________________________________________
>> Express yourself with the new version of MSN Messenger! Download today
>> - it's FREE!
>> http://messenger.msn.click-url.com/go/onm00200471ave/direct/01/
>> --------------------------------------------------------------------------
> -----
>> To send a message to this mailing list send it to
>> re-online@it.uts.edu.au. To unsubscribe from this mailing list, email
>> majordomo@it.uts.edu.au with
> the
>> message `unsubscribe re-online' in the BODY of the mail.
>>
> -------------------------------------------------------------------------------
> To send a message to this mailing list send it to
> re-online@it.uts.edu.au. To unsubscribe from this mailing list, email
> majordomo@it.uts.edu.au with the message `unsubscribe re-online' in the
> BODY of the mail.
This archive was generated by hypermail 2.1.6 : Mon May 24 2004 - 09:00:20 EST