Your SlideShare is downloading. ×
0
Searching for Key Stakeholders in Large-Scale Software Projects
Searching for Key Stakeholders in Large-Scale Software Projects
Searching for Key Stakeholders in Large-Scale Software Projects
Searching for Key Stakeholders in Large-Scale Software Projects
Searching for Key Stakeholders in Large-Scale Software Projects
Searching for Key Stakeholders in Large-Scale Software Projects
Searching for Key Stakeholders in Large-Scale Software Projects
Searching for Key Stakeholders in Large-Scale Software Projects
Searching for Key Stakeholders in Large-Scale Software Projects
Searching for Key Stakeholders in Large-Scale Software Projects
Searching for Key Stakeholders in Large-Scale Software Projects
Searching for Key Stakeholders in Large-Scale Software Projects
Searching for Key Stakeholders in Large-Scale Software Projects
Searching for Key Stakeholders in Large-Scale Software Projects
Searching for Key Stakeholders in Large-Scale Software Projects
Searching for Key Stakeholders in Large-Scale Software Projects
Searching for Key Stakeholders in Large-Scale Software Projects
Searching for Key Stakeholders in Large-Scale Software Projects
Searching for Key Stakeholders in Large-Scale Software Projects
Searching for Key Stakeholders in Large-Scale Software Projects
Searching for Key Stakeholders in Large-Scale Software Projects
Searching for Key Stakeholders in Large-Scale Software Projects
Searching for Key Stakeholders in Large-Scale Software Projects
Searching for Key Stakeholders in Large-Scale Software Projects
Searching for Key Stakeholders in Large-Scale Software Projects
Searching for Key Stakeholders in Large-Scale Software Projects
Searching for Key Stakeholders in Large-Scale Software Projects
Searching for Key Stakeholders in Large-Scale Software Projects
Searching for Key Stakeholders in Large-Scale Software Projects
Searching for Key Stakeholders in Large-Scale Software Projects
Searching for Key Stakeholders in Large-Scale Software Projects
Searching for Key Stakeholders in Large-Scale Software Projects
Searching for Key Stakeholders in Large-Scale Software Projects
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×
Saving this for later? Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime – even offline.
Text the download link to your phone
Standard text messaging rates apply

Searching for Key Stakeholders in Large-Scale Software Projects

690

Published on

Published in: Business, Technology, Education
0 Comments
1 Like
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total Views
690
On Slideshare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
0
Comments
0
Likes
1
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide
  • 22
  • What is the relationship
  • Transcript

    • 1. Searching for Key Stakeholders in Large-Scale Software ProjectsSoo Ling LimUniversity College London 13th CREST Open Workshop 12 May 2011
    • 2. What makes developers cry? cant communicate with stakeholders cant maintain 541 developers stakeholders cant find stakeholders stakeholders lack skill stakeholders lack commitment I.
Alexander
&
S.
Robertson
 (2004)
Understanding
 Project
Sociology
by
 Modeling
Stakeholders.

 IEEE
SoCware.

    • 3. S.L.
Lim,
D.
Quercia
&
A.
Finkelstein
(2010)
StakeNet:
Using
Social
Networks
to
Analyse
the
stakeholders
of
Large‐Scale
SoGware
Projects.
In
32nd
Int.
Conf.
on
SoG.
Eng.
(ICSE).

    • 4. Step 1: Find initial stakeholders Users Developers Legislators Decision-makers
    • 5. Step 2: Get recommendations
    • 6. Step 2: Get recommendations <Alice, Director of Estates, 4>
    • 7. Step 3: Build social network
    • 8. Step 3: Build social network Alice
    • 9. Step 3: Build social network Bob Carl Alice
    • 10. Step 3: Build social network Bob Carl Alice
    • 11. Step 4: Elicit requirements Bob Carl Alice
    • 12. Step 5: Prioritise requirements nImportanceR = ∑ ProjectInfluenceS × RatingS S=1
    • 13. Step 5: Prioritise requirements nImportanceR = ∑ ProjectInfluenceS × RatingS S=1 Use
social
network
measures,
e.g.,
 • 
Betweenness
centrality
 • 
PageRank
 • 
Out‐degree
centrality
 • 
In‐degree
centrality
S.L.
Lim
&
A.
Finkelstein
(2011)
StakeRare:
Social
Networks
and
CollaboraLve
Filtering
for
Large‐Scale
Requirements
ElicitaLon.
IEEE
TransacLons
on
SoCware
Engineering
(TSE).

    • 14. Step 5: Prioritise requirements 0.81
 0.70
 0.58
 0.56
 0.49
 0.48
S.L.
Lim
&
A.
Finkelstein
(2011)
StakeRare:
Social
Networks
and
CollaboraLve
Filtering
for
Large‐Scale
Requirements
ElicitaLon.
IEEE
TransacLons
on
SoCware
Engineering
(TSE).

    • 15. Step 5: Prioritise requirements 0.81
 n ImportanceR = ∑ ProjectInfluenceS × RatingS 0.70
 S=1 0.58
 0.56
 € 0.49
 0.48
S.L.
Lim
&
A.
Finkelstein
(2011)
StakeRare:
Social
Networks
and
CollaboraLve
Filtering
for
Large‐Scale
Requirements
ElicitaLon.
IEEE
TransacLons
on
SoCware
Engineering
(TSE).

    • 16. Use a genetic algorithm to search for real influence GA to search for weightsS.L.
Lim,
M.
Harman
&
A.
Susi.
Searching
for
Key
Stakeholders
in
Large‐Scale
SoCware
Projects
(submiVed).

    • 17. Step 5: Prioritise requirements nImportanceR = ∑ ProjectInfluenceS × RatingS S=1
    • 18. Step 5: Prioritise requirements n ImportanceR = ∑ ProjectInfluenceS × RatingS S=1 Actual importance(Based on post project knowledge)
    • 19. Step 5: Prioritise requirements n ImportanceR = ∑ ProjectInfluenceS × RatingS S=1 Actual importance(Based on post project knowledge)
    • 20. RALIC: UCL Access Control Project
    • 21. Ratings
    • 22. Data Set•  ~150 requirements•  68 stakeholders recommended other stakeholders•  76 stakeholders provided ratings•  actual ranked list of requirements based on post project knowledge
    • 23. Findings•  Existing social network measures can be used to prioritise stakeholders….but they are not optimal and may miss out key stakeholders (GA can always improve them).•  Evolution corrected assumptions made by the measures that don’t hold for the stakeholder.
    • 24. Findings•  The GA found many good solutions –  A good set of requirements can be constructed from many different subsets of stakeholders•  Some stakeholders hold unique knowledge (always selected by the GA), but the majority of stakeholders share similar knowledge (replaceable)•  The concept of who is a “key stakeholder” depends on which other stakeholders have already been identified.
    • 25. Soo
Ling
Lim
s.lim@cs.ucl.ac.uk


    ×