Prototype Study Guide

📖 Core Concepts Prototype – an early model or sample built to test a concept, design, or process before full production. Purpose – evaluate feasibility, gather user feedback, expose design flaws, and refine specifications. Workflow Position – sits between idea formalization and formal evaluation in most design processes. Prototype vs. Final Product – prototypes use cheaper materials & low‑volume fabrication; final products use production‑grade materials & mass‑production processes. Rapid Prototyping – quick, low‑cost creation of a partial design to test critical problem areas early. Virtual Prototype – a computer‑based model that simulates physical behavior (e.g., CAD‑driven crash or airflow studies). 📌 Must Remember Proof‑of‑Principle: proves a key function, not full product. Working Prototype: includes all or nearly all final functionality. Visual Prototype: shows size/appearance only; no functional performance. User‑Experience (UX) Prototype: enough look + function for user testing. Functional Prototype: combines function and appearance, may be built at different scale/technique. Paper Prototype: hand‑drawn UI used for early software design walkthroughs. Technology Demonstrator = proof‑of‑concept prototype for a new tech. Testbed = platform for systematic experimentation with new components or theories. Wizard of Oz = “fake” computer side, hidden human performs actions. 🔄 Key Processes Prototype Development Cycle Listen → gather stakeholder/user needs. Build → create appropriate prototype type (paper, visual, functional, etc.). Test → run user research, functional checks, or simulation. Refine → revise design based on feedback, repeat as needed. Rapid Prototyping Workflow Identify high‑risk area → select low‑fidelity prototype → test quickly → decide to keep, modify, or discard. Electronics Prototyping Steps Breadboard → verify circuit logic. Transfer to prototype PCB (stripboard/perfboard) → test under realistic conditions. Finalize layout → move to production PCB. Software Prototyping Stages Alpha: core functions only, internal testing. Beta: most features integrated, broader testing. 🔍 Key Comparisons Proof‑of‑Principle vs. Working Prototype Goal: concept validation vs. near‑complete functionality. Scope: limited features vs. full feature set. Paper Prototype vs. Digital UI Mockup Medium: hand‑drawn paper vs. screen‑based design tool. Speed: ultra‑quick, low‑cost vs. requires software setup. Visual Prototype vs. Functional Prototype Appearance: visual only vs. both look and operation. Testing: aesthetic feedback only vs. functional performance testing. Wizard of Oz vs. Fully Automated Prototype Human In‑the‑Loop: hidden operator vs. real software/hardware. Use Case: early UI concepts (e.g., voice) vs. mature, testable system. ⚠️ Common Misunderstandings “Prototype = final product” – prototypes are intentional compromises; they may use different materials and processes. “If a prototype works, the final product will work” – performance can differ due to material, scale, or manufacturing changes. “Only physical prototypes matter” – virtual prototypes can replace many physical tests, especially for aerodynamics or crashworthiness. “Higher fidelity always better” – low‑fidelity (paper) prototypes are faster for early user feedback; over‑engineering early wastes time. 🧠 Mental Models / Intuition “Sandbox” Model – think of a prototype as a sandbox where you can break things without costly consequences. “Scale‑Down, Cost‑Down” – prototypes shrink size/material cost to let you explore what could be before committing to what is. “Iterative Funnel” – each prototype iteration narrows design options, like a funnel concentrating ideas toward the final product. 🚩 Exceptions & Edge Cases Regulatory Prototypes – some industries (medical, aerospace) require validated prototypes that meet stricter standards, blurring prototype/final lines. Material Substitution Limits – substituting a cheap material may misrepresent thermal or structural behavior; use simulation to compensate. Virtual Prototypes Only – when physical testing is impossible (e.g., space hardware), virtual prototypes become the primary validation tool. 📍 When to Use Which Early Conceptual Phase → Paper or low‑fidelity visual prototype. User Interface Design → Paper → interactive digital mockup → Wizard of Oz for voice/AI. Critical Functional Validation → Proof‑of‑Principle → Functional → Working prototype. Cost‑Sensitive Projects → Rapid prototyping (3‑D printing, CNC) before committing to tooling. Complex Systems (e.g., automotive) → Virtual prototype for aerodynamics + physical mockup for ergonomics. 👀 Patterns to Recognize “Missing Function = Proof‑of‑Principle” – if a prototype lacks many features, it’s likely a proof‑of‑principle. “Hand‑made Appearance = Visual/UX Prototype” – rough materials indicate focus on look/feel, not performance. “Iterative Alpha/Beta Labels” – software stages signal readiness level; Alpha = internal, Beta = external testing. “Testbed Mention” → expect a platform designed for repeatable experiments rather than a final product. 🗂️ Exam Traps Confusing “Functional” with “Working” – functional prototypes may be built at a different scale; working prototypes aim to replicate final functionality. Assuming “Prototype Materials = Final Materials” – exam may present a cheaper material and ask if performance metrics are directly comparable (they’re not). Mixing “Wizard of Oz” with “Automation” – the presence of a hidden human operator means the prototype is not fully automated; answer choices that claim full system functionality are wrong. Over‑valuing Visual Prototypes for Performance – visual prototypes provide aesthetic data only; any performance claim is a distractor. --- Study tip: Review each prototype type, link it to its typical workflow stage, and practice matching a scenario (e.g., “early UI sketch”) to the correct prototype. This pattern‑recognition approach locks the information in for the exam.