Eclipse Community Forums: EPF » Define Vision#Gather stakeholder requests

Help

Home

Home » Archived » EPF » Define Vision#Gather stakeholder requests

Show: Today's Messages :: Show Polls :: Message Navigator

Define Vision#Gather stakeholder requests [message #37471]

Sat, 11 August 2007 13:47

Roman Smirak

Messages: 136
Registered: July 2009

Senior Member

Hi,

The task: Define vision contains steps as follows (simplified here):
* Identify stakeholders
* Understand the problem
....
* Gather stakeholder request
....
* Define features

My understanding (simplified again): To understand the problem (and
stakeholder's needs to solve it) I need to understand the context (current
work procedure and its pain or limits, for instance) and then I can suggest
appropriate solution in form of a working software system (particular form
of the solution to be implemented) specified by features.

Q: What does it mean in this context: 'Gather stakeholder request'? What is
the relationship among Need, Request, Requirement?
My interpretation: a stakeholder is already able to express sort of
requirement about the system (its particular behaviour or capability) - e.g.
we are developing next version of an existing system, or the stakeholder is
somehow experienced or software-enabled:-), etc. So the term belongs to the
particular (sw) solution space as well as a requirement which is probably
more formal or properly handled then (+ attributed, etc.) whereas a need
belongs to the problem space and it is software independent. Is this correct
meaning of the step?

Regards,

Roman

Report message to a moderator

Re: Define Vision#Gather stakeholder requests [message #37641 is a reply to message #37471]

Sun, 12 August 2007 23:51

Peter Haumer

Messages: 228
Registered: July 2009

Senior Member

The distinction goes back to Dean Leffingwell's RM book. See this article:

http://www.ibm.com/developerworks/rational/library/content/R ationalEdge/dec00/FeaturesUseCasesRequirementsOhMyDec00.pdf

Peter.

"Roman Smirak" <roman.smirak@tietoenator.com> wrote in message
news:f9kelm$lnm$1@build.eclipse.org...
> Hi,
>
> The task: Define vision contains steps as follows (simplified here):
> * Identify stakeholders
> * Understand the problem
> ...
> * Gather stakeholder request
> ...
> * Define features
>
> My understanding (simplified again): To understand the problem (and
> stakeholder's needs to solve it) I need to understand the context (current
> work procedure and its pain or limits, for instance) and then I can
> suggest appropriate solution in form of a working software system
> (particular form of the solution to be implemented) specified by features.
>
> Q: What does it mean in this context: 'Gather stakeholder request'? What
> is the relationship among Need, Request, Requirement?
> My interpretation: a stakeholder is already able to express sort of
> requirement about the system (its particular behaviour or capability) -
> e.g. we are developing next version of an existing system, or the
> stakeholder is somehow experienced or software-enabled:-), etc. So the
> term belongs to the particular (sw) solution space as well as a
> requirement which is probably more formal or properly handled then (+
> attributed, etc.) whereas a need belongs to the problem space and it is
> software independent. Is this correct meaning of the step?
>
>
> Regards,
>
> Roman
>

Report message to a moderator

Re: Define Vision#Gather stakeholder requests [message #37965 is a reply to message #37641]

Tue, 14 August 2007 07:23

Roman Smirak

Messages: 136
Registered: July 2009

Senior Member

Hi Peter,

thanks for info.

I went trough it very quickly, sounds familiar to me, however, I haven't
found an answer to my primary question concerning Gather stakeholder
request; can you please accept/reject my interpretation?

Thanks a lot,

Roman

