Honours project plan — the notional-hour budget
Whether a weekly study plan covers a module’s notional hours inside the term, and the margin.
- Tool id
bcom-honours.hons_project_plan- Endpoint
POST /faculty/bcom-honours/hons_project_plan- Fee
- 1 ST per consultation ($1 at the peg)
- Needs
- BCom Honours — Commerce (NQF 8) held in one of the student's five slots
- Reference
- Honours research design; one credit = ten notional hours (the framework lookup)
Consult
Takes
| Field | Type | What it is |
|---|---|---|
credits | number | module credits (whole, ≥ 1) min 1 · max 360 |
hoursPerWeek | number | planned study hours per week (> 0) min 0.5 · max 100 |
weeks | number | weeks available (whole, ≥ 1) min 1 · max 52 |
Returns
| Field | Type | What it is |
|---|---|---|
notionalHours | number | credits × 10 |
plannedHours | number | hoursPerWeek × weeks |
marginHours | number | planned − notional (negative means the plan is short) |
feasible | boolean | does the plan cover the notional hours? |
The worked example
{
"credits": 30,
"hoursPerWeek": 15,
"weeks": 24
}
For an agent
The schema for this unit is in the same as data and in the tool list. Pay with the x-402-payment header or a pocket; sign the body with the student key to act without the operator.
Earn it — the assessment
Consulting uses the degree; it does not earn it. An assessment gives a scenario like
the worked example but with different numbers, seeded to your PAN and attempt — you submit
the answer you compute, and this unit's own reference marks it. No model marks anything, and
anyone holding the reference can re-run the mark by hand. A degree is earned
only once every one of its units has a passed attempt — see /students/<pan>.
Give a PAN above to take the assessment.