Software interconnection models
ICSE '87 Proceedings of the 9th international conference on Software Engineering
Commercial realtime software needs different configuation management
SCM '89 Proceedings of the 2nd International Workshop on Software configuration management
Real-time object-oriented modeling
Real-time object-oriented modeling
Beyond definition/use: architectural interconnection
IDL '94 Proceedings of the workshop on Interface definition languages
Exploiting style in architectural design environments
SIGSOFT '94 Proceedings of the 2nd ACM SIGSOFT symposium on Foundations of software engineering
Modechart: A Specification Language for Real-Time Systems
IEEE Transactions on Software Engineering
Abstractions for Software Architecture and Tools to Support Them
IEEE Transactions on Software Engineering - Special issue on software architecture
Computer Networks and ISDN Systems - Special issue on SDL and MSC
Rapide: a language and toolset for simulation of distributed systems by partial orderings of events
POMIV '96 Proceedings of the DIMACS workshop on Partial order methods in verification
Concurrent Processes and Their Syntax
Journal of the ACM (JACM)
Communication and Concurrency
Modeling Complex Computer and Communication Systems: A Domain-Oriented Design Framework
Modeling Complex Computer and Communication Systems: A Domain-Oriented Design Framework
FORTE '90 Proceedings of the IFIP TC6/WG6.1 Third International Conference on Formal Description Techniques for Distributed Systems and Communication Protocols: Formal Description Techniques, III
Acme: an architecture description interchange language
CASCON '97 Proceedings of the 1997 conference of the Centre for Advanced Studies on Collaborative research
Three Concepts of System Architecture
Three Concepts of System Architecture
Hi-index | 0.00 |
Software engineers informally use block diagrams with boxes and lines to express system architectures. Diagrammatic representations of this type are also found in many specification techniques. However, rarely are architectural documents containing such representations systematically maintained; as a system evolves, architectural documents become obsolete, and the design history of the system is ultimately lost. Additionally, box-and-line representations used in these documents do not possess a precise semantics invariant across the different techniques that rely on them. This paper addresses expression of system evolution at the architectural level based on a formal model of box-and-line diagrams. The formal model (a) provides semantic uniformity and precision; and (b) allows evolutionary steps to be represented as structural transformations. Interesting classes of such transformations are characterized in terms of the underlying operators. With these tools, the architectural evolution of a system is captured as a directed acyclic graph of baselines, where each baseline consists of a system of box-and-line diagrams, and is mapped to a successor baseline by a set of structural transformations. It is also shown how familiar design concepts--such as extension, abstraction, and structural refinement-- can be formalized in simple terms within the framework developed.