A component model for hard real‐time systems: CCM with ARINC‐653

Dubey, Abhishek; Karsai, Gábor; Mahadevan, Nagabhushan

doi:10.1002/spe.1083

Cited by 43 publications

(32 citation statements)

References 34 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…In other words, a component is always single-threaded. Please see [14] for a detailed description of the component model and its operation.…”

Section: Component Operationsmentioning

confidence: 99%

“…This was correctly diagnosed by the Diagnosis Engine component and resulted in the Deliberative Reasoner being triggered. An additional constraint (¬V Sensor ), reflecting the non-availability of the faulty sensor component, was added to the set of clauses in Equation 14. The current state of the healthy components (GPS, NavDisplay and Sensor2) was fed as a set of assumptions to the SAT solver.…”

Section: Examplementioning

confidence: 99%

“…The foundation of the architecture is a real-time component framework (built upon an ARINC-653 platform) that defines a specific model of computation for software components [14]. This framework uses the concepts of temporal isolation, spatial isolation, and strict temporal deadlines from ARINC-653 and combines them with the well-defined component interaction patterns derived from the CORBA Component Model [52].…”

Section: Introductionmentioning

confidence: 99%

See 2 more Smart Citations

Deliberative, search-based mitigation strategies for model-based software health management

Mahadevan

Dubey

Balasubramanian

et al. 2013

Innovations Syst Softw Eng

Self Cite

View full text Add to dashboard Cite

Rising software complexity in aerospace systems makes them very difficult to analyze and prepare for all possible fault scenarios at design-time, therefore classical run-time fault-tolerance techniques, such as self-checking pairs and triple modular redundancy are used. However, several recent incidents have made it clear that existing software fault tolerance techniques alone are not sufficient. To improve system dependability, simpler, yet formally specified and verified run-time monitoring, diagnosis, and fault mitigation capabilities are needed. Such architectures are already in use for managing the health of vehicles and systems. Software health management is the application of these techniques to software systems. In this paper we briefly describe the software health management techniques and architecture developed by our research group. The foundation of the architecture is a real-time component framework (built upon ARINC-653 platform services) that defines a model of computation for software components. Dedicated architectural elements: the Component Level Health Manager (CLHM) and System Level Health Manager (SLHM) provide the health management services: anomaly detection, fault source isolation, and fault mitigation. The SLHM includes a diagnosis engine that (1) uses a Timed Failure Propagation (TFPG) model derived from the component assembly model, (2) reasons about cascading fault effects in the system, and (3) isolates the fault source component(s). Thereafter, the appropriate system level mitigation action is taken. The main focus of this article is the description of the fault mitigation architecture that uses goal-based deliberative reasoning to determine the best mitigation actions for recovering the system from the identified failure mode.

show abstract

“…In other words, a component is always single-threaded. Please see [14] for a detailed description of the component model and its operation.…”

Section: Component Operationsmentioning

confidence: 99%

Section: Examplementioning

confidence: 99%

Section: Introductionmentioning

confidence: 99%

See 1 more Smart Citation

Deliberative, search-based mitigation strategies for model-based software health management

Mahadevan

Dubey

Balasubramanian

et al. 2013

Innovations Syst Softw Eng

Self Cite

View full text Add to dashboard Cite

show abstract

“…Note that a component model for hard real-time systems has been developed in our earlier work [26]. That work merged the concepts of CCM with those of ARINC-653, and as such it should considered a precursor of this work.…”

Section: Related Workmentioning

confidence: 99%

A software platform for fractionated spacecraft

Dubey

Emfinger

Gokhale

et al. 2012

2012 IEEE Aerospace Conference

View full text Add to dashboard Cite

Abstract-A fractionated spacecraft is a cluster of independent modules that interact wirelessly to maintain cluster flight and realize the functions usually performed by a monolithic satellite. This spacecraft architecture poses novel software challenges because the hardware platform is inherently distributed, with highly fluctuating connectivity among the modules. It is critical for mission success to support autonomous fault management and to satisfy real-time performance requirements. It is also both critical and challenging to support multiple organizations and users whose diverse software applications have changing demands for computational and communication resources, while operating on different levels and in separate domains of security.The solution proposed in this paper is based on a layered architecture consisting of a novel operating system, a middleware layer, and component-structured applications. The operating system provides primitives for concurrency, synchronization, and secure information flows; it also enforces application separation and resource management policies. The middleware provides higher-level services supporting request/response and publish/subscribe interactions for distributed software. The component model facilitates the creation of software applications from modular and reusable components that are deployed in the distributed system and interact only through well-defined mechanisms.Two cross-cutting aspects -multi-level security and multilayered fault management -are addressed at all levels of the architecture. The complexity of creating applications and performing system integration is mitigated through the use of a domain-specific model-driven development process that relies on a dedicated modeling language and its accompanying graphical modeling tools, software generators for synthesizing infrastructure code, and the extensive use of model-based analysis for verification and validation.

show abstract

“…For example, dlSBRT could be a great mechanism to load SelfPortrait metadata into the running application, by intercepting the references to meta-data symbols, only the meta-data that is actually used would be loaded, reducing the meta-data memory footprint. Conversely, our work in dependency injection could be used to inject dlSBRT services into applications in a way that is more Another potentially interesting experiment would be to apply the work of Dubey and colleagues to SCA C++ with D.I [32]. They describe the work that was necessary to create a real-time component framework starting with CCM and a ARINC-653, a real-time operating system.…”

Section: Resultsmentioning

confidence: 99%

Flexible Composition for C Plus Plus 11

BAYSER¹

View full text Add to dashboard Cite

A component model for hard real‐time systems: CCM with ARINC‐653

Cited by 43 publications

References 34 publications

Deliberative, search-based mitigation strategies for model-based software health management

Deliberative, search-based mitigation strategies for model-based software health management

A software platform for fractionated spacecraft

Flexible Composition for C Plus Plus 11

Contact Info

Product

Resources

About