There has been no commonsense on how to identify problem domain concerns in architectural modeling of software systems. Even, there is no commonly accepted method for modeling the Non-Functional Requirements (NFRs) effectively associated with the architectural aspects in the solution domain. This thesis introduces the use of a Machine Learning (ML) method based on Support Vector Machines to relate NFRs to classified &quot / architectural concerns&quot / in an automated way. This method uses Natural Language Processing techniques to fragment the plain NFR texts under the supervision of domain experts. The contribution of this approach lies in continuously applying ML techniques against previously discovered &ldquo / NFR - architectural concerns&rdquo / associations to improve the intelligence of repositories for requirements engineering. The study illustrates a charted roadmap and demonstrates the automated requirements engineering toolset for this roadmap. It also validates the approach and effectiveness of the toolset on the snapshot of a real-life project.

Software product lines provide the opportunity to improve productivity, quality and time-to-market of software-based systems by means of systematic reuse. So as to accomplish systematic software reuse, elicitation of commonality knowledge is to be upheld by the analysis and management of variability knowledge inherent in domain requirements. Considerable effort is devoted to the management of functional variability, often neglecting the impact of quality concerns originating from non-functional requirements. In this thesis, a hybrid approach concentrating on the modeling of quantitative as well as qualitative concerns on quality has been proposed. This approach basically aims to support the domain design process by modeling non-functional variability. It further aims to support application design process by providing trade-off selection ability among quality concerns to control functional features that belong to the same domain. This approach is implemented and evaluated on an example domain to reveal its benefits on non-functional variability.

Während Formal- und Sacherschließung in der angloamerikanischen Tradition als etwas Zusammengehöriges betrachtet werden, besteht im deutschen Bibliothekswesen eine klare, zumeist auch personelle Trennung zwischen den beiden Bereichen. Jüngere Entwicklungen der internationalen Standardisierung könnten hier zu einem Umdenken führen: Das theoretische Modell "Functional Requirements for Bibliographic Records" (FRBR) hat eine neue Sicht auf das so genannte "bibliographische Universum" eingeläutet, das auch die Sacherschließung mit einbezieht. Auch "Resource Description and Access" (RDA), der Nachfolger von AACR2, versteht sich nicht mehr nur als ein Regelwerk für die Formalerschließung. Ganz konkrete Schritte für ein stärkeres Miteinander bringt das Projekt "Gemeinsame Normdatei" (GND) mit der Zusammenführung der Schlagwortnormdatei (SWD), der Personennamendatei (PND) und der Gemeinsamen Körperschaftsdate (GKD). Im Vortrag werden diese Entwicklungen näher beleuchtet und Überlegungen zu den damit verbundenen Chancen und Problemen angestellt.

Los requerimientos no funcionales de los sistemas software no son un todo homogéneo, hay una falta de consenso para responder preguntas tales como: ¿qué son? ¿cómo se clasifican dentro del contexto de desarrollo de software?, y ¿cómo se clasifican en el desarrollo de aplicaciones Web? Este trabajo presenta el estado de arte del concepto de Requerimientos No Funcionales dentro de la literatura existente en la Ingeniería de Requerimientos y establece como bases conceptuales que los Requerimientos No Funcionales son requerimientos de calidad y son restricciones. Sobre esta base se realiza un estudio comparativo de seis enfoques de desarrollo de aplicaciones Web. Se estudian los procesos de desarrollo que cada una de ellas utiliza para determinar los requerimientos no funcionales; las técnicas de la ingeniería de requerimientos que proponen para su elicitación, especificación, validación y gestión; y se establece en qué fase del ciclo de vida de desarrollo de software identifican y tratan a los requerimientos no funcionales. / Non-functional requirements of software systems are not a homogeneous whole; there is a lack of consensus to answer questions such as: what are they? How are classified within the context of software development? And how classify it in Web Applications developing? This text presents the state of art of the concept of non-functional requirements in the existing literature on the Requirements Engineering and establishes the conceptual foundations of non-functional requirements as quality requirements and restrictions. On this basis, we made a comparative study of six approaches of Web applications development. We studied the development processes that each approach uses to determine of non-functional requirements, the engineering techniques proposed for requirements elicitation, specification, validation and management, and established at what stage of software development life cycle they identify and address Non-functional requirements.

