The term Open Source Software (OSS) has been around for a long time in the world of computer science. Open source software development is a process by which we can manufacture economical and qualitative software and its source could be re-use in the improvement of the software. The success of OSS relies on several factors, e.g. usability, functionality, market focus etc. But in the end how popular the software will be measured by the number of users downloading the software and how much the software is usable to the users. Open Source Software achieve the status for stability, security and functionality. Most of this software has been utilized by expert level users of IT. But from the general users or the non-computer user’s point of view the usability issues of Open source software has been faced the most criticism [25, 26, 27, 28, 29, and 30]. This factor i.e. the usability issues of general user is also responsible for the limited distribution of the open source software [24]. The development process should apply the “user-centered” methodology [25, 26, 27, 28, 29, and 30]. In this thesis paper the issues of usability in OSS development and how the usability of open source software can be improved will be discussed. Beside this I investigate the usability quality of free Open Source Linux-based operating system Ubuntu and try to find out the usability standards of this OSS.

Quality and security of software are key factors in the software development. This thesis deals with the quality of open source software (OSS for short) and different questions that are related with open source and close source software has discussed in the thesis proposal. Open source software is a process by which we can produce cheap and qualitative software and its source could be re-use in the development of the software. Close source software is more expensive than open source software and we can not re-use its source code, so there should be a way by which cheap and qualitative software should be produced. This thesis describes that how the quality of the open source software can be evaluated and increased. There are different factors which are helpful to increase the software quality these factors are low cycle time, low cost and small size of software. These factors are also helpful for the development of software product according to the requirement of clients and the users of that software. This thesis also describes the security and performance of close and open source software and it also analyze different software development processes. The quality of OSS can be increased by use of best evaluation techniques, best quality measurement, best development tools and best development process. There are also many challenges for OSS, which it has to face for improvement of the quality of OSS. Initially there were many drawbacks in open source software but with the passage of time improvement has produced in it. This thesis also describes the compression, advantages and disadvantages of the close source and open source software. / 0046-737218653 , 0046-739131829

Today’s software companies face the challenges of highly distributed development projects and constant changing requirements. To be competitive, the software time to market has to be reduced as much as possible while keeping the expected quality. Development methodologies try to address this challenges by introducing new practices, techniques and methods for communication, requirements management, quality assurance, etc. This thesis proposes the adoption of relevant Free/Libre/Open Source Software practices to improve industrial developments. Many FLOSS projects have proven very successful, producing high quality products with steady frequent releases. The selection of the FLOSS best practices that would benefit industrial developments, and its adaptation for a corporate environment is the aim of this study. To achieve this goal, a framework to compare FLOSS and industrial development methodologies has been created and executed. Three successful FLOSS projects where selected as study targets, as well as two Ericsson’s projects. The framework served to identify FLOSS methodology strengths and compare them with the Ericsson projects. Analysing the significant differences resulting from this comparison, FLOSS best practices were tailored to fit industrial development environments. The final results of the thesis are six adoption opportunities that aim to improve software quality and overall development productivity while increasing practitioners’ motivation and commitment.

Software systems evolve over the life span to accommodate changes in order to meet technical and business requirements. Evolution of open source software (OSS) is challenging because of involvement from a large number of independent teams and developers who make modifications in the systems according to their own requirements. It is required to evaluate these changes as these are being incorporated into the system against the long term evolvability objectives. This paper presents the analysis of the Hackystat, an OSS framework; against analyzability, changeability, extensibility, testability domain specific quality attributes. The analysis of the processes used during the development of the OSS systems is also discussed. On the basis of the analysis and the early research conducted to evaluate software evolvability, an evolvability analysis method for OSS evolution is presented in this report. Guidelines of the model suggest that the requirements identification and analysis, identification of the system components that are to be affected as a result of the change, identification and prioritization of the potential solutions, evaluation of the potential solutions with respect to evolvability characteristics, use of test driven development and automated build tools are the important steps that should be performed to evaluate system changes. Evolvability analysis model also suggests that the team which is responsible to for system overall architecture (project control group) should also evaluate changes submitted by different teams. A case study to modify a service oriented architecture bases system into software as a service cloud model following the guidelines of evolvability analysis model is also presented.

Voice-enabled applications, applications that interact with a user via an audio channel, are used extensively today. Their use is growing as speech related technologies improve, as speech is one of the most natural methods of interaction. They can provide customer support as IVRs, can be used as an assistive technology, or can become an aural interface to the Internet. Given that the telephone is used extensively throughout the globe, the number of potential users of voice-enabled applications is very high. VoiceXML is a popular, open, high-level, standard means of creating voice-enabled applications which was designed to bring the benefits of web based development to services. While VoiceXML is an ideal language for creating these applications, VoiceXML gateways, the hardware and software responsible for interpreting VoiceXML applications and interfacing with the PSTN, are still expensive and so there is a need for a low-cost gateway. Asterisk, and open-source, TDM/VoIP telephony platform, can be used as a low-cost PSTN interface. This thesis investigates adding a VoiceXML service to Asterisk, creating a low-cost VoiceXML prototype gateway which is able to render voice-enabled applications. Following the Component-Based Software Engineering (CBSE) paradigm, the VoiceXML gateway is divided into a set of components which are sourced from the open-source community, and integrated to create the gateway. The browser requires a VoiceXML interpreter (OpenVXI), a Text-To-Speech engine (Festival) and a speech recognition engine (Sphinx 4). The integration of the components results in a low-cost, open-source VoiceXML gateway. System tests show that the integration of the components was successful, and that the system can handle concurrent calls. A fully compliant version of the gateway can be used in the real world to render voice-enabled applications at a low cost. / KMBT_363 / Adobe Acrobat 9.55 Paper Capture Plug-in

