User Tools

Site Tools


case_studies:subversion
  • Bookmark "The Subversion Project" at del.icio.us
  • Bookmark "The Subversion Project" at Digg
  • Bookmark "The Subversion Project" at Furl
  • Bookmark "The Subversion Project" at Reddit
  • Bookmark "The Subversion Project" at Ask
  • Bookmark "The Subversion Project" at Google
  • Bookmark "The Subversion Project" at Netscape
  • Bookmark "The Subversion Project" at StumbleUpon
  • Bookmark "The Subversion Project" at Technorati
  • Bookmark "The Subversion Project" at Live Bookmarks
  • Bookmark "The Subversion Project" at Yahoo! Myweb
  • Bookmark "The Subversion Project" at Facebook
  • Bookmark "The Subversion Project" at Newsvine
  • Bookmark "The Subversion Project" at Yahoo! Bookmarks
  • Bookmark "The Subversion Project" at Twitter
  • Bookmark "The Subversion Project" at myAOL
  • Bookmark "The Subversion Project" at Slashdot
  • Bookmark "The Subversion Project" at Mister Wong

The Subversion Project

Subversion The software development life cycle (SDLC) of a proprietary product differs from that of an open source product. While there are similarities in terms of the order of execution of tasks, the differences lay in the way the tasks are accomplished. The development of a proprietary product in a corporate environment takes place in a centralized manner. Individuals involved in the project have clearly defined roles for designing, managing the project, development, etc. However, in Open Source Software (OSS) development, there are no clearly defined roles. It usually consists of multiple users who also function as co-developers of the software. This peculiarity of the OSS development model necessitates that the general structure of the software itself be modular allowing for parallel development. In other words, the development and maintenance process followed for an OSS can be referred to as controlled chaos.

This report is a result of extensive research for OSS case study of Subversion Project. The research involved studying Subversion from Software Project Management perspective. In conclusion, the report compares and contrasts the processes followed in Subversion against the processes recommended by standard Software Engineering practices.

Table of Contents

  • Bookmark "The Subversion Project" at del.icio.us
  • Bookmark "The Subversion Project" at Digg
  • Bookmark "The Subversion Project" at Furl
  • Bookmark "The Subversion Project" at Reddit
  • Bookmark "The Subversion Project" at Ask
  • Bookmark "The Subversion Project" at Google
  • Bookmark "The Subversion Project" at Netscape
  • Bookmark "The Subversion Project" at StumbleUpon
  • Bookmark "The Subversion Project" at Technorati
  • Bookmark "The Subversion Project" at Live Bookmarks
  • Bookmark "The Subversion Project" at Yahoo! Myweb
  • Bookmark "The Subversion Project" at Facebook
  • Bookmark "The Subversion Project" at Newsvine
  • Bookmark "The Subversion Project" at Yahoo! Bookmarks
  • Bookmark "The Subversion Project" at Twitter
  • Bookmark "The Subversion Project" at myAOL
  • Bookmark "The Subversion Project" at Slashdot
  • Bookmark "The Subversion Project" at Mister Wong
case_studies/subversion.txt · Last modified: 2014/10/19 13:28 (external edit)