O desenvolvimento de aplicações móveis é guiado por uma especial atenção aos requisitos não funcionais (do inglês, NFR - Non Functional Requirements), sendo o principal objetivo proporcionar uma boa experiência ao usuário final. Entretanto, a avaliação de NFRs é ainda uma tarefa manual, não estruturada e que consome muito tempo. Esta dissertação apresenta um estudo de várias abordagens relacionadas à avaliação de desempenho (por exemplo, o uso de aplicações de benchmark) e de NFRs no âmbito de sistemas móveis. No entanto, os benchmarks atuais são genéricos, geralmente, voltados para a plataforma de execução e nem sempre instituem um consenso na classificação de dispositivos. Visando uma melhor avaliação de NFRs e uma classificação de dispositivos com base nas necessidades de aplicações reais, este trabalho propõe um framework para gerar benchmarks orientados às necessidades de cada aplicação e, assim, fornecer uma forma eficiente e eficaz para estimar requisitos não funcionais em sistemas móveis. Essa ferramenta é composta por uma biblioteca de testes parametrizáveis, métricas e uma estrutura para geração rápida de benchmarks orientados à aplicação. O framework foi construído utilizando o paradigma de programação orientada a aspectos para coleta das métricas por fornecer uma maior modularidade e separação de interesses, de modo que a sua evolução, através da adição de outras métricas ou testes, seja facilitada. Para validação da proposta, foram realizados experimentos com cinco aplicações Android reais disponíveis na Play Store, sendo que para cada aplicação foi gerado um benchmark específico cujos resultados foram comparados com os obtidos para as aplicações móveis reais. Os resultados são promissores, mostrando que é possível criar aplicações de teste com comportamento semelhante ao de aplicações reais e, assim, classificar dispositivos com base nas necessidades das aplicações, através da análise das métricas presentes no framework. Essas métricas podem, ainda, orientar o desenvolvedor na otimização de suas aplicações ou ainda na escolha de dispositivos com melhor custo benefício para executar seus aplicativos. / The mobile application development is guided by a special attention to non-functional requirements (NFRs), where a good experience for the end user is the primary goal. However, NFRs evaluation is still a manual, unstructured and time-consuming task. This thesis presents a study of several approaches related to performance and NFR evaluation within mobile systems. Among these approaches is the use of benchmark applications. Currently available benchmarks are generic, usually focused on the execution platform and do not always establish a consensus on the classification of devices. For a better NFRs assessment and classification of devices based on real application needs, this work proposes a framework for generating application-oriented benchmarks for the early estimation of non-functional requirements in mobile systems. This framework is composed of a configurable test library, a set of metrics and an engine the assembling of the test program. The framework uses aspect-oriented programming to collect the metrics of interest. This approach provides increased modularity and separation of concerns, thus facilitating the improvement of the framework itself, by adding other metrics or testing operations. In order to validate the proposed framework we used five application from the Android Play store. For each application, a specific benchmark is generated and executed in different devices. The results are compared to those of the execution of the actual applications in the same devices. Experimental results are promising, showing that it is possible to create test applications with similar behavior to that of real applications and thus classify devices based on the actual application needs, by analyzing the metrics present in the framework. These metrics can also guide the developer in optimizing her applications or in choosing devices with the best trade-off between cost and performance to run a given application.

