Beta 1

Title Support for Integrity Module as Plug-in in an Existing Wiki
Author Følsgaard, Christopher
Ludwigs, Mark
Supervisor Jensen, Christian D. (Embedded Systems Engineering, Department of Informatics and Mathematical Modeling, Technical University of Denmark, DTU, DK-2800 Kgs. Lyngby, Denmark)
Institution Technical University of Denmark, DTU, DK-2800 Kgs. Lyngby, Denmark
Thesis level Master's thesis
Year 2011
Abstract Today software development is one of the fastest evolving technologies on the planet. With the increasing amount of open source communities, we see a progressive tendency of developing large scale applications in tons of variations supporting individual needs. This is very conducive for software development as people with different backgrounds can contribute with their niche of interest in order to make very specialized applications available suited for many different people. Unfortunately, these communities are often characterized by ongoing discussions among senior members in relation to settling standards in their software. One way these large scale applications can survive these standards is to support a general structure which allows easy implementation of different ideas from each member of the community. Overall speaking, a general plug-in support or a so-called plug-in interface or infrastructure. This topic has been taken very seriously among many organizations, and today it is almost impossible to find a web browser or Integrated Development Environments which does not support some kind of plug-in interface and thereby enables developers to tailor the application to their needs. Organizations not particular interested in these concepts are large enterprise organizations with monopoly on specific application schematics. However, even they are starting to show interest for these concepts. Probably because they cannot compete with the open source communities and because it is very difficult to tailor large applications with thousands, if not millions, of users with individual needs, with the limited amount of resources in a single organization. Also, the number of wikis have exploded within the last 5 to 10 years and we see a gradual tendency to choose these as templates for writing documentation on a given subject. One of the largest and most famous wikis is probably Wikipedia, with more than 17 million articles1 and in the top 10 of most visited web pages on the world wide web2. The infrastructure of a wiki engine is very basic, compared to competitors in the top 10 like Google and Facebook. Therefore it seems strange that there still, to our knowledge, are no wiki engines implementing a plug-in interface which, in an easy way, makes it possible to tailor it to accommodate individual needs. Perhaps it is because the creators of the wiki engines assess that programming against a plug-in interface is just as extensive as hard coding the solution to accommodate these needs. Whether this is right or wrong, we believe that without a general plug-in architecture in an application, the overall potential is reduced. The benefit of open source development is to receive input from a very large community, consisting of developers with very different backgrounds, prerequisites and technical approaches. However, by not providing a plug-in architecture or interface for your application, you encourage the community to discuss the design instead of actually designing specialized plug-ins that t a wide scale of the end user's needs, whether this is an integrity module, like Sander's, or something completely different.
Imprint Technical University of Denmark (DTU) : Kgs. Lyngby, Denmark
Series IMM-M.Sc.-2011-04
Original PDF ep11_04.pdf (2.03 MB)
Admin Creation date: 2011-01-31    Update date: 2011-01-31    Source: dtu    ID: 274589    Original MXD