This week's book giveaway is in the OO, Patterns, UML and Refactoring forum. We're giving away four copies of Refactoring for Software Design Smells: Managing Technical Debt and have Girish Suryanarayana, Ganesh Samarthyam & Tushar Sharma on-line! See this thread for details.
Actors interact with the system. They might be humans sitting at the computer or other systems calling APIs or being called via APIs.
Stakeholders have some interest in the system. They include the users and many others, eg company officers who invest in a system to improve their business processes but never sign on the system themselves. I'd also include partners you'll need to get the system built and installed, like the network and production support folks.
A good question is never answered. It is not a bolt to be tightened into place but a seed to be planted and to bear more seed toward the hope of greening the landscape of the idea. John Ciardi
Joined: Oct 11, 2004
Thank you very much Stan ,
Stakeholders are just related to system but they don't directly act ( beheave ) with system ...
actors are always stakeholders but stakeholders are not always actor ...
is it right ?
Thanks . [ April 13, 2005: Message edited by: rathi ji ]
Joined: Jan 29, 2003
Yes, I'd buy that. I went to the dictionary for stake (not stack ) and found I had forgotten the gambling aspect of the word
The last definitions were the ones I was after, but investing in software development is a gamble, too.
The XP folks play word neat games with two stakeholder roles: the "Goal Doner" who wants the system and knows what he wants, and the "Gold Owner" who pays for it. [ April 12, 2005: Message edited by: Stan James ]