Project Possible Cheats
Kenneth
I overheard a student who said that they would use a project done in another course that semester as the final project in an entirely different course. (Let's call the original course Course 0 and the second course Course 2.)
I know it's bad practice to submit work to a class which had been submitted in previous semesters, but I've never heard of anyone turning in the same work to two different classes concurrently before. (Perhaps because opportunities to do so are rare?)
For the record: the project involves coding in a certain software (not for the sake of coding, it's just a means to an end), I do not know the name of the student who expressed their intent to do this, but I do know the professors of both courses. I'll edit this section with more pertinent information should anyone want it.
But there is an easy way out. Just ask both of them for permission to do this. They might say yes, or no, but then you have a clear answer. They might also give permission provided that you go a bit beyond the bare essentials to demonstrate sufficient work (and seriousness) to cover both.
And, you can even come off looking good on this if you actually make an offer to do more than the minimum and submit the result to both. It might mean a bit less work for you overall, and might also teach you some things you wouldn't otherwise have learned. Even for a previously submitted project, offering to extend the old work can be a plus.
And, I actually did this in secondary school because I changed schools. I asked an instructor at the new place if I could submit a report that I'd previously worked on, but wasn't actually graded for (since I left). I was given permission and it saved me a bit of work.
This was actually encouraged in the university I attended. The lecturers were of the opinion that the goal is to learn, not to make projects. If one project can teach you the skills required for two courses, why do two projects?
An example of a project I used for multiple courses was a bit of software I developed as a volunteer activity. I used this for the course in which we had to learn to gather requirements, in the course in which we learned how to develop complex software and in the course that worked on the soft skill of communicating with a client.
F. Multiple submission - submitting the same paper or oral report for credit in two University courses without the instructor's permission; making minor revisions in a paper or report for which credit has already been received and submitting it again as a new piece of work.
Every University I've worked at has had similar policy wording, and I can't think of any others where I've reviewed related sections of their policies where similar wording wasn't present, but I certainly haven't done an exhaustive search on this specifically.
The key provision here, of course, is "without the instructor's permission". If it has been discussed and approved, it is likely fine at most institutions (check the specific policies and procedures for your University or College, do not assume on this). It becomes academic dishonesty when it is not approved.
Work that is submitted for a course is expected to have been done for that course, not simply the student taking other work previously (or even concurrently) done and submitting it, even if they were in fact the one who did the work. Failing to discuss submitting the same work to multiple courses is an act of academic dishonesty, in the ethical sense at the least, as the student is not meeting the expectations of their actions in regards to the coursework for each individual course.
Practically, if the work without major edit does indeed fulfill the requirements for two classes, I say go with it. After all, why would you not? Even if the institution had a rule against it, I might elect to fight, as there is no logical reason one should arbitrarily do two separate works if one truly satisfies all requirements. What would YOU the student, get out of such an exercise?
If you have one class which is asking for a project which does A and another which is asking for one which does B, and you come up with a project which does both A and B, then that's likely okay. However, if they're both asking for slightly different variants of A, then it's less likely that a single project which does just A will be accepted.
For example, say you're in a Computer Science class which asks you to write a non-trivial program using multithreading and in a Biology class which is asking you to do a project on DNA sequence alignment. I think that most professors will think it actually a bit clever and pedagogically useful for you to write a computer program which does DNA sequence alignment in a multithreaded fashion to satisfy both projects. Similarly, even if it's two CS classes it can work if the courses are different enough (e.g. a compiler course and a GUI course).
A large part of this is how much "reuse" between the different project requirements there is. For example, in the multithreaded DNA alignment case, the part of the project the CS professor is interested in (multithreading) is disjoint from the part the biology professor is (DNA alignment). You're not really being "double graded", as even though project is the same, the core part being graded is different. -- It's less that you have one single project that you're submitting twice, and more that you are fusing the two distinct projects into one cohesive whole.
The other aspect is the deliberateness of combining. The point of projects isn't make work, it's to provide a demonstration that you have learned and are able to apply the course materials. There's thus an implicit requirement that the project should reflect and incorporate the course materials. To do so effectively, you need to have the class materials in mind while doing the project. This is one reason why reusing projects from previous semesters is frowned upon - you couldn't have consciously incorporated materials from the course in a project made before you took the course. That also potentially applies to projects made in the same semester. Did you deliberately set out to fulfill that specific project's requirements (incorporating and keeping in mind the course materials), or did you just happen to notice after-the-fact that the project for course 0 could be made to work for course 2?
That said, there can be a big difference in opinion between different professors. You definitely don't want to attempt to "slip one by" them. You should be upfront about the fact that you're combining projects. In certain cases, an attempt to deceive (even via omission) can be more ethically dishonest than the project combining itself.
There's a key point in here the other answers are overlooking. You mention it's a portion of code. As a software engineer code re-use is imperative. Not doing so is like a slap in the face to the men and women that worked so hard over the last several decades to provide us these easy to use development environments, frameworks, and platforms. If these are for computer science or related courses, I would be shocked if the professors wouldn't accept it.
Sometime, not only that the professors know that we use the same project for two subjects, but they also RECOMMEND it! No ones sees this as a hack or cheating, but it is just efficient and powerful. It is more fun to use several concepts in the same project or software than splitting them in 123 boxes.
I can give my opinion from the side of guy who codes a lot in the field of data analysis: if somebody created software that can do some computations which are easily transformed for needs of two separate tasks or projects, it is actually fantastic.
You can of course do copypasting things from your own code to make another look or even be different, but I doubt it adds anything to your skill as programmer, like is honest just being inspired by your code and do it very similar mor another course? ofc yes.
If in the university there are some very specific rules about it, then it is not great but on contrary one of the main aspect of programming is trying to stick to one style and one set of tricks(untill they are good) as much as possible and reusability of code is highly appretiated in software development in general.
In general if you have good reusable code and in the university there are indeed some strict rules about submitting same project I would recommend you just to use different datasets for your analysis, I bet where you found your dataset there are lots of others, so just make same approach to different data and it will never be your fault, but your achievement.
Since you wrote the software, you didn't copy it from anywhere, and (assuming) you aren't going to post your code in a publicly viewable location, the project would be perfectly acceptable as long as it fulfills all the stated requirements, for any number of assignments.
*The logic goes: you are welcome to post your project anywhere you want. But if someone else can see it and copy it, you'll be given a 0. If you want your project to be graded, make sure no one else can also submit it.
At any university I am familiar with, submitting a project in a class that you have submitted in another class without permission and without citation is considered self-plagiarism and, if discovered, will subject you to academic discipline. Check your student handbook. It's in there somewhere.
Submit the same work, or essentially the same work, for more than one course without explicitly obtaining permission from all instructors. A student must disclose when a paper or project builds on work completed earlier in his/her academic career.
I have been playing RedAlert on the CnC portal for years now, and learning strategies for fast build speeds as well as understanding the relative strengths and weaknesses of all units and buildings. I would consider myself to have improvede to a level of 'good average' but I am still beaten by excellent players.
4a15465005