Este trabalho descreve a definição e institucionalização de um processo de engenharia de requisitos que está em conformidade com as áreas de processo do CMMI (Capability Maturity Model) de Gerência de Requisitos e Desenvolvimento de Requisitos e cujos componentes (atividades, papéis, produtos de trabalho) são baseados em RUP (Rational Unified Process). A principal contribuição deste estudo é a definição de um processo de engenharia de requisitos baseado em abordagens de desenvolvimento diferenciadas, que foi implantado em uma organização específica, com foco em praticidade, eficiência e retorno do investimento. A implantação do processo em projetos reais permitiu sua experimentação, avaliação e refinamento, validando as alternativas de integração utilizadas para empregar as abordagens de desenvolvimento escolhidas. Complementando o processo proposto, como decorrência do foco em eficiência, são consideradas possibilidades de emprego de práticas de métodos ágeis na execução do processo, com o intuito de aumentar a produtividade do mesmo, sustentando sua garantia de qualidade. O processo proposto é descrito, do método de concepção aos passos envolvidos e artefatos gerados em cada atividade. Também são comentadas as etapas e áreas de trabalho envolvidas na institucionalização do trabalho. / This research depicts the definition and institutionalization of a requirements engineering process which is in conformance to CMMI (Capability Maturity Model) Requirements Management and Requirements Development process areas. The proposed process components (activities, roles, work products) are based on Rational Unified Process (RUP) process framework. The proposed process main contribution is the definition of a requirements engineering process, leveraging such diverse development approaches, which was implemented in a specific organization, focusing on practicality, efficiency and return on investment. Implementing such process in real projects has promoted its experimentation, evaluation and refinement, validating the integration alternatives used to bring together the chosen development approaches. The possibility of employing agile methods practices through the process execution is discussed, aiming at increasing the process productivity, while assuring product quality. The proposed process details are described, from method conception to each activity steps and generated artifacts. The process institutionalization phases and work areas are also commented.

