Engineering Design: Key Concepts and Vocabulary

1.1 Where and When Do Engineers Design?

Engineers design across diverse contexts: containers for new products, highway components, vehicle instrumentation, educational facilities, etc.
Three roles in every design effort: client (wants a design), user (will use the design), designer (solves the client’s problem for the user).
The client motivates the design and opens the design problem; the designer translates client needs into engineering terms; the user’s needs drive the design’s usefulness.
In many projects, roles may merge (e.g., a founder/designer who also acts as the client), but distinguishing client, user, and designer helps identify responsibilities and communication needs.
The user has a stake because designs must meet user needs; the client represents the user in many cases; the public may also be affected, especially in public projects (ethics considerations).
The designer–client–user triangle highlights potential conflicts among interests; trade-offs among design variables (e.g., material choice, thickness) can lead to ethics considerations.
Ethics: designers have obligations to clients, users, the profession, and the public; ethics issues are integral to design (Chapter 17).
Teams are common; many problems are multidisciplinary; large projects may focus on sub-systems while system-level design guides overall context.
Early design is conceptual; large projects show different interpretations of the same design statement (e.g., airplanes, wheelchairs) depending on mission and user needs.

Engineering design defined as a systematic, intelligent process in which engineers generate, evaluate, and specify solutions for devices, systems, or processes whose form and function achieve clients’ objectives and users’ needs while satisfying constraints.
Artifacts: devices, systems, or processes; can be physical objects or papers/software representing designs.
Design objective: a feature or behavior we wish the design to have or exhibit.
Design constraint: a limit or restriction on design features/behaviors; binary in nature (satisfied or not).
Functions: what a designed device/system is supposed to do; often involve transforming/transferring energy, information, or material.
Means: a way or method to make a function happen (e.g., friction as a means to apply braking).
Form: the shape/structure of something, distinct from its material; form is important in industrial/product design but not always the focus.
Objectives vs. constraints: objectives may be partially or fully unmet; constraints must be satisfied for a design to be acceptable.
Engineering design is systematic and intelligent, not purely formulaic; tools and methods support creative thinking and decision-making.

Design is a thoughtful, teachable process; tools support thinking, decision-making, and project management.
Formal methods for generating design alternatives stem from the need to clarify what a client wants (objectives), needs (constraints), and intended functions.
The design process begins with a client problem statement and ends with a functionally complete design.

Metric: a standard of measurement to assess how well objectives are met; used to quantify design progress.
Specifications: engineering statements of the extent to which a design’s functions are performed; used to express performance levels and requirements.
Requirements vs specifications: requirements = client objectives, constraints, and functions; specifications = designer’s expressions of how the design will perform.
Vocabulary can vary by discipline; in this text, we map requirements to client statements and specifications to engineering statements, with deeper discussion in Chapters 2 and 5.

Form and function are related but independent.
Function is not deducible from form; you cannot infer a device’s function from its shape alone (e.g., you can’t deduce smartphone’s function simply from its form).

No thing stands alone; designs operate within environments and interface with other devices.
Simon’s definition: design describes an artifact in terms of its organization and functioning—its interface between inner and outer environments; design is inherently systems-based.
Modern challenges emphasize large, complex engineering systems (e.g., interstate highways, power grids, the Internet) requiring systems thinking.

Communication is central throughout the design process; a shared language/representation is needed from problem statement to fabrication specs.
Fabrication specifications must be complete and unambiguous to realize the designer’s intent; failure to communicate intent can cause catastrophic outcomes (Hyatt Regency example).
Separation of designing from making can cause mismatch; involving fabricators early (design for manufacturing) helps ensure producibility.
There has been a shift toward integrating manufacturing considerations into the design phase; this fosters better alignment between design intent and fabrication capabilities.
Design is a human, social activity requiring ongoing communication among stakeholders.

Design problems are ill-structured: solutions cannot be found by simple formulas or routine methods.
Design problems are open-ended: several acceptable solutions may exist; there is no single universally best solution.
Examples (e.g., ladder designs) illustrate how purpose, use, materials, cost, and load considerations interact and why universal optimality is elusive.

Design education often uses a studio approach: learning by doing, with demonstrations, drills, and practice.
Knowledge in design combines tacit (unspoken) know-how with explicit understanding; practitioners rely on coaching and collaboration to improve both technical and interpretive aspects of design.
A key measure of mastery is being a "student of the game"—continuous learning through practice and reflection.

Good design results from careful consideration of client and user needs and explicit design requirements.
The book introduces management tools to support design thinking and project execution.
The 3S model of project management: Scope, Schedule, Spending.
- Scope: what a project must accomplish to be successful.
- Schedule: availability and use of resources to meet the due date.
- Spending: using only necessary resources to complete the project on time.
Tools exist to define work, schedule tasks, assign responsibilities, and monitor progress and expenditures.
In design, which is open-ended, PM tools are helpful but only partially applicable; the focus is on tools useful for small design teams.

The chapter builds a common vocabulary and frames design as a system, communication-centric, and multiparty process; sources include Dym, Levitt, and Simon’s design theories; real-world failures (e.g., Hyatt Regency) illustrate the stakes of clear design intent and fabrication communication.