Interface specification methods for software components

 |  Login

Show simple item record

dc.contributor Aalto-yliopisto fi
dc.contributor Aalto University en
dc.contributor.author Lampinen, Jani
dc.date.accessioned 2011-11-28T13:18:04Z
dc.date.available 2011-11-28T13:18:04Z
dc.date.issued 2008
dc.identifier.isbn 978-951-22-9454-1
dc.identifier.issn 1797-5042
dc.identifier.uri https://aaltodoc.aalto.fi/handle/123456789/875
dc.description.abstract This report presents an interface specification language developed as a part of the LIME-project (LightweIght formal Methods for distributed component-based Embedded systems) and a tool implementation to support it. The intention is to provide a methodology that is lightweight and complementary to the existing means of quality assurance in a software process. The specification language provides a mechanism for specifying both external usage of a software component, as well as the internal behavior of a one. The former is referred to as interface specification, and the latter to as library specification. Should the interface specification be breached between two interacting components, the calling component is incorrect. Likewise, if the called component does not obey library specification, it will be the one to take the blame. Both types of specification can be written using either propositional linear temporal logic (PLTL) or by regular expressions, and may contain claims about the component's state or the currently executing method. Java has been used as the implementation language on the approach because of the preexisting metadata mechanism (Java annotations) and good tool support. The tool implementation relies on aspect-oriented programming developed by Gregor Kiczales and his team at Xerox PARC in the late 90s. It employs annotation-guided generation of temporal safety aspects to synthesize the defined properties as behavioral invariants to the runtime execution of the program. The aspects simulate finite state automata which keep track of the state of the interaction and signal an exception in case of an error in it is observed. en
dc.format.extent v, 49
dc.format.mimetype application/pdf
dc.language.iso en en
dc.publisher Helsinki University of Technology en
dc.publisher Teknillinen korkeakoulu fi
dc.relation.ispartofseries TKK reports in information and computer science en
dc.relation.ispartofseries 4 en
dc.subject.other Computer science en
dc.title Interface specification methods for software components en
dc.type D4 Julkaistu kehittämis- tai tutkimusraportti taikka -selvitys fi
dc.contributor.school Faculty of Information and Natural Sciences en
dc.contributor.school Informaatio- ja luonnontieteiden tiedekunta fi
dc.contributor.department Department of Information and Computer Science en
dc.contributor.department Tietojenkäsittelytieteen laitos fi
dc.subject.keyword lightweight methods en
dc.subject.keyword interface specification en
dc.subject.keyword Java en
dc.subject.keyword PLTL en
dc.subject.keyword aspect-oriented programming en
dc.identifier.urn urn:nbn:fi:tkk-011478
dc.type.dcmitype text en


Files in this item

This item appears in the following Collection(s)

Show simple item record

Search archive


Advanced Search

article-iconSubmit a publication

Browse

My Account