Engineering Design: TExES Technology Education 6-12 171
Pearson Competency 002 treats design as an iterative method for solving technological problems.
- Candidates should connect user needs, criteria, constraints, prototypes, tests, feedback, material properties and communication.
- A strong design is evaluated against evidence and trade-offs, not appearance alone.
- Trace input, process, output and feedback through a new scenario, then revise when testing reveals a gap.
On this page7 sections
Where engineering design appears in the framework
The frozen title Engineering Design maps primarily to Pearson’s Technology Education 6-12 (171) Competency 002: understanding the design process and its application in technology. Its descriptive statements call for recognizing design as systematic and iterative, accounting for human characteristics and ergonomics, analyzing product quality and reliability through the universal systems model, evaluating criteria and trade-offs, using models, communicating designs, identifying material properties, and applying mathematics and science to problems.
Design also connects to the broader exam framework. Competency 001 concerns technology and society; Competency 003 includes system uses, maintenance and impacts; Competency 004 involves planning and managing technology projects. These relationships help explain why design questions may include user needs, safety, resources or consequences. The article focuses on Competency 002, but a design choice rarely exists without a user, system or operating context.
Pearson does not prescribe one universal list of design-process steps. Different teaching models may use different labels, such as define, research, ideate, plan, prototype, test and improve. The framework’s essential point is systematic iteration: identify the problem and criteria, develop and analyze possible solutions, test against evidence, and revise. Learn the logic of a cycle instead of assuming one brand or poster is the only correct sequence.
Translate a need into criteria and constraints
A design problem starts with a need or goal. Convert it into criteria that describe what a successful solution must do. Criteria should be specific enough to evaluate. “It should work well” is vague; “it supports a specified load without slipping” is testable. Constraints limit acceptable solutions. They can include size, cost, materials, time, safety, access, tools, environmental conditions or user capability. A solution must meet critical constraints while performing against its criteria.
Ask who will use the product and in what setting. Human characteristics can affect reach, grip, vision, strength, comfort, language and experience. Ergonomics concerns the fit between people and the designed object or environment. A control that is easy for one user may be inaccessible to another; an interface that is technically functional may still be confusing or unsafe. The problem statement should specify the relevant need rather than treat a single assumed user as universal.
Separate a requirement from a preference. A required dimension or safety condition is a constraint; a preferred finish may be an aesthetic criterion. When requirements conflict, describe the trade-off explicitly. A stronger material may add cost or mass. A lighter structure may need more bracing. Faster production may reduce customization. The designer evaluates compromises against the most important criteria rather than claiming every goal can be maximized simultaneously.
Before generating a solution, identify what evidence would count as success. A measurement, load test, time trial, user observation or comparison with a drawing can make a criterion observable. If the team cannot decide how to test the requirement, the criterion may be too vague. Set the test conditions before testing so that a prototype is judged consistently, not by whichever result the designer prefers.
Use the systems model to analyze the design
Pearson names the universal systems model as input, process, output and feedback. Inputs include materials, energy, information, people and resources. The process transforms or organizes those inputs. Outputs are the product, service or effect. Feedback provides information about performance that can guide control or redesign. A system may also include subsystems and control mechanisms, connecting design work to Competency 001’s systems content.
Consider a school storage device. Its inputs might include a user’s equipment, selected material, fasteners and assembly labor. The process includes measuring, cutting, joining and checking. The output is a device that should hold the equipment and fit a storage space. Feedback comes from a fit check, user handling and a load test. If the device tips or blocks access, that evidence goes back into the design decision rather than being dismissed as a one-time inconvenience.
A control mechanism uses information to adjust system behavior. In a design scenario, a thermostat senses temperature and controls heating, while a person may review test data and change a prototype. Redundancy can provide backup or improve reliability when a component fails, though it may add cost or complexity. When reading an exam problem, trace how the parts contribute to a shared goal and distinguish an input from a process, output or feedback signal.
Prototype, test and revise
A model is a representation of a proposed product or system. It may be physical, mathematical or computer-based. A low-cost physical prototype can reveal fit, balance or ease of use. A mathematical model can estimate load or dimensions. A computer model can help compare geometry or simulate system behavior. Choose a model suited to the question and scale of risk. A representation does not prove that a finished product will perform exactly the same way.
Testing compares observed performance with criteria. Keep the test connected to the need. If the requirement is that a frame support a load, record the load and any deformation. If the requirement concerns user access, observe whether users can reach and operate the control. A test that measures appearance does not establish structural reliability. Use repeatable procedures and record results, including unexpected effects.
Revision should respond to evidence. If a prototype meets the load criterion but fails to fit the storage area, revise dimensions and retest both fit and load. Changing one variable at a time can help determine why performance changed, although complex systems may require a broader redesign. Preserve notes about versions and test conditions so a team can distinguish an improvement from an uncontrolled change.
Reliability and quality involve consistent performance against defined requirements. A prototype that succeeds once under unusually favorable conditions may not be reliable. Consider repeated use, material variation, wear, environment and foreseeable misuse when relevant. Safety matters throughout the design cycle, not as a final checkbox. A design that meets a performance target through an unsafe procedure is not an acceptable success.
Work through an original design example
Problem: A technology class needs a small desktop stand for a tablet used in a display activity. It must fit within a marked 18-centimeter footprint, hold the tablet at a readable angle, remain stable when tapped, use available classroom material, and avoid sharp edges. The students have limited build time. The stand is a classroom project, not a tested commercial product, so the class should make modest claims about its performance.
First define measurable criteria. The stand must fit inside the footprint, hold the tablet at the chosen angle, stay upright during a specified light tap test, and present no sharp edge after inspection. Constraints include material availability and build time. The team should clarify the tablet size and mass, angle target, tap procedure and what “sharp edge” means before building. Otherwise, two prototypes might be judged under different conditions.
Next generate options. A folded sheet, triangular support or slotted frame may all be possible. Select a material based on stiffness, workability, thickness, cost and available tools. A triangular geometry may resist tipping, but it could make access to the charging port difficult. A wide base may improve stability while pushing against the footprint constraint. Sketch dimensions and evaluate each concept against the full criteria, not only its appearance.
Build a simple prototype and test it. Measure the footprint, place the specified tablet, check viewing angle, perform the agreed tap test and inspect edges. Suppose the stand fits and holds the device but shifts when tapped. The feedback identifies a stability gap. Possible revisions include widening the base within the allowed footprint, changing support geometry, adding a non-slip contact surface or adjusting the center of mass. Select one change, record why it should help, then repeat the tests.
This example demonstrates iteration rather than a single best design answer. If a question changes the constraints, the preferred solution may change. A small footprint can limit base width; a different user may need a lower angle; a fragile material may not tolerate a slot. The correct reasoning is to identify the requirements, compare alternatives, test and revise. Do not memorize the stand as the answer to unrelated design problems.
Communicate the design clearly
Competency 002 includes methods for communicating designs. Technical drawings can specify dimensions, materials, components and assembly relationships. Sketches help compare early concepts, while working drawings communicate details needed for construction. Models can demonstrate form or system behavior. A clear explanation identifies the user need, criteria, constraints, chosen design, evidence and remaining limitations. Use the representation that enables another person to evaluate or build the solution.
Communication should make assumptions visible. State units, scale, tolerances and material choices where needed. Label components and show how they connect. If a model is not to scale or a test is limited, say so. A polished rendering may help someone understand appearance, but it cannot replace dimensions or performance evidence. A technically sound design that is not communicated clearly can be misbuilt or evaluated incorrectly.
Team communication also supports iteration. Record decisions and reasons so a later team member can understand why a feature changed. Compare evidence rather than relying on the loudest preference. When users have different needs, gather input systematically and explain whose needs the design addresses. This relates design to collaboration, ethics and social effects while remaining anchored to the specific problem.
Common exam reasoning errors
One error is jumping to a favorite solution before defining the need. Another is treating a criterion and a constraint as identical. A third is choosing the most complex technology without evidence that complexity improves performance. Candidates may also ignore ergonomics, test only one requirement, confuse a model with a finished product, or revise without checking whether the change created a new failure.
When reviewing answer options, ask which option responds to the stated user need and measurable constraints. Eliminate choices that skip testing, ignore safety, or assert success without evidence. If the problem reports a prototype failure, look for a next step that uses the failure as feedback. If the question asks for quality, consider consistency and conformance to requirements rather than appearance alone.
Make a compact review table with need, criteria, constraints, model, test, result and revision. Use it for new scenarios from manufacturing, construction, energy or communication. This reinforces that design is a transferable problem-solving process, not a separate craft detached from the rest of the exam’s technical domains.
Material choice belongs inside the design reasoning. Mechanical properties such as strength, hardness, elasticity and ductility describe different behaviors, while physical and chemical properties can affect density, corrosion or compatibility. Select only the properties relevant to the need and operating conditions. A question may reward recognizing that a material’s strength does not automatically make it lightweight, easy to form or appropriate for every environment.
If two designs both meet minimum criteria, compare reliability, cost, aesthetics and usability against the prompt’s stated priorities.
State why the evidence supports the revision, not merely which feature you prefer.
Compare every option with the stated criteria.
Record the test conditions so results remain comparable.
Common questions
Which TExES 171 competency covers design?
Competency 002 covers the design process, its application, criteria, trade-offs, models, communication and material properties.
Is the design process always a fixed sequence?
No single step-label sequence is specified as universal. Pearson emphasizes a systematic, iterative problem-solving method.
What is the systems model in Competency 002?
It is input, process, output and feedback, used to describe and analyze technological products and systems.
Why are prototypes tested?
Testing compares performance with criteria and supplies feedback for revision. A model or prototype does not automatically prove final-product performance.
What makes a good design answer?
It fits the stated need and constraints, uses evidence, considers safety and trade-offs, and explains how performance will be evaluated.