This thesis investigates the following research questions: (1) What is open source project governance and how can it be conceptualized? (2) What is the relationship between the dimensions of OSS governance and the specific purposes that governance is hypothesized to serve in open source projects? (3) How do the major configurations of governance dimensions affect the performance of open source projects? Two studies were conducted to answer these questions: an exploratory qualitative study and a survey study. In the qualitative study, we clearly defined, developed, and validated the various dimensions of OSS governance. This allowed for the identification of a limited number of configurations of governance dimensions that most frequently occur in open source projects. We found that a patterning in governance dimensions takes place because dimensions are in fact interdependent. Therefore, only a fraction of the theoretically conceivable configurations of governance dimensions appear to be viable and were observed among a range of open source projects. This provided us with a preliminary understanding of how these dimensions configure to create three distinct configurations of project governance which were labeled as follows: Open Communities, Managed Communities, and Defined Communities. In the quantitative survey, we first validated these configurations of governance using cluster analysis and then tested the relationships between these configurations (clusters) and the specific purposes that governance is hypothesized to serve in open source projects, namely solve collective action dilemmas, solve coordination problems, and create a climate for project excellence, while assessing their influence on the performance of projects. The results confirmed the presence of three main governance configurations (clusters) and also showed that open source projects that adopt a Defined Community approach to governance were the most successful. In these types of projects, the combination of a tightly managed software development process with a decentralized community management structure was found to create a balance between anarchy and control that allows these projects to benefit from one of the virtues of open source development, the open contribution and participation of a wide variety of talented developers, while avoiding the pitfalls of an uncontrolled and scattered development process. / Thesis (Ph.D, Management) -- Queen's University, 2012-04-11 16:00:02.186

No description available.

No description available.

This is a study of the design and development of an Organisational Software Package (OSP). It particularly focuses on the ambitions and supplier strategy of building a ‘generic software solution’ (i.e., a software system that in principle can be used by everyone). The study is located in the distinctive context provided by China, with its particular history and in a period of rapid economic reform. The starting point of this research is the apparent empirical and theoretical gap in the social study of Organisational Software Packages, in which the construction of standard solutions and the supply side of the technology's story have been largely overlooked. Moving beyond conventional information system design perspectives, this thesis draws upon concepts developed within the Social Shaping of Technology (SST) perspective, adopting an interdisciplinary approach to analyse the creation and evolution of OSPs, which enables us to address both the dynamism and continuity of these developments. In order to avoid the shortcomings of snapshot studies, we applied the concepts of ‘social learning’ and in particular the ‘biography’ of software package to examine the evolution of the OSP supply as the supplier developed its product and market strategy over a number of product cycles. Lastly, we applied Rip’s (Rip and Kemp 1998) technological transitional model to explore the influence of both the broad socio-economic context and institutional arrangements on the OSPs' development, as well as the contribution of these and related changes to changing the setting of technology. Methodologically, an extremely detailed longitudinal and contextual analysis has been undertaken through a qualitative historical case study of the evolution of a Chinese software package from 1998- 2005 in the context of China, triangulating different methods: interviewing, document analysis and participant observation. The empirical findings of this study firstly show that achieving the ‘generic’ is not an impossible goal but is rather an evolutionary process which is filled with struggles and tensions. OSP suppliers are forced to maintain a strategic balance between a range of contextual factors with technical, financial and social dimensions. Secondly, and perhaps the key contribution of this study, is the complex multi-locus and multi-layered account it offers of the OSP innovation process, according to which the supplier learns about the representation of users and use in both ‘local’ and ‘community design’ spaces with different approaches and foci through interaction with user organisations and other social players. The findings show that OSP suppliers are required to readjust their relationships with user organisations and establish cycles that move between seeking to achieve the economic imperative through standardisation and seeking to accommodate local user requirements. Thirdly, while this empirical study confirms some observations that have been made about packaged OSP production in western countries, it also reveals some specifically Chinese characters. These particular features of the development process which were identified in the Chinese PDM development were framed (using the terminology of Rip’s transitional model) by the unstable landscape and socio-technical regimes. Finally, this case study also throws light on the applicability of SST in developing countries and on the policy and practice of China’s future technology development.

The purpose of this project was to develop, using Object Oriented Development (OOD), a software tool identified as the Ada Module Description Tool (AMDT). The AMDT provides an automated way to get a module level description of Ada code. A module level description will identify packages, subprograms, objects and type declarations and relationships. This software tool also has the ability to compare Ada source code with a module level description. The comparison shall identify any object, type, subprogram, or package declared in the module level description that does not match the provided source code.The AMDT is made up of two executable programs that run on a VAX/VMS system. The Module Description Generator (MDG) generates a module level description from a set of Ada source code files. The Module Description Checker (MDC) compares a module level description to the Ada source code. Ada is the required High Order Language for the Department Of Defense. The development methodology used was basically Object Oriented Development as described in the book Software Engineerinq With-AAA by Grady Booch and the Software Standards and Procedure Manual for Object Oriented Development (SSPM-M02.04 Draft).Booch's book is a description of Object Oriented Development methodology, while the SSPM is a set of instructions and standard format to implement the methodology. The total design of the AMDT is documented in five segments. The SSPM defines a segment as the code and documentation resulting from a pass through the OOD process. From a Software Quality Engineer's point of view the AMDT would save time in not having to check module descriptions by hand. From the Software Engineer's point of view, when the code is updated a new module description can be generated easily to keep the documentation current with the code. The AMDT tool as written does not find object declarations in the code. Fortunately the effect is minor because the module descriptions needs to be edited anyway. The module description generated by the MDG may have too much information in it. The designer wants only the types, objects, and operations that aid in the understandability of the design and how it is implemented. The only checks the MDC makes are to see if an identifier on the module description is in the code. It does not check to see if there are extra items in the code that should be required in the module description. / Department of Computer Science

