Avoiding Plagiarism and Collusion in Academic Writing

Understanding Plagiarism and Collusion

The incorporation of material (including text, graph, diagrams, videos etc.) derived from the work (published or unpublished) of another, by unacknowledged quotation, paraphrased imitation or other device in any work submitted for progression towards or for the completion of an award, which in any way suggests that it is the student's own original work. Such work may include printed material in textbooks, journals and material accessible electronically for example from web pages.'
Whereas collusion includes:

“Unauthorised and unacknowledged copying or use of material prepared by another person for use in submitted work. This may be with or without their consent or agreement to the copying or use of their work.”

To help you avoid plagiarism and collusion, you are permitted to submit your work once to a separate drop box entitled “Draft report” to view both the matching score and look at what areas are affected. It is then down to you to make any changes needed.

Turnitin cannot say if something has been plagiarised or not. Instead it highlights matches between your text and other Turnitin content. There is no Good or Bad score , it depends on the piece of work If you find your text matching there may be a problem, see the examples below.

1) The reference section is highlighted. This may mean you have referenced correctly and this has been matched with other well referenced documents online.

2) A table containing class data is highlighted. This is acceptable as long as any text accompanying the table is not similar picked up as identical

3) Paragraphs of text in the introduction or conclusion sections are highlighted. This may mean they have been copied exactly from another source. Even if this source is referenced this is bad practice, see advice below

4) A sentence, or part of a sentence is highlighted. Sometimes there are few ways to write a sentence, especially straightforward ones. As long as this does not occur throughout a paragraph this may be acceptable. There will be occasions where a few words within a sentence produce a match. This is acceptable but ensure that this not a common occurrence or a patchwork of copied statements from different sources.

Overall when you look at the work, put yourself in the place of the marker. Is a lot of the work highlighted so it does not really look like the author’s work? If so, then you need to work on it some more the module in understanding BOTH object-oriented analysis and design (OOAD), and objectoriented programming (OOP) using C++.

How Turnitin Can Help

In this assignment task, you are required to produce a working program in C++, a design overview based on a reversed engineered class and sequence diagram, and a structured report describing the testing and evaluation of the program and its design. The  System Specification for the C++ program is given below in Section B ‘C++ Assessment Scenario/Problem’. The Design Specification is given below in Section C ‘DesignSpecification’. The Report Specification is given below in Section D ‘Report Specification’. A short summary is given below.

Each lab worksheet will have a starred question that needs to be submitted to the ‘Lab Worksheet Questions’ dropbox by the Monday following the lab and lecture sessions. All of these submissions can contribute up to 5% of the portfolio grade.

A system (to be developed as a program written in C++ and using the command line for output) is required that allows the user to create and edit a list containing a number of initially unordered Banking Transaction objects. The Banking Transaction objects represent various types of currency withdrawals by debit card, cashpoint machine, direct debit, and deposits by transfer, creditpoint machine and interest payment. The Banking Transaction objects will be entered by the user and stored in a linked list (consisting of a List class and a Link class, which must be adapted from those used in lecture 8 and lab 8, or lecture 11 and lab 11).

The Banking Transaction objects will have a Transaction base class that has the derived classes: Debit, Cashpoint, DirectDebit, Transfer, Creditpoint and Interest. Transaction will be an abstract class and its subclasses will be concrete classes. All Transaction derived classes will have a type, date, time and amount (in pounds and pence). In addition:

• Class Debit will have attributes to store the card number used, retailer name, retailer location, authorisation method (online, phone, mail order).

• Class Cashpoint will have attributes to store the location id of the cashpoint machine, and the card used.

• Class DirectDebit will have an attribute to store a reference.

• Class Transfer will have attributes to store the account number and bank sort code from where the transfer originated.

• Class Creditpoint will have an attribute to store the type of payment (cheque or cash).

• Class Interest will have an attribute to store the type of interest (daily, monthly or annual).

C. Design Specification

Specification for the design of the Engine Inspection System You are required to reverse engineer your final program code to produce a class diagram.

The reverse engineering is to be performed using IBM Rational Software Architect. The class diagram will therefore show all of the classes used in your submitted program code. The classes will include the attributes, operations and associations.

Once the class diagram has been created using IBM Rational Software Architect, you are required to create one main sequence diagram for the use case: ‘I - Insert an object’. The sequence diagram is to be created by following the program code corresponding to the use case ‘I - Insert an object’ from user choice to the addition of an object to the Link. Messages should correspond to each operation in the code and object lifelines for each class object used during the code.