Your SlideShare is downloading. ×
Web Collaboration for Software Engineering
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×

Introducing the official SlideShare app

Stunning, full-screen experience for iPhone and Android

Text the download link to your phone

Standard text messaging rates apply

Web Collaboration for Software Engineering

1,366
views

Published on

My presentation for my master thesis. Main contents are: …

My presentation for my master thesis. Main contents are:

- Research on CSCW, Groupware, Social Software and Software Engineering
- Analysis of 47 Software Engineering tools
- Web prototype developed in Ruby on Rails
- Experiment for testing the prototype

It's in English.

Published in: Education, Technology

0 Comments
2 Likes
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total Views
1,366
On Slideshare
0
From Embeds
0
Number of Embeds
1
Actions
Shares
0
Downloads
93
Comments
0
Likes
2
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

Transcript

  • 1. Web collaboration for software engineering
    Tiago Mourão Teixeira
    Supervisor: Ademar Aguiar, Co-supervisor: Nuno Flores
    MIEIC - 17 July 2009
  • 2. Presentation outline
    Collaboration: What and why?
    Background on collaboration research areas
    Collaborative Software
    Software Engineering Tools
    Problem Statement and Solution
    Prototype and Experiment
    Conclusions and Future Research
    2
  • 3. Collaboration: what is?
    +
    Collaboration is a process where two or more parties
    work together towards a common goal.
    3
  • 4. Collaboration: why?
    Social nature
    Complexity
    Dimension
    4
  • 5. Background on collaboration research areas
    Groupware
    Computer-Supported Collaborative Work (CSCW)
    Collaboration in Software Engineering
    5
  • 6. Groupware
    Original definition:
    “intentional group processes plus software to support them” (Peter and Trudy Johnson-Lenz)
    Main goal
    Use computers to assist groups in:
    Communicating
    Collaborating
    Coordinating
    6
  • 7. cscw
    Definition:
    “ CSCW examines the possibilities and effects of technological support for humans involved in collaborative group communication and work processes” (J. M. Bowers and S.D. Benford)
    Interdisciplinary field
    7
  • 8. Groupware vs. cscw
    CSCW
    Groupware
    8
  • 9. cscw classification
    9
  • 10. Categories of collaboration
    Unstructured communication
    Coordination (E-mail, IM, …)
    Meetings and conversations in workplace
    Structured communication
    Formal and semi-formal artifacts
    (Reports, Diagrams, ...)
    Each artifact has its own model
    Collaboration in software engineering
    10
  • 11. Collaboration in software engineering
    11
  • 12. Collaborative software: asynchronous and different place cscw
    12
  • 13. Collaborative software: asynchronous and different place cscw
    13
  • 14. Collaborative software: asynchronous and same place cscw
    14
  • 15. Collaborative software: synchronous and different place cscw
    15
  • 16. Collaborative software: synchronous and same place cscw
    16
  • 17. Collaborative software: social software
    17
  • 18. Collaborative software: social software
    18
  • 19. Software engineering tools
    47 tools distributed among 6 areas:
    19
  • 20. Software engineering tools: Criteria
    Collaboration
    Awareness
    Communication
    Collective Knowledge
    Integration
    Other characteristics
    Context awareness
    20
  • 21. Software engineering tools: open issues
    E-mail
    Depended on external services
    Used primarily for notification purposes
    Group calendars
    Lack in the Engineering Management area
    21
  • 22. Software engineering tools: open issues
    Lack of features popular in the Web
    22
  • 23. Software engineering tools: open issues
    Inexistence of:
    Online whiteboard
    Usages: draft of a diagram (Design)
    Recommender
    Screen sharing
    Social bookmarking
    Social cataloging
    Lack of:
    23
  • 24. Problem statement
    Two gaps in the state of the art
    Need for better web-based tools covering a project’s life cycle
    Few studies on the impact of integrating collaboration features in those tools, by designing and conducting an experiment
    24
  • 25. Problem statement
    Uniqueness of the problem
    Collaboration tools
    Lack of support for the life-cycle of a project
    The majority provided support by integration with other tools
    Studies
    Measured the effects of collaboration in the workplace
    Lack of features integrated in web-based tools
    Didn’t monitor the life-cycle of a project
    However…
    25
  • 26. Solution
    First gap:
    Integrate collaboration features as plugins into a web-based tool (Redmine) and cover the life-cycle of a project
    Second gap:
    Design and conduct an experiment for assessing the prototype’s effectiveness.
    26
  • 27. Prototype
    Features integrated as plugins into Redmine, a project management web application
    27
  • 28. Prototype
    Features analyzed according to four criteria:
    Time
    Value
    Innovation
    Preference
    28
  • 29. Prototype
    Recommendations
    29
  • 30. Prototype
    Social networking
    30
  • 31. Prototype
    Architectural patterns: 3-tier and MVC
    31
  • 32. Prototype
    Logical architecture
    32
  • 33. Prototype
    Physical architecture
    33
  • 34. Experiment
    Experimental Group
    Control Group
    34
  • 35. Experiment
    Subjects must be:
    Familiar of collaborative software.
    Have participated at least in one Software Engineering project.
    Be willing perform teamwork.
    Attributes of interest:
    Task completion time.
    Tools used.
    9 tasks for developing game Pong in Scratch, an interactive programming language.
    Experiment wasn’t conducted due to the subjects’ unavailability.
    35
  • 36. Conclusions
    Objectives were in its majority successfully achieved
    Relevant achievements
    Depth and broadness of the research
    Degree of integration between plugins
    High number of implemented requirements
    36
  • 37. Conclusions
    Contributions
    Research multiple areas and use them to prioritize the features
    Innovation:
    Prototype
    Recommendations, Social bookmarking and Social cataloging plugins
    Experiment
    37
  • 38. Conclusions
    Future Research
    Conduct the experiment
    Resolve the identified open issues
    Fields of study
    Integration between web and desktop-based tools
    Effective support for Global Software Development
    Migration of tools to the web
    Prototype’s future developments
    E-mail with tags
    E-mail and feeds notifications of “watched” users’ actions
    Recommendations based on implicit data collection
    The prototype only provides generic support
    38
  • 39. Discussion
    Thank you!
    39