Your SlideShare is downloading. ×
  • Like
  • Save
Ensemble: a Recommendation Tool for Promoting Communications in Software Teams
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×

Now you can save presentations on your phone or tablet

Available for both IPhone and Android

Text the download link to your phone

Standard text messaging rates apply

Ensemble: a Recommendation Tool for Promoting Communications in Software Teams

  • 1,127 views
Published

Presentation by Annie Ying at the RSSE 2008 Workshop.

Presentation by Annie Ying at the RSSE 2008 Workshop.

Published in Technology , Business
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Be the first to comment
    Be the first to like this
No Downloads

Views

Total Views
1,127
On SlideShare
0
From Embeds
0
Number of Embeds
0

Actions

Shares
Downloads
0
Comments
0
Likes
0

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
  • Successful software development requires effective coordination among developers. In this talk, we propose Ensemble, an approach and a set of tools that aim to help developers better coordinate their work. Built on IBM Rational Team Concert, Ensemble helps developers select the right people to collaborate with, the right times to collaborate with them, and to stay coordinated with them over time.

Transcript

  • 1. Ensemble: a Recommendation Tool for Promoting Communications in Software Teams Annie Ying, IBM Watson Research Ctr with colleagues from IBM Research
  • 2. The Ensemble team...
    • Watson, in NY and Cambridge, MA
      • Kate Ehrlich (PI)
      • Mary Helander
      • Paul Matchen
      • Andrew Sempere
      • Peri Tarr
      • Clay Williams
      • Annie Ying
    • Beijing, China
      • Ping Cheng
      • Ya Bin Dang
      • Peng Ji
      • Pei Feng Xiang (former)
      • Shun Xiang Yang
  • 3. Distributed software teams face coordination challenges
    • Lack of awareness of evolving code dependencies
      • de Souza et al, 2007
    • Difficulty in maintaining coordination
      • Cheng et al, 2003
  • 4. Need for communication
    • Software gets developed faster when people working on related code communicate with each other
      • Cataldo et al, 2006
  • 5. Existing work on improving coordination
    • Collaboration features, such as extended instance messaging capabilities
      • e.g., Cheng et. al.
    • Expertise Recommendation Systems
      • e.g., Expertise Browser, EEL
    • Awareness tools
      • e.g., Palantir
  • 6. Ensemble
    • Select the right people
    • Select the right times to collaborate with them
    • Stay coordinated with them over time
    • 2 views built on the Jazz platform and the Rational Team Concert client:
      • Recommender
      • Watch List
  • 7. Our previous research based on gaps Node Tie Congruence Arc Mirroring Congruence P i P j S Gap G P (P, A P ) G s (S, A s ) P i P j S Congruence G P (P, A P ) G s (S, A s ) Gap P i P j S a G P (P, A P ) G s (S, A s ) S b Congruence P i P j S a G P (P, A P ) G s (S, A s ) S b
  • 8. Jazz
  • 9. Recommender
  • 10. Watch List
  • 11. Conclusion
    • Brief introduction to Ensemble, a developer Recommender and Watch List that helps developers
      • Select the right people
      • Select the right times to collaborate with them
      • Stay coordinated with them over time
    • Next steps
      • validating the tool in distributing development teams
    • Visit our website:
      • http://softdevgov.net
  • 12. Jazz and Jazz development data
    • A change set that is associated with a Work Item was delivered
    • An iteration plan with an initial deadline is created
    • A process rule: “All JUnit tests must be run before code is delivered” is added
    Web client Rational Team Concert client Jazz development data stored in a Jazz repository
  • 13. Software development governance (SDG)
    • Businesses need techniques for understanding the value provided by software development and delivery
    • Businesses need insights into the risks incurred through software development and delivery activities
  • 14. Tempo
    • Addresses project scheduling risks
    • Allowing developers to express uncertainty in task estimates
    • Computes the probability that tasks given estimates that developers provide