%0 Conference Paper %1 zhang_xsadl:_2005 %A Zhang, S. %A Goddard, S. %B International Conference on Information Technology: Coding and Computing, 2005. ITCC 2005 %D 2005 %I IEEE %K Architecture Architecture; Communication Component Computer Connectors; Description Finite Language; Logic; Middleware; Processes; Protocols; Software State aided architecture architecture-based architecture; behavior component component-based computer connector control; description description; design; development engineering; environment; formal graphical implementation; interfaces; language languages; message middleware mismatch; object-oriented programming; software specification specification; system systems; technology; tool; user {3CoFramework}; {CASE} {GUI-based} {xADL}; {xSADL} %P 443-- 448 Vol. 2 %R 10.1109/ITCC.2005.303 %T xSADL: an architecture description language to specify component-based systems %V 2 %X Software architecture (SA) provides a formal basis to describe and analyze a software system as a collection of components and their interactions (connectors). However, the current understanding and specification for a connector are still insufficient. Furthermore, there still exists a gap between architecture design and component-based implementation. This paper attempts to tackle these problems by providing an architecture description language (ADL), xSADL. In the specification of a connector, xSADL can help designers to deal with two kinds of architectural mismatches: behavior mismatch and message mismatch. xSADL is also supported by a GUI-based CASE tool. To help transform the architecture design by xSADL to a component-based software implementation, a component framework, 3CoFramework, is also introduced. xSADLand 3CoFramework complement each other and construct an architecture-based component development environment. %@ 0-7695-2315-3

@inproceedings{zhang_xsadl:_2005, abstract = {Software architecture {(SA)} provides a formal basis to describe and analyze a software system as a collection of components and their interactions (connectors). However, the current understanding and specification for a connector are still insufficient. Furthermore, there still exists a gap between architecture design and component-based implementation. This paper attempts to tackle these problems by providing an architecture description language {(ADL)}, {xSADL.} In the specification of a connector, {xSADL} can help designers to deal with two kinds of architectural mismatches: behavior mismatch and message mismatch. {xSADL} is also supported by a {GUI-based} {CASE} tool. To help transform the architecture design by {xSADL} to a component-based software implementation, a component framework, {3CoFramework}, is also introduced. {xSADLand} {3CoFramework} complement each other and construct an architecture-based component development environment.}, added-at = {2013-02-28T11:13:35.000+0100}, author = {Zhang, S. and Goddard, S.}, biburl = {https://www.bibsonomy.org/bibtex/23a15b761a419ae22546a60606c7d92cc/fritzsolms}, booktitle = {{International Conference on Information Technology: Coding and Computing, 2005. {ITCC} 2005}}, doi = {10.1109/ITCC.2005.303}, interhash = {545a690cb76b5c4b3ee1590c1a45606f}, intrahash = {3a15b761a419ae22546a60606c7d92cc}, isbn = {0-7695-2315-3}, keywords = {Architecture Architecture; Communication Component Computer Connectors; Description Finite Language; Logic; Middleware; Processes; Protocols; Software State aided architecture architecture-based architecture; behavior component component-based computer connector control; description description; design; development engineering; environment; formal graphical implementation; interfaces; language languages; message middleware mismatch; object-oriented programming; software specification specification; system systems; technology; tool; user {3CoFramework}; {CASE} {GUI-based} {xADL}; {xSADL}}, lccn = {0005}, month = apr, pages = {443-- 448 Vol. 2}, publisher = {{IEEE}}, review = {{SUMMARY} {(Fritz)} Define {sxADL}, an extension of {xADL} ======================== {xADL} is a simple, extensible {XML} based {ADL} with {XML} schema. It provides basic architecture element descriptions but its strength is extensibility. Support architecture prescription \& architecture-level configuration mngmnt. Lacks specifications to describe what component is and what a connector is. Extend {xADL} with following core features ========================== - Component \& connector specs incl both, interface \& formal behaviour spec * component = interface {(I/O} + header) + {providedService} {(FSP} based process spec) * behaviour specified via an extended Finite State Processes {(FSP)} formalism which is based on Labeled Transition System {(LTS)} and extends {FSP} for component contexts. - Connectors specification includes both, formal component composition behaviour \& incompatible msg adapting (adapters) - {xSADL} integrates with {3CoFramework} which supports explicit connector implementation. - Configuration = connecting to specific service providers via specific adapters. Critic: ==== - No support for architectural strategies (load balancing, component reuse, active or passive concurrency, ...) - No support for architectural patterns. Note: Many {ADLs} are merely design languages. Claims: ===== - different {ADLs} focus on diff aspects of architecture and that traditional {ADLs} only support asmall sets of modeling constructs. - currently there is a gap betw architecture le vel specification and concrete component-based implementations.}, shorttitle = {{xSADL}}, timestamp = {2013-02-28T11:14:12.000+0100}, title = {{{xSADL:} an architecture description language to specify component-based systems}}, volume = 2, year = 2005 }