APS111H1 Chap.1 Engineering Design Process
Engineering Design Process
Engineering Design Process in practice
Treat the project as a chain of justified transformations. A client statement initiates inquiry; it does not settle the problem. Problem definition establishes the need and design criteria, concept development creates alternatives, and selection supports a conceptual design recommendation.
Documentation belongs at every transition because later reviewers need to recover which evidence changed the team's direction and why a discarded path was rejected.
Decision focus: Client statement
The chapter goal is to convert an open-ended request into a record that runs through problem definition, criteria, alternatives and a recommendation, with each link traceable.
In the chapter case, a community client asks for an improvement but describes a preferred device before the underlying need has been tested.
Hold the facts the client supplied apart from the design process interpretation, and state the decision before choosing a method.
Connect Design process to the evidence
Define client statement at the scale of the case, explain the analytical role of design process and use conceptual design to challenge the initial result.
Disconfirming evidence for conceptual design must be named rather than treating the preferred client statement conclusion as fixed.
Boundary for Conceptual design
A polished solution is premature when the problem, evidence and decision criteria have not been made explicit.
The narrower client statement result should remain defensible when the conceptual design boundary is reached, and the chapter must identify what would reopen that decision.
Revision task
Sketch the entire design process as a chain, then annotate each arrow with the evidence required to move forward.
Use a fresh client request and identify where iteration would return the team to an earlier stage.
Failure pattern in Engineering Design Process
A frequent failure is designing the device the client named instead of first removing it from the wording and recording the outcome underneath.
Another failure skips a stage on the map from client statement to problem definition, criteria, alternatives and conceptual recommendation. Teams also lose the thread when handoffs go undocumented, since each handoff deserves a notebook note of evidence, assumptions and a review question.
A weakening observation can tempt a team to restart everything, when only the dependent criteria comparison needs revising and the supported need and scope can stay.
Evidence-led closing move
Before leaving the chapter, draw one arrow per stage and confirm that every arrow carries the evidence justifying the step.
Reconcile the client statement evidence with the conceptual design claim before moving to another design stage.
Transfer beyond the first case
Carry the same reasoning to any new request: the first account a client gives opens the inquiry, and the team still has to define the need, set criteria, generate alternatives and select a concept.
Whatever the project, notes kept at each transition let a later reviewer see which evidence shifted the direction and why a rejected option was set aside.
Chapter vocabulary in use
In use, a client statement is read as the opening account of a request, its context and the client's preferences, all of which need critical interpretation.
Calling the design process iterative means the team can loop back while defining the problem, developing alternatives and building support for a recommendation. A concept counts as a conceptual design once it is developed and described well enough to justify how it is meant to operate and why it was selected.
What this chapter covers
- 01
Client statement
- 02
Design process
- 03
Conceptual design
- 04
Turn an open client request into a traceable sequence of problem definition, criteria, alternatives and recommendation
- 05
A polished solution is premature when the problem, evidence and decision criteria have not been made explicit
Worked example · free
From request to a traceable recommendation
- 2Locate the evidence for client statement.
- 2Explain the role of design process.
- 2Challenge the result through conceptual design.
- 2Close inside the engineering design process boundary.
Key terms
- Client statement
- A client statement is the initial account of a project request, context and preferences that must be critically interpreted.
- Design process
- The design process is an iterative route for defining a problem, developing alternatives and supporting a recommendation.
- Conceptual design
- A conceptual design is a developed solution concept described well enough to justify its intended operation and selection.
Engineering Design Process FAQ
How does client statement change the design decision?
Client statement opens the inquiry rather than settling the decision, so the team drops the preferred device from the wording, records the outcome the community needs and lets that outcome, not the named device, drive problem definition and criteria.
Because the statement is only a starting point, a later observation that weakens the concept sends the team back to the dependent comparison alone, the supported need and scope stay fixed, and the answer stays inside the chapter boundary by naming one feasible next check.
Exam move
Rehearse Client statement
Close your notes and redraw the route from a client request to a conceptual recommendation, writing beside every arrow what evidence lets the team advance.
Afterwards, pick a different request of your own and mark the points where iterating would send the team back a stage.
Review Engineering Design Process
Compare the result with this limit: A polished solution is premature when the problem, evidence and decision criteria have not been made explicit Record the first failed move and the evidence that exposed it.
