Academic Projects in Computing
Key Concepts, Project Types, and Stakeholders
Working on an academic project is a unique experience. It’s not just about getting something done; it’s about exploring ideas, diving deep into research, and contributing to knowledge in the field. When I first started academic projects, I quickly realized they required more than just technical skills; they pushed me to think critically, justify my choices, and reflect on the bigger picture.
In this blog, we will explore the essential elements of academic projects, how they differ from industry work, and the key stakeholders involved in the project. This will provide an overview before we dive into different research methods. Let's get started!
What is an Academic Computing Project?
Projects in computing and information systems have distinct characteristics that set them apart from other disciplines. They often:
Have defined start and end points.
Go beyond software development to include elements of research.
Involve a blend of hard sciences (e.g., math, physics) and soft sciences (studying people and society).
By appreciating these unique traits, students can better position themselves for success, whether in academic or industry-focused computing projects.
Academic vs. Industry Projects
In academia, the focus is on critical thinking and the development of original ideas. Projects in this space require a deep dive into concepts, where you not only justify your methods but also thoroughly analyze and contextualize the results. A typical academic project involves:
Extensive research to explain methodologies.
Evaluating the effectiveness of the approach.
Critical assessment of strengths, weaknesses, and gaps in the existing body of knowledge.
In contrast, industry projects are designed with a more practical mindset. The goal is to solve specific problems and meet business needs. Here, the emphasis is on functionality and efficiency rather than deep theoretical exploration. Key aspects include:
Developing functional tools or methods to solve immediate problems.
Prioritizing performance and outcomes over detailed explanation.
Delivering results that align with business objectives.
Project Spectrum
Computing projects generally fall into three broad categories: theory → practice → application.
Theory: This area emphasizes mathematics, logic, formal methods, and artificial intelligence, and is typically the focus of Computer Science and AI degree programs.
Practice: Centered around software system development and project management, these projects are common in Software Engineering and E-business courses. They address design, development processes, and requirements capture.
Application: This category explores the use and influence of computers in real-world contexts, often seen in Information Systems and Business Information Systems programs. The focus is on how computing can be applied to solve practical problems.
Project Types
Academic computing projects can vary widely in scope and objective. Here are some common categories:
Research-based Projects: These involve reviewing literature to identify gaps in knowledge and typically focus on making original contributions, especially at the PhD level.
Development Projects: These projects emphasize creating software or hardware systems. They demand a robust documentation process, covering everything from designs to user manuals.
Evaluation Projects: Often centered on comparing methods or technologies, these projects may assess different problem-solving approaches or evaluate programming languages and interfaces.
Industry-based Projects: Collaborations with real-world clients, these projects combine academic rigor with practical problem-solving, though they must still meet academic standards.
Problem-solving Projects: Focused on finding new solutions, these projects are about improving or adapting existing methods, with an emphasis on evaluation and refinement.
No matter the type of project, critical evaluation remains essential. In academic environments, it’s not enough to simply solve a problem—you must also reflect on the process and its outcomes.
Taught vs. Research Degree Structures
Taught Degrees (BSc, MSc)
These degrees are mostly course-based, with some project work. While projects here don’t need to lead to groundbreaking discoveries, they often involve software development or case studies. The emphasis is on applying known methods rather than pushing the boundaries of knowledge.
Research Degrees (MPhil, PhD)
Research degrees are more demanding. An MPhil project should be publishable, making a small but meaningful contribution to knowledge. For a PhD, the goal is to make an original and significant contribution to the field, often leading to publications before the thesis is completed.
“The contribution of knowledge of a Master’s thesis can be in the nature of an incremental improvement in an area of knowledge, or the application of known techniques in a new area. The PhD must be a substantial and innovative contribution to knowledge”.
Chinneck (1999)
Key Stakeholders in Academic Projects
👨🏻🏫 Supervisors
Think of your project as a big, heavy rock. At first, it's hard to move - just like starting a project is tough. But once you get it rolling, it becomes easier and picks up speed. Now, imagine your supervisor is right there with you. Their job is to help and guide you as you push this rock (your project) along. Here's what they do:
They encourage you when you're trying to get started
They make sure you're going in the right direction
They keep an eye on your progress and give you a little push now and then to keep you on track
They offer support and help when you feel tired or stuck
Your supervisor is there to help from the early struggles to the final steps of your project, offering direction and encouragement every step of the way.
🙋🏻♂️Clients and Users
If your project involves developing software or doing research with real people, you'll likely work with clients and/or users. It's important to understand the difference between these two groups:
Clients: They're usually the project sponsors who request the system or study.
Users: They're the people who will actually use the system or benefit from the project results.
Sometimes, the client and user are the same person, but often they're not. For example, if you're making a website for a company to sell products, the client is your contact at the company, the users are the people who will visit the website.
When clients and users are different, conflicts can arise. For instance, the client might want something that users won't like or you might need to convince the client that a feature is necessary for users, even if the client thinks it's not.
In some cases, your supervisor might also be your client and/or user if they proposed the project. This can lead to conflicts too. For example, as a user, they might want certain features, but as a supervisor, they might advise against including those features if they require too much work for little benefit.
👩🏻🏫 Examiners
The number and type of examiners for your project will depend on your course level (undergraduate or postgraduate) and your institution's rules. These rules can vary between schools and countries. Here's a general overview:
Undergraduate projects: Often, your supervisor will grade the project. In many cases, an additional examiner from your department or another will also review your work.
Postgraduate projects: External examiners from other departments or universities are usually involved. Depending on the project, there may be a single examiner or a panel of them acting as a committee.
What examiners look for in your project depends on its level:
For an undergraduate software development project, they'll look at whether you used the right methods and techniques
For a PhD project, they'll focus on your contribution to new knowledge
🧑🏻💻 Evaluators and testers
If you're developing software for your project, you'll need to test and evaluate it. It's important not to do all this testing by yourself. You should involve other people, such as:
The client (the person who asked for the software)
The users (people who will actually use the software)
Other people not directly involved in the project (like your classmates) who can give useful feedback
These people can be experts or non-experts. Their input is valuable because they can provide different perspectives on your software.
Academic projects are all about exploring, thinking critically, and making meaningful contributions to your field. By understanding their unique characteristics, you can better navigate your next project and set yourself up for success.
In the next blog, we’ll dive deeper into academic research, what it really means, how to approach a research project, and tips to make the process smoother. Stay tuned!
Reference
This blog is based on ideas and concepts from Dawnson’s book: Projects in Computing and Information Systems: A Student’s Guide (3rd ed.). If you want to explore more detail, please refer to the book for comprehensive coverage.
Dawson, C. W. (2015). Chapter 1, In Projects in computing and information systems: A student’s guide (3rd ed., pp. 3-16). Pearson Education.