Good Practice and Unfair Practice

1. Good Practice and Unfair Practice And other things…

2. Overview • Outline Project Specification • Plagiarism • Bibliography • IPR

3. Outline Project Specification • See the website for details • Title Page • Two pages of content • Template available (not required) • Due by 6pm Monday 22nd October (i.e. next week) • Blackboard submission • All modules - use the CS39440 module

4. Plagiarism

5. Good Practice and Unfair Practice • What is plagiarism? • Why is now a good time to think about it? • What happens if I am suspected? • How to avoid it… i.e. adopting good practice

6. What is plagiarism? • It is the intentional use of other people's ideas and words and claiming them as your own • e.g. taking someone else's code and handing it in as if you wrote it • e.g. taking someone else's words and putting them into a document that you are writing without attribution (see later)

7. Plagiarism includes… • Reusing writing without attribution • Reusing diagram without attribution • Reusing code without attribution • Reusing ideas without attribution

8. Why is this topical? • You will be writing reports on this module • You will be writing code • Some people try to pass of other people’s work as their own • We need to see what is YOUR work

9. What happens if plagiarism is suspected? • Case is reported to Department Exam Board Chairperson (Prof. Dave Barnes at present) • Student receives a formal letter from the Chair • Enquiry committee is established • Less than 20 credits: dealt with in the department (but can be handled at the University level) • More than 20 credits: must be handled at the University level • There is a hearing • If the student is found guilty, a penalty will be applied

10. Possible penalties • Lower or zero mark awarded • Decision about whether a retake is allowed • Exclusion from University

11. “Unfair” vs “Bad” practice • Unfair practice – you have attempted to gain an unfair advantage • Bad practice – you have not followed good practice for some areas • Plagiarism has some grey areas • Always use good practice so that you won’t leave yourself open to accusations

12. How to avoid bad practice • 1. For course work or project work, NEVER write down words taken directly from another source without putting quotation marks around it and a reference to where you found it • 2. Unless it is an impressive quote you are better of explaining things in your own words (with a reference) • Never just cut and paste someone else’s code into your program. If you are supposed to do the coding yourself, then look at the code, learn from the code, put it to one side and write your own implementation. • If you are using 3rd party code, record exactly where you obtained the code from, when you accessed the code and how the code has been used in your project.

13. Bibliography

14. Building a bibliography • For your reports, you need to tell us the sources that you have been reading to support your work • Information such as: • Authors/Editors and Year of Publication • Title (book/journal) • Edition / Volume / Series • Publisher and Place of Publication • Page References • URLs for web resources and dates when you accessed the resource • Digital Object Identifiers • Start keeping detailed records: tools may help (BibTeX, EndNote)

15. Author-Date (Harvard Style) • IEEE Style (Numeric) • Useful Resource • Pears, R., Shields, G. (2010). Cite them right: the essential referencing guide. 8th Edition. Basingstoke: Palgrave Macmillan.

16. Annotated Bibliography • A bibliography, with a paragraph for each entry to describe the main points/ideas that are of interest to your project. • Might be more difficult with the tool support…

17. Example Bibliographies (1) Bibliography: Major/Minor Project

18. Example Bibliographies (2) Bibliography [1] http://www.microsoft.com/ [2] http://www.mysql.com/ [3] http://www.java.com/ [4] Newborn, M., (1975) Computer Chess. Academic Press. [5] Connolly, Thomas M & Begg, Carolyn E. (2000) Database Solutions, A step-by-step guide to building databases. Addison-Wesley. Major/Minor Project

19. Example Bibliographies (3) [1] Loosemore, M., Uher T. Essentials of Construction Project Management, UNSW Press, 2003. This book covers the process of managing large construction projects. In particular, it discusses the production of a design management plan, and how it can be used in managing the construction phase. This is useful for the modelling phase of my project. [2] Eriksson, H., Penker, M., Lyons, B., Fado, D. UML2 Toolkit, Wiley, 2004. UML2 updates the UML standard, but many of the extra features are related to the needs of Model-Driven Development, and so are not relevant to this project, where modelling with the simpler UML1 will be sufficient. [3] Stevens, P., PooleyR.Using UML: software engineering with objects and components, Addison-Wesley, 1999. A useful summary of UML when I was doing the modelling, but too short on examples to be useful when learning how to use the various components of UML in the first place. Major/Minor Project

20. IPR

21. IPR • Who owns the outputs of the project? • General statement on the website • Read this • Talk to me about any questions • May involve CCS as appropriate

22. Questions?