How architects see non-functional requirements: Beware of modifiability

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

Abstract

This paper presents the analysis and key findings of a survey about dealing with non-functional requirements (NFRs) among architects. We find that, as long as the architect is aware of the importance of NFRs, they do not adversely affect project success, with one exception: highly business critical modifiability tends to be detrimental to project success, even when the architect is aware of it. IT projects where modifiability is perceived to have low business criticality lead to consistently high customer satisfaction. Our conclusion is that modifiability deserves more attention than it is getting now, especially because in general it is quantified and verified considerably less than other NFRs. Furthermore, IT projects that applied NFR verification techniques relatively early in development were more successful on average than IT projects that did not apply verification techniques (or applied it relatively late in development). © 2012 Springer-Verlag.

Cite

CITATION STYLE

APA

Poort, E. R., Martens, N., Van De Weerd, I., & Van Vliet, H. (2012). How architects see non-functional requirements: Beware of modifiability. In Lecture Notes in Computer Science (including subseries Lecture Notes in Artificial Intelligence and Lecture Notes in Bioinformatics) (Vol. 7195 LNCS, pp. 37–51). https://doi.org/10.1007/978-3-642-28714-5_4

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