OU blog

Personal Blogs

Christopher Douce

TM470 Referencing

Visible to anyone in the world

Referencing is really important in any academic project, and it is especially important in your final project.

This short blog post offers some practical guidance about what you should reference, and how you should go about it. It is intended to complement many of the resources that you already have access to.

Referencing fundamentals

There are a number of reasons why referencing is important:

  • It is assessed as a part of the learning outcomes for your project. In the project module, this is learning outcome number 7, which is all about effective communication.
  • It demonstrates the extent of your knowledge.
  • It demonstrates the extent of your reading and how you have applied your reading (and knowledge) to the solving of a problem.
  • It provides useful information that an examiner could use to find out more about the ideas, tools and technologies that you have used.
  • It demonstrates knowledge of academic practices for your discipline.
  • It prevents you from being inadvertently accused of plagiarism.

There are two key concepts that are really important:

  1. A citation. This is when you refer to something in the body of your project report. You might, for example, include a citation in a paragraph of text, to show the examiner where an idea (or some other resource) has come from, or how an idea is used. You might use a citation with a diagram or a figure.
  2. A reference. This is an entry within the references section that you can find towards the end of your report. This gives precise information about the resource (an article, a book, or some software) that you have used, along with where the reader (or examiner) might be able to find it if they want to find out more.

A useful principle to bear in mind is that anything that exists in the world can be referenced, and cited. It is possible to reference a personal email, as well as a museum artefact, such as a vase. A related principle is that a reference should be unique, and be able to be unambigiously identified. What you need to practically reference will be different depending on your academic discipline. This means that a referencing approach for engineering will be different to what is required for English literature.

Since computing draws on a variety of different subjects, you may come across articles that use different referencing formats; each have their own advantages and disadvantages. Journals and conferences published by the Institute of Electrical and Electronics Engineers (IEEE) use a referencing format where articles are given numbered. Whilst this helps to create articles that are relatively short, it detracts from the readability and understandability of articles. A more friendly approach is the Harvard style, which is the one that you should use for your project report.

Examples

Your ‘go to’ resource for everything that relates to referencing is the Cite Them Right website. From the choose referencing style menu, you should then click on Harvard.

Here is a prototype of a Harvard reference:

Surname, Initial (year) ‘Title of article’, Title of publication. Volume number(Issue number), Page range. Available at: URL. (Accessed: today’s date).

Note the writing convention of putting the title of a publication in italics. This also applies to when you are writing the body of your report. Page numbers are expressed using the format ‘pp. 100-110’, where ‘pp.’ is used to begin a range of pages.

The URL should ideally be what is known as a DOI, which is an abbreviation for Digital Object Identifier (Wikipedia) which is a stable web address for a published article. DOIs are typically used to refer to journal articles. If you don’t have a DOI for an article but you have a web address, you can leave that, but you should then leave the accessed date. The reason for this is that links that are not DOIs can age.

Here’s an example of a citation, that you leave within the body of your report:

(Surname, 2026, p. 32)

If you refer to the author a number of times within a paragraph, you could just include the page reference, which saves a bit of typing, and helps with the clarity.

If you need to, you could also combine references together in a small list:

(Surname1, 2026; Surname2, 2025)

More extensive guidance is provided within Quick guide to Harvard referencing (Cite Them Right).

What follows are some examples of referencing that you will typically wish to use in your project.

Module materials

There is an expectation that you will demonstrate a connection between your project,and your previous studies. To do this well, it is important that you take the time to materials from your earlier studies.

There are different types of module materials: printed books, module websites, and booklets (such as ‘readers’ that accompany module materials). Given that an important principle of referencing is the need to unambiguously refer to sources, an important question to ask is: ‘does the resource I am using have an easily identifiable author?’ It it does, you should use the name of the author. If not, you should reference the author as The Open University.

For a module that has printed books, you might include the following references:

The Open University (2025a) Block 1 Units 1-4 From domain to requirements: TM354 Software Engineering. Third edition. The Open University.

