Trots att användarmedverkan borde vara ”best practice” för att skapa ömsesidigt värde för både beställare och användare inom kravfångst är detta inte fallet. Eftersom Service Design betraktas vara bra för ömsesidigt värdeskapande undersöker rapporten vilka tre Service Designverktyg som kan vara ett alternativ för att fånga krav som speglar ömsesidigt värde. Genom en litteraturstudie visar rapporten att Customer journey maps, personas och shadowing är de tre vanligaste verktygen; av dessa tre anser systemutvecklare att Customer journey maps lämpar sig bäst för kravfångst på grund av förmågan att belysa problem hos både användare och beställare. Detta verktyg tillämpas tillsammans med serviceleverantör och användare i tre workshops och utifrån dessa redogörs egna praktiska erfarenheter och hur dessa upplevdes av deltagande serviceleverantör och användare. Rapporten visar att Customer journey maps är ett bra alternativ för ömsesidigt värdeskapande inom kravfångst och att shadowing och personas fokuserar mer på användaren än beställaren av ett system. / In order to create co-value for both clients and users in requirements elicitation, user participation should be best practice – but research shows that it is not. In this thesis, Service Design is seen as an enabler for co-value creation between clients and users. The thesis examines if the three most common Service Design tools can be an alternative to capture requirements that reflect co-value for both the client and the users. Through a literature review this thesis reveals that customer journey maps, personas and shadowing are the three most common tools and that system developers believes that the Customer journey maps are best suited for requirements elicitation due to the ability to highlight problems of both users and clients. This tool is applied together with the service provider and the user in three workshops and based on these, the thesis outlines practical experiences and how this tool is experienced by participating service provider and user. The report reveals that Customer journey maps is a viable option for co-value creation in requirements elicitation whereas shadowing and personas are more focused on the users of a system than the client of a system.

The purpose of the study is to elaborate the Wizard-of-Oz (WOz) technique by using it at a distance for design and elicitation of requirements and requests as part of a Participatory Design process (i.e. remotely - where the wizard and participant are located in different geographical locations). This study aims at evaluating what the salient traits in the participatory discussions are by using the WOz technique at a distance, what similarities there are in function or expression between non-verbal expressions in GUI-ii and ordinary physical interviews, and how WOz at a distance fit into the current state of the Participatory design field. In an early design phase of a project, ten experimental WOz-at-a-distance sessions and five face-to-face interviews were held. The experimental sessions’ focus was on the codesign of early drafts of the interaction design for a digital tool for the planning of crisis management exercises. The interaction design was developed with a WOz system. The sessions offered co-design between a designer and a co-designer by having joint access to a graphical user interface (GUI), and to verbally communicate with each other. These sessions had a twofold approach where the focus could shift seamlessly between design and walkthrough. The results from this study show that WOz at a distance, as used in this study, offers an approach for a seamless switch between design-phase and evaluation-phase in the form of walkthroughs. Having the GUI present as a boundary object whilst discussing the GUI and its interaction design enables a natural way of designing and evaluating the functions and interaction design of the upcoming system. The results also show that even if the participatory discussion lacks the face-to-face meeting between the interlocutors there are some similarities between those discussions and the face-to-face interviews in function and use of non-verbal expressions. Participatory discussions, when using WOz technique at a distance is a method where the participatory mindset is prominent and is a flexible approach that fits well with the overarching views on Participatory design.