Abstract Requirements engineering (RE) is an important process in systems development. This research was carried out in the context of Very Large-Scale Requirements Engineering (VLSRE) within the scope of a requirement screening (RS) process. The RS process is defined as a front-end process for screening incoming requests, which are received in a constant flow. The goal of the RS process is to efficiently identify the most promising requests for further analysis, development and implementation while filtering out non-valuable ones as early as possible. The objective of this study was to understand the challenges related to the RS process and develop solutions to address those challenges. A qualitative research approach was utilised to achieve the research goals. The overall research process follows an action research method, in which each action research cycle includes at least one individually defined and executed case study. Action research and case studies are research methods that are well suited to studying real-life phenomena in their natural settings. This research was carried out in two case companies in the information and communication technology domain. Data from 45 interviews were analysed for preparing publications I–V, which are included in this thesis. In addition, during the longitudinal action research study described in this thesis, data from 26 interviews and 132 workshops were utilised to develop solutions for the RS process, which is an industrial implementation of the VLSRE process. The conducted action research contributes to the field of software engineering, in which such research efforts are currently lacking. This research has identified a number of significant challenges that different stakeholders face related to requirements processing and decision making in the VLSRE context. Examples of these challenges are the great number of incoming requirements, the lack of information for decision making and the feasibility of utilised tools. To address the identified challenges, a requirements architecting method was developed. The method includes a dynamic requirement template, which gathers structured information content for eliciting requests, documenting and communicating requirements and forming features while considering the needs of different stakeholders. The method was piloted, validated and deployed in industry. / Tiivistelmä Tutkimus toteutettiin laajamittaisen vaatimusmäärittelyprosessin kontekstissa keskittyen vaatimusten seulontaprosessiin. Vaatimusten seulontaprosessi määritellään tuotekehityksen alkuvaiheen prosessiksi, jossa käsitellään jatkuvana vuona tulevia kehityspyyntöjä. Vaatimusten seulontaprosessissa pyritään tunnistamaan tehokkaasti lupaavimmat pyynnöt jatkoanalyysiä, tuotekehitystä ja toteutusta ajatellen sekä suodattamaan pois niin aikaisessa vaiheessa, kun mahdollista ne pyynnöt, joilla ei ole arvontuotto-odotuksia. Tutkimuksen tavoite oli ymmärtää haasteita, jotka liittyvät vaatimusten seulontaprosessiin sekä kehittää ratkaisuja näihin haasteisiin. Tutkimuksessa käytettiin laadullisen tutkimuksen menetelmiä. Kokonaisuutena tutkimusprosessi noudattaa toimintatutkimuksen periaatteita siten, että jokainen sykli tai sen vaihe sisältää yhden tai useamman itsenäisesti määritellyn tapaustutkimuksen suunnittelun ja läpiviennin. Valitut tutkimusmenetelmät soveltuvat hyvin tilanteisiin, joissa tutkimuskohteina ovat reaalimaailman ilmiöt niiden luonnollisissa ympäristöissä havainnoituina. Tutkimusaineisto kerättiin kahdesta informaatio- ja kommunikaatioteknologia-alan kohdeorganisaatiosta. Väitöskirjaan sisällytettyihin julkaisuihin I-V on analysoitu 45 haastattelun aineisto. Näiden lisäksi väitöskirjassa kuvatun pitkäkestoisen toimintatutkimuksen aikana hyödynnettiin 26 haastattelun ja 132 työpajan aineistoa kehitettäessä ratkaisuja vaatimusten seulontaprosessin haasteisiin. Vaatimusten seulontaprosessi on laajamittaisen vaatimusmäärittelyprosessin teollinen toteutus. Tutkimuksessa tunnistettiin useita merkittäviä haasteta, joita eri sidosryhmillä on liittyen vaatimusten seulontaprosessiin ja päätöksentekoon laajamittaisessa vaatimusmäärittelyprosessissa. Vaatimusten suuri määrä, päätöksentekoon tarvittavan tiedon puute ja käytössä olevien työkalujen soveltumattomuus ovat esimerkkejä tunnistetuista haasteista. Ratkaisuna haasteisiin kehitettiin vaatimusten seulonta- ja analyysimenetelmä. Kehitetty menetelmä sisältää dynaamisen vaatimusdokumentin, jonka avulla voidaan kerätä kehityspyyntöjen tietosisältö jäsennellysti, dokumentoida ja kommunikoida vaatimukset sekä muodostaa niistä tuotteisiin toteutettavia ominaisuuksia ottaen huomioon eri sidosryhmien tarpeet. Kehitetty menetelmä on koestettu, validoitu ja soveltuvin osin otettu käyttöön teollisuudessa.

