[pt] Um dos possíveis meios utilizados para a coleta de fatos na elicitação de requisitos é o uso do questionário. Um questionário consiste num documento usado para guiar uma ou mais pessoas a responder a uma ou mais perguntas. A elaboração de um questionário é um processo bem mais complexo do que possa aparentar. Um questionário mal formulado pode levar a considerações erradas, o que acaba sendo prejudicial ao projeto em questão. Não existe um método padrão para a construção de questionários, porém existem recomendações de diversos autores com relação a essa importante tarefa no processo de pesquisa científica. O trabalho aqui apresentado detalha a técnica de questionários, identificando as etapas necessárias e comuns à criação de um questionário eficaz. Será proposto um método para a construção de perguntas de questionários, que utiliza como base uma listagem de requisitos para a construção de questionários de qualidade, obtida após a realização de uma extensa pesquisa nas áreas de ciências sociais e marketing. Posteriormente apresentamos uma ferramenta utilizada para elicitação de requisitos de software, através da utilização de questionário, questionário esse gerado através do método proposto no presente trabalho. / [en] Questionnaire is one of the techniques available for requirements elicitation. A questionnaire is a document used to guide one or more people to answer one or more questions. The elaboration of a questionnaire is a process more complex than it can make look like. A questionnaire that is not well formulated can lead to unreliable information and may be harmful to the project in question. Although there is no standard method for the construction of questionnaires, there are recommendations from diverse authors with regard to this important task in the process of eliciting information. The work presented here details a technique for identifying the necessary and common stages for the creation of a questionnaire. A method for the construction of questions is proposed, which uses as base a list of requirements for the construction of quality questionnaires, obtained from the literature in the areas of social sciences and marketing. A tool for the elicitation of software requirements, by means of questionnaires is presented.

It has previously been shown that the quality of the onboarding process affects the chances of a new hire staying at a company, yet it is common that companies have problems in succeeding to maintain a well-organized onboarding. To aid new hires in their onboarding, and to lower the amount of work for the HR personnel, chatbots can be used. In this project, a chatbot was developed for the onboarding process of a large company. Interviews were held with new hires and HR personnel which were used to create requirements for the chatbot. These were divided into two categories; information and functional requirements. A third category, non-functional requirements, was created based on Microsoft’s guidelines for development of conversational AI. Based on the requirements, a chatbot prototype was built using Microsoft Bot Framework with the use of two cognitive services, LUIS and QnA Maker. Both the requirements and the prototype were created iteratively. The information that the interview participants requested from the chatbot was eitherpractical or personal information, or information about the employer, the internal systems, or other employees. It was revealed that the chatbot mainly needed to answer simple questions and didn’t demand any procedural conversation flow which made the use of QnA Maker appropriate. However, for questions and tasks that would benefit or require a procedural flow QnA Maker’s follow-up prompts could be used in future work to create multi-turn conversations.

A oferta de bens e serviços para atendimento da demanda dos consumidores atuais tem uma forte base na personalização, ou seja, na busca da satisfação individual dos clientes. Essa tem sido a forma que as empresas tem encontrado para se diferenciar. Para tanto, as organizações necessitam de modelos de negócios que permitam ajustar seus processos com as freqüentes necessidades de mudanças. A metodologia utilizada foi a observação de estudo de casos com projetos de Inovação Tecnológica, que possuem altos índices na característica de mudança dos requisitos. A proposta deste trabalho é permitir que essa volatilidade seja identificada na fase de eliciação de requisitos, com base nas intenções de cada envolvido no processo de engenharia de requisitos, e que tais solicitações possam ser melhor compreendidas através da prototipação baseada nas perspectivas dos participantes: de negócio, operacional, de design e gerencial. Como resultado foi definido o volaRE, que permite se conhecer a volatilidade de um requisito, com base nas características definidas do mesmo, ainda na fase de eliciação. / Current consumers have demanded a special attention in the production and distribution of goods and services which have turned organizations to mass customization, looking for an individual satisfaction of their customers. This has been the form that companies have found to differentiate themselves. Therefore, the integration of business and productive processes must be adaptable to the frequent changes in the company\'s environment. The used methodology was the observation of cases study with of Technological Innovation projects, which have high rates of requirements changes. The proposal of this work is that this volatility could be identified in the requirements elicitation phase, based on the intent of each involved in the process of requirements engineering, and that such requests can be better understood through perspectives prototyping based of those participants: business, operational, design and management. As result volaRE was defined, that lets to know the requirement\'s volatility, based on defined characteristics, yet at elicitation phase.