O desenvolvimento de aplicações móveis é guiado por uma especial atenção aos requisitos não funcionais (do inglês, NFR - Non Functional Requirements), sendo o principal objetivo proporcionar uma boa experiência ao usuário final. Entretanto, a avaliação de NFRs é ainda uma tarefa manual, não estruturada e que consome muito tempo. Esta dissertação apresenta um estudo de várias abordagens relacionadas à avaliação de desempenho (por exemplo, o uso de aplicações de benchmark) e de NFRs no âmbito de sistemas móveis. No entanto, os benchmarks atuais são genéricos, geralmente, voltados para a plataforma de execução e nem sempre instituem um consenso na classificação de dispositivos. Visando uma melhor avaliação de NFRs e uma classificação de dispositivos com base nas necessidades de aplicações reais, este trabalho propõe um framework para gerar benchmarks orientados às necessidades de cada aplicação e, assim, fornecer uma forma eficiente e eficaz para estimar requisitos não funcionais em sistemas móveis. Essa ferramenta é composta por uma biblioteca de testes parametrizáveis, métricas e uma estrutura para geração rápida de benchmarks orientados à aplicação. O framework foi construído utilizando o paradigma de programação orientada a aspectos para coleta das métricas por fornecer uma maior modularidade e separação de interesses, de modo que a sua evolução, através da adição de outras métricas ou testes, seja facilitada. Para validação da proposta, foram realizados experimentos com cinco aplicações Android reais disponíveis na Play Store, sendo que para cada aplicação foi gerado um benchmark específico cujos resultados foram comparados com os obtidos para as aplicações móveis reais. Os resultados são promissores, mostrando que é possível criar aplicações de teste com comportamento semelhante ao de aplicações reais e, assim, classificar dispositivos com base nas necessidades das aplicações, através da análise das métricas presentes no framework. Essas métricas podem, ainda, orientar o desenvolvedor na otimização de suas aplicações ou ainda na escolha de dispositivos com melhor custo benefício para executar seus aplicativos. / The mobile application development is guided by a special attention to non-functional requirements (NFRs), where a good experience for the end user is the primary goal. However, NFRs evaluation is still a manual, unstructured and time-consuming task. This thesis presents a study of several approaches related to performance and NFR evaluation within mobile systems. Among these approaches is the use of benchmark applications. Currently available benchmarks are generic, usually focused on the execution platform and do not always establish a consensus on the classification of devices. For a better NFRs assessment and classification of devices based on real application needs, this work proposes a framework for generating application-oriented benchmarks for the early estimation of non-functional requirements in mobile systems. This framework is composed of a configurable test library, a set of metrics and an engine the assembling of the test program. The framework uses aspect-oriented programming to collect the metrics of interest. This approach provides increased modularity and separation of concerns, thus facilitating the improvement of the framework itself, by adding other metrics or testing operations. In order to validate the proposed framework we used five application from the Android Play store. For each application, a specific benchmark is generated and executed in different devices. The results are compared to those of the execution of the actual applications in the same devices. Experimental results are promising, showing that it is possible to create test applications with similar behavior to that of real applications and thus classify devices based on the actual application needs, by analyzing the metrics present in the framework. These metrics can also guide the developer in optimizing her applications or in choosing devices with the best trade-off between cost and performance to run a given application.

Agile software development methodologies, such as Scrum, have gained tremendous popularity and proven successful in quickly delivering quality Functional Requirements (FRs). However, agile methodologies have not adequately identified, modeled, and linked Non-Functional Requirements (NFRs) with FRs in early development phases. Researchers agree that NFRs have been generally ignored in conventional methodologies, especially ignored in agile environments. This dissertation develops a conceptual framework for NFR modeling in agile processes. The proposed Non-functional Requirements Modeling for Agile Processes (NORMAP) Methodology investigated the feasibility of identifying, linking, and modeling Agile Loose Cases (ALCs) with Agile Use Cases (AUCs) and Agile Choose Cases (ACCs). AUCs are newly proposed hybrid of use cases and agile user stories. ALCs are proposed—loosely—defined agile NFRs. ACCs are proposed potential solutions (operationalizations) for ALCs. A lightweight adapted version of the NFR Framework was developed including 25 important NFRs selected out of 161 for this study. Further, an enhanced risk-driven agile requirements implementation sequence (NORPLAN) was developed and visualized as a tree-like view (NORVIEW). The NORMAP Methodology was validated through developing NORMATIC--a Java-based agile visual modeling simulation tool and two case studies. NORMATIC utilized Natural Language Processing (NLP) tools to parse requirement sentences and identify potential ALCs. The first case study utilized the Predictor Models in Software Engineering (PROMISE) dataset used in NFRs classification. NORMAP successfully parsed and classified ALCs for 529 out of 607 (87.15%) independent user requirements. The second case study utilized the European Union eProcurement System’s 26 functional requirements. NORMAP successfully parsed and classified ALCs for 50 out of 57 sentences that included possible ALCs (87.71%). Furthermore, requirements quality and project management metrics were used to calculate a risk-driven requirements implementation sequence using three priority schemes. Results showed that Riskiest-Requirements-First priority scheme planned requirements in 17 sprints--two months earlier than the Highest-Business-Value-First scheme (21 sprints) and one month earlier than the Riskiest-Requirements-Last scheme (19 sprints). Agile communities can potentially benefit from the NORMAP Methodology by utilizing a systematic and risk-driven lightweight engineering process to visually model and plan NFRs as first-class artifacts in agile environments.

