Dynamic structure in software architectures
SIGSOFT '96 Proceedings of the 4th ACM SIGSOFT symposium on Foundations of software engineering
A formal basis for architectural connection
ACM Transactions on Software Engineering and Methodology (TOSEM)
Component software: beyond object-oriented programming
Component software: beyond object-oriented programming
Component-based software engineering: putting the pieces together
Component-based software engineering: putting the pieces together
Behavior-consistent specialization of object life cycles
ACM Transactions on Software Engineering and Methodology (TOSEM)
Compatibility and inheritance in software architectures
Science of Computer Programming
Component-based software architectures: a framework based on inheritance of behavior
Science of Computer Programming
Architecting families of software systems with process algebras
ACM Transactions on Software Engineering and Methodology (TOSEM)
Specification and Refinement of Dynamic Software Architectures
WICSA1 Proceedings of the TC2 First Working IFIP Conference on Software Architecture (WICSA1)
Checking behavioural subtypes via refinement
FMOODS '02 Proceedings of the IFIP TC6/WG6.1 Fifth International Conference on Formal Methods for Open Object-Based Distributed Systems V
Relating state-based and behaviour-oriented subtyping
Nordic Journal of Computing
Remote updating procedures for mobile point of sale terminals
WSEAS Transactions on Information Science and Applications
Hi-index | 0.00 |
The component-based software development (CBSD) has been paid more attention by software practicers in recent years. How to analyze and verify behavior-level component substitutability is very important when the component-based software system needs upgrading or maintaining. Concentrating on the component-based software system, this paper formally specifies the components and their interaction behaviors, analyzes the behavior of the new component compared with the old one, and then presents a set of rules for verifying behavioral substitutability of components in software system to ensure the behavioral compatibility whenever a component is replaced by a new one. Finally, an example of e-commerce is presented to illustrate the feasibility and pertinence of this approach.