Stakeholder satisfaction has in the modern day, become an imperative criterion to achieve project success. Satisfaction of stakeholders’ requirements however is challenging because these requirements evolve as the project progresses. Previous research indicates that as stakeholders continuously interact with a project, they gain more information and new requirements or request for modifications are likely to emerge as a result of this increased intelligence.  Nonetheless, conventional project management elicits requirements from stakeholders at the onset of the project, and uses these pre-defined requests to design the project. This practice hinders the ability of stakeholders to influence the project as it advances, and ill equips managers to handle and implement stakeholder requirements that materialize at subsequent phases. It is therefore important to investigate how emergent requirements of stakeholders come about and how they are managed in practice.  The objective of this thesis is to answer the research question, “From the perspective of managers, in the Scandinavian management context, how do emergent requirements of key stakeholders materialize, and how are they managed?” by probing into the ways via which emergent requirement of stakeholders come about, and investigating how managers deal with these emergent requirement upon their occurrence.  This qualitative study was conducted in the Scandinavian region using semi-structured interviews. Five respondents in managerial positions of the Umeå wastewater treatment plant project participated in the research and data collected concerned materialization and management of emergent requirements that surfaced during different phases of the project. The resulting data was then analyzed with reference to previously established theoretical frameworks.  Results from this study confirm that, new or modified requirements and consequently, requests for changes do emerge at even the execution phase of projects, despite careful planning. These emergent requirements are traced to three different sources and are managed in different ways depending on the type of requirement, whether strategic and critical or minor.

A oferta de bens e serviços para atendimento da demanda dos consumidores atuais tem uma forte base na personalização, ou seja, na busca da satisfação individual dos clientes. Essa tem sido a forma que as empresas tem encontrado para se diferenciar. Para tanto, as organizações necessitam de modelos de negócios que permitam ajustar seus processos com as freqüentes necessidades de mudanças. A metodologia utilizada foi a observação de estudo de casos com projetos de Inovação Tecnológica, que possuem altos índices na característica de mudança dos requisitos. A proposta deste trabalho é permitir que essa volatilidade seja identificada na fase de eliciação de requisitos, com base nas intenções de cada envolvido no processo de engenharia de requisitos, e que tais solicitações possam ser melhor compreendidas através da prototipação baseada nas perspectivas dos participantes: de negócio, operacional, de design e gerencial. Como resultado foi definido o volaRE, que permite se conhecer a volatilidade de um requisito, com base nas características definidas do mesmo, ainda na fase de eliciação. / Current consumers have demanded a special attention in the production and distribution of goods and services which have turned organizations to mass customization, looking for an individual satisfaction of their customers. This has been the form that companies have found to differentiate themselves. Therefore, the integration of business and productive processes must be adaptable to the frequent changes in the company\'s environment. The used methodology was the observation of cases study with of Technological Innovation projects, which have high rates of requirements changes. The proposal of this work is that this volatility could be identified in the requirements elicitation phase, based on the intent of each involved in the process of requirements engineering, and that such requests can be better understood through perspectives prototyping based of those participants: business, operational, design and management. As result volaRE was defined, that lets to know the requirement\'s volatility, based on defined characteristics, yet at elicitation phase.

