Behavior Protocols for Software Components
IEEE Transactions on Software Engineering
Automated Software Engineering
Specifying Distributed Software Architectures
Proceedings of the 5th European Software Engineering Conference
Microcomponent-Based Component Controllers: A Foundation for Component Aspects
APSEC '05 Proceedings of the 12th Asia-Pacific Software Engineering Conference
Software—Practice & Experience
Model Checking of Software Components: Combining Java PathFinder and Behavior Protocol Model Checker
SEW '06 Proceedings of the 30th Annual IEEE/NASA Software Engineering Workshop
A component model engineered with components and aspects
CBSE'06 Proceedings of the 9th international conference on Component-Based Software Engineering
CoCoTA --- Common Component Task
The Common Component Modeling Example
Model Checking of Control-User Component-Based Parametrised Systems
CBSE '08 Proceedings of the 11th International Symposium on Component-Based Software Engineering
Model Checking of Component Protocol Conformance -- Optimizations by Reducing False Negatives
Electronic Notes in Theoretical Computer Science (ENTCS)
A road to a formally verified general-purpose operating system
ISARCS'10 Proceedings of the First international conference on Architecting Critical Systems
Identifying future field accesses in exhaustive state space traversal
ASE '11 Proceedings of the 2011 26th IEEE/ACM International Conference on Automated Software Engineering
BeJC: checking compliance between Java implementation and behavior specification
Proceedings of the 17th international doctoral symposium on Components and Architecture
H: A component-based specification language for heterogeneous applications
Computer Standards & Interfaces
| Hi-index | 0.00 |
This chapter presents our solution to the CoCoME assignment that is based on the Fractal component model. The solution involves (i) modeling architecture in Fractal ADL, (ii) specification of component behavior via behavior protocols, (iii) checking compatibility of components, (iv) verification of correspondence between component code and behavior specification, and (v) run-time monitoring of non-functional properties. Among the issues we have faced was the need to modify the architecture - the component hierarchy was reorganized in order to improve clarity of the design and the hierarchical bus was split into two independent buses. These were modeled by primitive components, since Fractal does not support message bus as a first-class entity. Since the CoCoME assignment does not include a complete UML behavior specification (e.g. via activity diagrams and state charts), behavior protocols for all the components are based on the provided plain-English use cases, the UML sequence diagrams, and the reference Java implementation.