Managing a software project is an increasingly complex task as it demands the quality of the final product to increase. Thus, e ective management is required from project design to software deployment and maintenance. According to the literature found, Requirements Engineering is the most important phase in terms of final impact on a software project. Changes in software requirements occur throughout the software process, from elicitation and requirements analysis to software operation. Requirements traceability enables one to identify the source and the dependency among software requirements. Studies show that current requirements traceability tools and methods are insu cient which makes it di cult to use traceability in practice. The goal of this work was the proposal of a requirements traceability technique combined with a modeling language and supported by a tool. To achieve this goal, bibliographic review, state-of-the-art research, comparative analysis, questionnaire and interviews were used as research instruments. Initially, an analysis of requirements traceability techniques and evaluation of requirements traceability tools were performed to evaluate if the techniques are used in practice and are being supported by software tools. After these analysis, an event-based traceability technique was proposed using concepts from the SysML modeling language. A software tool was developed to support this technique. Whenever a requirement is modified, the tool notifies stakeholders of such change made to the system requirements through e-mail. The technique and the tool were evaluated by twenty four information technology professionals using a questionnaire based on the TAM model that encompasses the concepts of perceived utility, perceived ease of use and perceived use, and interviews. As a result, the lack of relationship between the techniques and the tools surveyed was observed, and the criterion of automatic communication with stakeholders was not addressed in any evaluated tool. With regard to the proposed technique and tool, a wide acceptance of technique and tool was observed. The acceptance of the proposals was carried out by professionals with varied experiences in software development. / Gerenciar um projeto de software é uma tarefa cada vez mais complexa à medida que as exigências sobre a qualidade do produto final aumentam. Assim, é preciso um gerenciamento eficaz desde a concepção do projeto até a implantação e manutenção do software. Segundo a literatura encontrada, a Engenharia de Requisitos é a fase que possui maior impacto em um projeto de software. As mudanças nos requisitos de software ocorrem ao longo do processo de software, desde a elicitação e análise de requisitos até a operação do software. A rastreabilidade de requisitos possibilita identificar a origem e a dependência entre os requisitos de software. Estudos mostram que as ferramentas e métodos de rastreabilidade de requisitos atuais são insuficientes e dificultam o uso prático da rastreabilidade. O objetivo deste trabalho é a criação de uma técnica de rastreabilidade de requisitos combinada com uma linguagem de modelagem e que seja apoiada por uma ferramenta. Para atingir este objetivo, foram utilizados como instrumentos de pesquisa a revisão bibliográfica, uma pesquisa do tipo estado da arte, análise comparativa, questionário e entrevistas. Inicialmente, foram realizadas análise das técnicas de rastreabilidade de requisitos e avaliação de ferramentas de rastreabilidade de requisitos com intuito de avaliar se as técnicas são utilizadas na prática, e se estão sendo apoiadas por ferramentas de software. Após estas análises, foi proposta uma técnica de rastreabilidade entre requisitos baseada em eventos utilizando conceitos da linguagem de modelagem SysML. Uma ferramenta de software foi desenvolvida para apoiar essa técnica. Sempre que um requisito é modificado, a ferramenta notifica aos stakeholders a alteração realizada nos requisitos do sistema por meio de e-mails. A técnica e a ferramenta foram avaliadas por vinte e quatro profissionais de tecnologia da informação utilizando questionário, baseado no modelo TAM, que engloba os conceitos de utilidade percebida, facilidade de uso percebido e uso percebido, e entrevistas. Como resultado, foram observados a falta de relação entre as técnicas e as ferramentas pesquisadas e que o critério de comunicação automática com stakeholders não foi abordado em nenhuma ferramenta avaliada. Com relação à técnica e ferramenta propostas, observou-se uma ampla aceitação da técnica e da ferramenta. A aceitação das propostas foi realizada por profissionais com experiências variadas em desenvolvimento de software.

Kravhanteringen är en av de viktigaste delarna i ett systemutvecklingsprojekt. I kravhanteringen ingår aktiviteter som att samla in krav, analysera och prioritera vilket är för att skaffa sig en så tydlig bild av det framtida resultatet som möjligt. I alla aktiviteter i kravhanteringen kommuniceras det mellan olika intressenter. Kommunikation är en vital del av kravhanteringen då projektteamet tillsammans med kunden identifierar och tar fram kund- och användarbehov genom en rad aktiviteter.Covid-19 pandemin påverkade hela världen och för att begränsa smittspridningen togs beslut om att de som kunde jobba hemifrån skulle göra det. Detta ledde till att många verksamheter fick anpassa sig efter distansarbete och kommunikation i virtuella miljöer vilket påverkade kommunikationen på olika sätt. Syftet med uppsatsen är att besvara frågan hur kravhanteringsfasen har påverkats av en omställning till distansarbete. För att samla in relevant data har kvalitativ forskningsmetod använts och semi-strukturerade intervjuer har genomförts. Den insamlade data har analyserats med hjälp av en tematisk analys där två systemutvecklingsmodeller agila metoden och vattenfallsmodellen togs upp. Resultatet av uppsatsen påvisar att alla på ett eller annat sätt påverkats av distansarbete. Det framgick att kommunikationen i kravhanteringen påverkats extra. Projektteamen försökte lösa utmaningarna genom en rad olika metoder, men lösningarna resulterade i att kravhanteringen inte påverkades resultatmässigt eller påverkat systemutvecklingsprojektet utgång. Kravhanteringen tog dock längre tid och projektteamen fick arbeta hårdare för att nå samma resultat som om det skett ansikte mot ansikte. Resultatet av studien beskriver att kommunikation i virtuell miljö bara är ett substitut i stället för att genomföra fysiska möten. / Requirements management is one of the most important parts of a system development project. Activities such as collecting requirements, analyzes and prioritizing to obtain as clear picture of the future result as possible. In all the activities in requirements management, it communicates between different stakeholders. Communication is a vital part of requirements management, as the project team together with the customer identifies and develops customer and user needs through the process. The Covid-19 pandemic affected the whole world and to limit the spread of infection, it was decided that everyone who could work from home would work from home. This led to many businesses having to adapt to teleworking and communication in virtual environments. This affected communication in different ways. The purpose of the thesis is to answer the question of how the requirements management phase has been affected by the transition to telework. To collect relevant data, qualitative research methods have been used and semi-structured interviews have been conducted. The collected data have been analyzed with the help of a thematic analysis where two system development models were taken up, the agile method and the waterfall model. The results of the essay show that everyone has been affected in one way or another by teleworking. It appeared that communication in requirements management was particularly affected. The project teams tried to solve the challenges through a number of different methods, but the solutions resulted in the requirements management not being affected in terms of results or affecting the outcome of the system development project. However, the requirements management took longer, and the project teams had to work harder to achieve the same results as if it had happened face to face. The results of the study describe that communication in a virtual environment is only a substitute for meeting face to face.

