Hello !
Trace:

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
en:safeav:softsys [2026/06/10 13:09] – karlisberkoldsen:safeav:softsys [2026/06/10 13:14] (current) – karlisberkolds
Line 1: Line 1:
 ====== Software Systems and Middleware ====== ====== Software Systems and Middleware ======
- 
-**Computational foundation of modern cyber-physical and autonomous systems** 
  
 Programmable hardware, operating systems, real-time execution platforms, communication middleware, and software supply chains have evolved from conventional information technology into safety-critical engineered products. Software is no longer a secondary implementation detail: in autonomous systems, it coordinates sensing, perception, decision-making, communication, actuation, diagnostics, updates, and fault handling. As a result, the behavior of the overall system increasingly depends on software architecture, timing predictability, update discipline, and the dependability of third-party components. Programmable hardware, operating systems, real-time execution platforms, communication middleware, and software supply chains have evolved from conventional information technology into safety-critical engineered products. Software is no longer a secondary implementation detail: in autonomous systems, it coordinates sensing, perception, decision-making, communication, actuation, diagnostics, updates, and fault handling. As a result, the behavior of the overall system increasingly depends on software architecture, timing predictability, update discipline, and the dependability of third-party components.
  
-Software systems combine both general principles and domain-specific constraints. General aspects include:    +Software systems combine both general principles and domain-specific constraints. General aspects include abstraction, modularity, operating systems, toolchains, networking, open-source ecosystems, configuration management, software lifecycle processes, and middleware services such as message passing, publish–subscribe communication, device drivers, and hardware abstraction layers. These concepts are common across information technology and cyber-physical systems. Domain-specific aspects appear when software interacts directly with the physical world. Ground systems, aircraft, marine systems, and spacecraft all rely on software, but they differ in timing constraints, certification culture, operational lifetime, redundancy strategy, update frequency, environmental uncertainty, and acceptable risk. Automotive systems combine large-scale production with over-the-air updates and functional-safety expectations; airborne systems emphasise rigorous certification and partitioning; marine systems often have long lifecycles and heterogeneous equipment; and space systems require remote autonomy, fault tolerance, and operation under extreme constraints.
-  * Abstraction; +
-  * Modularity; +
-  * Operating systems; +
-  * Toolchains; +
-  * Networking; +
-  * Open-source ecosystems; +
-  * Configuration management; +
-  * Software lifecycle processes; +
-  * Middleware services. +
-These concepts are common across information technology and cyber-physical systems. Domain-specific aspects appear when software interacts directly with the physical world. Ground systems, aircraft, marine systems, and spacecraft all rely on software, but they differ in timing constraints, certification culture, operational lifetime, redundancy strategy, update frequency, environmental uncertainty, and acceptable risk.  +
-  * **Automotive systems** combine large-scale production with over-the-air updates and functional-safety expectations;  +
-  * **Airborne systems** emphasise rigorous certification and partitioning; +
-  *  **Marine systems** often have long lifecycles and heterogeneous equipment;  +
-  * **Space systems** require remote autonomy, fault tolerance, and operation under extreme constraints.+
  
 Middleware is especially important because it connects application logic to hardware, networks, sensors, actuators, and other software components. In autonomous systems, middleware must support both flexibility and assurance. It enables modular development and reuse, but it also introduces dependencies, timing effects, integration risk, cybersecurity exposure, and possible failure propagation across components. Therefore, middleware architecture must separate safety-critical real-time functions from less critical IT-style services while still allowing communication, monitoring, diagnostics, and updates. Middleware is especially important because it connects application logic to hardware, networks, sensors, actuators, and other software components. In autonomous systems, middleware must support both flexibility and assurance. It enables modular development and reuse, but it also introduces dependencies, timing effects, integration risk, cybersecurity exposure, and possible failure propagation across components. Therefore, middleware architecture must separate safety-critical real-time functions from less critical IT-style services while still allowing communication, monitoring, diagnostics, and updates.
en/safeav/softsys.txt · Last modified: by karlisberkolds
CC Attribution-Share Alike 4.0 International
www.chimeric.de Valid CSS Driven by DokuWiki do yourself a favour and use a real browser - get firefox!! Recent changes RSS feed Valid XHTML 1.0