O crescente aumento da complexidade dos sistemas embarcados demanda consigo a necessidade do uso de novas abordagens que acelerem o seu desenvolvimento, como por exemplo, o desenvolvimento baseado em modelos. Essas novas abordagens buscam aumentar o nível de abstração, utilizando conceitos de orientação a objetos e UML para modelar um software embarcado. Porém, com o aumento do nível de abstração, o projetista de software embarcado não possui a ideia exata do impacto de suas decisões de modelagem em questões importantes, como desempenho, consumo de energia, entre tantas outras que são de suma importância em um projeto embarcado. Dessa forma, se fazem necessárias técnicas de análise e/ou estimação de projeto que, em um ambiente de desenvolvimento mais abstrato, possam auxiliar o projetista a tomar melhores decisões nas etapas inicias de projeto, garantindo assim, as funcionalidades (requisitos funcionais) e os requisitos não funcionais do sistema embarcado. Neste trabalho, propõe-se estimar os requisitos não funcionais de um sistema embarcado a partir de informações (métricas) extraídas das etapas iniciais do projeto. Pretende-se com isso auxiliar o projetista na exploração do espaço de projeto já nos estágios iniciais do processo de desenvolvimento, através de uma rápida realimentação sobre o impacto de uma decisão de projeto no desempenho da aplicação em uma dada plataforma de execução. Os resultados experimentais mostram a aplicabilidade da abordagem, principalmente para um ambiente de evolução e manutenção de projetos de software, onde se tem um histórico de métricas de aplicações semelhantes para serem usadas como dados de treinamento. Neste cenário, a abordagem proposta possui acurácia de pelo menos 98% para as estimativas apresentadas ao projetista. Em um cenário heterogêneo, assumindo o uso da metodologia em um sistema diferente daquele usado para treinamento, a acurácia do método de estimação cai para pelo menos 80%. / The increasing complexity of embedded systems demands the use of new approaches to accelerate their development, such as model-driven engineering. Such approaches aim at increasing the level of abstraction using concepts such as object-orientation and UML for modeling the embedded software. However, with the increase of the abstraction level, the embedded software developer looses controllability and predictability over important issues such as performance, power dissipation and memory usage for a specific embedded platform. Thus, new design estimation techniques that can be used in the early development stages become necessary. Such a strategy may help the designer to make better decisions in the early stages of the project, thus ensuring the final system meets both functional and non-functional requirements. In this work, we propose an estimation technique of non-functional requirements for embedded systems, based on data (metrics) extracted from early stages of the project. The proposed methodology allows to better explore different design options in the early steps of software development process and can therefore provide a fast and yet accurate feedback to the developer. Experimental results show the applicability of the approach, particularly for software evolution and maintenance, which has a history of similar applications metrics to be used as training data. In this scenario, the accuracy of the estimation is at least of 98%. In a heterogeneous scenario, where the estimation is performed for a system that is different from the one used during training, the accuracy drops to 80%.

A inovação é fator crucial para o crescimento da economia de uma nação e pode ser vista como o resultado bem articulado das necessidades do consumidor frente a possibilidades de novas tecnologias, novos produtos e novos serviços. A eficácia no entendimento das necessidades dos usuários é considerada um dos principais pilares nos estudos em inovação, principalmente no entendimento das necessidades e requisitos nas fases iniciais do processo de desenvolvimento de novos produtos. No entanto, como consequência da falta de informação direta sobre suas reais necessidades, as informações dos usuários são reduzidas a requisitos generalistas, atendendo essencialmente a aspectos normativos, representados em manuais de referência e diretrizes de design, desconectados do contexto cultural, ambiental e de trabalho. Assim, tem-se como objetivo principal desta tese uma proposta de avaliação de requisitos funcionais e emocionais do produto, sob a perspectiva do usuário. Foram abordados métodos qualitativos (como entrevistas, grupo focado e estudo de caso), bem como métodos quantitativos (como análise multivariada de dados). Esta pesquisa apresenta cinco artigos relacionados ao tema. Ressalta-se como principais resultados: (i) uma revisão de conceitos que apresentam como a percepção do usuário contribui para a inovação no contexto de desenvolvimento de produto; (ii) uma classificação de métodos de avaliação de requisitos de acordo com os requisitos do usuário; (iii) um modelo conceitual de integração dos métodos QFD (Desdobramento da Função Qualidade) e Engenharia Kansei, relacionados aos requisitos funcionais e emocionais respectivamente, aplicado ao caso de um produto da indústria de higiene e beleza; (iv) proposta e validação de um instrumento de coleta de dados, para avaliação da sessão de hemodiálise, sob a perspectiva do paciente, considerando os requisitos de usabilidade, emocionais e econômicos; (v) avaliação da sessão de hemodiálise, a partir da percepção dos pacientes, considerando o atendimento a requisitos de usabilidade, emocionais e econômicos. Como principal conclusão, a tese apresenta uma avaliação de produtos em seu contexto de uso de acordo com as funções prática e estética avaliadas de forma combinada, numa perspectiva multidimensional. Desta forma é possível extrapolar diretrizes de melhorias em produtos e prover inovação em projetos futuros. / Innovation is a crucial factor for growth of the economy of a nation and can be seen as the result of well-articulated consumer needs front the possibilities of new technologies, new products and new services. The effectiveness in understanding the users’ needs is considered one of the main pillars in the studies about innovation, especially in understanding the needs and requirements in the early stages of the new products development process. However, as a result of the lack of direct information about their real needs, the information of users are reduced to generalists requirements, essentially serving normative aspects, represented in reference manuals and design guidelines, disconnected from the cultural context, and environmental work. Therefore, the main objective of this thesis is a proposal for evaluation of functional and emotional requirements of the product, under the user's perspective. Qualitative methods were addressed (such as interviews, focus group and case study) and quantitative methods (such as multivariate data analysis). This research presents five articles related to the topic. It is emphasized as main results: (i) a review of concepts which show how the perception of the user contributes to innovation in product development context; (ii) a classification of requirements assessment methods according to users’ requirements; (iii) a conceptual model for integration of QFD (Quality Function Deployment) and Kansei Engineering methods, that is related to functional and emotional requirements respectively, was applied to the case of a product from hygiene and beauty industry; (iv) proposal and validation of a data collection instrument for evaluation of hemodialysis session, under the patient's perspective, considering the usability, emotional and economic requirements; (v) evaluation of the hemodialysis session, from the patients’ perception, considering attending to usability, emotional and economic requirements. As main conclusion, the thesis presents a product evaluation in its context of use, according to the aesthetic and practical functions which was evaluated in combination, in a multidimensional perspective. Thus it is possible to extrapolate guidelines for improvements in products and provide innovation in future projects.

