Chapter 1 sets up your whole project: it tells the reader what problem you are solving, for whom, and what your system will do about it. Get it right and the rest of the document — and your defense — becomes far easier. Here is each section, what it must contain, and a short worked example.
1. Background of the study
Describe the context and the pain point. Move from the general (the industry or setting) to the specific (the exact organisation or process you will improve). Example: “Many small clinics still record patient visits on paper, which makes retrieving records slow and error-prone…”
2. Statement of the problem
State the general problem in one sentence, then list specific sub-problems as questions. Example general problem: “There is no efficient system to manage patient records and appointments at the clinic.” Sub-problems: How can the system store and retrieve patient records quickly? How can it prevent double-booked appointments?
3. Objectives of the study
One general objective, then specific objectives that mirror your sub-problems. Make them measurable (use verbs like design, develop, evaluate). Your Chapter 4 results should later answer each one.
4. Scope and limitations
State clearly what the system will do (scope) and what it will not (limitations). This protects you in the defense — you can’t be faulted for leaving out something you explicitly placed out of scope.
5. Significance of the study
List who benefits — the organisation, its staff, its clients, future researchers — and how.
6. Definition of terms
Define technical or domain terms the way you use them in the study.
Common mistakes to avoid
- Objectives that can’t be measured (“to make a good system”).
- Sub-problems that don’t line up with objectives.
- A scope so wide you can’t finish it in a semester.
Ready for the rest? See the full chapter-by-chapter template and pick a topic from our project ideas list.