Finite transition systems: semantics of communicating systems
Finite transition systems: semantics of communicating systems
Proceedings of the 8th European software engineering conference held jointly with 9th ACM SIGSOFT international symposium on Foundations of software engineering
Architecting families of software systems with process algebras
ACM Transactions on Software Engineering and Methodology (TOSEM)
Behavior Protocols for Software Components
IEEE Transactions on Software Engineering
Requirements Documentation: Why a Formal Basis is Essential
ICRE '00 Proceedings of the 4th International Conference on Requirements Engineering (ICRE'00)
Enforcing a lips Usage Policy for CORBA Components
EUROMICRO '03 Proceedings of the 29th Conference on EUROMICRO
Mapping COSA Software Architecture Concepts into UML 2.0
ICIS-COMSAR '06 Proceedings of the 5th IEEE/ACIS International Conference on Computer and Information Science and 1st IEEE/ACIS International Workshop on Component-Based Software Engineering,Software Architecture and Reuse
SOFA 2.0: Balancing Advanced Features in a Hierarchical Component Model
SERA '06 Proceedings of the Fourth International Conference on Software Engineering Research, Management and Applications
| Hi-index | 0.00 |
In this paper we will present a formal technique for describing complex systems consisting a number of interacting components. To meet this, we will consider a mathematical model for a single component and specify abstract communication protocols of components by using a lightweight formal language Interface Automata. To model hierarchal design for hierarchal systems, beside the basic component's model, we will present other components, called Nodes. A Node consists of a set of components interacting under the supervision of a Controller. A Controller is a set of interface automata that specify interaction protocol of components inside a Node. In addition, we will prove that each Node is equal to a component. Therefore, a Node can be composed of components which are in turn Nods. To address state space explosion problem in system verification, a Node will not be directly analyzed, Instead, we will analyze the Controller and prove its conformance.