Thesis (Ed. D.)--Teachers College, Columbia University, 1987. / Typescript; issued also on microfilm. Sponsor: Lenore Pogonowski. Dissertation Committee: Robert Pace. Bibliography: leaves 184-188.

No description available.

While Role Based Access Control (RBAC) has been a popular topic of research over the last several years, there are some gaps in the literature that have been waiting to be addressed. One of these gaps involves the application of RBAC to free and open source software (FOSS). With the prevalence of FOSS in most information systems growing rapidly, there is a need to be able to provide a level of confidence that the software will not compromise the data integrity of an environment, nor will it enable the violation of established access controls. Additionally, when utilizing FOSS software it is desirable to do so without having to modify its source code whenever an update is released in order to maintain a secure environment; this makes adding proprietary modules both time consuming and expensive. The challenges involved in maintaining proprietary changes to FOSS generates a particular interest in an RBAC environment that could be deployed without requiring modification to the source code. Developing this type of a framework presented a significant challenge due to the software having been established prior to the definition of any security requirements that would have to be applied by the proposed framework. What this research paper shows are the results of the development of a software framework that allowed security requirements engineering to seamlessly meld with an application after it had already been developed. This framework provided a mechanism to measurably reduce the attack surface of the application against which the framework was implemented, while performing these tasks without requiring alterations to the source code of the application. Additionally, this research introduced a mechanism that was utilized to measure the effectiveness of the framework. This mechanism provided a means of comparing the relative effectiveness of different frameworks against the same software, as well as the effectiveness of a framework against different pieces of software.

Thesis (D.M.A.)--Univeristy of Oklahoma, 1997. / Includes bibliographical references.

We aim to determine the features of four popular FOSS scanning tools, FOSSology,FOSSA, FOSSID(SCAS), and Black Duck, thereby providing references for users tochoose a proper tool for performing open-source license compliance in their projects.The sanity tests firstly verify the license detection function by using the above tools toscan the same project. We consider the number of found licenses and scanned sizes asmetrics of their accuracy. Then we generate testing samples in different programminglanguages and sizes for further comparing the scanning efficiency. The experiment datademonstrate that each tool would fit different user requirements. Thus this project couldbe considered as a definitive user guide.

Free and Open Source Software (FOSS) licences channel the exclusionary and individualising force of copyright to establish a qualitatively different, somewhat subversive, system for the exploitation of software. This thesis examines how it is that FOSS licences establish this 'system within a system' under both German and United States law. The inquiry begins with a detailed examination of FOSS licence templates as the instruments which transform code from its default position as the 'res' of proprietary relations to its status as 'open' or 'free'. The thesis then considers whether FOSS licence templates, as the legal basis for this subversive move, are valid and enforceable under domestic law. In addressing this question, the thesis undertakes a critical analysis of the leading case law in each jurisdiction. Going beyond the immediate case law, the thesis considers the broader systemic effects of FOSS licence enforcement. It highlights how building a system within a system foments certain tensions and contradictions within the law, in turn giving rise to unintended consequences and legal uncertainty. By highlighting these tensions, the thesis argues that the questions of FOSS licence enforcement in Germany and the United States may not be as settled as some may think.

