According to Raymond [42], the participation of more people will result in the identification and elimination of more bugs, which in turn will likely result in faster software improvement. Along with this, a further claim is that the resulting rapid evolution of software via the OSS model also results in better software. The cited reason for this is that the traditional closed model is seen by "only a very few programmers" [38], while most users are obliged to use the software "blindly." When taking the above into account, OSS development can be said to be a process of perpetual maintenance. It is a series of maintenance efforts by multiple users who identify and report bugs. The voluntary nature of most OSS projects [14][48] necessitates providing a platform from which workers can make the minimal effort for significant results. Many researchers have investigated the phenomenon of OSS contribution, and the motivation behind it [34], but very little attention has been paid to possible inhibitors to such contributions. Von Hippel and Von Krogh [51] mention that the complexity of the source code and the level of difficulty of the embedded algorithms is a major concern for developers. Logic suggests, and authors such as Fitzgerald [15]...
It is therefore vitally important to cultivate an understanding of the source code complexity, as well as how this could impact on software and OSS development.Our semester plans gives you unlimited, unrestricted access to our entire library of resources —writing tools, guides, example essays, tutorials, class notes, and more.
Get Started Now