Scope & Limitation
Scope says what the study WILL cover. Limitation says what it explicitly will NOT cover. Both protect you during defense.
Scope and Limitation
What this section does
Defines the boundary of the study so the panel cannot ask 'why did you not include X?' - because you stated upfront that X is out of scope, and why.
Scope vs Limitation - side by side
| Dimension | Scope (will do) | Limitation (will NOT do) |
|---|---|---|
| Functional | Ordering, inventory, SMS notification | Accounting, payroll |
| User | Owner, 3 staff, customers | Multi-branch managers |
| Geographic | Sample City branch | Multi-branch rollout |
| Time | Jan-Apr 2026 | Holiday-season-specific testing |
| Technical | Desktop + tablet browsers | Native mobile app |
Why each limitation must have a reason
| Weak limitation | Strong limitation (with reason) |
|---|---|
| No time | One-semester timeline; mobile app deferred to future work |
| Did not want to | Bakery accepts cash only; payment integration unnecessary |
| Too hard | Accounting requires CPA validation - out of student scope |
Worked example paragraphs
Scope:
The study covered the design, development, and acceptance evaluation of a web-based ordering and inventory management system for Sample Bakery Shop in Sample City. The system was developed for use by the bakery's owner, three counter staff, and customers placing online orders. Data were collected from January to April 2026 through interviews and a 30-respondent acceptance survey. The system targets modern desktop and tablet browsers.
Limitation:
The system did not include accounting or payroll modules, which require CPA-licensed validation. A customer-facing mobile application was not developed within the one-semester timeline. Payment integration was out of scope because the bakery accepts cash and bank transfer on pickup. Findings are limited to Sample Bakery Shop and are not generalisable to multi-branch chains without further study.
Panel defense checklist
- [ ] Scope covers functional, user, geographic, time, and technical bounds.
- [ ] Each limitation has a justification (not 'no time').
- [ ] No surprise additions in Chapter IV that were not in the scope.
- [ ] Limitations align with what is acknowledged as future work in Chapter V.
- [ ] No defensive over-limitation that makes the project look trivial.
Mentor’s tip: Scope is the in. Limitation is the out, with reasons. Every limitation should map to a Future Work bullet in Chapter V. Weak excuses like time will not survive panel scrutiny.
Discussion
Loading…