Context. Non-functional requirements (NFRs) are important aspects which directly or indirectly determine whether a product is a success or a failure. It becomes essential to incorporate and understand them, before the software product enters the development phase. Despite the increasing emphasis put into NFR studies (namely; models and frameworks etc.) over the past few years, most industries prefer not use these techniques or to deal with NFRs later, in simpler manners. This could limit the efficiency of the development process. Integration of the existing NFR models/frameworks into the earlier phases of the product life cycle can provide a systematic approach to plan and anticipate NFRs for any software product. Objectives. This study aims to provide a generic meta model which acts as a compilation of the best NFR models/frameworks integrated into the early phases of the software product life cycle. This study also provides a real-world example which applies the conceptual meta model. Lastly, the meta model undergoes some limited validation to determine its relevance to what is being used and the extent of its practical use. Methods. Initially, a systematic literature review (snowballing) was conducted, to identify the different types of NFR models/frameworks. A comparative pro-con analysis was performed on the results of the SLR, which was the basis of the inclusion criteria for the meta model. The conceptual meta model was developed based on the International Software Product Management Association’s (ISPMA) definition of a product life cycle. Each phase of this meta model was imbedded with an NFR model/framework associated to the purpose of that phase and the results from the SLR. The application of the meta model was then demonstrated using a mobile phone example. Finally, the meta model was validated limitedly via an exploratory survey and the results were analyzed. Results. The meta model introduced can be used for the constructive inclusion of NFRs from product inception to product development. All phases required for the fulfillment of an NFR, are included. The overall positive feedback of the meta model is at 67%. Validations and assessments by practitioners helped determine to some extent that some industries are open to using the approach. Keeping in mind most of the available models on NFRs have not been validated, the NFR works used in this research have gone through some preliminary validation in this study. Conclusions. The study promotes the use of NFR models in the early phases of the software product life cycle. Some of the best modeling techniques were included based on results of literature analysis and their capability to fit into each phase. This study also analyzed the various insights of practitioners and researchers, justifying the significance of modeling, and the proposed technique. Possible extensions to this research were also mentioned.

Requirement engineering (RE) is an important phase in any project. Both functional and non-functional requirements are required to be elicited. Quality requirements (QRs) are usually catered at the end of software development process. Along with functional requirements, non-functional (QRs) also need to be handled and implemented through a structural way. It is observed that most organizations do not have proper management for quality requirements in their project life cycles. Especially if we consider the case of market driven requirement engineering (MDRE), it is a dire need to handle those QRs along with the functional requirement using a structural way. In this study we investigate Requirements Abstraction Model (RAM), which is basically designed for MDRE and is the case of continuous RE. The purpose was to analyze RAM specifications, which could be able to provide an effective way of manage QRs. RAM also deals with the specification of QRs, so it was required to investigate that how effective RAM can handle the creation of QRs.

In this thesis, we tried to solve those problems by adapting agile development methods with Non-functional requirements-framework (NFR-Framework). In this thesis, we have inspected many research papers, and we have met industrial experts for feedback regarding our theoretical results. As a result of the inspection, we have been able to adapt agile development methods (extreme programming (XP)) with NFR-framework. We use XP since it is more practically oriented process than other agile development methods. In the first try for this process model, we got three alternatives for applying it. The first one is based on collecting all NFRs from the beginning of the development process. The second one is based on updating the SIG (software interdependency graph) every time we have new functional requirements (FR) and the third one is based on the incremental nature of agile development methods. Each one of these alternatives has it is own advantages and disadvantages. We tried to extract those advantages and disadvantages by brainstorming and reading research papers. The most important issue in all of the three alternatives is the applicability. Finally we got industrial feedback regarding all of them. As a result of the industrial feedback, we were able to find another alternative of how to apply the process model which is presented in 7.2.

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). ..."

