What does NESA expect in an engineering report, and how do drawing and diagram conventions support engineering communication?
Investigate the structure and purpose of engineering reports in HSC Engineering Studies, the Australian drawing standards (AS 1100 series, orthographic projection, IEC circuit symbols), block diagrams and data sheets, and the application of these conventions to a telecommunications subsystem
A focused HSC Engineering Studies answer on engineering reports. Mandatory NESA report structure, AS 1100 drawing conventions, first-angle orthographic projection, IEC 60617 circuit symbols, block diagrams, data sheets, and a worked telecommunications-subsystem example.
Reviewed by: AI editorial process; not yet individually human-reviewed
Have a quick question? Jump to the Q&A page
Jump to a section
What this dot point is asking
NESA's Engineering Studies syllabus makes engineering reports mandatory school-based components: one per HSC module, with at least one in Year 12 contributing 20 percent or more of the school-based assessment mark, and at least one HSC report completed collaboratively. The HSC written exam also tests the communication skills the reports develop, including diagram interpretation, calculation presentation, and structured argument. This dot point covers the report structure NESA expects, the Australian drawing standards (AS 1100 series), the circuit and block-diagram conventions, and how to apply them to a telecommunications subsystem.
The answer
Why engineering reports exist in the HSC
The 2011 Engineering Studies syllabus treats the engineering report as the way students demonstrate the full engineering method: define a problem, research, calculate, design, evaluate, communicate. Band 6 performance band descriptors require students to "construct and evaluate engineering reports in order to recommend and predict solutions to engineering problems". The reports also build the technical-writing skills the HSC written paper rewards in longer-response questions.
Mandatory report structure
A typical NESA-compliant engineering report follows this skeleton:
- Title page. Project name, author, school, date, module.
- Executive summary or abstract. A short paragraph stating the problem, approach and main conclusion.
- Introduction. Background, scope, why the project matters.
- Aim. A single sentence describing what the report sets out to achieve.
- Background research. Literature and prior-art review; existing solutions; standards that apply.
- Method. What the engineer did, step by step.
- Calculations. Force balances, electrical analyses, signal budgets. Each calculation shows formula, substituted values, units, and answer to appropriate precision.
- Technical drawings. Orthographic views, assembly drawings, circuit schematics, block diagrams.
- Materials and components list. What was used, with quantities and references to data sheets.
- Results. What was observed or measured.
- Discussion / Evaluation. What the results mean; how the design met the aim; what would be done differently.
- Conclusion. A short restatement of outcome and significance.
- References. All sources, including standards (cite by number, e.g. AS 1100.101-1992).
- Appendices. Raw data, full drawings, source code, data sheets.
The expected length and depth vary by school and weighting, but the structure above is the conventional template.
Drawing conventions: AS 1100 series
The Australian Standard AS 1100 series governs technical drawing in Australia. The relevant parts for HSC students:
- AS 1100.101. General principles: paper sizes, scales, line types, lettering, title blocks.
- AS 1100.301. Mechanical engineering drawing: orthographic views, sectional views, dimensioning, surface texture.
- AS 1100.401. Engineering survey drawing.
- AS 1100.501. Structural engineering drawing.
Key conventions students must apply:
- Orthographic projection (first-angle). Australia uses first-angle projection: the views (front, top, side) are arranged with the top view below the front, the right side view to the left of the front, etc. (This contrasts with third-angle projection used in the United States.) A symbol on the drawing identifies which projection has been used.
- Line types. Continuous thick (visible edges); continuous thin (dimensions, leaders); dashed (hidden edges); chain (centrelines, axes); chain-thick (cutting planes).
- Dimensioning. Dimensions in millimetres unless otherwise stated; arrowheads; clear separation from the object; consistent placement.
- Title block. Bottom-right, with drawing title, drawn-by, checked-by, date, scale, drawing number.
The diagram below shows the standard first-angle arrangement: the object is imagined sitting inside a glass box, and each view is projected onto the box wall behind it, so the top view lands below the front view and the side view lands on the side it was viewed from.
Circuit diagram conventions: IEC symbols
Electrical and electronic schematics use IEC 60617 symbols (International Electrotechnical Commission). Selected examples HSC students should recognise:
- Resistor: a rectangle (IEC) or zig-zag (older ANSI style; either is usually accepted at HSC level if consistent within the drawing).
- Capacitor: two parallel lines (non-polarised) or one straight line plus one curved (polarised electrolytic).
- Inductor: a series of arches or a coil symbol.
- Diode: triangle pointing into a bar.
- Transistor: circle with three connections (emitter, base, collector) and direction-of-current arrow.
- Operational amplifier: triangle with positive and negative inputs and a single output.
- Ground: horizontal lines decreasing in length.
- Connection / no-connection at crossing wires: a dot indicates a junction; no dot indicates the wires cross without connection.
Schematic conventions: signal flow generally left-to-right; power supplies at the top, ground at the bottom; component values and reference designators next to each part.
Block diagrams
A block diagram abstracts a system into functional rectangles connected by arrows showing signal flow. Block diagrams are the right tool when:
- A schematic would have too many components to be readable.
- The intended audience is non-specialist.
- The design is at the architecture stage rather than the implementation stage.
Each block carries a clear functional label (e.g. "Low-noise amplifier", "ADC", "Channel encoder"). Arrows are labelled with the signal name and, where relevant, the data rate or signal level.
Data sheets
A data sheet is the manufacturer's technical specification for a component (transistor, op-amp, antenna, integrated circuit). HSC students should know how to read a data sheet:
- Maximum ratings. Voltages, currents, temperatures that must not be exceeded.
- Electrical characteristics. Typical and worst-case parameters at specified conditions.
- Application circuits. Suggested usage patterns.
- Mechanical drawings. Package dimensions, pin numbering.
A report that selects a component from a data sheet should cite the part number and the relevant parameter (e.g. "selected 2N3904 for the input buffer because the data sheet specifies hFE >= 100 at IC = 10 mA, satisfying the design requirement").
Examples in context
Example 1. A collaborative report on a small antenna design. A pair of HSC students design and test a quarter-wave monopole for a 433 MHz remote-control link. The collaborative report divides labour: one student handles the electromagnetic design (length, ground-plane size, expected radiation pattern) with calculations referencing standard antenna theory; the other handles the PCB layout and measurement (S11 return-loss measurement with a vector network analyser, if available, or a spectrum-analyser-based check). Both contribute to the evaluation and conclusion. The report meets NESA's collaborative requirement and demonstrates the team-engineering outcome (H5.1).
Example 2. An individual report on a fibre-optic transmitter PCB. A student designs a small PCB combining a microcontroller, an SFP fibre transceiver, and the requisite power supply and decoupling. The report includes a block diagram (microcontroller, encoder, SFP, power supply); the circuit schematic in IEC symbols; the PCB layout drawings to AS 1100.101 conventions; selected component data-sheet excerpts; and the test results. The same project would be infeasible without the drawing and circuit conventions to communicate the design clearly to the assessor and to peers who reviewed the work.
Try this
Q1. List five required components of a NESA engineering report. [5 marks]
- Cue. Any five of: aim; background research; method; calculations; technical drawings; results; evaluation / discussion; conclusion; references. Markers expect the student to know the report is more than a method-results pair.
Q2. Distinguish a block diagram from a circuit schematic, and identify a situation where each is the appropriate communication tool. [4 marks]
- Cue. Block diagram: rectangles labelled with function (LNA, mixer, ADC) connected by arrows; abstracts the architecture without component-level detail. Right tool for system overview, non-specialist audience, design-architecture stage. Circuit schematic: every component drawn with its IEC symbol, with reference designators and values; specifies the implementation. Right tool for assembly, debugging, and demonstrating that the design is realisable. A report on a complex system typically includes both: a block diagram up front, schematics in the detailed sections.
Q3. Describe the role of AS 1100 in engineering communication, and identify three specific conventions an HSC student must apply in a telecommunications-subsystem drawing. [6 marks]
- Cue. AS 1100 is the Australian Standard for technical drawing; it sets the conventions that make a drawing legible across organisations and over time. Three specific conventions: (1) First-angle orthographic projection with the appropriate symbol identifying the projection. (2) Line types distinguishing visible edges (thick continuous), hidden edges (dashed), and centrelines (chain). (3) Dimensioning in millimetres unless otherwise stated, with dimensions on the most informative view and arrows / leaders following the standard. Also acceptable: title block at bottom-right with drawing number, scale, drawn-by, date; lettering style; standard paper sizes (A4, A3, A2). The exam looks for evidence the student knows the conventions exist and can name specifics.
Exam-style practice questions
Practice questions written in the style of NESA exam questions on this dot point, with worked answer explainers. The year tag is the paper they imitate, not the source.
2023 HSC3 marksDraw the symbols which match the electronic components named in the table: open switch, power cell, light emitting diode, resistor, light dependent resistor, NPN transistor, capacitor.Show worked answer →
This 3 mark question tests standard electronic schematic symbols. Use current conventions, not outdated ones.
- Open switch: a break in the line with a hinged lever that does not touch the second contact.
- Power cell: a long thin line (positive) and a short thick line (negative).
- Light emitting diode (LED): a diode triangle and bar with two small arrows pointing away from it.
- Resistor: a plain rectangle (do NOT use the old jagged zig-zag line, which markers penalise).
- Light dependent resistor (LDR): a resistor rectangle inside a circle with two arrows pointing towards it.
- NPN transistor: a circle with base, collector and emitter, the emitter arrow pointing away from the base.
- Capacitor: two parallel lines of equal length.
Markers reward correct, current AS style symbols and deduct for outdated symbols such as the jagged resistor.
Practice questions
Original practice questions graded from foundation to exam level, each with a full worked solution. Try them before revealing the solution.
foundation3 marksState three sections a NESA engineering report must include beyond a simple method-and-results structure, and explain what each contributes.Show worked solution →
Any three of the following, each with its contribution:
- Background research: reviews existing solutions and relevant standards, showing the design is informed rather than arbitrary.
- Evaluation/discussion: judges whether the design met the aim and identifies what would be done differently, going beyond stating raw results.
- Conclusion: restates the outcome and its significance concisely for a reader who may only read this section.
Marking criteria: 1 mark per correctly identified section with a valid one-line explanation of its contribution (up to 3 marks); no marks for sections that are just "method" or "results" restated.
foundation4 marksA drawing shows an object outline in a continuous thick line, a dashed line around a hidden hole, and a long-short-long dashed line through the centre of a circular feature. Identify each line type and state what it represents under AS 1100.Show worked solution →
- Continuous thick line: represents a visible edge or outline of the object.
- Dashed line (short, evenly spaced dashes): represents a hidden edge, in this case the hole's edge not visible from the drawn view.
- Chain line (long-short-long dashes): represents a centreline, here the axis of the circular feature.
Marking criteria: 1 mark for each correctly named line type (3 marks), 1 mark for correctly stating what all three collectively achieve, i.e. distinguishing visible geometry from hidden geometry and symmetry axes without needing a written note on the drawing.
core5 marksA data sheet extract for two candidate transistors is shown below for a telecommunications subsystem input buffer that must handle a collector current of 15 mA at a supply of 9 V. Using the data, select the suitable component and justify the choice with reference to the maximum ratings.
| Parameter | Transistor X | Transistor Y |
|---|---|---|
| Max collector-emitter voltage (Vceo) | 40 V | 6 V |
| Max collector current (Ic max) | 200 mA | 500 mA |
| hFE (typical, at Ic = 10 mA) | 120 | 300 |
| Max power dissipation | 350 mW | 200 mW |Show worked solution →
Step 1: check each rating against the design requirement.
The subsystem needs V and mA continuous.
- Transistor Y has V, which is below the 9 V supply rail. Operating it here would exceed its maximum rated voltage, risking breakdown. Transistor Y is therefore unsuitable regardless of its higher hFE and current rating.
- Transistor X has V, comfortably above 9 V, and mA, comfortably above the 15 mA requirement.
Step 2: check power dissipation.
This is below Transistor X's 350 mW maximum, with reasonable margin for thermal safety.
Step 3: select and justify. Transistor X is the correct choice. Its and maximum ratings both exceed the operating point with margin, and the calculated power dissipation (135 mW) sits well within its 350 mW limit. Transistor Y's voltage rating is exceeded by the supply rail alone, disqualifying it despite its higher gain.
Marking criteria: 1 mark for identifying Transistor Y as unsuitable (voltage rating exceeded), 1 mark for identifying Transistor X's ratings exceed requirements, 1 mark for correctly calculating power dissipation with units, 1 mark for comparing dissipation to the rated maximum, 1 mark for a clear final justified selection with a data-sheet citation.
core5 marksDistinguish a block diagram from a circuit schematic as communication tools, and identify which is appropriate at (a) the concept-design stage of a telecommunications subsystem and (b) the assembly/debugging stage, with reasons.Show worked solution →
A block diagram abstracts a system into labelled functional rectangles (e.g. "LNA", "mixer", "ADC") joined by arrows showing signal flow, without specifying individual components. A circuit schematic shows every component with its IEC 60617 symbol, reference designator and value, specifying exactly how the design is implemented.
(a) Concept-design stage. A block diagram is appropriate. At this stage the engineer is deciding the system architecture (which functional stages are needed and how signals flow between them) rather than the exact components; a schematic would be premature and would obscure the architecture with implementation detail not yet decided.
(b) Assembly/debugging stage. A circuit schematic is appropriate. Building and troubleshooting requires knowing exactly which component sits where, its reference designator, and its value, information a block diagram deliberately omits.
Marking criteria: 1 mark for correctly defining a block diagram, 1 mark for correctly defining a schematic, 1 mark for correctly justifying the block diagram at concept stage, 1 mark for correctly justifying the schematic at assembly stage, 1 mark for explicitly contrasting abstraction level as the reason (not just "one is simpler").
core6 marksA student's engineering report on a fibre-optic transmitter PCB includes only a parts list and a photograph of the finished board, with no block diagram, schematic or orthographic drawing. Explain three specific ways this report fails to meet AS 1100 and NESA communication expectations, and describe what should be added.Show worked solution →
- Failure 1: no block diagram
- Without a block diagram (e.g. microcontroller, encoder, SFP transceiver, power supply), a reader cannot quickly understand the system architecture or signal flow before drilling into detail. Add a block diagram with labelled functional stages and arrows showing signal direction.
- Failure 2: no circuit schematic
- A photograph does not specify component values, reference designators, or connections in a way that lets another engineer verify, rebuild or troubleshoot the design. Add a schematic using IEC 60617 symbols with reference designators (e.g. R1, C1, U1) and values next to each component.
- Failure 3: no orthographic PCB layout drawing
- Without dimensioned orthographic views (to AS 1100.101/.301, first-angle projection, correct line types, dimensions in millimetres, title block bottom-right), manufacturing or replicating the board precisely is not possible from the report alone.
Marking criteria: 1 mark for each correctly identified failure (3 marks) and 1 mark for each correctly described remedy (3 marks); full marks require reference to the specific AS 1100/IEC 60617 convention missing in each case, not a general "needs more diagrams" answer.
exam8 marksEvaluate the effectiveness of engineering reports, as structured by NESA, in preparing students for professional engineering communication, using the passive RF filter project as your example. Your response should address report structure, drawing/circuit conventions, and the evaluation section.Show worked solution →
This 8-mark EVALUATE question rewards a judgement supported by specific evidence from the report structure, not a description alone.
Plan.
- Thesis: the NESA structure mirrors professional practice (research, calculation, communication, evaluation), though school reports are smaller in scope and lower-stakes.
- Background research into filter topologies (Butterworth vs Chebyshev vs elliptic) mirrors an industry prior-art review before committing to a design.
- Calculations with substituted units (nH, pF) and predicted attenuation mirror the traceable, checkable working an industry reviewer expects.
- AS 1100 PCB layout drawings and IEC 60617 schematics with reference designators are the exact notation a manufacturing team would need.
- Comparing measured to predicted results and naming discrepancies (component tolerances, PCB parasitics) mirrors the professional habit of accounting for the sim-versus-build gap.
- Limitation: school reports are usually completed alone or in pairs over weeks, so formal design reviews and compliance sign-off are only approximated.
Model paragraph (excerpt). The NESA structure prepares students for professional communication because it enforces the same sequence an engineer follows under review: justified background (comparing filter topologies), traceable calculations with units, and drawings using standard notation (AS 1100, IEC 60617) a reviewer or manufacturer would expect. The evaluation section is the clearest parallel: comparing measured insertion loss against the predicted response and attributing the gap to component tolerance and PCB parasitics teaches the habit central to engineering sign-off. The main limitation is scale: a single report cannot replicate a multi-person design review, so it approximates rather than fully reproduces professional communication.
Marking criteria: top-band answers (1) state an explicit judgement, (2) tie at least three report elements to a professional-practice parallel, (3) use accurate RF filter detail (topology names, units, named discrepancy sources), (4) acknowledge a genuine limitation.