Aus Punkt 1.: "We state a growing importance in of implicit factors in user's decision making. The products they choose to use are no longer sufficient only addressing the basic functional requirements. Due to higher living standards, the users now ask for more than just the consideration of accessibility terms. "[…] People have gradually enhanced their survival mentality from the materialistic fulfilment into the emotional one. This phenomenon has transcended producers’ role in the market. They do not only manufacture products and provide goods, but they should also create a kind of product that can create atmosphere and stories, so that consumers can experience deeper satisfaction and emotions in their purchase behaviour." (Huang & Guan 2014) There is a stronger focus on emotional aspects affecting users' product selection as ever before. Physiological UCD, however, already is a challenging task itself, regarding all parties and factors influencing its decision making process, so the concentration on other, more subjective factors still remain widely unconsidered. Recent User Centred Design (UCD) approaches already take up this fact, but still this is at the very beginning regarding UCD implementation (Law et al. 2010). ..."

[pt] Em geral, os Requisitos Não-funcionais (RNFs) só são tratados nas atividades relacionadas à arquitetura do software, e, muitas vezes, apenas durante a implementação. Essa situação resulta em custos mais altos e menor qualidade do software. Este trabalho estuda mecanismos para ressaltar os RNFs durante as atividades de construção de requisitos. A escolha dos requisitos pelos diversos interessados, dentro do processo de elicitação de requisitos do software através do consenso, é um problema complexo. Representar e estruturar dinâmicas de grupos, que são compostas por ações humanas, é um desafio. Durante o processo de decisão em grupo ocorre o debate de um conjunto de idéias, nem sempre expostas de maneira clara e nem sempre entendidas por todos da mesma forma. O debate envolve vários perfis de participantes, com pontos de vista distintos, e por vezes conflitantes. Sendo tais diferenças, em contra partida, fundamentais para a qualidade da decisão em grupo, pois as ideias são analisadas sob vários ângulos. Um processo colaborativo de construção de RNFs e seu suporte computacional são propostos. A abordagem de Negociação - Colaboração é reutilizada para trabalhar especificamente RNFs. Leva em consideração não apenas a construção dos RNFs em si, mas também a construção de suas interdependências. Tais interdependências entre os requisitos impactam a própria decisão sobre os RNFs a serem construídos. A avaliação do processo foi apoiada por um software desenvolvido para suporte, ao mesmo tempo, de mecanismos de Negociação-Colaboração e de atividades de especificação de RNFs. O software é assíncrono e distribuído geograficamente, facilitando a comunicação em grupo, mesmo que com membros distantes fisicamente. Foram realizadas três atividades avaliativas e os resultados produzidos demonstraram indícios positivos ao uso do processo na construção de RNFs. Para cada um dos projetos usados nas avaliações, foi produzida uma lista de RNFs cujo a consistência foi julgada pelos participantes envolvidos como suficientemente satisfatória. O número de RNFs foi dobrado nas três atividades de construção, revelando uma maior cobertura relativa aos atributos de qualidade inicialmente elencados para os softwares. / [en] Non-Functional Requirements (NFRs) are often managed late, either during design or, more often, just at implementation. This trend results in higher costs and low-quality software. Our work studies mechanisms to support RNFs, based on the collaborative dynamics of a negotiation process, during the requirements construction activities As such, we created a collaborative strategy for the construction of NFRs. An evaluation was conducted using a tailored tool built to implement the proposed Negotiation-Collaboration mechanisms. The choice of requirements by various stakeholders, within the process of eliciting software requirements through consensus, is a complex problem. Representing and structuring group dynamics, which are composed of human actions, is a challenge. During the group decision-making process, a set of ideas is debated, not always clearly expressed and not always understood by everyone in the same way. The debate involves several profilesq of participants, with different and sometimes conflicting points of view. Such differences, however, are fundamental to the quality of the group decision, as the ideas are analyzed from various perspectives. A collaborative strategy for building RNFs and their computational support is proposed. The Negotiation-Collaboration approach is reused to work specifically with RNFs. It takes into account not only the construction of the RNFs themselves, but also the construction of their interdependencies. Such interdependencies between the requirements impact the decision on the RNFs to be built. The strategy evaluation was supported by software developed to support, at the same time, Negotiation-Collaboration mechanisms and RNFs specification activities. The software is asynchronous and geographically distributed, facilitating group communication, even with physically distant members. Three evaluative activities were carried out, and the results showed positive indications for the use of the strategy in the construction of RNFs. For each of the projects used in the evaluations, a list of RNFs was produced, whose consistency was judged by the participants involved to be sufficiently satisfactory. The number of RNFs was duplicated in the three construction activities, revealing greater coverage regarding the quality attributes initially listed for the software.

