Software Source Code Plagiarism and Direction Detection Based on PDG

2013 ◽  
Vol 373-375 ◽  
pp. 1172-1177
Author(s):  
Bo Shu ◽  
Xiao Jun Du
Keyword(s):  
Software Development ◽  
Open Source ◽  
Open Source Software ◽  
Process Design ◽  
Source Code ◽  
Detection Algorithm ◽  
Plagiarism Detection ◽  
Software Developers ◽  
Development Cycle ◽  
Direction Detection

Because of the complexity of the software development, some software developers may plagiarize source code that comes from other projects or open source software in order to shorten development cycle. Usually the copyist would modify and disguise the source code copied to escape plagiarism detection. So far, most algorithms cant completely detect the source disguised by the copyist, especially cant exactly distinguish between the source code and the plagiaristic code. In this paper, we summarize and analyze the effect of disguised source to the detection process, design the strategy to remove the effect of disguised source, and propose a PDG-based software source code plagiarism detection algorithm. The algorithm can detect the existence of disguised source, so as to find out source code plagiarism. And we propose a heuristic rule to make the detection algorithm have the ability to give the plagiarism direction. Any existing algorithm does not have this function. We prove the availability of the algorithm by experiment.

Key Concepts and Definitions of Open Source Communities

2010 ◽  
pp. 753-760
Author(s):  
Ruben van Wendel de Joode ◽  
Sebastian Spaeth
Keyword(s):  
Software Development ◽  
Open Source ◽  
Open Source Software ◽  
Online Communities ◽  
Source Code ◽  
Professional Organizations ◽  
Large Numbers ◽  
Key Concepts ◽  
Open Source Communities ◽  
Do So

Most open source software is developed in online communities. These communities are typically referred to as “open source software communities” or “OSS communities.” In OSS communities, the source code, which is the human-readable part of software, is treated as something that is open and that should be downloadable and modifiable to anyone who wishes to do so. The availability of the source code has enabled a practice of decentralized software development in which large numbers of people contribute time and effort. Communities like Linux and Apache, for instance, have been able to connect thousands of individual programmers and professional organizations (although most project communities remain relatively small). These people and organizations are not confined to certain geographical places; on the contrary, they come from literally all continents and they interact and collaborate virtually.

scholarly journals Use of Free and Open-Source Software (FOSS) in the U.S. Department of Defense

2003 ◽  
Vol 2003 (01) ◽  
pp. 0102
Author(s):  
Terry Bollinger
Keyword(s):  
Software Development ◽  
Open Source ◽  
Open Source Software ◽  
Department Of Defense ◽  
Low Cost ◽  
Source Code ◽  
Leading Edge ◽  
Cyber Attacks ◽  
Software Analysis ◽  
The U.S

This report documents the results of a study by The MITRE Corporation on the use of free and open-source software (FOSS) in the U.S. Department of Defense (DoD). FOSS gives users the right to run, copy, distribute, study, change, and improve it as they see fit, without asking permission or making fiscal payments to any external group or person. The study showed that FOSS provides substantial benefits to DoD security, infrastructure support, software development, and research. Given the openness of its source code, the finding that FOSS profoundly benefits security was both counterintuitive and instructive. Banning FOSS in DoD would remove access to exceptionally well-verified infrastructure components such as OpenBSD and robust network and software analysis tools needed to detect and respond to cyber-attacks. Finally, losing the hands-on source code accessibility of FOSS source code would reduce DoD’s ability to respond rapidly to cyberattacks. In short, banning FOSS would have immediate, broad, and strongly negative impacts on the DoD’s ability to defend the U.S. against cyberattacks. For infrastructure support, the deep historical ties between FOSS and the emergence of the Internet mean that removing FOSS applications would strongly negatively impact the DoD’s ability to support web and Internet-based applications. Software development would be hit especially hard due to many leading-edge and broadly used tools being FOSS. Finally, the loss of access to low-cost data processing tools and the inability to share results in the more potent form of executable FOSS software would seriously and negatively impact nearly all forms of scientific and data-driven research.

scholarly journals USABILITY IN OPEN SOURCE SOFTWARE DEVELOPMENT: OPINIONS AND PRACTICE

2006 ◽  
Vol 35 (3) ◽  
Author(s):  
Morten Sieker Andreasen ◽  
Henrik Villemann Nielsen ◽  
Simon Ormholt Schrøder ◽  
Jan Stage
Keyword(s):  
Empirical Study ◽  
Software Development ◽  
Open Source ◽  
Open Source Software ◽  
Common Sense ◽  
Questionnaire Survey ◽  
Usability Evaluation ◽  
Software Developers ◽  
Commercial Software ◽  
Proprietary Software