Several studies have applied recommender technologies to support requirements engineering activities. As in other application areas of recommender systems (RS), many studies have focused on the algorithms’ prediction accuracy, while there have been limited discussions around users’ interactions with the systems. Since recommender systems are designed to aid users in information retrieval, they should be assessed not just as recommendation algorithms but also from the users’ perspective. In contrast to accuracy measures, user-related issues can only be effectively investigated via empirical studies involving real users. Furthermore, researchers are becoming increasingly aware that the effectiveness of the systems goes beyond recommendation accuracy, as many factors can be relevant to their adoption besides accuracy. To better understand recommender systems in RE, it has become necessary to explore them from users’ perspectives. Consequently, this research evaluates a feature recommender system from users’ perspectives adopting the “Recommender systems’ Quality of user experience” (ResQue) model - a user-centered evaluation model from the RS field. This was done by designing a content-based feature recommender system and then assessing it from the users’ view point. A between-subjects user study was conducted involving two groups of participants, an experimental and a control group. The experimental group interacted with the feature recommender system while developing a list of software requirements for a software product (an antivirus software). In contrast, the control group performed the same task without receiving support from the recommender. After completing the task, both groups completed a post-task evaluation questionnaire, including questions about their experiences and opinions about the task they completed. In addition, participants in the experimental group rated their perceptions of various aspects of the recommender; question items were adapted from the ResQue questionnaire. Users’ subjective evaluation of the recommender was investigated using the ResQue constructs - perceived system qualities, user beliefs, user attitudes, and behavioral intentions. Additionally, the impact of recommendations on the requirements elicitation process was assessed in terms of the process and outcome level measures. Possible qualitative differences were also examined. Users' preferences were identified, and possible HCI issues requiring attention in recommender systems used in RE are discussed.

[pt] Esta dissertação estuda um meio de apoiar a elicitação de requisitos, utilizando reuniões. Para isso utiliza a gerência de conflitos, que através do estímulo aos conflitos funcionais e do controle e tratamento dos conflitos não funcionais, visa à criação de idéias e o dinamismo da reunião, aumentando o volume de conhecimento elicitado. Tudo isso é realizado através de um trabalho cooperativo entre os interessados no sistema a ser desenvolvido. O método proposto é uma evolução de um trabalho anterior e baseia- se na gerência de conflitos em um ciclo de reuniões. Essa gerência é levada adiante por meio de um processo de retroalimentação de responsabilidade dos participantes das reuniões, que utilizam um questionário para fornecimento destas informações. Uma ferramenta Web foi construída para a coleta das respostas ao questionário, bem como para apoiar à análise dos conflitos. / [en] This work reports research on the automation support for requirements elicitation performed by means of meetings. In order to provide this support, we ground our work on conflict management, stimulating functional conflicts and controlling non-functional conflicts in order to increase the volume of elicited knowledge. This is based on cooperative work among the stakeholders of the demanded system or demanded changes on an existing system. The method is an evolution of a previous work on the topic and is based on conflict management over a cycle of meetings. This management is performed by a feedback process enacted by the meeting participants by means of a questionnaire for the provision of information. A Web tool to support the method was built to collect the information and analyze the conflicts.

Many software development projects fail because they do not meet the needs of users, are over-budget, and abandoned. To address this problem, the user requirements elicitation process was modified based on principles of Appreciative Inquiry. Appreciative Inquiry, commonly used in organizational development, aims to build organizations, processes, or systems based on success stories using a hopeful vision for an ideal future. Spanning five studies, Appreciative Inquiry was evaluated for its effectiveness with eliciting user requirements. In the first two cases, it was compared with traditional approaches with end-users and proxy-users. The third study was a quasi-experiment comparing the use of Appreciative Inquiry in different phases of in the software development cycle. The final two case studies combined all lessons learned using Appreciative Inquiry, with multiple case studies to gain additional understanding for the requirements gathered during various project phases. Each study evaluated the requirements gathered, developer and user attitudes, and the Appreciative Inquiry process itself. Requirements were evaluated for the quantity and their type regardless of whether they were implemented or not. Attitudes were evaluated for process feedback, as well as requirements and project commitment. The Appreciative Inquiry process was evaluated with differing groups, projects, and project phases to determine how and when it is best applied. Potentially interceding factors were also evaluated including: team effectiveness, emotional intelligence, perceived stress, the experience of the facilitator, and the development project type itself. Appreciative Inquiry produced positive results for the participants, the requirements obtained, and the general requirements eliciting-process. Appreciative Inquiry demonstrated benefits to the requirements gathered by increasing the number of unique requirements as well as identifying more quality-based (non-functional) and forward-looking requirements. It worked well with defined projects, when there was time for participants to reflect on the thought-provoking questions, structured questions and extra time to facilitate the extraction and translation of requirements, and a knowledgeable interviewer. The participants (end-users and developers) expressed improved vision and confidence. End-users participated consistently with immediate buy-in and enthusiasm, especially those users who were technically-inhibited. Development teams expressed improved confidence, and improved user communication and understanding.