"Peter Haumer" <phaumer@us.ibm.com> wrote in message
news:f9o6di$at3$1@build.eclipse.org...
> The distinction goes back to Dean Leffingwell's RM book. See this
> article:
>
> http://www.ibm.com/developerworks/rational/library/content/R ationalEdge/dec00/FeaturesUseCasesRequirementsOhMyDec00.pdf
>
> Peter.
>
>
>
> "Roman Smirak" <roman.smirak@tietoenator.com> wrote in message
> news:f9kelm$lnm$1@build.eclipse.org...
>> Hi,
>>
>> The task: Define vision contains steps as follows (simplified here):
>> * Identify stakeholders
>> * Understand the problem
>> ...
>> * Gather stakeholder request
>> ...
>> * Define features
>>
>> My understanding (simplified again): To understand the problem (and
>> stakeholder's needs to solve it) I need to understand the context
>> (current work procedure and its pain or limits, for instance) and then I
>> can suggest appropriate solution in form of a working software system
>> (particular form of the solution to be implemented) specified by
>> features.
>>
>> Q: What does it mean in this context: 'Gather stakeholder request'? What
>> is the relationship among Need, Request, Requirement?
>> My interpretation: a stakeholder is already able to express sort of
>> requirement about the system (its particular behaviour or capability) -
>> e.g. we are developing next version of an existing system, or the
>> stakeholder is somehow experienced or software-enabled:-), etc. So the
>> term belongs to the particular (sw) solution space as well as a
>> requirement which is probably more formal or properly handled then (+
>> attributed, etc.) whereas a need belongs to the problem space and it is
>> software independent. Is this correct meaning of the step?
>>
>>
>> Regards,
>>
>> Roman
>>
>
>

Report message to a moderator

Re: Define Vision#Gather stakeholder requests [message #38180 is a reply to message #37965]

Fri, 17 August 2007 02:20

Peter Haumer

Messages: 228
Registered: July 2009

Senior Member

Stakeholders are normally not trained in requirements engineering. Hence,
their request could be of any of the kinds described in the paper. They
could request "to reduce costs by 10%", which is a Need or Business Goal,
they could request to provide a "order entry function that checks for
validity of the customer no", which is a Requirement, they could request
"that the solution must run on their existing DB2 DBMS", which is a Design
Constraint, or they could request "to fix a calculation bug in the order
summary report", which is a Bug. Hence, Stakeholder Request is a catch all
that a system analyst then transforms into the right artifact. Using tools
like Clear Quest for stakeholder request and Requisite Pro for requirements
artifacts would allow you to trace the relationship between the two. Of
course, many people just manage everything in their stakeholder request
system and perhaps just qualify the request type with attributes and
categories.

Hope that helps,
Peter.

"Roman Smirak" <roman.smirak@tietoenator.com> wrote in message
news:f9rla1$u05$1@build.eclipse.org...
> Hi Peter,
>
> thanks for info.
>
> I went trough it very quickly, sounds familiar to me, however, I haven't
> found an answer to my primary question concerning Gather stakeholder
> request; can you please accept/reject my interpretation?
>
> Thanks a lot,
>
> Roman
>
> "Peter Haumer" <phaumer@us.ibm.com> wrote in message
> news:f9o6di$at3$1@build.eclipse.org...
>> The distinction goes back to Dean Leffingwell's RM book. See this
>> article:
>>
>> http://www.ibm.com/developerworks/rational/library/content/R ationalEdge/dec00/FeaturesUseCasesRequirementsOhMyDec00.pdf
>>
>> Peter.
>>
>>
>>
>> "Roman Smirak" <roman.smirak@tietoenator.com> wrote in message
>> news:f9kelm$lnm$1@build.eclipse.org...
>>> Hi,
>>>
>>> The task: Define vision contains steps as follows (simplified here):
>>> * Identify stakeholders
>>> * Understand the problem
>>> ...
>>> * Gather stakeholder request
>>> ...
>>> * Define features
>>>
>>> My understanding (simplified again): To understand the problem (and
>>> stakeholder's needs to solve it) I need to understand the context
>>> (current work procedure and its pain or limits, for instance) and then I
>>> can suggest appropriate solution in form of a working software system
>>> (particular form of the solution to be implemented) specified by
>>> features.
>>>
>>> Q: What does it mean in this context: 'Gather stakeholder request'? What
>>> is the relationship among Need, Request, Requirement?
>>> My interpretation: a stakeholder is already able to express sort of
>>> requirement about the system (its particular behaviour or capability) -
>>> e.g. we are developing next version of an existing system, or the
>>> stakeholder is somehow experienced or software-enabled:-), etc. So the
>>> term belongs to the particular (sw) solution space as well as a
>>> requirement which is probably more formal or properly handled then (+
>>> attributed, etc.) whereas a need belongs to the problem space and it is
>>> software independent. Is this correct meaning of the step?
>>>
>>>
>>> Regards,
>>>
>>> Roman
>>>
>>
>>
>
>

Report message to a moderator