Skip to main content
Article thumbnail
Location of Repository

Declarative specification of software architectures

By John Penix, Perry Alexander and Klaus Havelund


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 of breakzng down a system rnfo a set of tnterconnected components We use archztecture theorzes to speczfy the behavzor of a system zn terms of the behuuaor of zts components vza a collectzon of axzoms The axaoms descrabe the eflects and lzmzts of component varzaizon and the assumptzons a component can make about the envzronment provzded by the archztecture As a result of the method, the verzjicatron of the baszc archztecture can be separated from the verzjicatron of the zndrvadual component znstantzatzons. We present an example of uszng archztecture theoraes to model the task coordznatzon archztecture of a multz-threaded plan execution system

Publisher: IEEE Press
Year: 1997
OAI identifier: oai:CiteSeerX.psu:
Provided by: CiteSeerX
Download PDF:
Sorry, we are unable to provide the full text but you may find it at the following location(s):
  • (external link)
  • (external link)
  • Suggested articles

    To submit an update or takedown request for this paper, please submit an Update/Correction/Removal Request.