Improving the separation of non-functional concerns in requirements artifacts

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

Abstract

One of the most important principles in Software Engineering is the separation of concerns. When this principle is correctly applied, it helps to promote comprehensibility, maintainability and reusability of software system artifacts. However, often, the specification of non-functional requirements is scattered and tangled with functional artifacts they affect. Hence, in order to produce better requirements specifications, this paper presents an approach to improve the separation of concerns in requirements artifacts, providing a way to represent non-functional concerns apart from the requirements they affect and to specify the composition between them in a noninvasive way. ?? 2004 IEEE.

Cite

CITATION STYLE

APA

Sousa, G., & Castro, J. (2004). Improving the separation of non-functional concerns in requirements artifacts. In Proceedings of the IEEE International Conference on Requirements Engineering (pp. 350–351). https://doi.org/10.1109/icre.2004.1335696

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