Paper Info
Title
Exceptions in component interaction protocols – necessity
Abstract
At ADL level, most of the current interaction protocols designed to specify components' behavior at their interfaces do not allow to capture exceptions explicitly. Based on our experience with real-life component based applications, handling exceptions as first class entities in a (formal) behavior specification is an absolute necessity. Otherwise, due to the need to capture exceptions indirectly, the specification becomes very complex, therefore hard to read and, consequently, error-prone. After analyzing potential approaches to introducing exceptions to LTS-based interaction specification (expressed via terms/expressions) in ADL, the paper presents the way we built exceptions into the behavior protocols. Finally, we discuss the positive experience with applying these exception-aware behavior protocols to a real-life Fractal component model application.
Year
DOI
Venue
2004
10.1007/11786160_13
Architecting Systems with Trustworthy Components
Keywords
Field
DocType
component interaction protocol,positive experience,current interaction protocol,behavior specification,lts-based interaction specification,real-life fractal component model,real-life component,absolute necessity,adl level,behavior protocol,exception-aware behavior protocol,component model
Dependability,Programming language,Expression (mathematics),Computer science,Exception handling,Formal specification,First class,Artificial intelligence,Component-based software engineering,Systems architecture,Fractal component model,Distributed computing
Conference
Volume
ISSN
ISBN
3938
0302-9743
3-540-35800-5
Citations 
PageRank 
References 
0
0.34
11
Authors
2
Name
Order
Citations
PageRank
Frantisek Plasil194574.69
Viliam Holub2495.38