Skip to main content
  • 1036 Accesses

Abstract

This chapter is an extension to that. As I proposed in that chapter, imagine that two students submit code that looks plagiarized. Should credit be given for originality, and if so, who should get it? Who might be the original author and who might have been plagiarizing content?

This is a preview of subscription content, log in via an institution to check access.

Access this chapter

eBook
USD 19.99
Price excludes VAT (USA)
  • Available as EPUB and PDF
  • Read on any device
  • Instant download
  • Own it forever
Softcover Book
USD 16.99
Price excludes VAT (USA)
  • Compact, lightweight edition
  • Dispatched in 3 to 5 business days
  • Free shipping worldwide - see info

Tax calculation will be finalised at checkout

Purchases are for personal use only

Institutional subscriptions

Author information

Authors and Affiliations

Authors

Rights and permissions

Reprints and permissions

Copyright information

© 2016 Sudipta Mukherjee

About this chapter

Cite this chapter

Mukherjee, S. (2016). Code Forensics. In: Source Code Analytics With Roslyn and JavaScript Data Visualization. Apress, Berkeley, CA. https://doi.org/10.1007/978-1-4842-1925-6_6

Download citation

Publish with us

Policies and ethics