2008 · 125 citations · 16 references
ComputingAutonomous SystemsSystems EngineeringSoftware EngineeringSystems ArchitectureSystems DesignComponent-based Software EngineeringLayered ArchitectureSoftware ArchitectureSoftware DesignSoftware Fault ToleranceTask ModelsComponent ArchitectureComponent ModelsComponent-based ArchitecturesExecution Plan SelectionGoal AnalysisReactive System ModelingSemi-autonomous SystemsSoftware Components
Autonomous systems are deployed in environments with limited human contact, requiring self‑adaptation to new circumstances for reliable operation. The paper proposes a combined approach for adaptable software architecture and task synthesis from high‑level goals using a three‑layer model. The approach uses a three‑layer architecture: reactive plans are generated from temporal‑logic goals, a middle layer executes plans and assembles domain‑specific component configurations, and it selects alternative components when the current configuration fails. Implementation results show the approach handles environmental non‑determinism and unexpected software component failures.
Autonomous or semi-autonomous systems are deployed in environments where contact with programmers or technicians is infrequent or undesirable. To operate reliably, such systems should be able to adapt to new circumstances on their own. This paper describes our combined approach for adaptable software architecture and task synthesis from high-level goals, which is based on a three-layer model. In the uppermost layer, reactive plans are generated from goals expressed in a temporal logic. The middle layer is responsible for plan execution and assembling a configuration of domain-specific software components, which reside in the lowest layer. Moreover, the middle layer is responsible for selecting alternative components when the current configuration is no longer viable for the circumstances that have arisen. The implementation demonstrates that the approach enables us to handle non-determinism in the environment and unexpected failures in software components.
16