Thesis (M.S.)--Oregon State University, 2010. / Printout. Includes bibliographical references (leaves 42-44). Also available on the World Wide Web.

Thesis (Ph. D.)--Oregon State University, 2011. / Printout. Includes bibliographical references (leaves 203-216). Also available on the World Wide Web.

Zugl.: Hamburg, Univ., Diss., 2008

Techn. University, Diss., 2005--München.

Zugl.: Hagen, FernUniversiẗat, Diss., 1997.

University, Diss., 2004--Saarbrücken.

Made available in DSpace on 2014-06-12T15:50:44Z (GMT). No. of bitstreams: 2 arquivo1986_1.pdf: 7023849 bytes, checksum: ba0e9dc1eb31198972dbb6ceaf580dba (MD5) license.txt: 1748 bytes, checksum: 8a4605be74aa9ea9d79846c1fba20a33 (MD5) Previous issue date: 2008 / A engenharia de requisitos argumenta que, para o desenvolvimento de software complexo ser bem sucedido, é necessário que o processo de modelagem suporte mecanismos e ferramentas de rastreamento. Rastreabilidade de requisitos refere-se à habilidade de assegurar um alinhamento contínuo entre requisitos dos stakeholders e às várias saídas do processo de desenvolvimento de software. O processo de rastreamento de requisito descreve e segue a vida dos requisitos nas direções forward e backward (i.e. da sua origem, através do seu desenvolvimento e especificação, para sua subseqüente implementação e uso, e através de todos os períodos de refinamento e interação em qualquer uma dessas fases). Rastreamento de software é executado gerando, representando, armazenando e mantendo relações de rastreabilidade entre os artefatos de software tanto manualmente como automaticamente. Desenvolvedores de softwares têm usado agentes como uma forma de entender, modelar e desenvolver sistemas complexos mais naturalmente. Sistemas multiagentes (SMA) refletem a natureza descentralizada dos modernos sistemas distribuídos, dando suporte a situações dinâmicas e imprevisíveis nas quais se espera que o software opere atualmente, sendo apropriado para sistemas abertos nos quais seus componentes e padrões de interação mudam constantemente. O uso de agentes com uma maior dependência em conhecimento codificado, flexibilidade, adaptabilidade e autonomia, introduz novos desafios ao suporte de rastreamento de requisitos. As capacidades dos agentes e aspectos sociais devem ser consideradas. Uma contribuição neste campo é Tropos, um framework usado para modelar sistemas multiagentes. Ele faz uso das abstrações e conceitos das disciplinas organizacional e social para entender, modelar, analisar e projetar. Assim, Tropos fornece uma maior flexibilidade, e um conjunto de construtores de alto nível para tratar com um mundo operando mais nos princípios sociais do que nas regras mecanicistas. A flexibilidade, a adaptabilidade e a autonomia introduzidas pelos MAS apresentam novos desafios para as abordagens de rastreabilidade atuais. Nós advogamos que um modelo e um processo de rastreamento específico devem ser usados para tratar as necessidades específicas de um SMA de forma satisfatória. Nesta tese, nós propomos um Metamodelo de Rastreamento para facilitar a identificação das novas relações necessárias ao paradigma de agent system, the individual issues of each agent and their social aspects as well as the impact analysis when changes happen. The DBSitter-AS example will be used to illustrate how our proposal captures agent characteristics such as autonomy and cooperation

Requirements reuse is based upon the idea that it is possible to reuse requirements from previous software development projects. Requirements reuse leads to efficiency and quality gains in the beginning of the development process. One of the obstacles for requirements reuse is that there is a lack of appropriate tools for it. This work approaches this hinder by identifying properties that are important, that is, that the properties represent something that has so much influence that it should be in a requirements reuse tool. These identified properties may then guide the development when building requirements reuse tools. In order to find the properties this work is conducted as a literature study where both tool-specific and non-tool specific articles were searched in order to elicitate the properties. The work focuses on properties present in both tool-specific and non-tool specific articles. This makes the result more reliable since two different sources have identified them. 18 verified properties were identified through this work.

It is important to track how a requirement changes throughout the software lifecycle. Each requirement should be validated during and at the end of each phase of the software lifecycle. It is common to build traceability matrices to demonstrate that requirements are satisfied by the design. Traceability matrices are needed in various tasks in the software development process. Unfortunately, developers and designers do not always build traceability matrices or maintain traceability matrices to the proper level of detail. Therefore, traceability matrices are often built after-the-fact. The generation of traceability matrices is a time consuming, error prone, and mundane process. Most of the times, the traceability matrices are built manually. Consider the case where an analyst is tasked to trace a high level requirement document to a lower level requirement specification. The analyst may have to look through M x N elements, where M and N are the number of high and low level requirements, respectively. There are not many tools available to assist the analysts in tracing unstructured textual artifacts and the very few tools that are available require enormous pre-processing. The prime objective of this work was to dynamically generate traceability links for unstructured textual artifacts using information retrieval (IR) methods. Given a user query and a document collection, IR methods identify all the documents that match the query. A closer observation of the requirements tracing process reveals the fact that it can be stated as a recursive IR problem. The main goals of this work were to solve the requirements traceability problem using IR methods and to improve the accuracy of the traceability links generated while best utilizing the analysts time. This work looked into adopting different IR methods and using user feedback to improve the traceability links generated. It also applied wrinkles such as filtering to the original IR methods. It also analyzed using a voting mechanism to select the traceability links identified by different IR methods. Finally, the IR methods were evaluated using six datasets. The results showed that automating requirements tracing process using IR methods helped save analysts time and generate good quality traceability matrices.

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.