The Open University (2025b) Block 2 Units 5-8 From analysis to design: TM354 Software Engineering. Third edition. The Open University.

The second mention of The Open University refers to the name of the book publisher.

You might cite the first text as follows:

‘(The Open University, 2025a, p.32)’

For materials located on a module website, you might provide a reference similar to the following:

The Open University (2026) ‘Unit 9 Architecture, patterns and reuse’, TM354 Software Engineering. Available at: https://learn2.open.ac.uk/mod/oucontent/view.php?id=... (Accessed: date).

Since there is no page number, you should cite the reference as follows:

‘(The Open University, 2026)’

Academic articles

During your project there is an expectation that you will read beyond your module materials and look to original source materials, and academic articles that may potentially inform or influence the work that you do within your project.

Here is an example of how to reference a famous software engineering article:

Parnas, D. (1972) ‘On the criteria to be used in decomposing systems into modules’, Communications of the ACM, 15(12), pp. 1053-1058. Available at: https://doi.org/10.1145/361598.361623

No date of access is needed to be given, since the DOI is understood to be stable.

It can be cited as follows:

‘Parnas (1972) stated … (p.1052).’

Books

If you create a software product during your project, you will usually refer to reference texts. A really useful library source is the O’Reilly Safari library. You might reference a programming text as follows:

Lutz, M. (2026) Learning Python. Sixth Edition. O'Reilly Media, Inc.

You make cite it using the form:

‘A useful resource was the chapter on Lists and Dictionaries found in Learning Python (Lutz, 2026).’

If you only consult an electronic version of a text, you may not have a explicit page number, but do demonstrate both your reading and understanding by referring to specific section numbers.

Edited books

Useful articles can often be found within edited books. Best practice is to provide references to specific chapters rather than an entire text:

Müller, V.C. (2023) ‘The History of Digital Ethics’, in C. Véliz (ed.) Oxford Handbook of Digital Ethics. Oxford University Press, pp.18-38. Available at: https://doi.org/10.1093/oxfordhb/9780198857815.013.1.

An article that has been downloaded from a repository might have its own page number, rather than the page numbers of the edited text. If this is the case, a practical approach is to reference the page numbers from the article. For example:

‘Müller begins with Babbage’s analytical engine (Müller, 2023, p.4)’

Software

You should provide a reference to practically every software product you have used. This might include element of your software architecture, or software development environments you have used to create your software product.

You should give the name of the author, which might be the organisation that created the software. Software if often referred to in terms of their websites. The Cite Them Right website offers some useful guidance.

Here is a practical example:

Apache.org (2026) Apache Netbeans (Version 31) [Computer program]. Available at: https://netbeans.apache.org/front/main/index.html (Accessed: 13 November 2026)

A citation example:

‘During the project, I made extensive use of Netbeans (Apache.org, 2026).

Websites

You might refer to websites if you wish to show your examiner how you have made use of documentation during your project. For example:

Python.org (2026a) 5. Data Structures. Available at: https://docs.python.org/3/tutorial/datastructures.html (Accessed 13 November 2026)

Python.org (2026b) 9. Classes¶. Available at: https://docs.python.org/3/tutorial/classes.html (Accessed 13 November 2026)

If there is no visible or distinguishable year of publication, do give the current year. If there is the need to provide several references to a single website, add letters, i.e. ‘a’, ‘b’, ‘c’ etc. after the year to provide a way to make each reference unambigious.

The first reference could be cited as follows:

‘A useful illustration about how to use a list as a stack could be found in Python language documentation (Python.org, 2026a)’.

When using and referring to resources, avoid the use of blog posts (except this one, of course), since they may not be reliable. Prioritise the use of module materials, academic articles and reputable textbooks.

Generative AI

My advice about Generative AI is simple - avoid using it. This said, some projects might focus on the exploration and application of AI tools and products. Whilst it is permissible to use AI within a project module, if you do use it, it is necessary to justify and explain its use.

An important aspect of referencing within academic writing is all about helping your examiner to understand what your sources were, why you have chosen them and how they are applied in the context of your project.

