Incorporating non-functional requirements into software architectures

15Citations
Citations of this article
15Readers
Mendeley users who have this article in their library.
Get full text

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. © 2000 Springer-Verlag Berlin Heidelberg.

Cite

CITATION STYLE

APA

Rosa, N. S., Justo, G. R. R., & Cunha, P. R. F. (2000). Incorporating non-functional requirements into software architectures. In Lecture Notes in Computer Science (including subseries Lecture Notes in Artificial Intelligence and Lecture Notes in Bioinformatics) (Vol. 1800 LNCS, pp. 1009–1018). Springer Verlag. https://doi.org/10.1007/3-540-45591-4_138

Register to see more suggestions

Mendeley helps you to discover research relevant for your work.

Already have an account?

Save time finding and organizing research with Mendeley

Sign up for free