Compositional specification of software architecture
ISAW '98 Proceedings of the third international workshop on Software architecture
A survey of software reuse libraries
Annals of Software Engineering
Efficient Specification-Based Component Retrieval
Automated Software Engineering
The unified problem-solving method development language UPML
Knowledge and Information Systems
A software architecture for knowledge-based systems
The Knowledge Engineering Review
A unified Semantic Web services architecture based on WSMF and UPML
International Journal of Web Engineering and Technology
Problem-solving methods: understanding, description, development, and reuse
Problem-solving methods: understanding, description, development, and reuse
| Hi-index | 0.00 |
Scaling formal methods to large, complex systems requires methods of modeling systems at high levels of abstraction. In this paper, we describe such a method for specifying system requirements at the software architecture level. An architecture represents a way breaking down a system into a set of interconnected components. We use architecture theories to specify the behavior of a system in terms of the behavior of its components via a collection of axioms. The axioms describe the effects and limits of component variation and the assumptions a component can make about the environment provided by the architecture. As a result of the method the verification of the basic architecture can be separated from the verification of the individual component instantiations. We present an example of using architecture theories to model the task coordination architecture of a multi-threaded plan execution system.