Made available in DSpace on 2016-08-17T14:53:00Z (GMT). No. of bitstreams: 1 Eduardo Henrique Ferro Freire.pdf: 1730877 bytes, checksum: 44902c3681fbe938f8092414e357d83a (MD5) Previous issue date: 2005-12-09 / In this work we present an e-commerce systems requirements elicitation methodology, based on organizational modeling. We propose an application of value concepts to organizational requirements modeling, more specifically for early requirements, which turns requirements elicitation more informative. The methodology is well suited for e-commerce systems, because economical value information will be modeled with organizational aspects. In this methodology, we define tasks to be done, techniques to be used, and products to be obtained so that requirement engineers can have an orientation to achieve a good requirement elicitation, and in particular an initial vision about economical viability of e-commerce systems. / Neste trabalho apresentamos uma metodologia para elicitação de requisitos de sistemas de Comércio Eletrônico baseada na Modelagem Organizacional. Propomos uma aplicação dos conceitos de valor à representação de requisitos organizacionais, no que se refere a requisitos iniciais (early requirements), tornando a elicitação de requisitos mais informativa e abrangente para sistemas de Comércio Eletrônico, pois as informações de valor econômico estarão modeladas juntamente com os aspectos organizacionais. Com a metodologia proposta, buscamos definir tarefas a realizar, técnicas a utilizar e produtos a obter, a fim de orientar os engenheiros de requisitos com vistas a que possam realizar uma elicitação de requisitos bem mais especificada e um levantamento inicial de informações da viabilidade econômica da solução de Comércio Eletrônico.

Capturing client’s needs and expectations for a product or service is an important problem in software development. Software requirements are normally captured in natural language and mostly they are unstructured which makes it difficult to automate the process of going from software requirements to the executable code. A big hurdle in this process is the lack of consistency and standardization in software requirements representation. Thus, the aim of the thesis is to present a method for transforming natural language requirement text into ontology. It is easy to store and retrieve information from ontology as it is a semantic model, and it is also easy to infer new knowledge from it. As it is clear from the aim of this work, the main component of our research was software requirements, so there was a need to investigate and decide the types of requirements to define the scope of this research. We selected INCOSE guidelines as a benchmark to scrutinize the properties which we desired in the Natural Language Requirements. These natural language requirements were used in the form of user stories as the input of the transformation process. We selected a combination of two methods for our research i.e. Literature Review and Design Science Research. The reason for selecting these methods was to obtain a good grip on existing work going on in this field and then to combine the knowledge to propose new rules for the requirements to ontology transformation. We studied different domains during literature review such as Requirements Engineering, Ontologies, Natural Language Processing, and Information Extraction. The gathered knowledge was then used to propose the rules and the flow of their implementation. This proposed system was named as “Reqtology”. Reqtology defines the process, from taking the requirements in form of user stories, to extracting the useful information based on the rules and then classifying that information so that it can be used to form ontologies. The workflow consists of a 6-step process which starts from input text in form of user stories and at the end provides us entities which can be used for ontologies formation.

[pt] Este trabalho descreve a mineração de informações em linguagem natural a partir do repositório de projetos GitHub. É explicada como o conteúdo de projetos semelhantes dada uma busca por domínio podem ser úteis para o reuso de conhecimento, e assim, ajudar nas tarefas de Elicitação de Requisitos. Técnicas de mineração de textos, regularidades independentes do domínio, e os metadados de GitHub são os métodos utilizados para selecionar projetos relevantes e as informações dentro deles. Uma abordagem para atingir nossa meta utilizando pesquisa exploratória é explicada, bem como descrevemos os resultados alcançados. / [en] This work describes the mining of information in natural language from the GitHub repository. It is explained how the content of similar projects given a search domain can be useful for the reuse of knowledge, and thus help in the Requirements Elicitation tasks. Techniques of text mining, regularities independent from domain, and GitHub metadata are the methods used to select relevant projects and the information within them. One approach to achieve our goal is explained with an exploratory research and the results achieved.