Today's vehicles are increasingly controlled by embedded computer systems. Such systems are of safety-critical nature, where an error in the computation could have dire consequences. A common way to ensure that software works is testing, but as the complexity of these systems grows larger it gets harder to ensure enough coverage in the tests. Another way to ensure that software fulfills its requirements is formal verification, where properties of the code are proven mathematically to hold under certain conditions. Formal verification gives a higher level of confidence in the correctness of code than testing alone, but it is not as widely used within the industry. This project has examined whether current state-of-the-art tools for formal verification are ready to be used to verify real-life safety-critical code. To answer this, a case study on a module running in Scania's vehicles was performed. Several of the requirements were successfully verified. The thesis also identifies for what type of code and requirements this is possible, and describes a process for how it can be done. / Idag kontrolleras fordon allt mer av inbyggda datorsystem. Sådana system är säkerhetskritiska, där ett fel kan ha ödesdigra konsekvenser. Ett vanligt sätt att försäkra sig om att mjukvaran fungerar är testning, men när komplexiteten av dessa system växer blir det allt svårare att försäkra sig om att testen har tillräcklig täckning. Ett annat sätt att försäkra sig om att mjukvaran uppfyller dess krav är formell verifiering, där egenskaper hos koden bevisas matematiskt att hålla under vissa villkor. Formell verifiering ger ett högre förtroende för kods korrekthet än vad enbart testning skulle göra, men används ännu inte i lika stor utsträckning inom industrin. Detta projekt har undersökt huruvida moderna verktyg för formell verifiering är mogna att användas för att verifiera riktig säkerhetskritisk kod. För att svara på detta har en fallstudie av en modul i Scanias fordon genomförts. Flera av dess krav lyckades verifieras. Rapporten identifierar också för vilka typer av kod och krav detta är möjligt, och beskriver en process för hur det kan utföras.

[pt] Modelos orientados a metas tornaram-se ferramentas importantes para a Engenharia de Requisitos Não Funcionais (RNF). Porém, o tratamento de RNFs é uma tarefa não trivial, visto que esta classe de requisitos abrange as características de qualidade de um sistema. Isso implica que, ao lidar com requisitos subjetivos, precisamos nos concentrar em mecanismos que possam enriquecer a semântica de sua representação. É o caso da atribuição e propagação de rótulos na análise de modelos orientados a metas. A definição de rótulos nos modelos de metas, realizada pelos métodos de análises qualitativos existentes, tem baixa granularidade e muitas vezes falha em refletir o potencial informativo que esse tipo de artefato pode oferecer. Esse é o caso do NFR Framework. A propagação no modelo ocorre de baixo para cima (bottom-up) e o entendimento sobre o grau de satisfação de uma meta torna-se difícil. Este trabalho explora uma lógica para aumentar o poder informativo dos rótulos atribuídos as metas flexíveis, utilizando conceitos de colorimetria em modelos do tipo SIG (Softgoal Interdependency Graph). Investigamos como o uso de cores mitiga o desafio de aumentar a granularidade da análise dos modelos de metas, melhorando assim o entendimento sobre o grau de satisfação a contento definido para os RNFs analisados. / [en] Goal-oriented models have become important tools for the analysis of non-functional requirements (NFRs). However, the treatment of NFRs is a non-trivial task, considering that this class of requirements covers quality characteristics. This implies that when dealing with subjective requirements, we need to focus on mechanisms that can enrich the semantics of their representation. This is the case of assigning and propagating labels in the evaluation of goal-oriented models. The definition of labels in the goal models, carried out by the existing qualitative analysis methods, has low granularity and often fails to reflect the information potential that this type of artifact may offer. This is the case of the NFR Framework. Propagation in the model is bottom-up and understanding the degree of goal satisficing becomes difficult. This paper explores a rationale to increase the informative power of the labels assigned to the goals, using the concepts of colorimetry in the SIG (Softgoal Interdependency Graph). We discuss how color mitigates the challenge of increasing the granularity of goal models analysis, thus improving the evaluation of these models.

No description available.

A lot of research is done in requirements engineering and testing but often the extensive literature is missing on defining good methods for linking functional requirements with test cases. Most of the delays occurring in the software development projects are because of incomplete or inaccurate functional requirements. The two main goals of our project are to achieve a successful software project by First, to design a template, which will merge functional requirements with test cases and second is to find the benefits of the aligning requirements to test cases. Changing, updating and tracing the requirements during the development of the project is not an easy task. The main reason for project failure is due to possibility of not fulfilling specified project requirements, so one way to solve this problem is to merge functional requirements with test cases. Thus removes the need of creating a separate requirements document, which will improve the traceability process between requirements and testing, thus leads to high quality and efficient development. The template helps us to drive a successful project by identifying the issues at an earlier stage of the development cycle.