Open Source Software (OSS) development has gained significant importance in the production of soft-ware products. Open Source Software developers have produced systems with a functionality that is competitive with similar proprietary software developed by commercial software organizations. Yet OSS is usually designed for and by power-users, and OSS products have been criticized for having little or no emphasis on usability. We have conducted an empirical study of the developers’ opinions about usability and the way usability engineering is practiced in a variety of OSS projects. The study included a questionnaire survey and a series of interviews, where we interviewed OSS contributors with both technical and usability backgrounds. Overall we found that OSS developers are interested in usability, but in practice it is not top priority, and OSS projects rarely employs systematic usability evaluation. Most of the efforts are based on common sense. Most developers have a very limited understanding of usability, and there is a lack of resources and evaluation methods fitting into the OSS paradigm.

Motivation of Open Source Developers

2011 ◽  
pp. 233-249
Author(s):  
Mark R. Allyn ◽  
Ram B. Misra
Keyword(s):  
Open Source ◽  
Open Source Software ◽  
Organizational Design ◽  
Source Code ◽  
Software Developers ◽  
Open Source Code ◽  
And Performance ◽  
The Many ◽  
And Control ◽  
Work Done

The motivational drivers of open source software developers have been researched by various investigators since about 2000. This work shows that developers are motivated by different extrinsic and intrinsic drivers, among them community aspirations, reciprocity and fairness, creative impulses, and monetary and career ambitions. There has been some work done in studying whether the profile of developer motivations is constant across open source projects or is sensitive to project organizational design. Among the many factors that could influence the mix of motives of OS developers is the license under which the work is performed. Licenses range in openness between those such as the GNU GPL that severely restrict the freedom of developers to mingle their OS code with proprietary code to those such as BSD licenses which allow programmers much greater latitude in integrating open source code with proprietary code. In addition to formal rules, meritocracies emerge to reward effort and performance, and also to direct, coordinate, and control other participants. The authors discuss these variables and how they may be related to motivations.

scholarly journals Evaluation indicators for open-source software: a review

Cybersecurity ◽  
2021 ◽  
Vol 4 (1) ◽  
Author(s):  
Yuhang Zhao ◽  
Ruigang Liang ◽  
Xiang Chen ◽  
Jing Zou
Keyword(s):  
Supply Chain ◽  
Comparative Analysis ◽  
Open Source ◽  
Open Source Software ◽  
Source Code ◽  
Comprehensive Understanding ◽  
Security Risks ◽  
Software Developers ◽  
Security Vulnerabilities ◽  
The Past

AbstractIn recent years, the widespread applications of open-source software (OSS) have brought great convenience for software developers. However, it is always facing unavoidable security risks, such as open-source code defects and security vulnerabilities. To find out the OSS risks in time, we carry out an empirical study to identify the indicators for evaluating the OSS. To achieve a comprehensive understanding of the OSS assessment, we collect 56 papers from prestigious academic venues (such as IEEE Xplore, ACM Digital Library, DBLP, and Google Scholar) in the past 21 years. During the process of the investigation, we first identify the main concerns for selecting OSS and distill five types of commonly used indicators to assess OSS. We then conduct a comparative analysis to discuss how these indicators are used in each surveyed study and their differences. Moreover, we further undertake a correlation analysis between these indicators and uncover 13 confirmed conclusions and four cases with controversy occurring in these studies. Finally, we discuss several possible applications of these conclusions, which are insightful for the research on OSS and software supply chain.

scholarly journals The relevance of Open Source to hydroinformatics

2002 ◽  
Vol 4 (4) ◽  
pp. 219-234 ◽  
Author(s):  
Hamish Harvey ◽  
Dawei Han
Keyword(s):  
Operating System ◽  
Software Development ◽  
Open Source ◽  
Open Source Software ◽  
Rapid Development ◽  
Source Code ◽  
Web Server ◽  
High Profile ◽  
History Of ◽  
Closed Approach

Open Source, in which the source code to software is freely shared and improved upon, has recently risen to prominence as an alternative to the more usual closed approach to software development. A number of high profile projects, such as the Linux operating system kernel and the Apache web server, have demonstrated that Open Source can be technically effective, and companies such as Cygnus Solutions (now owned by Red Hat) and Zope Corporation have demonstrated that it is possible to build successful companies around open source software. Open Source could have significant benefits for hydroinformatics, encouraging widespread interoperability and rapid development. In this paper we present a brief history of Open Source, a summary of some reasons for its effectiveness, and we explore how and why Open Source is of particular interest in the field of hydroinformatics. We argue that for technical, scientific and business reasons, Open Source has a lot to offer.

To Fork or Not to Fork

2011 ◽  
Vol 3 (3) ◽  
pp. 1-9 ◽  
Author(s):  
Linus Nyman ◽  
Tommi Mikkonen
Keyword(s):  
Open Source ◽  
Open Source Software ◽  
Software Package ◽  
Source Code ◽  
Original Version ◽  
Development Work ◽  
Software Developers

