Welcome!
To use the personalized features of this site, please log in or register.
If you have forgotten your username or password, we can help.
|
 |
Incorporating Non-functional Requirements into Software Architectures
| |
|
Incorporating Non-functional Requirements into Software Architectures
Nelson S. Rosa5, 6, George R. R. Justo5 and Paulo R. F. Cunha6
| (5) |
Centre for Parallel Computing, University of Westminster, 115 New Cavendish Street, London, W1M 8JS, UK |
| (6) |
Universidade Federal de Pernambuco, Centro de Informática, Cidade Universitária, Av. Prof. Luiz Freire, s/n, CEP 50732-970 Recife, Pernambuco, Brasil |
Abstract
The concept of software architecture has created a new scenario for incorporating non-functional and transactional requirements
into the software design. Transactional and non-functional requirements can be included in an architecture-based software
development through formal approaches in which first-order and temporal logic are utilised to deal with them. In this paper,
we present an approach in which transactional and non-functional requirements are formally incorporated into a special class
of software architectures, known as dynamic software architectures. In order to demonstrate how this proposal can be utilised
in a real application, an appointment system is presented.
This research was supported by the Brazilian Government Agency — CAPES Foundation — under process BEX1779/98-2.
Fulltext Preview (Small, Large)
 References secured to subscribers.
|
|
|
|
|
|