[pt] O projeto de software resulta das decisões ao longo do seu desenvolvimento. Algumas dessas decisões podem levar a problemas de projeto, afetando negativamente os requisitos não funcionais (RNFs). Embora seja crucial identificar esses problemas, essa é uma tarefa complexa, especialmente quando o código-fonte é o único artefato disponível. Nessa tarefa, os desenvolvedores podem ter que considerar vários sintomas (por exemplo, anomalias de código) para identificar até mesmo um único problema de projeto. Estudos anteriores sugerem que usar um único sintoma pode ser inadequado para identificar tais problemas. Portanto, nesta tese, investigamos como múltiplos sintomas podem ser usados nessa identificação. Em nosso primeiro estudo, nos concentramos em investigar o uso de anomalias de código bem conhecidos (anomalias de manutenabilidade). Nós identificamos que os desenvolvedores podem se beneficiar desse tipo de sintoma quando as ocorrências das anomalias afetam a mesma localização do programa e formam um padrão, podendo indicar melhor a presença de um problema de projeto. No entanto, também revelamos as limitações ao depender exclusivamente desse tipo de sintoma, destacando a necessidade de contexto adicional. Isso nos levou ao segundo estudo, onde investigamos um tipo adicional de sintoma, anomalias de robustez, e seu uso combinado com anumalias de manutenabilidade. Nós identificamos que ambos os tipos de anomalia de código podem ajudar os desenvolvedores na identificação de problemas de projeto principalmente relacionados à má modularização do sistema. Através desses dois estudos, observamos a necessidade de compreender as perspectivas e estratégias dos desenvolvedores em relação aos RNFs do sistema. Ao fazê-lo, podemos potencialmente entender quem são os desenvolvedores mais capazes de prevenir, discutir e identificar problemas de projeto. Isso nos levou ao terceiro estudo, onde investigamos como os desenvolvedores discutem e abordam RNFs em seus sistemas, revelando estratégias comuns em relação a esses requisitos. Esses resultados nos proporcionaram uma compreensão mais abrangente de como os desenvolvedores podem combinar diferentes sintomas e como percebem sua importância dentro de seus sistemas. / [en] Software design results from stakeholder decisions made through software development. Some of these decisions may lead to design problems, negatively impacting non-functional requirements (NFRs). Even though identifying design problems is crucial, this is a complex task, especially when the source code is the only artifact available. Along this task, developers may have to reason about multiple symptoms (e.g., code smells and nonconformities with NFRs) to identify even a single design problem. In fact, previous studies suggest that relying on a single symptom may be inadequate for the design problem identification. Thus, in this thesis, we investigate the role that the use of multiple symptoms may have on the identification of design problems. In our first study, we focused on investigating the use of well-known code smells (called here maintainability smells) to support this task. Our results indicated that developers could benefit from this type of symptom when smell occurrences affect the same program location and form a pattern; i.e., a set of co-occurring maintainability smells may better indicate the presence of a design problem. Nevertheless, we also reveal the limitations of relying solely on this type of symptom, highlighting the need for additional context. This leads us to the second study, where we investigate an additional type of symptom, robustness smells, and its combined use with maintainability smells. Our results indicated that the use of both types of smells can help developers in the identification of design problems mainly related to bad modularization of the system (e.g. excess of responsibilities assigned to the same component). Through these two studies, we observed the need to understand the perspectives and strategies of developers toward the NFRs of the system. In doing so, we can potentially understand who are the developers better able to prevent, discuss and identify design problems. That led us to our third study, where we investigated how developers discuss and address NFRs in their systems, uncovering common strategies toward these requirements. These results led us to a more comprehensive understanding of how developers can combine different symptoms and how they perceive their significance within their systems.