Made available in DSpace on 2014-12-17T15:48:11Z (GMT). No. of bitstreams: 1 RomeuFO_DISSERT.pdf: 4788717 bytes, checksum: 385df6854e63e9219358e4b7d5fe1ee8 (MD5) Previous issue date: 2014-02-26 / Coordena??o de Aperfei?oamento de Pessoal de N?vel Superior / In the context of Software Engineering, web accessibility is gaining more room, establishing itself as an important quality attribute. This fact is due to initiatives of institutions such as the W3C (World Wide Web Consortium) and the introduction of norms and laws such as Section 508 that underlie the importance of developing accessible Web sites and applications. Despite these improvements, the lack of web accessibility is still a persistent problem, and could be related to the moment or phase in which this requirement is solved within the development process. From the moment when Web accessibility is generally regarded as a programming problem or treated when the application is already developed entirely. Thus, consider accessibility already during activities of analysis and requirements specification shows itself a strategy to facilitate project progress, avoiding rework in advanced phases of software development because of possible errors, or omissions in the elicitation. The objective of this research is to develop a method and a tool to support requirements elicitation of web accessibility. The strategy for the requirements elicitation of this method is grounded by the Goal-Oriented approach NFR Framework and the use of catalogs NFRs, created based on the guidelines contained in WCAG 2.0 (Web Content Accessibility Guideline) proposed by W3C / No contexto de Engenharia de Software, a Acessibilidade Web vem ganhando cada vez mais espa?o, se firmando como um importante atributo de qualidade. Esse fato se deve a iniciativas de institui??es como a W3C (World Wide Web Consortium) e ao surgimento de normas e leis como a Section 508 que fundamentam a import?ncia de elaborar sites e aplica??es Web acess?veis. Apesar dessas melhorias, a falta de acessibilidade na web ainda ? um problema persistente, e pode est? relacionada ao momento ou a fase em que este requisito ? tratado dentro do processo de desenvolvimento. Tendo em vista que a Acessibilidade Web geralmente ? considerada como um problema de programa??o ou tratada quando o aplicativo j? est? totalmente desenvolvido. Dessa forma, considerar a acessibilidade j? durante as atividades de an?lise e especifica??o de requisitos se mostra uma estrat?gia para facilitar o andamento do projeto, evitando retrabalho em fases avan?adas do desenvolvimento de software por causa de poss?veis erros, falhas ou omiss?es na elicita??o. O objetivo desta pesquisa ? desenvolver um m?todo e uma ferramenta para apoiar a elicita??o dos requisitos de acessibilidade web. A estrat?gia de elicita??o presente neste m?todo ? fundamentada atrav?s da abordagem orientada a metas do NFR Framework e na utiliza??o de cat?logos de RNFs, criados com base nas diretrizes contidas no WCAG 2.0 (Web Content Accessibility Guideline) proposto pela W3C

[pt] Considerando a disponibilidade do Big Data para engenharia de software, como no caso do GitHub, a semi-automação da elicitação de requisitos não funcionais (NFRs) é uma estratégia fundamental para a definição de requisitos. Como tal, a elicitação de NFRs, dentro da automação da leitura de documentos, pode gerenciar a massa de informações valiosas existentes nos dados disponíveis. Esta tese explora esse contexto em três partes, a escolha de fontes apropriadas de informação, uma elicitação de descoberta de fatos e a identificação de NFRs. As avaliações realizadas mostraram que a automação enfrenta um balance entre eficiência e eficácia. Esse equilíbrio é detalhado com diferentes estratégias inovadoras. O conhecimento adquirido é organizado como um catálogo SIG (Softgoal Interdependence Graph). / [en] Considering the availability of Big Data for software engineering, as the case of GitHub, the semi-automation of non-functional requirements (NFRs) elicitation is a key strategy towards requirements definition. As such, NFRs elicitation, within the automation of document reading, can manage the mass of valuable information existing in available data. This thesis explores this context in three parts, the choice of proper sources of information, a fact-finding elicitation, and NFRs identification. The assessments performed showed that the automation faces a trade-off between efficiency and efficacy. This trade-off is detailed with different novel strategies. The acquired knowledge is organized as a SIG (Softgoal Interdependence Graph) catalog.