ATOMIC Requirements Engineering for Embedded Systems

Applying Assessable, Traceable, and Independent Principles to Embedded System Specifications

Introduction to ATOMIC Requirements in Embedded Contexts

In the constrained world of embedded systems, where resources are limited and reliability is paramount, the ATOMIC requirements methodology offers exceptional value. ATOMIC requirements for embedded systems represent a rigorous approach that addresses the unique challenges faced by firmware engineers, hardware designers, and system integrators.

The ATOMIC methodology in embedded systems stands for:

• Assessable: Verifiable through measurement or observation on the target hardware

• Traceable: Connected to system specifications and hardware capabilities

• One function: Describes a single embedded function or behavior

• Measurable: Can be quantitatively evaluated against hardware constraints

• Independent: Minimizes dependencies on other system components

• Concise: Clearly stated within hardware and firmware limitations

Critical Importance in Embedded Systems

Embedded systems development faces unique challenges that make ATOMIC requirements particularly valuable:

1. Resource Constraints: Limited memory, processing power, and energy capacity

2. Real-time Requirements: Precise timing and deterministic behavior

3. Safety Criticality: Often used in applications where failure threatens life or property

4. Hardware-Software Interaction: Requirements must address both domains

5. Long Lifecycle: Many embedded systems remain in service for decades

Traditional vs. ATOMIC Requirements in Embedded Systems

Traditional Embedded Requirement (Non-ATOMIC)

[EMB-T001]: The thermal management subsystem shall monitor the processor temperature, activate cooling fans at 70°C, increase fan speed proportionally until 85°C, throttle the CPU if temperature exceeds 90°C, and shut down the system if temperature exceeds 100°C for more than 5 seconds.

ATOMIC Embedded Requirements

[EMB-A001]: The thermal management subsystem shall sample the processor temperature sensor at intervals not exceeding 500ms.

[EMB-A002]: The thermal management subsystem shall activate the cooling fan when the processor temperature exceeds 70°C.

[EMB-A003]: The thermal management subsystem shall control fan speed using PWM with a linear scale from 30% duty cycle at 70°C to 100% duty cycle at 85°C.

[EMB-A004]: The thermal management subsystem shall signal the processor to reduce clock frequency by 20% when temperature exceeds 90°C.

[EMB-A005]: The thermal management subsystem shall initiate a controlled system shutdown sequence if the processor temperature exceeds 100°C continuously for more than 5 seconds.

Structure of an Embedded ATOMIC Requirement

Effective embedded ATOMIC requirements incorporate several key elements:

1. Unique Identifier: Module prefix and sequential number (e.g., PWR-042)

2. System Component: Specific hardware or firmware element

3. Action/Behavior: Precisely defined function or response

4. Measurable Parameters: Quantifiable values with units

5. Timing Constraints: Performance or response time requirements

6. Operating Conditions: Environmental or system state context

7. Interfaces: Communication with other system components (when necessary)

Example with Structure Breakdown

[PWR-042] Under normal operating conditions [OPERATING CONDITION], the power management unit [SYSTEM COMPONENT] shall transition [ACTION] from active to low-power mode within 50ms [TIMING CONSTRAINT] when the standby signal [INTERFACE] remains asserted for 200ms [MEASURABLE PARAMETER].

ATOMIC Requirements for Key Embedded Domains

Power Management Domain

Non-ATOMIC: [PWR-001] The battery management system shall monitor cell voltage, balance cells during charging, prevent over-discharge, limit charging current based on temperature, and report battery status to the main processor.

ATOMIC Reformulation:

[PWR-001] The battery management system shall measure individual lithium cell voltages with a minimum resolution of 10mV at a sampling rate of at least 1Hz.

[PWR-002] The battery management system shall activate cell balancing when any cell voltage difference exceeds 50mV during charging phases.

[PWR-003] The battery management system shall disconnect the battery output when any cell voltage falls below 3.0V.

[PWR-004] The battery management system shall reduce maximum charging current linearly from 1000mA at 25°C to 250mA at 45°C.

[PWR-005] The battery management system shall report battery state-of-charge, temperature, and health status to the main processor via I2C interface at 10-second intervals.

Real-Time Control Domain

Non-ATOMIC: [RTC-001] The motor controller shall accept position commands, implement PID control, limit acceleration and velocity, detect stall conditions, and provide position feedback.

ATOMIC Reformulation:

[RTC-001] The motor controller shall accept position commands via CAN bus with a message rate of up to 100Hz.

[RTC-002] The motor controller shall implement position control using a PID algorithm with configurable P, I, and D coefficients.

[RTC-003] The motor controller shall limit acceleration to a maximum of 5000 steps/second² regardless of command input.

[RTC-004] The motor controller shall limit velocity to a maximum of 20000 steps/second regardless of command input.

[RTC-005] The motor controller shall detect a stall condition when the error between commanded and measured position exceeds 100 steps for more than 500ms while motor current exceeds 80% of maximum.

[RTC-006] The motor controller shall provide position feedback via CAN bus at a fixed rate of 50Hz.

Communication Protocol Domain

Non-ATOMIC: [COMM-001] The wireless module shall establish connections with paired devices, maintain connection during brief interruptions, encrypt all transmissions, adapt data rates based on signal quality, and enter low power states when idle.

ATOMIC Reformulation:

[COMM-001] The wireless module shall establish Bluetooth Low Energy connections with previously paired devices within 2 seconds of power-up.

