How do software architects consider non-functional requirements: a survey
Document typeConference lecture
Rights accessRestricted access - publisher's policy
Abstract. [Context and motivation] Non-functional requirements (NFRs) play a fundamental role when software architects need to make informed decisions. Criteria like efficiency or integrity determine up to a great extent the final form that the logical, development and deployment architectural views take. [Question/problem] Continuous evidence is needed about the current industrial practices of software architects concerning NFRs: how do they consider them, and what are the most influential types in their daily work. [Principal ideas/results] We ran a web survey addressed to software architects about these issues. We got 60 responses that give some light to the questions above. [Contribution] Some empirical data has been gathered from industry. The results of this survey may serve as input for researchers in order to decide in which types of NFRs may be necessary to invest more research effort.
CitationAmeller, D.; Franch, J. How do software architects consider non-functional requirements: a survey. A: International Working Conference on Requirements Engineering: Foundation for Software Engineering. "16th International Working Conference on Requirements Engineering: Foundation for Software Engineering". Essen: 2010, p. 276-277.