Engineering Project
What this domain tests
Engineering Project tests the process of solving a real problem: identifying a need, specifying requirements, planning, building, testing, evaluating and reporting.
Core rules
- Aims are broad intentions; objectives are specific, measurable and time-bound. A specification lists functions, constraints, materials, safety and cost limits.
- Planning tools: Gantt charts show timing; network diagrams (PERT/CPM) show dependencies. The critical path is the longest path through the network and sets the minimum project duration; float is spare time on non-critical activities.
- Design iteration: generate options, evaluate against criteria, select, prototype, test, refine. Record decisions and test data.
- Risk management: identify hazards, rate likelihood and severity, plan controls, review.
- Evaluation compares actual performance with the specification, not with personal opinion. Reports use clear method, results, discussion, conclusion and references.
Worked example
Activities: A (3 days), then B (4 days) and C (2 days); D (5 days) follows both B and C. Path A–B–D = 3 + 4 + 5 = 12 days. Path A–C–D = 3 + 2 + 5 = 10 days. The critical path is A–B–D at 12 days; C has 2 days of total float. Delaying C by 1 day does not delay the project; delaying B by 1 day does.
Traps
Writing an aim as an objective; omitting dependencies from a network; calculating float on the critical path; testing only at the end; ignoring risks; presenting opinions as evaluation; copying sources without citation; leaving out units or sample size in results.