Requirements engineering (RE) is the primary task (process) that is done when agreed upon to develop a software product. The success of the software product is gauged on its ability to meet the intended needs of the stakeholders. There is abundant literature emphasizing the significance of RE and its influence on the entire software project, apart from its importance as the first step for a successful development endeavor. There are several established methodologies that are acknowledged to support the RE process and assist in creating a reliable structure of creating software. Despite the availability of such techniques and solutions, it was observed that umpteen number of software product failures are attributed to unsatisfactory RE practices. In this thesis, we have conducted a study with six organizations to emphasize the gap between the state of the art and the state of the practice, and consequently identify the factors that hinder the industrial community to implement state of the art RE. As a result of this empirical research we have found that to a great extent, state of the art practices are unpopular, more specifically in small organizations. Interestingly the majority of the problems associated with RE are associated to non technical issues.

Context: In the requirements engineering phase, requirements elicitation is considered as the most important task as it is the initial phase in which the requirements are gathered and prioritised. Changes in requirements may lead to project failure or delay in project deliveries. So, it is essential to elicit the requirements at the early stage to avoid changes in requirements in the later stage of development. Therefore, there is a need to study the impact of volatility in elicitation techniques to gather requirements appropriately in the early stages. Objectives: In the present thesis, we focused on the analysis of the requirements volatility in the requirement elicitation phase. The main objectives we have formulated to achieve our goal are Objective 1: To identify and determine the various causes of requirement volatility. Objective 2: To examine the impact of requirement volatility in the requirement elicitation process. Objective 3: To examine whether the procedure of elicitation techniques differ if volatility occurs while eliciting the requirements. Methods: In this thesis, we have implemented a Systematic Literature Review(SLR) and Survey research methods in order to attain our aim and objectives. SLR is performed for objective 1, to receive the data about the causes of volatility in various development life cycle phases. A survey is conducted to identify the causes of volatility in all phases of development, in the elicitation phase, and check whether the process of elicitation techniques differ if volatility occurs while eliciting the requirements. Results: From the SLR and survey, numerous factors of causes of volatility on the software development lifecycle were identified. Several new factors were identified from both the research methods. The factors have its own interpretation for the cause of volatility. Moreover, from the survey results, we can determine that the volatility occurs in the elicitation phase and has a huge impact while eliciting the requirements. Most of the practitioners working with the agile development process and waterfall model have stated that the impact of volatility results in prolonging the elicitation phase, slowing down the project, etc. Conclusions: For this research, our contribution is to provide insights on the impact of volatility in the elicitation process and check whether the elicitation techniques and its process change due to volatility. Based on the results of the respondents, we can conclude that the elicitation techniques procedure change is not intentional and not only because of the volatility but also due to some external factors while eliciting the requirements.

This thesis was conducted by two students as part of their Strategic Information Systems Management degree program at Stockholm University. As presented in this study, the manual elicitation processes in Requirements Engineering are error-prone and time-consuming. Traditional approaches and techniques often produce requirements that are characterized by ambiguity, inadequacy, incompleteness, inconsistency, and obsolescence. The research problem is focused on the lack of clear understanding regarding AI's specific role in supporting the identification of precise and detailed requirements, and the need for summarizing findings of related work. The goal of this thesis is to investigate the impact of AI in Requirements Engineering, focusing primarily on Requirements Elicitation and Analysis. After presenting essential background knowledge of Requirements Engineering, traditional elicitation methods, and Artificial Intelligence, a systematic literature review was performed to unveil Artificial Intelligence methods, techniques, and tools used in Requirements Elicitation and Analysis. With the assistance of the PRISMA methodology, the key findings and results were summarized and presented. The majority of the online literature focused on various issues connected with traditional methods and presented how Artificial Intelligence Chatbots, Text Mining and Natural Language Processing techniques, Virtual Reality, Sentiment Analysis, Crowdsourcing, Deep Learning Techniques, Gamification, and Bayesian Networks are improving the quality and speed of Requirements Elicitation. One of the main challenges faced is that there is no extensive comparison with traditional methods and metrics on how Artificial Intelligence overall helps Requirements Elicitation – only metrics per case. Also, there is not explicit definition regarding which AI methodologies and tools are appropriate for each elicitation and analysis method.

