Chapter overview and learning outcomes
This chapter develops the theory and practical foundations of research methods, ethics and final-year project, linking core concepts to the design, evaluation and responsible operation of computing systems.
- Define key concepts and use technical vocabulary accurately.
- Explain relevant models, processes and underlying assumptions.
- Apply methods to realistic problems and interpret results.
- Evaluate alternatives, trade-offs, risks and limitations.
- Communicate findings using appropriate diagrams and evidence.
1. Research in computer science and problem selection
Computer science research may develop theory, algorithms, systems, empirical evidence, human-centred evaluations or applied solutions. A strong project addresses a clear problem whose significance can be explained to a defined audience. Start by exploring a domain, identifying a gap or practical need, and checking feasibility. Consider access to data, equipment, participants, supervision, time and skills. A project should make a contribution proportionate to its level and available resources.
Applied study: Work through a realistic scenario from the domain. Identify the assumptions, constraints, relevant stakeholders and expected outcome. Explain the reasoning behind a proposed method, compare it with at least one alternative, and discuss reliability, security, performance, ethical implications and limitations.
Learning activity: Prepare a labelled model or worked example, define how you would test it, and write a short reflection on what evidence would change your conclusion.
2. Research questions, aims and objectives
A research question is focused, answerable and aligned with the problem. The aim states the overall purpose; objectives break it into observable tasks. Hypotheses make testable predictions where appropriate, but not all computing research requires a hypothesis. Define key terms, scope, assumptions and success criteria. Questions should avoid being too broad, leading or dependent on inaccessible evidence. Map each objective to a method and an expected form of result.
Applied study: Work through a realistic scenario from the domain. Identify the assumptions, constraints, relevant stakeholders and expected outcome. Explain the reasoning behind a proposed method, compare it with at least one alternative, and discuss reliability, security, performance, ethical implications and limitations.
Learning activity: Prepare a labelled model or worked example, define how you would test it, and write a short reflection on what evidence would change your conclusion.
3. Literature search and critical review
A literature review identifies and evaluates existing work relevant to the question. Search scholarly databases, conference proceedings, books, standards and authoritative technical reports using planned keywords and inclusion criteria. Track search dates and sources. Evaluate methods, datasets, assumptions, sample sizes, limitations and reproducibility rather than merely summarising abstracts. Organise findings by themes and disagreements. A research gap should be demonstrated from evidence, not asserted because a topic seems new.
Applied study: Work through a realistic scenario from the domain. Identify the assumptions, constraints, relevant stakeholders and expected outcome. Explain the reasoning behind a proposed method, compare it with at least one alternative, and discuss reliability, security, performance, ethical implications and limitations.
Learning activity: Prepare a labelled model or worked example, define how you would test it, and write a short reflection on what evidence would change your conclusion.
4. Research paradigms and methodology selection
Methodology explains the reasoning behind the chosen research approach. Quantitative methods measure variables and analyse numerical data; qualitative methods investigate experiences, meanings and processes; mixed methods combine approaches when justified. Design science may create and evaluate an artefact; experimental research tests controlled interventions; case studies investigate systems in context. Choose methods that can answer the research question and acknowledge what they cannot establish.
Applied study: Work through a realistic scenario from the domain. Identify the assumptions, constraints, relevant stakeholders and expected outcome. Explain the reasoning behind a proposed method, compare it with at least one alternative, and discuss reliability, security, performance, ethical implications and limitations.
Learning activity: Prepare a labelled model or worked example, define how you would test it, and write a short reflection on what evidence would change your conclusion.
5. Experimental design and evaluation
A good experiment defines independent and dependent variables, controls, comparison conditions, sampling, procedures and outcome measures. Benchmarks must be representative and their limitations stated. For algorithm evaluation, compare against appropriate baselines and report hardware, software versions, parameter settings and repeated runs. Avoid changing multiple factors without a design that can separate their effects. Distinguish statistical significance from practical importance and report uncertainty.
Applied study: Work through a realistic scenario from the domain. Identify the assumptions, constraints, relevant stakeholders and expected outcome. Explain the reasoning behind a proposed method, compare it with at least one alternative, and discuss reliability, security, performance, ethical implications and limitations.
Learning activity: Prepare a labelled model or worked example, define how you would test it, and write a short reflection on what evidence would change your conclusion.
6. Data collection, sampling and analysis
Data may come from experiments, surveys, interviews, logs, public datasets or system measurements. Sampling strategy affects generalisability; convenience samples may be biased. Define inclusion and exclusion criteria, data dictionaries and missing-data handling. Quantitative analysis may include descriptive statistics, confidence intervals and suitable tests; qualitative analysis may use coding and thematic interpretation. Keep raw data protected and retain an audit trail of transformations and analysis decisions.
Applied study: Work through a realistic scenario from the domain. Identify the assumptions, constraints, relevant stakeholders and expected outcome. Explain the reasoning behind a proposed method, compare it with at least one alternative, and discuss reliability, security, performance, ethical implications and limitations.
Learning activity: Prepare a labelled model or worked example, define how you would test it, and write a short reflection on what evidence would change your conclusion.
7. Research ethics, privacy and responsible computing
Ethical research respects participants, minimises harm, protects privacy and obtains required institutional approval before recruitment or data collection. Informed consent should explain purpose, procedures, risks, benefits, confidentiality and withdrawal rights. Use data minimisation, secure storage, access restrictions and appropriate retention periods. Avoid collecting sensitive information without justification. Computing projects also require attention to accessibility, algorithmic bias, cyber safety, intellectual property and environmental impact.
Applied study: Work through a realistic scenario from the domain. Identify the assumptions, constraints, relevant stakeholders and expected outcome. Explain the reasoning behind a proposed method, compare it with at least one alternative, and discuss reliability, security, performance, ethical implications and limitations.
Learning activity: Prepare a labelled model or worked example, define how you would test it, and write a short reflection on what evidence would change your conclusion.
8. Project planning, scope and risk management
A project plan translates objectives into deliverables, tasks, dependencies, milestones and responsibilities. Define scope and exclusions to prevent uncontrolled expansion. Estimate time for literature review, design, implementation, testing, evaluation, writing and revision. Maintain a risk register covering technical uncertainty, data access, participant recruitment, equipment, security and schedule. Use version control, regular supervisor feedback and contingency plans. Record changes and their effects on objectives.
Applied study: Work through a realistic scenario from the domain. Identify the assumptions, constraints, relevant stakeholders and expected outcome. Explain the reasoning behind a proposed method, compare it with at least one alternative, and discuss reliability, security, performance, ethical implications and limitations.
Learning activity: Prepare a labelled model or worked example, define how you would test it, and write a short reflection on what evidence would change your conclusion.
9. Software implementation, testing and reproducibility
A computing artefact should be designed so that its behaviour can be inspected and evaluated. Use version control, modular design, tests, code review and documented dependencies. Reproducibility requires a clear account of environment, configuration, data preprocessing, random seeds where relevant and execution steps. Do not expose credentials or private data in repositories. Provide a clean installation or execution guide and distinguish reproducible results from results that depend on unavailable services.
Applied study: Work through a realistic scenario from the domain. Identify the assumptions, constraints, relevant stakeholders and expected outcome. Explain the reasoning behind a proposed method, compare it with at least one alternative, and discuss reliability, security, performance, ethical implications and limitations.
Learning activity: Prepare a labelled model or worked example, define how you would test it, and write a short reflection on what evidence would change your conclusion.
10. Results, discussion, limitations and validity
Present results clearly using tables, figures and appropriate statistical summaries. Explain what the evidence supports and avoid causal claims from observational data unless the design justifies them. Discuss internal, external, construct and conclusion validity where relevant. Identify limitations such as sample bias, measurement error, hardware dependence, small datasets or incomplete testing. A balanced discussion explains unexpected findings and compares results with prior work.
Applied study: Work through a realistic scenario from the domain. Identify the assumptions, constraints, relevant stakeholders and expected outcome. Explain the reasoning behind a proposed method, compare it with at least one alternative, and discuss reliability, security, performance, ethical implications and limitations.
Learning activity: Prepare a labelled model or worked example, define how you would test it, and write a short reflection on what evidence would change your conclusion.
11. Technical writing, citation, presentation and project defence
A final report typically includes an abstract, introduction, literature review, methodology, implementation or study, results, discussion, conclusion, references and appendices. Use consistent terminology, numbered figures and tables, and a recognised citation style required by the institution. Cite ideas, data, code and quotations accurately; never fabricate references or results. A presentation should explain the problem, contribution, method, evidence and limitations. Prepare to defend design decisions and acknowledge uncertainty.
Applied study: Work through a realistic scenario from the domain. Identify the assumptions, constraints, relevant stakeholders and expected outcome. Explain the reasoning behind a proposed method, compare it with at least one alternative, and discuss reliability, security, performance, ethical implications and limitations.
Learning activity: Prepare a labelled model or worked example, define how you would test it, and write a short reflection on what evidence would change your conclusion.
Conceptual diagram for learning and revision.
Conceptual diagram for learning and revision.
Conceptual diagram for learning and revision.
Practical laboratory or project activity
- Choose a bounded problem relevant to this chapter and state its purpose.
- Identify inputs, outputs, constraints, assumptions and potential failure cases.
- Develop a small model, prototype, experiment or worked analysis.
- Use appropriate tools and authorised datasets or test environments.
- Test normal, boundary and failure conditions; record reproducible observations.
- Write a report explaining method, evidence, limitations and recommendations.
Follow institutional rules, protect private information and obtain permission before testing systems or collecting data.
Worked reasoning and self-assessment
Start by translating the question into a precise problem statement. Define variables and assumptions before calculating or implementing. Work through a small example manually, then verify it with an appropriate tool. Explain why the selected approach is suitable, identify an alternative, and discuss its trade-offs. For empirical claims, describe the data and method needed to support them; for system claims, specify observable tests and expected outcomes.
Examination and revision questions
Answer using precise definitions, diagrams, calculations and examples where appropriate.
What makes a research question good?
Show answer guidance
It is focused, significant, answerable, feasible and aligned with available evidence and methods.
Differentiate aim and objectives.
Show answer guidance
The aim states the overall purpose; objectives specify measurable steps toward it.
What is a literature review?
Show answer guidance
A critical synthesis of relevant existing research, methods, evidence and gaps.
Differentiate quantitative and qualitative research.
Show answer guidance
Quantitative methods analyse numerical measurements; qualitative methods examine meanings, experiences and processes.
What is a control condition in an experiment?
Show answer guidance
A comparison condition used to interpret the effect of an intervention or treatment.
Why document data provenance?
Show answer guidance
To establish where data came from, how they were collected and what limitations apply.
What is informed consent?
Show answer guidance
A voluntary agreement based on adequate understanding of purpose, procedures, risks and rights.
What is reproducibility?
Show answer guidance
The ability to obtain consistent results using the same data, methods, code and documented environment.
What is a project risk register?
Show answer guidance
A record of risks, likelihood, impact, owners, mitigations and review status.
Name two forms of validity.
Show answer guidance
Internal, external, construct and conclusion validity.
Why use version control in a research project?
Show answer guidance
To track changes, collaborate, reproduce versions and recover earlier work.
What should a methods section explain?
Show answer guidance
Design, data, participants or systems, procedures, measures, analysis and relevant ethical safeguards.
Why report limitations?
Show answer guidance
To make the scope and uncertainty of conclusions transparent.
What is plagiarism?
Show answer guidance
Presenting another person's words, ideas or work as one's own without appropriate acknowledgement.
What should a project defence communicate?
Show answer guidance
The problem, contribution, methods, evidence, limitations and justification of key decisions.
Revision checklist
- Can I explain the chapter's central concepts without relying on memorised phrases?
- Can I reproduce and interpret the diagrams?
- Can I apply the methods to a new scenario?
- Can I justify assumptions and compare alternative approaches?
- Can I identify technical, ethical, privacy and security risks?
- Can I explain limitations and what further evidence is needed?
Further study and academic references
Consult current university textbooks, peer-reviewed conference and journal papers, official standards and authoritative technical documentation. Verify versions and publication details before citing sources. Use the citation style required by your institution, cite data and software as well as written sources, and distinguish published evidence from your own analysis. Do not invent references, measurements or experimental outcomes.