Software architecture: perspectives on an emerging discipline
Software architecture: perspectives on an emerging discipline
Pattern-oriented software architecture: a system of patterns
Pattern-oriented software architecture: a system of patterns
The Unified Modeling Language user guide
The Unified Modeling Language user guide
The Unified Modeling Language reference manual
The Unified Modeling Language reference manual
Reusable component interconnection patterns for distributed software architectures
SSR '01 Proceedings of the 2001 symposium on Software reusability: putting software reuse in context
Designing Concurrent, Distributed, and Real-Time Applications with Uml
Designing Concurrent, Distributed, and Real-Time Applications with Uml
ICSE 2002 workshop on architecting dependable systems
Proceedings of the 24th International Conference on Software Engineering
IEEE Transactions on Knowledge and Data Engineering
Failure Detectors as First Class Objects
DOA '99 Proceedings of the International Symposium on Distributed Objects and Applications
Software Fault Tolerance: A Tutorial
Software Fault Tolerance: A Tutorial
An autonomic failure-detection algorithm
WOSP '04 Proceedings of the 4th international workshop on Software and performance
Self-healing components in robust software architecture for concurrent and distributed systems
Science of Computer Programming - Special issue on system and software architectures(IWSSA'04)
Increasing system dependability through architecture-based self-repair
Architecting dependable systems
Characteristics of multiple-component defects and architectural hotspots: a large system case study
Empirical Software Engineering
Hi-index | 0.00 |
This paper describes an approach to detecting anomalies in a software architectural style that is structured with components and connectors between the components. Each component is designed with tasks (concurrent or active objects), connectors between tasks, and passive objects accessed by tasks. Anomalies in the software architecture are detected twofold by each Component Monitor, which supervises objects in a component, and by a System Monitor, which monitors message communications between components. The monitors encapsulate the specifications of objects being monitored, which are represented using statecharts. The execution of statecharts in the monitors depends on notification messages from connectors between tasks, passive objects accessed by tasks in a component, and connectors between components.