Design Document

Description

The design document communicates the complete and detailed design of your project. It is substantially more detailed than the proposal and prepares you for the assembly phase of the semester. A quality design document is the key to a successful project (sample document). Use the following format:

  1. Introduction

    • Problem and Solution:

      One to two paragraphs explaining the context of the problem to be solved by your project, including any relevant references to justify the existence and/or importance of the problem (i.e., the need or want for a solution). Justify the novelty of your solution or explain the expected improvements of your solution over previous results.

    • Visual Aid

      A pictorial representation of your project that puts your solution in context. Not necessarily restricted to your design. Include other external systems relevant to your project (e.g. if your solution connects to a phone via Bluetooth, draw a dotted line between your device and the phone). Note that this is not a block diagram and should explain how the solution is used, not a breakdown of inner components.

    • High-level requirements list:

      A list of three to four objective characteristics that this project must exhibit in order to solve the problem. These should be selected such that if any of these requirements were not met, the project would fail to solve the problem. Avoid vague requirements that can be interpreted a number of ways (e.g. "The radio subsystem should work reliably."). Each high-level requirement must be stated in complete sentences and displayed as a bulleted list.

  2. Design

    • Block Diagram:

      A general block diagram of the design of your solution. Each block should be as modular as possible and represent a subsystem of your design. In other words, they can be implemented independently and re-assembled later. The block diagram should be accompanied by a brief (1 paragraph) description of the critical subsystems and what they do.

    • Physical Design (if applicable):

      A physical diagram of the project indicating things such as mechanical dimensions or placement of sensors and actuators. The physical diagram should also be accompanied by a brief one paragraph description.

    • [Subsystem X]

      For each subsystem in your block diagram, you should include a highly detailed and quantitative block description. Each description must include a statement indicating how the block contributes to the overall design dictated by the high-level requirements. Any and all design decisions must be clearly justified. Any interfaces with other blocks must be defined clearly and quantitatively.

      Include any relevant supporting figures and data in order to clearly illustrate and justify the design. Typically a well justified block design will include some or all of the following items: Circuit schematics, simulations, calculations, measurements, flow charts, mechanical diagrams (e.g. CAD drawings, only necessary for mechanical components).

      You must include a Requirements and Verifications table. Please see the R&V page for guidance on writing requirements and verification procedures.

    • [Subsystem Y]

      ...

    • [Subsystem Z]

      ...

    • Tolerance Analysis: Through discussions with your TA, identify the block or interface critical to the success of your project that poses the most challenging requirement. Analyze it mathematically and show that it can be feasibly implemented and meet its requirements. See the Tolerance Analysis guide for further guidance.
  3. Cost and Schedule

    1. Cost Analysis: Include a cost analysis of the project by following the outline below. Include a list of any non-standard parts, lab equipment, shop services, etc., which will be needed with an estimated cost for each.
      • Labor: (For each partner in the project)
        Assume a reasonable salary
        ($/hour) x 2.5 x hours to complete = TOTAL
        Then total labor for all partners. It's a good idea to do some research into what a graduate from ECE at Illinois might typically make.
      • Parts: Include a table listing all parts (description, manufacturer, part #, quantity and cost) and quoted machine shop labor hours that will be needed to complete the project.
      • Sum of costs into a grand total
    2. Schedule:

      Include a time-table showing when each step in the expected sequence of design and construction work will be completed (general, by week), and how the tasks will be shared between the team members. (i.e. Select architecture, Design this, Design that, Buy parts, Assemble this, Assemble that, Prepare mock-up, Integrate prototype, Refine prototype, Test integrated system).

  4. Discussion of Societal Impact, Engineering Standards, Ethics, and Safety Considerations:

    1. Discuss how your project makes a positive contribution to public health, safety and welfare considering economic, environmental, social, cultural, and global factors.
    2. Identify the engineering standards (IEEE, ACM, UL, etc.) that apply to your project.
    3. Explain how IEEE/ACM codes of ethics and course ethics guidelines relate to your project. Discuss ethical concerns for your project.
    4. Discuss electrical and mechanical safety concerns referring to course safety guidelines page. Add any ethical and safety concerns that arose since your proposal.
    5. Document procedures to mitigate the safety concerns of your project. For example, include a lab safety document for batteries, human/animal interfaces, aerial devices, high-power, chemicals, etc. Justify that your design decisions sufficiently protect both users and developers from unsafe conditions caused by your project. Projects dealing with flying vehicles, high voltage, or other high-risk factors, will be required to produce a Safety Manual and demonstrate compliance with the safety manual at the time of demo.
  5. Citations:

    Any material obtained from websites, books, journal articles, or other sources not originally generated by the project team must be appropriately attributed with properly cited sources in a standardized style such as IEEE, ACM, APA, or MLA.

Submission and Deadlines

Your design review document should be uploaded to PACE in PDF format by the deadline shown on the course calendar . If you have uploaded a mock DR document to PACE, please make sure that it has been removed before DR.

OmniSense-Dual — Dual-Wearable 360° Blind-Spot Detection, Directional Haptic Hazard Alerts, and Belly-Based Navigation for Pedestrian Safety

Alex Jin, Jiateng Ma, Simon Xia

Featured Project

Team Members:

- Simon Xia (hx17)

- Jiateng Ma (jiateng4)

- Alex Jin (jin50)

**1. Problem Statement**

Pedestrians in urban and campus environments frequently share space with bicycles, e-scooters, cars, and other pedestrians approaching from all directions. Unlike drivers, who benefit from mirrors and active driver-assistance systems, pedestrians have:

- Unprotected blind spots

Fast-approaching objects from behind or from diagonal sectors are often perceived too late, especially on shared bike/pedestrian paths and narrow sidewalks.

- Reduced situational awareness

Headphones, smartphones, and other distractions degrade auditory and visual awareness, making it harder to detect hazards or notice subtle visual cues.

- Navigation burden

Outdoor and indoor navigation typically depend on visually checking a smartphone map or listening to voice guidance. Both approaches demand attention, occupy hands or ears, and can themselves be unsafe in traffic or crowded environments. For visually impaired users, relying solely on audio is also not ideal.

Existing systems (smartphone maps, voice navigation, cycling radars, blind canes) each address part of the problem but do not provide integrated 360° safety sensing plus hands-free navigation with clear separation of meaning.

**2. Solution Overview**

We propose OmniSense-Dual, a dual-wearable system consisting of:

- A waist/belly-mounted sensing, compute, and navigation haptic module, and

- A head-mounted sensing + haptic hazard alert module

Key design choice:

- Head channel = hazard alerts only

- Belly channel = navigation cues only

This cleanly separates “something is dangerous around you” from “where you should go.”

Core functions:

- 360° Blind-Spot Hazard Awareness

The belly module uses mmWave and ToF/ultrasonic sensors to detect approaching objects around the torso. The head module provides an additional sensing plane for head-level obstacles. When a hazard is detected, the headband vibrates on the corresponding side/direction, signaling an urgent warning.

Hands-Free Navigation

- A smartphone app provides waypoints (outdoor via GPS; optionally indoor via BLE/UWB). The belly module fuses waypoints with IMU heading and encodes navigation instructions as gentle vibration patterns on the belly module (e.g., left side of belt = turn left soon). Navigation never uses the head motors, so it cannot be confused with hazard alerts.

OmniSense-Dual is designed for campus walking, urban commuting, and accessibility support, with a strong emphasis on non-visual, non-auditory, and clearly distinguishable feedback.

**3. Solution Components**

**Component A: Waist/Belly Perception & Compute Module**

Placement:

Worn around waist or belly using elastic belt.

Sensors:

- Rear + Rear-Diagonal (L/R): mmWave radar (60 GHz)

- Left + Right: ToF (e.g., VL53 series) or ultrasonic

- Front-Lower: ToF/IR for low obstacles (curbs, poles, steps)

Functions:

- Provides 360° sensing at waist plane

- Detects moving vs static obstacles

- Includes 6-DoF IMU for heading + gait

- Includes battery + charger + regulators

- Belly haptics used only for navigation

**Component B: Head-Mounted Hazard Alert Module**

Placement:

Headband, cap insert, or lightweight strap.

Haptic Feedback:

8 directional motors placed at:

- Front (0°)

- Front-Left (45°)

- Left (90°)

- Rear-Left (135°)

- Rear (180°)

- Rear-Right (225°)

- Right (270°)

- Front-Right (315°)

Electronics:

- Small BLE SoC/MCU

- Optional short-range ToF for head-height obstacles

- Small battery or wired power from belt

Role:

- Only hazard alerts

- No navigation patterns

**Component C: Navigation & Belly Haptic Interface**

Input Source:

Phone provides route via GPS (outdoor) or BLE/UWB (indoor).

Processing on Belt Module:

- Receives desired bearing from phone

- Computes angle difference using IMU

- Triggers haptic cue on belt

**Component D: Safety Hazard Logic**

Inputs:

- mmWave + ToF/ultrasonic

- Optional head ToF

- IMU heading

Hazards Detected:

- Approaching fast objects (bike, scooter)

- Sudden close static obstacles

- Rear or diagonal intrusion

- Low objects in walking path

Head Feedback Patterns (Hazard Only):

- Default hazard → strong 0.5–1.0s pulse in correct motor direction

- High severity → repeated strong pulses

- Multiple hazards → priority by time-to-collision

**Component E: Electronics & PCB**

Belly PCB Includes:

- MCU (e.g., STM32H7 or ESP32-S3)

- Sensor interfaces (mmWave, ToF, IMU)

- BLE for phone + headband

- Haptic drivers for belt motors

- Li-ion charging + regulation

Head PCB Includes:

- BLE SoC (e.g., nRF52832/ESP32-C3-Mini)

- 8 motor drivers (directional)

- Optional ToF

- Small battery or connector

**4. Criterion for Success**

Safety

- Detect bikes/scooters ≥ 5 m away with ≥90% recall

- Head direction correctness ≥90%

- Alert latency ≤250 ms

- Dual-plane sensing reduces occlusion misses ≥30%

Navigation

- Turn accuracy using belly haptics ≥85%

- Heading deviation during “straight” ≤10°

- Navigation update latency ≤200 ms

Channel Separation

- Head = hazard, belly = navigation

- User classification accuracy (hazard vs nav) ≥90%

Usability

- Battery life ≥4 hours

- Total mass ≤350 g (head ≤150 g)

Project Videos