Made available in DSpace on 2015-04-11T14:02:51Z (GMT). No. of bitstreams: 1 Sergio Roberto Costa Vieira.pdf: 3218639 bytes, checksum: 3935b43e35cc99b70f873c5ddb6e1882 (MD5) Previous issue date: 2012-07-18 / This thesis presents a requirements elicitation technique guided by business processes modeling. This technique, called REMO (Requirements elicitation by oriented Business Process Modeling), uses a set of heuristics to extract the software requirements from business process diagrams. The purpose of the technique is to aid systems analysts in the identification of functional requirements, non-functional requirements, and business rules. To accomplish such task, the REMO technique uses business process diagrams created using the BPMN (Business Process Modeling Notation) notation. This thesis describes how the REMO technique was created and evaluated using an empirical-based research method. Furthermore, we present the analyses of the results obtained through three controlled experiments, which showed evidence that the REMO technique may be considered useful to be applied in software development during a requirements elicitation. / Esta dissertação apresenta uma técnica de elicitação de requisitos orientada pela modelagem de processos de negócios. A técnica de elicitação é denominada como REMO (Requirements Elicitation oriented by business process MOdeling), uma técnica que utiliza um conjunto de heurísticas para extrair os requisitos de software a partir dos diagramas de processos de negócios. O propósito da técnica é apoiar os analistas de sistemas na identificação dos requisitos funcionais, não funcionais e regras de negócios a partir dos diagramas de processos de negócios feitos em BPMN (Business Process Modeling Notation). Esta dissertação descreve como a técnica REMO foi elaborada e avaliada por meio de um método de pesquisa baseado em experimentação. Além disso, apresentam-se as análises dos resultados obtidos de três estudos experimentais controlados, que apontaram indícios de que a técnica REMO pode ser considerada útil para ser aplicada no desenvolvimento de software durante a elicitação de requisitos.

Context. Global Software Development (GSD) is the plan of action in which software development is performed under temporal, political, organizational and cultural boundaries. Offshore outsourced software development is the part of GSD, which refers to the transfer of certain software development activities to an external organization in another country. The primary factors driving offshore outsourced software development are low cost, access to a large pool of skilled laborers, increased productivity, high quality, market access and short development cycle. Requirements engineering (RE) and especially requirements elicitation is highly affected by the geographical distribution and multitude of stakeholders. Objectives. The goal of conducting this study is to explore the challenges and solutions associated with requirements elicitation phase during offshore software projects, both in research literature and in industrial practice. Moreover, this study examines that which of the challenges and practices reported in literature can be seen in industrial practice. This helped in finding out the similarities and differences between the state of art and state of practice. Methods. Data collection process has been done through systematic literature review (SLR) and web survey. SLR has been conducted using guidelines of Kitchenham and Charters. During SLR, The studies have been identified from the most reliable and authentic databases such as Compendex, Inspec (Engineering village) and Scopus. In the 2nd phase, survey has been conducted with 391 practitioners from various organizations involved in GSD projects. In the 3rd phase, qualitative comparative analysis has been applied as an analysis method. Results. In total 10 challenges and 45 solutions have been identified from SLR and survey. Through SLR, 8 challenges and 22 solutions have been identified. While through industrial survey, 2 additional challenges and 23 additional solutions have been identified. By analyzing the frequency of challenges, the most compelling challenges are communication, control and socio-cultural issues. Conclusions. The comparison between theory and practice explored the most compelling challenges and their associated solutions. It is concluded that socio-cultural awareness and proper communication between client and supplier organization’s personnel is paramount for successful requirements elicitation. The scarcity of research literature in this area suggests that more work needs to be done to explore some strategies to mitigate the impact of additional 2 challenges revealed through survey. / 0046 707123094