A project fork occurs when software developers take a copy of source code from one software package and use it to begin an independent development work that is maintained separately. Although forking in open source software does not require the permission of the original authors, the new version competes for the attention of the same developers that have worked on the original version. The motivations developers have for performing forks are many, but in general they have received little attention. The authors present the results of a study of forks performed in SourceForge (http://sourceforge.net/) and list the developers’ motivations for their actions.

To Fork or Not to Fork

2013 ◽  
pp. 142-150 ◽  
Author(s):  
Linus Nyman ◽  
Tommi Mikkonen
Keyword(s):  
Open Source ◽  
Open Source Software ◽  
Software Package ◽  
Source Code ◽  
Original Version ◽  
Development Work ◽  
Software Developers

A project fork occurs when software developers take a copy of source code from one software package and use it to begin an independent development work that is maintained separately. Although forking in open source software does not require the permission of the original authors, the new version competes for the attention of the same developers that have worked on the original version. The motivations developers have for performing forks are many, but in general they have received little attention. The authors present the results of a study of forks performed in SourceForge (http://sourceforge.net/) and list the developers’ motivations for their actions.

THE TECHNOLOGY OF DETECTION INFORMATION ABOUT VULNERABILITY IN THIRD-PARTY OPEN SOURCE SOFTWARE

2020 ◽  
pp. 347-364
Author(s):  
Алексей Леонидович Сердечный ◽  
Игорь Васильевич Герасимов ◽  
Олег Юрьевич Макаров ◽  
Юрий Геннадьевич Пастернак ◽  
Николай Михайлович Тихомиров ◽  
...  
Keyword(s):  
Risk Assessment ◽  
Open Source ◽  
Open Source Software ◽  
Rapid Detection ◽  
Source Code ◽  
Third Party ◽  
Version Control ◽  
Software Developers ◽  
Open Source Code

В статье приведены результаты разработки технологии выявления сведений об уязвимостях сторонних компонентов программного обеспечения (ПО), позволяющей своевременно обнаруживать проблемы безопасности, связанные с использованием заимствованных компонентов с открытым исходным кодом. Технология отличается процедурами оперативного обнаружения, ранжирования и подтверждения достоверности первоисточников сообщений о таких проблемах. Разработанная технология основана на проведении сбора и семантического анализа сведений об ошибках и средствах (алгоритмах) эксплуатации уязвимостей ПО, содержащихся в сообщениях, публикуемых на информационных ресурсах разработчиков ПО с открытым исходным кодом. Технология включает процедуру подтверждения сведений о наиболее опасных уязвимостях с последующей оценкой рисков для подтверждённых уязвимостей. В статье также приводятся результаты реализации предлагаемой технологии в виде средства сбора и интерактивного анализа сообщений о ошибках в ПО с открытым исходным кодом, размещаемым на платформах для совместной разработки GitHub и GitLab. Технология выявления сведений об уязвимостях сторонних компонентов позволяет повысить защищённость ПО, использующего в своём составе общедоступные компоненты с открытым исходным кодом. The article presents the results of the development the technology of detection information about vulnerability in third-party open source software, which allows timely detection of security problems associated with the use of borrowed components provided with open source code. The technology is characterized by procedures for rapid detection, ranking, and confirmation of the authenticity sources of primary reports about such problems. The technology is based on collecting and mining information about bugs, vulnerabilities and exploits contained in messages that published in sources of open source software developers. The technology includes a procedure for confirming information about the most dangerous vulnerabilities, followed by a risk assessment for confirmed vulnerabilities. The article also presents the results of implementing the proposed technology as a tool for collecting and interactively analyzing bug messages in open source software hosted on the GitHub and GitLab collaborative version control platforms. The technology for detecting information about vulnerabilities of third-party components allows you to increase the security of software that uses publicly available open source components.

Motivation of Open Source Developers

2009 ◽  
Vol 1 (4) ◽  
pp. 65-81 ◽  
Author(s):  
Mark R. Allyn ◽  
Ram B. Misra
Keyword(s):  
Open Source ◽  
Open Source Software ◽  
Organizational Design ◽  
Source Code ◽  
Software Developers ◽  
Open Source Code ◽  
And Performance ◽  
The Many ◽  
And Control ◽  
Work Done

The motivational drivers of open source software developers have been researched by various investigators since about 2000. This work shows that developers are motivated by different extrinsic and intrinsic drivers, among them community aspirations, reciprocity and fairness, creative impulses, and monetary and career ambitions. There has been some work done in studying whether the profile of developer motivations is constant across open source projects or is sensitive to project organizational design. Among the many factors that could influence the mix of motives of OS developers is the license under which the work is performed. Licenses range in openness between those such as the GNU GPL that severely restrict the freedom of developers to mingle their OS code with proprietary code to those such as BSD licenses which allow programmers much greater latitude in integrating open source code with proprietary code. In addition to formal rules, meritocracies emerge to reward effort and performance, and also to direct, coordinate, and control other participants. The authors discuss these variables and how they may be related to motivations.

Sign in / Sign up

Export Citation Format

Share Document