From a practical perspective, to reference your use of generative AI, you should:

  • Provide a clear reference to the tool you have used.
  • Provide an exact copy of the prompt that you have used with that tool.
  • Provide a complete copy of response gained in response to your prompt.

Since specific guidance about how to reference generative AI is likely to change as practices become more refined, it is best to consult the CiteThemRight website. This said, here is a very simply practical example that begins with a citation, and then offers a reference.

In text citation:

‘Copilot was used to interrogate my choice of framework (Microsoft, 2026)’.

Reference:

Microsoft (2026) AI-generated text by Copilot with prompt ‘List the 5 most popular PHP frameworks and their most significant advantage and disadvantages’, 13 November 2026, Transcript presented in Appendix 1.

Assuming the project report is not to be made publicly accessible and is only to be used as a part of a formal assessment, it is acceptable to keep the response from the AI product within the boundaries of the project report. There must be sufficient to enable the examiner to make an informed judgement about how you have critically evaluated and have made use of any responses.

Keeping track of your resources

Whilst working on an essay or project, I need to keep track of a lot of different sources. To address this challenge, there are bits of software known as reference management tools (blog article). These software products help you to keep a record of all your sources, and can also help you with adding citations and references to your documents. In some cases, these tools may help you to move between referencing formats if this is something you need to do. There is, of course, a learning curve and an administrative overhead which accompanies the use of these tools. You also need to ask yourself the question of whether using a reference management tool is worth the investment of your time.

My personal preference is to use a low tech approach. I create a folder where I store all my references. In this folder, I save everything that relates to my project. I use a really simple system for everything I add to the folder. I give each document an author name, followed by a title of the article. If you prefer, you can also add the year of publication. If I need to reference a website, I also create a hyperlink (I right click with the mouse, and then click on ‘new’ followed by ‘shortcut’). This simple approach not only helps me to easily find articles after I have downloaded them, but it helps me to check my references list.

Points to remember

The following points might be useful:

  • If you use something, or refer to something in the body of your report, ask whether you need to provide a citation, and a reference. If you are referring to a bit of software may times, a practical approach is to refer to it once, which is, where you first refer to it in your report.
  • Don’t finish a paragraph with a citation. If you are using a writing framework, such as PEEL (an abbreviation for Point, Evidence, Explain, Link), the final sentence should be either a linking sentence to another paragraph, or a concluding sentence.
  • Only include a references section in your project report. You don’t need to provide a bibliography section.
  • For every reference you provide in your references section, there should be one or more citations.
  • When providing a citation, do provide a page number, if it is appropriate to do so. Page numbers signal to the examiner that you have closely read your source materials.
  • You must organise your reference list alphabetically, in order of surname.
  • Never mix referencing formats; this will just confuse your examiner, and it also looks as if you have copy/pasted from somewhere. It is important that your references section is consistent.
  • Give a DOI reference if you have one.
  • If you’re unsure about how to reference something, ask your tutor.

Other blog posts

In addition to the earlier article about referencing tools, the following blog posts might be useful:

Library resources

The following resources might be helpful:

I've found the browser extension particularly useful, since it allows you to access articles without having to explicitly login to the library website.

Reflections

When I am a project report examiner, one of the first thing I do is to look to the references section. This section gives me a good idea of what the project is going to be about. I come to it with a set of questions:

  • What module materials are referenced, and how have they contributed to this project?
  • What software products have been used?
  • Is there evidence of significant further reading beyond the boundaries of the module?

I also look for how the references section is formatted. Is it in alphabetical order? Is it well presented? What is the mix of resources that are used? From my examiner’s perspective, the reference section shows off the extent of your knowledge, and the extent of your reading.

There are two other thoughts that cross my mind with respect to referencing. Good referencing demonstrates good academic practice. It also provides good evidence of good academic conduct.

From the perspective of your project, the references section might be one of the last sections that you edit, but from the examiner’s perspective, it might be one of the first sections they read.

Permalink Add your comment
Share post