Submitted by Renata Lopes (renatasil82@gmail.com) on 2017-06-22T18:25:08Z No. of bitstreams: 1 accacioferreiradossantosneto.pdf: 2827890 bytes, checksum: 63ffac13e0cef4ee756375e990b7ba3d (MD5) / Approved for entry into archive by Adriana Oliveira (adriana.oliveira@ufjf.edu.br) on 2017-08-07T19:24:53Z (GMT) No. of bitstreams: 1 accacioferreiradossantosneto.pdf: 2827890 bytes, checksum: 63ffac13e0cef4ee756375e990b7ba3d (MD5) / Made available in DSpace on 2017-08-07T19:24:54Z (GMT). No. of bitstreams: 1 accacioferreiradossantosneto.pdf: 2827890 bytes, checksum: 63ffac13e0cef4ee756375e990b7ba3d (MD5) Previous issue date: 2013-05-10 / CAPES - Coordenação de Aperfeiçoamento de Pessoal de Nível Superior / Face aos desafios atuais dos sistemas industriais, que necessitam operar de forma econômica, eficiente e sustentável, novos procedimentos e estratégias para o controle destes processos estão sempre em busca de inovações. Esta situação motivou e direcionou o objetivo do presente trabalho que foi utilizar ferramentas abertas, inovadoras, de utilização atual na indústria, para desenvolver um módulo laboratorial, com características multivariáveis, emulando a ambiência industrial, no que tange às dinâmicas das malhas selecionadas. Foram utilizados o protocolo de comunicação digital "OLE for Process Control - OPC" e software "Free and Open Source Software - FOSS" Scilab, ambas ferramentas de código aberto. O protocolo OPC é específico para ambientes industriais, agregando qualidades que propiciam o gerenciamento e controle de um sistema em tempo real com eficiência e qualidade. E o software Scilab, uma ferramenta FOSS que, dentre suas diversas funcionalidades, permite o desenvolvimento e a comunicação de um supervisório para um sistema físico, interagindo através do protocolo de comunicação OPC. Para o alcance da proposta foi desenvolvido um módulo laboratorial multivariável para controle de processos, que permitiu a modelagem e o controle de um sistema composto por malhas de nível e temperatura, comuns no meio industrial. Foi ainda desenvolvido um ambiente supervisório amigável que contempla técnicas diferenciadas de controle para o controlador "Proportional Integral Derivative - PID", além de análise e controle de dinâmicas monovariáveis e multivariáveis do sistema. / In face of the challenges of the current industrial systems, which needs to operate in an economic, efficient and sustainable forms, new procedures and strategies for control these processes are always in search of innovation. This situation motivated and directed the aim of this work that was to use open tools, innovative, current use in industry, to develop a laboratory module, with characteristics multivariable, emulating the industrial ambience, with respect to the dynamics of the selected loops. We used the digital communication protocol " OLE for Process Control - OPC software" and " Free and Open Source Software - FOSS" Scilab, both open source tools. The OPC protocol is specific to industrial environments, adding qualities that enable the management and control of a real-time system with efficiency and quality. And the Scilab software, FOSS tool that, among its many features, allows the development and communication of a supervisory for a physical system, interacting throught the OPC communication protocol. For the scope of the proposal we developed a laboratory module for multivariable process control, allowing the modeling and control of a system composed of meshes of level and temperature, common in industry. It was also developed an environment friendly supervisory techniques which includes different control for the "Proportional Integral Derivative - PID" controller, as well as analysis and control of dynamic SISO and multivariable of the system.

Visualization of digital geographic data is often accomplished through custom symbology that is saved in a proprietary format called a layer file (.lyr). The sharing of free geographical information system (GIS) data can be limited as the symbology data is bound inthe .lyr file format. This makes it harder and more tedious to work with open software tools since it is not possible to convert or open the .lyr file in free and open GIS software and thus limits the distribution of free GIS data. The aim of this thesis is to increase the interoperability of .lyr data between proprietary and free and open GIS software. This was done by revers eengineering the .lyr file format to document the file structure and to distribute the knowledge and metadata gained from this project to the open source community. Reverse engineering the.lyr format provided a well needed metadata and documentation about the format which increases the interoperability and enable future work to continue to lessen the gap between open source and commercial software. This groundwork can therefore, enable a continued development of data interoperability between proprietary and free and open GIS software.

