Consider the statement: “Computation (calculations) and design sketches may be considered technical drawings.” Decide whether this is correct, noting that calculations themselves are not drawings while properly annotated sketches are part of technical drawing practice.

Introduction / Context:
Technical drawings communicate geometry, size, tolerances, finishes, and other manufacturing or construction requirements using standardized conventions. The statement groups computations with design sketches and claims both may be considered technical drawings. We examine why this is not correct.

Given Data / Assumptions:

• Computation: numbers, formulas, and results—no graphical projection.
• Design sketch: freehand but conveys geometry, proportion, and intent.
• Technical drawing: graphical representation using views, dimensions, and symbols.

Concept / Approach:
Sketches can be part of the technical drawing workflow (especially “technical sketching”). Computations support design decisions but are not themselves drawings because they lack the graphical conventions of orthographic, isometric, sectioning, and dimensioning.

Step-by-Step Solution:
1) Define “drawing”: a graphical medium that uses projection and dimensioning.2) Classify sketches: when they depict geometry and include dimensions/notes, they function as preliminary technical drawings.3) Classify computations: purely textual/numerical, so not drawings.4) Because the statement claims both computations and sketches may be considered drawings, it is overall incorrect.

Verification / Alternative check:
Standards emphasize lines, symbols, and views; calculations are attached as supporting documents (e.g., calculation packages), not drawings.

Why Other Options Are Wrong:
“Correct”: Would incorrectly elevate calculations to drawings.“Only computations qualify as drawings”: Incorrect by definition.“Only sketches qualify as drawings”: Partially true for sketches, but the statement in question bundled computations, so overall evaluation is “Incorrect”.

Common Pitfalls:
Treating any design artifact as a “drawing”; blurring document roles can cause QA issues during reviews and approvals.

Final Answer:
Incorrect