Software engineers currently rely on lengthy source code reviews, testing, and static analysis tools to attempt identification of software vulnerabilities. While these are sometimes effective, the methods used are limited and don't catch all security vulnerabilities.Work has been done in identifying areas of software prone to failure through a design metrics approach, and with success. This study aims to extend this idea to software security. The premise of this thesis is that the set of security vulnerabilities overlaps (or may be a subset of) the overall set of software bugs and failures. It is postulated that a good, reliable design should also be a secure design. This thesis identifies design issues which may lead to security vulnerabilities and proposes possible design metric enhancements to capture these design properties. / Department of Computer Science

The development of a software package is a complex and time consuming process. Computer Assisted Software Engineering (CASE) tools, such as Excelerator, DesignAid and SA Tools have offered an alternative to the traditional methods of system design. While the use of these design tools can lessen the burden of project management, there currently exists no systematic method for describing or evaluating existing products.This study identifies criteria for software development tools by examining three products used in a PC-based computing environment. The three software development tools studied are DesignAid version 4.0 by Nastec Corporation, SA Tools by Tekcase Corporation, and Excelerator version 1.7 by Index Technology Corporation. In order to give the "look and feel" of the products, the same design project is implemented on each of the tools. Then each product is evaluated with respect to a given set of criteria. / Department of Computer Science

Metrics calculated during the design phase of a software life-cycle can be used to predict the errors in the software project at an early stage, improve the overall software quality, and increase the efficiency of the software life-cycle.In this thesis, a design metric D(G) for the structure design G is presented. The need and importance of the design metric is shown, the metric is explained in detail, results are given and the solutions are presented to improve the design quality based on the results. A strategy is explained to implement the design metric into a company-wide program. The limitations of the metrics model are also given. A complete model of the software development life-cycle, incorporating the metrics is also presented. / Department of Computer Science

Information system development (ISD) projects have been associated with the "software crisis" for over three decades. A set of common "root causes" has often been cited in literature with corresponding "solutions". Yet the overall project success rate has remained low, resulting in a paradox of many solutions and little progress over the years. This study examines the management of application software acquisition from external suppliers in ISD projects. Three case studies are documented based on participant observation with complete membership roles. After within-case analyses highlighting issues in individual cases, crosscase analyses are conducted, first to identify a pattern of ISD project challenges and then to search for their explanations. Concepts from agency theory, contract theory and product development literature are used in the process of diagnosing root causes behind the observations. The proposed explanation is that the Traditional Systems Development Framework (TSDF), characterized by competitive-bidding-monopolized-development, underlies the identified root causes. Accordingly, competitive development is suggested as an alternative approach. Following the "Inference to the Best Explanation" (IBE) analytical strategy, the suggested approach is subject to two contrastive analyses, first with the prepackaged software development and then with the construction industry, to demonstrate that the suggestion is a "warranted inference". Further analogical analyses illustrate the feasibility of development competition for software product development. A Performance-Based Systems Development Framework (PBSDF) is outlined as a tentative implementation of the suggested competitive development approach for ISD projects supported by risk-sharing supplier contract and a relative product evaluation approach. A number of future research implications are described as a result of this study after summarizing the research contributions.

A bulk export orientated company has to optimise their packaging to be able to compete in a globalised world. Therefore it is important to maximise the container load to save shipping costs. This can be done in different ways, • by changing the product weight, • the packaging material or size, • the pallet/container size or, for some products, • the bulk density. With so many parameters affecting the container load finding the best packaging solution is difficult. To solve the problem an Add-on to for the existing packaging optimisation software Cape Pack called SADIE was developed. SADIE automates the process of data input into Cape Pack and allows browsing of different packaging combinations in a short time. Main feature of SADIE is that it allows testing complete weight and/or bulk density ranges in one Query. For that it takes the weight and the bulk density combination that is going to be tested and calculates the start dimension for a regular slotted case (RSC) with a 2:1:2 ratio, which, for a RSC, is the ratio that uses a minimum quantity of board. Those dimensions are then, with many other parameters, transferred into the Cape Pack Design mode where the new packaging solution is calculated and transferred back to SADIE. The data coming from SADIE was tested for consistency and was also used for physical pack size validations, both successfully. Packaging solutions for products with higher bulk densities could be optimised. A new packaging solution calculated for salted butter could save 231 container per annum. Depending on the destination of the butter cost savings from 184,000 US$ to 577,500 US$ would be possible. The results show that there are improvements in container load possible, especially for products in a higher bulk density range, like butter and cheese. An increase in container load for Whole milk powder (WMP) might be possible if another packaging system is used whereas for Skim milk powder (SMP), with its higher densities compared to WMP, the program can calculate improved container load without a change to the packaging system used.