Sources and References

• Dym, Little, and Orwin, Engineering Design: A Project-Based Introduction (Wiley)
• Ulrich and Eppinger, Product Design and Development (McGraw-Hill)
• Buxton, Sketching User Experiences (Morgan Kaufmann)
• IDEO, The Field Guide to Human-Centered Design
• Brown, Change by Design (Harper Business)

Chapter 1: Design as a Discipline

1.1 What Design Is

Engineering design creates artefacts, systems, or processes to meet human needs within technical, economic, environmental, and ethical constraints. Unlike analysis, which seeks the unique answer to a bounded question, design confronts problems with many solutions, ambiguous requirements, and trade-offs that require judgment. Designers weigh fitness-for-purpose, manufacturability, cost, sustainability, and user experience simultaneously.

1.2 Design Processes

The classical iterative model moves through stages of need identification, problem framing, concept generation, selection, detailed design, prototyping, testing, and implementation. Human-centered design adds that each stage be grounded in user empathy and stakeholder participation. Systems design further expects that the artefact sits in an organisational and ecological context that shapes its performance. No design process is strictly linear; good designers cycle between stages as insight accumulates.

Chapter 2: Understanding Problems and Users

2.1 Needs Assessment

Needs assessment begins with identifying stakeholders — primary users, secondary users, those affected but not using, regulators, funders. Ethnographic methods (observation, shadowing, contextual interviews) reveal what people do, complementing surveys that capture what they say. Journey mapping and service blueprints externalise workflows and pain points across time.

2.2 Framing and Problem Statements

A well-framed problem statement includes a specific user, a context, a need or goal, and relevant constraints. “How might we help elderly residents move safely between floors without reliance on others?” directs design more usefully than “design a better stair lift.” Multiple reframings expose hidden assumptions about who, what, and why.

Chapter 3: Ideation and Concept Development

3.1 Divergent and Convergent Thinking

Design alternates between divergent phases — generating many ideas without judgment — and convergent phases where ideas are filtered and combined. Brainstorming, brainwriting, SCAMPER, analogy mapping, and morphological analysis support divergence. Weighted matrices, Pugh charts, concept screening and concept scoring support convergence.

3.2 Specifications

Design specifications translate user needs into measurable engineering targets. A cantilever crutch for mountain use must support 120 kg, weigh less than 0.8 kg, fit into a 60 cm pack, and cost under $100. Metrics must be measurable, fall within achievable ranges, and be verifiable by testing. Ill-specified projects drift and over-specified projects lose creative headroom.

3.3 Concept Generation

Early concepts live as sketches, storyboards, and cardboard mock-ups. “Low-resolution prototyping” is cheap, fast, and invites feedback from users without implying commitment. Generating multiple concepts per team member mitigates anchoring on the first idea; structured variation (changing one aspect at a time) explores the solution space more systematically.

Chapter 4: Prototyping and Testing

4.1 Types of Prototypes

Prototypes answer specific questions: feasibility, usability, desirability, performance. Appearance prototypes communicate form; functional prototypes test behaviour; role-playing enacts workflows; digital mock-ups (CAD, wireframes) explore geometry and interaction. Fidelity should match the question, not ambition. A paper prototype can reveal navigation issues that a polished app obscures.

4.2 Testing

User testing observes representative users attempting representative tasks, recording performance metrics (time, errors, task completion) and subjective impressions. Think-aloud protocols surface mental models. Five users typically uncover roughly 85% of usability issues with a single iteration; iteration between testing and refinement often matters more than sample size.

Functional testing against engineering specifications uses instrumentation — load cells, cameras, accelerometers — to quantify performance. Statistical design of experiments makes testing efficient when multiple variables interact.

Chapter 5: Verification, Validation, and Professional Practice

5.1 V&V

Verification confirms that the artefact is built right — meeting its specifications. Validation confirms that the artefact solves the original user problem — that the specifications were the right ones. Verification can be done in lab; validation demands real-world or near-real-world deployment. Many engineering failures reflect successful verification of incorrect specifications.

5.2 Engineering Professionalism

Professional engineers hold obligations to the public, employer, colleagues, and profession. Licensing and codes of ethics (PEO in Ontario, IEEE Code of Ethics, ACM Code) formalise expectations: public welfare paramount, competence within area of practice, honest representation of work, protection of confidentiality, avoidance of conflicts of interest. Engineering design that ignores these dimensions exposes users and the environment to risk and the engineer to liability.

5.3 Project Management

Design projects require time, cost, and scope management. Gantt charts, critical-path analysis, and burndown charts help teams plan, track, and communicate. Agile practices — sprints, daily stand-ups, retrospectives — handle rapidly evolving requirements. Team dynamics (Tuckman’s forming-storming-norming-performing, psychological safety, shared leadership) determine whether a competent team succeeds or stalls. Documentation and reproducibility protect future maintainers and customers.

Chapter 6: Design in Context

6.1 Human-Centered Design

Human-centered design (HCD) keeps users central throughout. Empathy — genuinely understanding a user’s lived experience — is the cornerstone. Accessibility, inclusivity, and equity should shape design from the start rather than as afterthoughts; universal design benefits all users, not only those with disabilities.

6.2 Systems Perspective

Artefacts live in systems: social, economic, technical, and environmental. A solar water pump is not only a pump but part of a livelihood, a local economy, and an ecosystem. Systems-level thinking identifies stakeholders beyond direct users, anticipates unintended consequences, and considers life-cycle impacts. Failure modes often emerge at boundaries between components, disciplines, or organisations.

6.3 Ideation, Prototyping, and Iteration

Successful design projects share a rhythm: understand deeply, reframe generously, ideate broadly, prototype quickly, test with real users, synthesise honestly, iterate. Milestones (concept review, design review, critical design review) provide checkpoints. Design review panels catch blind spots and align stakeholders. Documentation of rationale, not just final specifications, supports future change.

6.4 The Team-Based Design Project

The hallmark of introductory design courses is a semester-long, team-based project. Teams of four or five select or are assigned a real problem — a device for an accessibility user, a community energy issue, a sports-equipment need — and cycle through needs assessment, specifications, concept selection, prototyping, verification, and validation. Documents (requirements, concept selection, test plans, final report), artifacts (working prototype), and presentations (pitch, demo) give structure. The ultimate learning is the integration of analysis, synthesis, teamwork, and professional communication into a coherent engineering practice.