One of the main challenges that modern software developers face is the coordination of dependent agents such as software projects and other developers. Transparent development environments that make low-level software development activities visible hold much promise for assisting developers in making coordination decisions. However, the wealth of information that transparent environments provide is potentially overwhelming when developers are wading through information from potentially millions of developers and millions of software repositories when making decisions around tasks that require coordination with projects or other developers. Overcoming the risk of overload and better assisting developers in these environments requires a principled understanding of what exactly developers need to know about dependencies to make their decisions. My approach to a principled understanding of how developers use information in transparent environments is to model the process using signaling theory as a theoretical lens. Developers making key coordination decisions often must determine qualities about projects and other developers that are not directly observable. Developers infer these unobservable qualities through interpreting information in their environment as signals and use this judgment about the project or developer to inform their decision. In contrast to current software engineering literature which focuses on technical coordination between modules or within projects such as modularity or task assignment mechanisms, this work aims to understand how developers use signals to information coordination decisions with dependencies such as other projects or developers. Through this understanding of the signaling process, I can create improved signals that more accurately represent desired unobservable qualities. My dissertation work examines the qualities and signals that developers use to inform specific coordination tasks through a series of three empirical studies. The specific key coordination tasks studied are evaluating code contributions, discussing problems around contributions, and evaluating projects. My results suggest that when project managers evaluate code contributions, they prefer social signals over technical signals. When project managers discuss contributions, I found that they attend to political signals regarding influence from stakeholders to prioritize which problems need solutions. I found that developers evaluating projects tend to use signals that are related to how the core team works and the potential utility a project provides. In a fourth study, using signaling theory and findings from the qualities and signals that developers use to evaluate projects, I create and evaluate an improved signal called “supportiveness” for community support in projects. I compare this signal against the current signal that developers use, stars count, and find evidence suggesting that my designed signal is more robust and is a stronger indicator of support. The findings of these studies inform the design of tools and environments that assist developers in coordination tasks through suggestions of what signals to show and potentially improving existing signals. My thesis as a whole also suggests opportunities for exploring useful signals for other coordination tasks or even in different transparent environments.

In recent years, a surprising new phenomenon has emerged in which globally-distributed online communities collaborate to create useful and sophisticated computer software. These open source software groups are comprised of generally unaffiliated individuals and organizations who work in a seemingly chaotic fashion and who participate on a voluntary basis without direct financial incentive. The purpose of this research is to investigate the relationship between the social network structure of these intriguing groups and their level of output and activity, where social network structure is defined as 1) closure or connectedness within the group, 2) bridging ties which extend outside of the group, and 3) leader centrality within the group. Based on well-tested theories of social capital and centrality in teams, propositions were formulated which suggest that social network structures associated with successful open source software project communities will exhibit high levels of bridging and moderate levels of closure and leader centrality. The research setting was the SourceForge hosting organization and a study population of 143 project communities was identified. Independent variables included measures of closure and leader centrality defined over conversational ties, along with measures of bridging defined over membership ties. Dependent variables included source code commits and software releases for community output, and software downloads and project site page views for community activity. A cross-sectional study design was used and archival data were extracted and aggregated for the two-year period following the first release of project software. The resulting compiled variables were analyzed using multiple linear and quadratic regressions, controlling for group size and conversational volume. Contrary to theory-based expectations, the surprising results showed that successful project groups exhibited low levels of closure and that the levels of bridging and leader centrality were not important factors of success. These findings suggest that the creation and use of open source software may represent a fundamentally new socio-technical development process which disrupts the team paradigm and which triggers the need for building new theories of collaborative development. These new theories could point towards the broader application of open source methods for the creation of knowledge-based products other than software.

This master's thesis focuses on the issues of selecting the Business Intelligence tools distributed under open source licenses. The main objective of this work is to compare the different instruments in all layers of the Business Intelligence architecture. The first part is focused on the definition of key concepts of the main topic. Provides necessary theoretical basis for understanding the context used in the practical part, which is dedicated to comparison tools realized according to the established methodology. These tools are selected and compared with predetermined criteria. Then each tool is introduced and verbally and numerically compared with others. At the conclusion of each comparison group of instruments referred to their final assessment and recommendations. This work is intended to provide the information base needed to select the proper tools to create a complete BI solution.

Esta dissertação tem por objetivo apresentar as licenças de software livre mais importantes, sob a luz dos seus principais aspectos jurídicos e da inter-compatibilidade, de forma a auxiliar pessoas envolvidas no desenvolvimento de software a compreender as implicações destas licenças ao fazer uso delas em seus projetos. A dissertação contextualiza as licenças, tanto no tocante à legislação brasileira, quanto no que diz respeito às restrições de licenciamento, de forma a viabilizar a análise de compatibilidade que se segue. Casos de projetos proeminentes de software livre cujo desenvolvimento foi afetado pelas implicações mencionadas ilustram a investigação, que é complementada por uma análise de ferramentas e metodologias existentes que auxiliam na gestão dos aspectos de licenciamento. / The purpose of this Master thesis is to present the most common free software licenses, regarding their main legal and inter-compatibility aspects, to help people involved in software development understand the implications of these licenses when using them in their projects. It contextualizes the licenses, both in terms of the Brazilian legislation, and regarding licensing restrictions, to make the subsequent compatibility analysis possible. Cases of free and open source software in which development was affected by the mentioned implications illustrate the research, and it is complemented by an analysis of existing tools and methodologies that assist in the management of licensing issues.

Der Vortrag wurde zum UNIX-Stammtsich am 25.5.2010 gehalten.