[COMM-002] The wireless module shall maintain logical connection state during physical signal interruptions of up to 10 seconds.

[COMM-003] The wireless module shall encrypt all data transmissions using AES-128 with rotating session keys.

[COMM-004] The wireless module shall dynamically adjust data transmission rates between 125Kbps and 2Mbps based on measured RSSI values.

[COMM-005] The wireless module shall enter sleep mode when no data transmission has occurred for 30 seconds.

Advanced Verification Strategies for Embedded ATOMIC Requirements

Each embedded ATOMIC requirement must have a clear verification method aligned with hardware capabilities:

1. Hardware-in-the-Loop (HIL) Testing

Requirement: [SENS-015] The pressure sensor subsystem shall provide readings with accuracy of ±0.5 kPa across the operating range of 0-500 kPa.

Verification Method: Apply calibrated pressure source at 0, 100, 200, 300, 400, and 500 kPa. Record sensor readings at each point. Verify accuracy within ±0.5 kPa across all test points.

2. Power Consumption Measurement

Requirement: [PWR-023] In sleep mode, the microcontroller shall consume less than 5μA of current.

Verification Method: Place system in sleep mode. Measure current consumption using calibrated ammeter over 10-minute period. Calculate average current draw.

3. Timing Analysis

Requirement: [INT-007] The interrupt service routine shall complete execution within 50μs.

Verification Method: Configure GPIO pin to toggle at ISR entry and exit. Measure time between rising and falling edges using oscilloscope across 1000 interrupt triggers.

4. Boundary Condition Testing

Requirement: [ADC-003] The analog input subsystem shall reject input voltages exceeding 3.6V by activating the overvoltage protection circuit within 10μs.

Verification Method: Apply step voltage from 3.0V to 4.0V with rise time <1μs. Measure time between input exceeding 3.6V and protection circuit activation signal.

ATOMIC Requirements Traceability Matrix for Embedded Systems

ATOMIC requirements enable sophisticated traceability across the embedded development lifecycle:

System Requirement ATOMIC Requirement Hardware Component Firmware Function Test Case Validation Status SYS-01: Low power operation PWR-023: Sleep mode current MCU sleep_mode() TC-056: Power measurement Passed SYS-02: Temperature monitoring SENS-034: Temperature sampling Temp sensor read_temperature() TC-112: Sensor accuracy Failed - 2°C error SYS-03: Secure communication COMM-015: Data encryption RF module encrypt_packet() TC-201: Encryption validation In Progress

Implementation in Resource-Constrained Environments

Implementing ATOMIC requirements in embedded systems requires balancing precision with practical constraints:

1. Memory Usage Impact: Ensure verification does not consume excessive memory

2. Performance Overhead: Minimize impact of measurement on system behavior

3. Testability: Design with hardware test points and diagnostic interfaces

4. Simulation Integration: Create models for requirements verification before hardware

5. Documentation Scale: Balance detail with maintainability

Specialized ATOMIC Requirements for Embedded Edge Cases

Safety-Critical Requirements

[SAF-001] The watchdog timer shall reset the system if not serviced by the main control loop within 500ms.

[SAF-002] The emergency stop function shall de-energize all motor drive outputs within 20ms of emergency stop signal activation regardless of processor state.

Power Integrity Requirements

[PWR-101] The power supply brownout detection circuit shall trigger a system reset when input voltage falls below 4.65V for more than 5ms.

[PWR-102] The power sequencing controller shall ensure the analog voltage rail stabilizes within ±5% of nominal voltage for at least 20ms before enabling digital components.

Environmental Requirements

[ENV-045] The temperature compensation algorithm shall adjust sensor readings by a factor of 0.15% per °C deviation from the 25°C calibration point.

[ENV-046] The humidity sensor heater shall activate for 5 seconds prior to measurement when ambient relative humidity exceeds 85%.

ATOMIC Requirements in Mixed-Criticality Embedded Systems

Modern embedded systems often combine functions of varying criticality levels. ATOMIC requirements support this through clear separation:

High Criticality (Safety): [CRIT-H1] The airbag deployment controller shall make the deployment decision within 8ms of impact sensor trigger.

Medium Criticality (Functional): [CRIT-M1] The climate control system shall maintain cabin temperature within ±2°C of the set point under normal operating conditions.

Low Criticality (Comfort): [CRIT-L1] The ambient lighting controller shall transition between color states over a period of 2 seconds.

Integration with Hardware Development Workflow

ATOMIC requirements methodology aligns with hardware development through:

1. Requirements-to-Schematic Mapping: Each requirement traces to specific circuits

2. Component Selection Criteria: Requirements drive parameter specifications

3. Test Point Integration: Hardware designed with verification access

4. Boundary Scan Support: Requirements for testability implementation

5. Calibration Procedures: Requirements for production alignment

Conclusion

ATOMIC requirements engineering transforms embedded systems development by breaking complex behaviors into precisely defined, independently verifiable units. This methodology provides significant advantages in resource-constrained environments where every byte of memory and milliwatt of power matters.

When implemented effectively, ATOMIC requirements create a robust framework that connects system specifications to hardware capabilities, firmware implementation, and verification procedures, ensuring that embedded systems perform reliably within their design constraints throughout their operational life.

By adopting ATOMIC requirements, embedded systems developers can achieve greater precision in specifications, better allocation of limited resources, more effective testing, and ultimately more reliable products in the field.