The Computer Journal
Communicating sequential processes
Communicating sequential processes
The Z notation: a reference manual
The Z notation: a reference manual
Foundations for the study of software architecture
ACM SIGSOFT Software Engineering Notes
Specification and Analysis of System Architecture Using Rapide
IEEE Transactions on Software Engineering - Special issue on software architecture
Formalizing style to understand descriptions of software architecture
ACM Transactions on Software Engineering and Methodology (TOSEM)
Software architecture: perspectives on an emerging discipline
Software architecture: perspectives on an emerging discipline
A formal basis for architectural connection
ACM Transactions on Software Engineering and Methodology (TOSEM)
A Field Guide to Boxology: Preliminary Classification of Architectural Styles for Software Systems
COMPSAC '97 Proceedings of the 21st International Computer Software and Applications Conference
The specification of process synchronization by path expressions
Operating Systems, Proceedings of an International Symposium
Software Architecture in Practice
Software Architecture in Practice
A Framework for Automatic Debugging
Proceedings of the 17th IEEE international conference on Automated software engineering
The Golden Age of Software Architecture
IEEE Software
Software Abstractions: Logic, Language, and Analysis
Software Abstractions: Logic, Language, and Analysis
A direct path to dependable software
Communications of the ACM - A Direct Path to Dependable Software
"The Golden Age of Software Architecture" Revisited
IEEE Software
CHARMY: A Framework for Designing and Verifying Architectural Specifications
IEEE Transactions on Software Engineering
| Hi-index | 0.01 |
This paper suggests an approach to formal software system architecture specification based on behavior models. The behavior of the system is defined as a set of events (event trace) with two basic relations: precedence and inclusion. The structure of event trace is specified using event grammars and other constraints organized into schemas. The schema framework is amenable to stepwise architecture refinement up to executable design and implementation models, reuse, composition, visualization, and application of automated tools for consistency checks.