Na década de 90, os Sistemas ERP (Enterprise Resource Planning) alcançaram larga utilização, principalmente em empresas de grande porte, devido ao seu elevado custo. Em contrapartida, o interesse por sistemas livres data dos primeiros softwares desenvolvidos para computadores na década de 60 e 70 até os dias atuais com sistemas empresariais como os sistemas ERP. O problema desta pesquisa encontra-se em como adotar, selecionar e implementar um ERP livre. Assim, o objetivo deste trabalho é compreender e avaliar o processo de adoção, seleção e implementação de ERP livre. Para esta finalidade, o trabalho é dividido em duas partes: a parte inicial, baseada na pesquisa bibliográfica, apresenta como 3 capítulos iniciais a Introdução, Fundamentação Teórica e Metodologia. A parte final que apresenta a contribuição desta pesquisa, composta dos capítulos Modelo Inicial, Trabalho de Campo, Modelo Final e Conclusão. As contribuições do trabalho iniciam-se com a proposição pelo autor de um modelo inicial de ciclo de vida de ERP abrangendo estes processos considerando não haver distinções entre o modelo para um ERP proprietário ou livre. Refina-se este modelo inicial através da aplicação do método de pesquisa-ação em um trabalho de campo com a implantação de um ERP livre em uma organização brasileira. Como resultado deste trabalho obteve-se um modelo final de ciclo de vida de ERP independente do mesmo ser desenvolvido na forma de software livre ou proprietário. Identificaram-se também as diferenças nos processos de adoção, seleção e implementação entre ERP proprietário e livre. Encontraram-se conclusões que suportam as empresas a considerar ou não a inclusão do ERP livre nos processos de adoção, seleção e implementação. / In the 90s, the ERP systems (Enterprise Resource Planning) have achieved wide use, especially in large-sized companies because of its high cost. By contrast, interest in free systems date of the first software designed for computers in the 60s and 70s until the present day with enterprise systems such as ERP systems. The problem of this research is on how to adopt, select and implement an ERP free. The objective of this work is to understand and evaluate the process of adoption, selection and implementation of ERP free. To this, work has two parts: the initial part, based on bibliographic research has 3 chapters: initial introduction, theoretical fundaments and methodology. The final part shows the contribution of this research composed of chapters: Initial Model, Work of Field and Final Model. Finally, present the conclusion. The contributions of work begin with the proposition by the author of an original model of the life cycle of ERP covering these processes considering no distinctions between the proprietary and free ERP. Initial model was refined using the method of action research with the adoption, selection and implementation of a free ERP in a Brazilian company. As result of this study, published a final model of the life cycle of ERP independent of development form (free or proprietary). Was identified also the differences between free and proprietary ERP in adoption, selection and implementation process. We found conclusions that support companies to consider whether or not the inclusion of ERP free in cases of adoption, selection and implementation.

Free/Open Source Software (FOSS) communities often use open bug reporting to allow users to participate by reporting bugs. This practice can lead to more duplicate reports, as inexperienced users can be less rigorous about researching existing bug reports. The purpose of this research is to determine the extent of this problem, and how FOSS projects deal with duplicate bug reports. We examined 12 FOSS projects: 4 small, 4 medium and 4 large, where size was determined by number of code contributors. First, we found that contrary to what has been reported from studies of individual large projects like Mozilla and Eclipse, duplicate bug reports are a problem for FOSS projects, especially medium-sized projects. These medium sized projects struggle with a large number of submissions and duplicates without the resources large projects use for dealing with these. Second, we found that the focus of a project does not affect the number of duplicate bug reports. Our findings point to a need for additional scaffolding and training for bug reporters of all types. Finally, we examine the impact that automatic crash reporting has on these bug repositories. These systems are quickly gaining in popularity and aim to help end-users submit vital bug information to the developers. These tools generate stack traces and memory dumps from software crashes and package these up so end-users can submit them to the project with a single mouse-click. We examined Mozilla's automatic crash reporting systems, Breakpad and Socorro, to determine how these integrate with the open bug reporting process, and whether they add to the confusion of duplicate bug reports. We found that though initial adoption exhibited teething troubles, these systems add significant value and knowledge, though the signal to noise ratio is high and the number of bugs identified per thousand reports is low. / Graduation date: 2012