Sweden produced 215 kilotons of electronic waste in 2016. One way to reduce this amount is to repair electronic devices when they fail instead of replacing them. The company Mavenoid has a troubleshooting service in the form a web application to help troubleshoot machines like for example consumer electronics. The company desired a tool to visualize data about the usage of the troubleshooting models in their web app. The prospect was that the users who build the troubleshooting models would be able to analyse how their models are being used and how well they work with the tool. To implement the tool, a method with three phases was used. An initial preparation phase with requirements elicitation via a domain analysis and set-up of the development environment, a development phase with iterative development and requirements management with weekly meetings and an analysis phase with evaluation of the tool according to the requirements and the status of a pull request. The product met eight out of ten requirements and was of a sufficiently high quality that it could be integrated into the company’s system. The use of the library C3 resulted in a 21% increase of the web application’s build size. / Sverige producerade 2016 215 kiloton elektronikavfall. Ett sätt att minska denna mängd är att reparera elektronik när den fallerar istället för att byta ut den. Företaget Mavenoid erbjuder en tjänst i form av en React webapplikation för att underlätta felsökning av maskiner som t.ex. hemelektronik. Företaget eftersökte ett verktyg för att visualisera data om användningen av felsökningsmodellerna i sin webbapplikation. Förhoppningen var att de användare som bygger modellerna via det nya verktyget skulle kunna analysera hur deras modeller används och väl de fungerar. För att utveckla verktyget användes en metod med tre faser. En inledande förberedelsefas med kravinsamling via en domänundersökning och uppbyggnad av utvecklingsmiljö, en utvecklingsfas med iterativ utveckling och kravhantering med veckomöten och en analysfas med utvärdering av verktyget efter kraven och status på en pull-request. Produkten uppfyllde åtta utav tio av de insamlade kraven och var av tillräckligt hög kvalitet att integreras i företagets system. Användningen av biblioteket C3 medförde att webapplikationens transaktionsstorlek ökade med ca 21%

This report describes the development of a RESTful web service for mobile applications. The web service makes resources from an existing system called kompetensdatabasen ("the competence database") available. Kompetensdatabasen holds information about the capabilities of consultants and about assignments carried out at the IT consultant business Nethouse AB. The web service was developed according to the principles of REST and ROA (Resource Oriented Architecture) which puts focus on making resources available. The resources are made available through the HTTP protocol and the methods associated with it. This means it was designed to use the same technologies as the world wide web. Following these principles when designing the system has been of great importance. To make sure that the service does not leak information to competing companies or violate the Personal Data Act some kind of solution for securing the service had to be implemented. A model for authentication was produced to make the system accessible only for employees of the company. / Rapporten beskriver utvecklandet av en RESTful web service för mobilapplikationer. Web servicen tillgängliggör resurser från ett befintligt system som kallas kompetensdatabasen. Kompetensdatabasen innehåller information om konsulters kompetenser och de uppdrag som utförts vid IT-konsultföretaget Nethouse AB. Web servicen utvecklades enligt principerna för REST och ROA (Resource Oriented Architecture) vilket innebär ett fokus på att tillgängliggöra resurser. Resurserna görs nåbara genom HTTP-protokollet och dess metoder, det vill säga samma tekniker som används på webben. Stor vikt har lagts på att designa systemet enligt dessa principer. För att servicen inte skulle läcka information till konkurrenter eller bryta mot personuppgiftslagen behövde någon form av säkerhetslösning implementeras. En autentiseringsmodell togs fram för att göra systemet nåbart enbart för anställda vid företaget.