How to Write a Harvard Referencing for Computer Science

Computer science students frequently engage with a diverse range of technical sources, from peer-reviewed IEEE journals to open-source software repositories and technical whitepapers. In this discipline, Harvard referencing requires precision to distinguish between foundational theoretical frameworks and rapidly evolving technical documentation.

What Is a Harvard Referencing in Computer Science?

Harvard referencing in computer science is an author-date system used to credit the intellectual origin of algorithms, architectures, and methodologies. Unlike other fields that rely heavily on books, CS referencing often prioritizes conference proceedings, technical reports, and digital documentation, requiring specific formats for URLs and version numbers.

Before You Start

• Verify the specific version of the Harvard style requested by your department (e.g., Cite Them Right or a custom institutional variation).
• Identify the primary author or the corporate body responsible for technical documentation, such as the World Wide Web Consortium (W3C).
• Locate the Digital Object Identifier (DOI) for all journal articles and conference papers to ensure permanent link stability.
• Differentiate between a published paper and a pre-print repository version like arXiv to ensure you cite the most authoritative copy.
• Collect the specific version or build number for software libraries or frameworks you intend to cite.

Cite a Journal Article with Multiple Authors

When citing foundational research in journals like 'Artificial Intelligence', list the author's surname and year in-text. For the reference list, include all authors up to a certain limit, followed by the article title and journal details.

Example: In-text: (Russell and Norvig). Reference: Russell, S. and Norvig, P. 'A Modern Approach to Intelligent Agents', Journal of AI Research, vol. 12, pp. 45-67.

Tip: Always use italics for the journal title, not the article title.

Reference Conference Proceedings

In CS, conference papers (like those from ACM or IEEE) are often more current than books. You must include the full name of the conference and the location where it was held.

Example: LeCun, Y. 'Deep Learning for Image Recognition'. Proceedings of the International Conference on Machine Learning (ICML). Montreal, Canada, pp. 10-15.

Tip: Look for the 'Series Editor' if the conference is part of a series like 'Lecture Notes in Computer Science'.

Cite Software and Code Repositories

When referencing a library like TensorFlow or a specific GitHub repository, treat the developer or organization as the author and include the version number.

Example: Google Brain. 'TensorFlow', version 2.10.0 [Software]. Available at: https://github.com/tensorflow/tensorflow (Accessed: 12 October).

Tip: Include the 'Accessed' date because code repositories change frequently.

Format Technical Whitepapers

Corporate whitepapers from companies like Intel or NVIDIA provide crucial architectural data. Cite the company as the author and include the report number if available.

Example: NVIDIA. 'NVIDIA Ampere Architecture Whitepaper', v1.1. [Whitepaper]. NVIDIA Corporation.

Tip: If no individual author is listed, use the company name as the corporate author.

Reference Online Technical Documentation

For languages or frameworks (e.g., Python or React documentation), use the official maintainer as the author and provide the direct URL.

Example: Python Software Foundation. 'The Python Language Reference', version 3.9. [Online]. Available at: https://docs.python.org/3/ (Accessed: 5 September).

Tip: Ensure the URL leads directly to the version of the documentation you actually used.

Cite a Book with an Edition Number

Standard textbooks on operating systems or algorithms often have multiple editions. It is critical to cite the specific edition used for page numbering accuracy.

Example: Silberschatz, A., Galvin, P.B. and Gagne, G. 'Operating System Concepts'. 10th edn. Wiley.

Tip: The first edition does not need an edition statement; only subsequent editions do.

Handle In-Text Citations for Direct Quotes

If you are quoting a specific definition of 'Big O Notation' or a theorem, you must include the page number in your in-text citation.

Example: Knuth states that 'algorithm analysis is the study of resource consumption' (Knuth, p. 104).

Tip: Use 'p.' for a single page and 'pp.' for a range of pages.

Reference Pre-print Servers

For the latest breakthroughs in areas like Large Language Models, you may need to cite arXiv papers. Clearly label these as pre-prints.

Example: Vaswani, A. et al. 'Attention Is All You Need'. [Pre-print]. Available at: https://arxiv.org/abs/1706.03762.

Tip: Check if a pre-print has been formally published in a journal before submitting your final draft.

Common Mistakes to Avoid

• Using 'Anonymous' for code with no clear author; instead, use the repository name or the organization (e.g., Apache Foundation).
• Forgetting to include the version number of a compiler or library, which can lead to reproducibility issues.
• Citing Wikipedia for technical definitions like 'Dijkstra's Algorithm' instead of citing the original paper or a standard textbook.
• Inconsistent capitalization of programming languages or specific hardware architectures (e.g., writing 'arm' instead of 'ARM').
• Omitting the 'Accessed' date for dynamic technical web pages that are updated frequently.
• Confusing the conference venue with the publisher (e.g., mixing up IEEE as the publisher with the specific conference name).

Pro Tips

• Use BibTeX keys that follow a consistent naming convention (AuthorYearTitle) to stay organized before exporting to Harvard format.
• Always check the 'How to Cite' section on official documentation sites; many provide the preferred Harvard format string.
• Prioritize DOIs over URLs for journal articles; DOIs are permanent and more professional.
• If citing a GitHub commit, include the specific commit hash for absolute precision in code-based research.
• Keep a 'master' bibliography file so you can reuse complex citations for foundational papers like Turing's 1936 work.

Frequently Asked Questions

How do I cite a GitHub repository in Harvard style?

List the author or organization, the year of the last update, the title of the repository in italics, the version or commit hash, and the URL with an access date. For example: Facebook (Year) 'React', version 18.0 [Source code]. Available at: URL (Accessed: Date).

Do I need to cite the programming language I used?

Generally, you do not need to cite a standard language like C++ or Java unless your paper specifically discusses the language's design or features. However, you should cite specific third-party libraries or APIs.

What is the correct way to cite a lecture slide in CS?

Include the lecturer's name, the year, the title of the lecture, the module code and name, and the platform where it was accessed (e.g., Canvas or Moodle). Example: Smith, J. 'Data Structures'. CS101 Introduction to CS [Lecture notes]. Available at: [URL].

How do I cite a YouTube tutorial for a coding project?

Treat the uploader as the author. Include the year of upload, the title of the video in italics, the platform in brackets, and the URL. Example: Computerphile (Year) 'Binary Search Explained' [Online video]. Available at: URL (Accessed: Date).

Related Resources

• How to Write a Harvard Referencing for Biology

• How to Write a Harvard Referencing for Psychology

• How to Write a Harvard Referencing for Nursing

• How to Write a Sentence Rewriting for Computer Science

• How to Write Topic Sentences for Computer Science

• How to Write a Paragraph Structure for Computer Science

• Find Peer-Reviewed Sources with Sourcely

• Polish Your Writing with Revise AI