RA 8 : Open Source Software

Issues of Dependability in Open Source Software Development

Lawrie, Tony (May, 2002). Issues of Dependability in Open Source Software Development. Retrieved Sept 10, 2009 from http://delivery.acm.org/10.1145/640000/638584/p34-lawrie.pdf?key1=638584&key2=0798262521&coll=ACM&dl=ACM&CFID=51206778&CFTOKEN=14041621


Abstract:

The article “Issues of Dependability in Open Source Software
Development” discusses many aspects of Open Source Software revolving
around its dependability and the processes that contribute to that
dependability. To the author, dependability as discussed pertains to
reliability, security and safety of these processes.

First, it discusses the dependability of OSS products. Software
developed as Open Source needs to maintain attributes such as
security, reliability and availability to be called dependable. It
also makes comparisons between Open Source and Non-Open Source
Software Development, citing that the former is not necessarily more
dependable than the latter and gives examples of scenarios where OSS
is at a disadvantage.

Then it discusses the dependability of OSS Processes. It mentions that
OSS processes are less constrained compared to Non-OSS ones because
commercial, time and political barriers apply less. Also, OSS codes
are exposed to higher level of reused and increased knowledge
accumulation is promoted. It mentions that increased potential for
diverse collaboration is found in communities practicing OSS
development.

Issues and implications for OSS and Dependability were also discussed.
It states that there is a need to determine at which attributes assure
dependability of both OSS and Non-OSS software and the evidence that
leads to these conclusions. The nature and type of products, business
and government attitudes, and the tools and paradigms that these
approaches use are to be taken into consideration. Even with the
obvious differences, the article states that there is no substitute
for human intelligence in the development process.

As a conclusion, the author states that OSS products may be limited to
the development of systems oriented software which is vital for
further trustworthy composition and building of dependable systems.
The OSS approach is not subjected to the same of constraints like time
and budget. Tools and methods will contribute to the drive to improve
process and quality assurance.


Three things I learned from the Article:
1. Open Source Software products and processes are less limited by
time and budget constraints compared to Non-OSS software.
2. Tools and Processes do a lot to improve Open Source development
even if they lack the resources in comparison to Non-OSS development.
3. Dependability can be defined under a number of things, such as
reliability, availability, security, and even the perception of the
users.


Reflection:

As a librarian I can put to good use these practices discussed in the
article. While I recognize that I work under a government institution
such as Engineering Library II which at times can be subject to
limitations such as manpower or budget constraints, it is by no means
an excuse not to provide dependable services to our clients. What we
can do is to improve our processes the same way these OSS developers
have done to get around these limitations. We can also establish
better tools such as better indexes and loaning protocols so as to
enhance the security of our materials without subjecting our clientele
experience to less than satisfied. We can also establish relationships
with other libraries as a collaborative effort to provide information,
the same way boundaries were not considered in OSS developers efforts
to create their products.