Dependable element: dependable_element_message_passing

• Assumed System
  • Assumed System Requirements
  • Assumptions of Use
• Software Architectural Level
  • Feature Requirements
  • Static Design
    • New Message Passing design
      • The challenges
      • General approach
      • Message Passing client
        • Client Connection state
        • Client Connection callbacks
        • Message sending and delivery
        • Client Connection creation and shared resources
      • Message Passing server
        • Memory allocation
        • Server Connection
        • Server Connection initiation
        • Server callbacks
      • Implementation considerations
        • Client-Server communication protocol
        • Client-side implementation
        • Server-side implementation
        • Use of threads
      • Safety concerns for QNX implementation
        • General scenarios
        • Timings
      • Questions to QNX support
      • Examples
        • DataRouter: logging and tracing sources
        • DataRouter: subscribers
        • DataRouter: diagnostics and control
        • DataRouter: configurable logging and tracing services
    • Static Design
    • Private Api
  • Public API
    • Public Api
  • Dependability Analysis
    • message_passing_fmea
      • Overview
      • Failure Modes
      • Control Measures
• Components
  • component_message_passing
    • Component Requirements
      • Component Requirements
        • Behaviour Requirements
        • API Requirements
        • Server Unit Requirements
        • Client Unit Requirements (client_connection)
    • Units
      • client_connection
        • Implementation
        • Tests
      • server_connection
        • Implementation
      • unix_domain
        • Implementation
        • Tests
      • qnx_dispatch
• Traceability
  • L.O.B.S.T.E.R. Traceability Report

Submodules

This module includes the following submodules:

• Bitmanipulation

• Containers

• Futurecpp

• Os