A contract-based approach to describe and deploy non-functional adaptations in software architectures
Autor(a) principal: | |
---|---|
Data de Publicação: | 2004 |
Outros Autores: | , , |
Tipo de documento: | Artigo |
Idioma: | eng |
Título da fonte: | Journal of the Brazilian Computer Society |
Texto Completo: | http://old.scielo.br/scielo.php?script=sci_arttext&pid=S0104-65002004000200002 |
Resumo: | This paper presents a comprehensive approach to describe, deploy and adapt component-based applications having dynamic non-functional requirements. The approach is centered on high-level contracts associated to architectural descriptions, which allow the non-functional requirements to be handled separately during the system design process. This helps to achieve separation of concerns facilitating the reuse of modules that implement the application in other systems. Besides specifying non-functional requirements, contracts are used at runtime to guide configuration adaptations required to enforce these requirements. The infrastructure required to manage the contracts follows an architectural pattern, which can be directly mapped to specific components included in a supporting reflective middleware. This allows designers to write a contract and to follow standard recipes to insert the extra code required to its enforcement in the supporting middleware. |
id |
UFRGS-28_1f50af257b669e2b4ab99a7b6e339451 |
---|---|
oai_identifier_str |
oai:scielo:S0104-65002004000200002 |
network_acronym_str |
UFRGS-28 |
network_name_str |
Journal of the Brazilian Computer Society |
repository_id_str |
|
spelling |
A contract-based approach to describe and deploy non-functional adaptations in software architecturescontractsnon-functional requirementssoftware architecturesdynamic configuration adaptationseparation of concernsmiddlewareThis paper presents a comprehensive approach to describe, deploy and adapt component-based applications having dynamic non-functional requirements. The approach is centered on high-level contracts associated to architectural descriptions, which allow the non-functional requirements to be handled separately during the system design process. This helps to achieve separation of concerns facilitating the reuse of modules that implement the application in other systems. Besides specifying non-functional requirements, contracts are used at runtime to guide configuration adaptations required to enforce these requirements. The infrastructure required to manage the contracts follows an architectural pattern, which can be directly mapped to specific components included in a supporting reflective middleware. This allows designers to write a contract and to follow standard recipes to insert the extra code required to its enforcement in the supporting middleware.Sociedade Brasileira de Computação2004-07-01info:eu-repo/semantics/articleinfo:eu-repo/semantics/publishedVersiontext/htmlhttp://old.scielo.br/scielo.php?script=sci_arttext&pid=S0104-65002004000200002Journal of the Brazilian Computer Society v.10 n.1 2004reponame:Journal of the Brazilian Computer Societyinstname:Sociedade Brasileira de Computação (SBC)instacron:UFRGS10.1007/BF03192350info:eu-repo/semantics/openAccessLoques,OrlandoSztajnberg,AlexandreCurty,RomuloAnsaloni,Sidneyeng2010-05-25T00:00:00Zoai:scielo:S0104-65002004000200002Revistahttps://journal-bcs.springeropen.com/PUBhttps://old.scielo.br/oai/scielo-oai.phpjbcs@icmc.sc.usp.br1678-48040104-6500opendoar:2010-05-25T00:00Journal of the Brazilian Computer Society - Sociedade Brasileira de Computação (SBC)false |
dc.title.none.fl_str_mv |
A contract-based approach to describe and deploy non-functional adaptations in software architectures |
title |
A contract-based approach to describe and deploy non-functional adaptations in software architectures |
spellingShingle |
A contract-based approach to describe and deploy non-functional adaptations in software architectures Loques,Orlando contracts non-functional requirements software architectures dynamic configuration adaptation separation of concerns middleware |
title_short |
A contract-based approach to describe and deploy non-functional adaptations in software architectures |
title_full |
A contract-based approach to describe and deploy non-functional adaptations in software architectures |
title_fullStr |
A contract-based approach to describe and deploy non-functional adaptations in software architectures |
title_full_unstemmed |
A contract-based approach to describe and deploy non-functional adaptations in software architectures |
title_sort |
A contract-based approach to describe and deploy non-functional adaptations in software architectures |
author |
Loques,Orlando |
author_facet |
Loques,Orlando Sztajnberg,Alexandre Curty,Romulo Ansaloni,Sidney |
author_role |
author |
author2 |
Sztajnberg,Alexandre Curty,Romulo Ansaloni,Sidney |
author2_role |
author author author |
dc.contributor.author.fl_str_mv |
Loques,Orlando Sztajnberg,Alexandre Curty,Romulo Ansaloni,Sidney |
dc.subject.por.fl_str_mv |
contracts non-functional requirements software architectures dynamic configuration adaptation separation of concerns middleware |
topic |
contracts non-functional requirements software architectures dynamic configuration adaptation separation of concerns middleware |
description |
This paper presents a comprehensive approach to describe, deploy and adapt component-based applications having dynamic non-functional requirements. The approach is centered on high-level contracts associated to architectural descriptions, which allow the non-functional requirements to be handled separately during the system design process. This helps to achieve separation of concerns facilitating the reuse of modules that implement the application in other systems. Besides specifying non-functional requirements, contracts are used at runtime to guide configuration adaptations required to enforce these requirements. The infrastructure required to manage the contracts follows an architectural pattern, which can be directly mapped to specific components included in a supporting reflective middleware. This allows designers to write a contract and to follow standard recipes to insert the extra code required to its enforcement in the supporting middleware. |
publishDate |
2004 |
dc.date.none.fl_str_mv |
2004-07-01 |
dc.type.driver.fl_str_mv |
info:eu-repo/semantics/article |
dc.type.status.fl_str_mv |
info:eu-repo/semantics/publishedVersion |
format |
article |
status_str |
publishedVersion |
dc.identifier.uri.fl_str_mv |
http://old.scielo.br/scielo.php?script=sci_arttext&pid=S0104-65002004000200002 |
url |
http://old.scielo.br/scielo.php?script=sci_arttext&pid=S0104-65002004000200002 |
dc.language.iso.fl_str_mv |
eng |
language |
eng |
dc.relation.none.fl_str_mv |
10.1007/BF03192350 |
dc.rights.driver.fl_str_mv |
info:eu-repo/semantics/openAccess |
eu_rights_str_mv |
openAccess |
dc.format.none.fl_str_mv |
text/html |
dc.publisher.none.fl_str_mv |
Sociedade Brasileira de Computação |
publisher.none.fl_str_mv |
Sociedade Brasileira de Computação |
dc.source.none.fl_str_mv |
Journal of the Brazilian Computer Society v.10 n.1 2004 reponame:Journal of the Brazilian Computer Society instname:Sociedade Brasileira de Computação (SBC) instacron:UFRGS |
instname_str |
Sociedade Brasileira de Computação (SBC) |
instacron_str |
UFRGS |
institution |
UFRGS |
reponame_str |
Journal of the Brazilian Computer Society |
collection |
Journal of the Brazilian Computer Society |
repository.name.fl_str_mv |
Journal of the Brazilian Computer Society - Sociedade Brasileira de Computação (SBC) |
repository.mail.fl_str_mv |
jbcs@icmc.sc.usp.br |
_version_ |
1754734669612449792 |