How do software architects consider non-functional requirements: An exploratory study

Ameller, David; Ayala, Claudia; Cabot, Jordi; Franch, Xavier

doi:10.1109/re.2012.6345838

Cited by 85 publications

(116 citation statements)

References 29 publications

Supporting

Mentioning

Contrasting

Unclassified

Order By: Relevance

“…not those such as performance etc.) [2]. Overall, this implies a conclusion where, either values are systematically ignored in the practice of NFR elicitation or values may not be NFRs.…”

Section: Non Functional Requirementsmentioning

confidence: 91%

Do You Own a Volkswagen? Values as Non-Functional Requirements

Barn

2016

Lecture Notes in Computer Science

View full text Add to dashboard Cite

Abstract. Of late, there has been renewed interest in determining the role and relative importance of (moral) values in the design of software and its acceptance. Events such as the Snowden revelations and the more recent case of the Volkswagen "defeat device" software have further emphasised the importance of values and ethics in general. This paper posits a view that values accompanied by an appropriate framework derived from non-functional requirements can be used by designers and developers as means for discourse of ethical concerns of the design of software. The position is based on the Volkswagen dieselgate case study and a qualitative analysis of developers views from Reddit discussion forums. The paper proposes an extension of an existing classification of requirements to include value concerns.

show abstract

“…not those such as performance etc.) [2]. Overall, this implies a conclusion where, either values are systematically ignored in the practice of NFR elicitation or values may not be NFRs.…”

Section: Non Functional Requirementsmentioning

confidence: 91%

Do You Own a Volkswagen? Values as Non-Functional Requirements

Barn

2016

Lecture Notes in Computer Science

View full text Add to dashboard Cite

show abstract

“…As such a conceptual framework that captures the concepts present in the technological context of the system can be used to reason about the decisions after the fact from the source code. Non-functional quality attributes are especially prone to not being documented [14], further strengthening the need for tools to reason about decisions after the fact. Researchers have also found that there is a need to investigate if domain-specific requirements can improve requirements documentation [15].…”

Section: Related Workmentioning

confidence: 99%

A Conceptual Model for Architecting Mobile Applications

Barnett

Vasa

Tang

2015

2015 12th Working IEEE/IFIP Conference on Software Architecture

View full text Add to dashboard Cite

Quality attributes are essential in software architecture and they are determined by identifying the concerns of the stakeholders of a system. The concerns of constructing mobile applications (apps) are quite specific due to the characteristics of mobile devices. These concerns have not been adequately addressed in industry standards and practices. In this paper, we present a mobile app development conceptual model comprising six key concepts that impact quality. Using two case studies, we show that these interrelated concepts influence the architectural decisions of mobile apps and their tradeoffs need to be well considered. As such, we suggest that these concepts should be first class entities when designing mobile app architecture to ensure that the quality attributes are satisfied.

show abstract

“…¿Quién decide los RNF, qué tipos de RNF importan? [27] Perspectiva de los arquitectos y cualidades del software. El conocimiento se intercambia al momento de la obtención de los requisitos [28].…”

Section: Cómo Se Aborda El Conocimiento Fundamentaciónunclassified

Elicitación de requisitos no funcionales basada en la gestión de conocimiento de los stakeholders

Buitrón

Flores-Ríos

Pino

2018

Ingeniare. Rev. chil. ing.

View full text Add to dashboard Cite

RESUMENLa Elicitación de Requisitos implica un proceso de entendimiento de las necesidades funcionales y las restricciones (Requisitos No Funcionales -RNF) establecidas por los stakeholders, las cuales serán entrada para las demás etapas del desarrollo de software. En dicha elicitación, la inclusión de los RNF depende de las estrategias para gestionar el conocimiento de los interesados (stakeholders y elicitadores) con el objetivo de generar productos software de alta calidad. Este documento se centra en establecer los diferentes flujos de transformación del conocimiento que se generan en el proceso de Elicitación de RNF al integrar diferentes componentes de la gestión del conocimiento. El núcleo de transformación del conocimiento propuesto fue valorado mediante las técnicas Focus Group y reporte de experiencia obteniendo resultados positivos para su implementación dentro de las prácticas de las organizaciones dedicadas al desarrollo de software.Palabras clave: Ingeniería de software, elicitación de requisitos, gestión del conocimiento, requisitos no funcionales. (Non-Functional Requirements -NFR) ABSTRACT Requirements elicitation involves a process of understanding of the functional requirements and restrictions

show abstract

How do software architects consider non-functional requirements: An exploratory study

Cited by 85 publications

References 29 publications

Do You Own a Volkswagen? Values as Non-Functional Requirements

Do You Own a Volkswagen? Values as Non-Functional Requirements

A Conceptual Model for Architecting Mobile Applications

Elicitación de requisitos no funcionales basada en la gestión de conocimiento de los stakeholders

Contact Info

Product

Resources

About