Module 01 · Phase 2: Hardware engineering
Robotics System Architecture & Requirements
Turn an application requirement into a complete robot architecture: requirements, operational design domain, subsystem split, interfaces and an integration plan.
This overview is open. 6 of 6 guides are written; the others show Coming soon until they are complete and tested.
Questions this module answers
- How do customer requirements become engineering requirements?
- What is the robot’s operational design domain, and how does it constrain every later choice?
- How do I split the system into hardware and software subsystems and document the interfaces between them?
- How do I run an engineering trade-off analysis and write an integration plan?
What it covers
- Functional and non-functional requirements
- Operational design domain
- Architecture selection
- System block diagram
- Interface control document
- Requirement allocation
- Subsystem dependencies
- Trade-off analysis
- Integration plan
Guides and design decisions
A. Engineering Guides (4)
B. Design & Selection (2)
Diagnostics, tools and challenges
E. Design challenges (1)
- Challenge 1: Design an Autonomous Mobile RobotIndoor differential-drive robot: sensors, motor sizing, compute, power, ROS 2, LiDAR+IMU, SLAM, Nav2, tuning and validation.
Practical deliverables
- Robot architecture templates
- System requirements checklist
- Hardware/software interface checklist
- Block-diagram examples
- Example architecture for an autonomous mobile robot
Read first: existing FixTheRobot lessons and labs
This module builds on these instead of repeating them.
- Engineering Trade-offs and Safety Cases Navigation · Lesson
- Measuring Navigation: Success, Efficiency, Safety and Comfort Navigation · Lesson