Defining Your Computing Project: Scope, Aims and Research Questions

Alex: We're starting Unit 6 today: Planning a Computing Project. This is a Pearson-set unit, which means there's a specific brief you work to. Sam, let's start with the first lesson, which is all about defining your project. What does that involve?

Sam: Defining a project well is one of the most critical things you can do. It determines the direction of all subsequent work, and a poorly defined project almost always leads to problems down the line. The definition stage involves establishing the scope, which sets the boundaries of what your project covers; the aims, which are the high-level goals you want to achieve; and the objectives, which are the specific, measurable steps that will get you to those aims.

Alex: How do you decide on an appropriate scope?

Sam: Scope needs to be realistic for the time and resources available while being substantial enough to meet the unit's requirements. For a Pearson-set unit, the brief itself will constrain the broad topic area, but within that you need to make specific choices about focus. A scope that's too broad means you try to cover too much and end up doing nothing well. A scope that's too narrow doesn't generate enough meaningful work. The skill is in finding the right level.

Alex: What's the difference between aims and objectives?

Sam: Aims are aspirational and directional: 'to investigate the feasibility of implementing a cloud-based solution for the organisation's data management needs'. Objectives are specific and measurable: 'to conduct a literature review of current cloud storage solutions by the end of week three'. Objectives should follow the SMART framework: Specific, Measurable, Achievable, Relevant, and Time-bound. The SMART criteria help ensure your objectives are concrete enough to be meaningful.

Alex: What are research questions and how do they relate to aims and objectives?

Sam: Research questions are the specific questions your project is designed to answer. They provide a precise intellectual focus. A good research question should be genuinely open: you shouldn't know the answer before you start. It should be answerable with the data you can realistically collect. And it should be relevant to the context you're working in. 'What cloud storage solution best meets the security and cost requirements of a small legal practice?' is a well-formed research question.

Alex: Should you also state your assumptions and limitations at the outset?

Sam: Yes, and this is a sign of academic maturity. Assumptions are things you're taking for granted that affect your project; for example, you might be assuming that the organisation will cooperate with your data collection. Limitations are constraints on your project that affect the generalisability or completeness of your findings; for example, the time available means you can only survey 30 users rather than the full population. Stating these upfront demonstrates intellectual honesty.

Alex: Is there a specific format you should use?

Sam: Most institutions and organisations use a project initiation document or a project proposal as the formal record of the project definition. It sets out the context, scope, aims, objectives, research questions, methodology, timeline, and any ethical considerations in a structured way. It's reviewed and signed off before substantive work begins, which ensures everyone has a shared understanding of what the project is trying to achieve.

Alex: Brilliant. Defining the project well really is the foundation.

Sam: It absolutely is. Invest time in it, because everything else builds on it.

Alex: Thanks Sam. Next we look at research methods and data collection.