Menu
I'm currently working on my Bachelors dissertation. This involves developing a software product and a 12000 word write-up, mainly covering research, design and development. Now where I am quoting other peoples written work, I am obviously referencing this, but what about code? There have been plenty of times where I've looked for a solution to a problem I was unsure of and found someone who had solved the problem. Most of the time I took their code, worked to understand what they were doing, and then wrote my own version in my application, so should it be referenced somehow?
What would you guys do, put a comment in the code referencing the original author, add a reference in the write up or my bibliography, or nothing at all? Where its a significant or interesting piece of code used, I will probably refer to it in my write-up, but for solutions that don't warrant this, I’m trying to come up with a good solution.
If you were the author of some code I had either used, or been inspired by, what would make you happy that I wasn't plagiarizing you?
To take this a bit further, there's really 2 different things here. If I go to MSDN to lookup how to use a particular part of the .net framework, is that something that should be referenced, or is it fair use of the framework. Where as if I've used an algorithm that someone clearly developed and put a lot of time into, that's something I would definitely reference.
349
The best way I’ve ever discovered to read and understand someone else’s code is to: 1. Find one thing you know the code does, and trace those actions backward, starting at the end. Say, for example, you know that the code you’re viewing ultimately creates a file with a list of movie titles.
It is not always clear how to correctly reference programs and source code. The information on this page explains how to cite programs and source code correctly within reports and in the source code itself.
A good example of this is a "hello world" program such as the following (in Java): If you are unsure about whether a section of code that you are using needs to be cited then you should ask your professor.
There may by additional information depending on the citation style, for example the issue number for citing journal articles, URLs, ISBN/ISSN. But these additional pieces of information, the formatting and even the ordering of the information in the reference generally depend on publication venue, as Suresh wrote in his answer.
It all depends on context. Many algorithms are so well known that they are generally considered public domain and as long as you reference a well known source on the subject then you shouldn't have any worries (Sorting, Searching)
When dealing with specific problems, especially in other people code, you have to read really carefully. If its published (book, journal, web, etc..) then you must always reference the original, at some point in your dissertation (technically once in then write up and then a comment in the source)
If it's other peoples work they deserve proper credit. Anything else is plagiarism
131
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With
