No description available.

Traceability in the software industry is a topic which has been studied for a long time, but there still remain questions to be answered. This thesis looks into the state of software traceability in the software industry is today. It is also a case study in implementing traceability in a model-based testing process at a large automotive company. The thesis finds that while progress has been made in identifying the important aspects of traceability, there does not yet exist a clear consensus on general traceability models which can be used to implement traceability in an arbitrary company or project. Through a case study in implementing traceability in a model-based testing process, the thesis gives one example of how this could potentially be done.

No description available.

No description available.

No description available.

Today, Software is becoming increasingly important. Systems are growing and will continue to increase in complexity in the future. This makes maintenance complicated and expensive. Therefore traceability between requirements and source code by trace-links is becoming more important. But many software systems either have no or few trace-links. In some cases, it is urgent to recover these links, for example, to find out the status of a project. This recovery is made more difficult by distributed or incomplete requirements documents. Experts and strong tools are necessary. These theses visualize and analyze the items and their dependencies within the requirements document and the source code based on the results of an expert tool. We found six attributes that support the recovery of trace-links between these items of the requirements document and source code.:1 Einleitung 1.1 Motivation - Warum Traceability? 1.2 Aufgabenstellung 1.3 Aufbau der Arbeit 2 Grundlagen & Begriffsklärungen 2.1 Softwareartefakt 2.2 Softwareprojekt 2.3 Vollständigkeit eines Softwareprojektes 3 Traceability 3.1 Bedeutung von Traceability 3.1.1 Traceability Ziele 3.1.2 Traceability in der Realität 3.2 Herausforderungen von Traceability 3.2.1 Vorbereitung und Planung 3.2.2 Erstellung und Pflege von Links 3.2.3 Ergebnis und Auswertung 3.2.4 Austausch 3.3 Vorhandene Methoden zum Traceability Recovering 3.3.1 Basierend auf Feature Analysis 3.3.2 Basierend auf Information Retrieval 3.3.3 Basierend auf dem Verhalten der Programmierer 3.3.4 Basierend auf Versionsverwaltung 3.4 Vergleich der Methoden 4 Traceability Werkzeuge 4.1 Erwartungen 4.2 SoftRepo 4.3 Eclipse Capra 4.4 YAKINDU Traceability 4.5 DOORS 4.6 Vergleich der Anwendungen 5 Trace-Link Visualisierung 5.1 Vorhandene Arbeiten zur Trace-Link Visualisierung 5.2 Anforderungen 5.2.1 Anforderungen an Trace-Link Informationen 5.2.2 Anforderungen an die Visualisierungsanwendung 5.3 Visualisierungsformen 6 Entwurf und Implementierung 6.1 Verwendete Technologien 6.1.1 Prototyp 6.1.2 Resultierende Anwendung 6.2 Architektur 6.3 Datengrundlage 6.3.1 Entitäts Daten 6.3.2 Relation 6.4 Datenverarbeitung 6.4.1 Erstmalige Datenaufbereitung (von Schritt 3) 6.4.2 Berechnung der Koordinaten (von Schritt 6) 6.5 Benutzeroberfläche 6.5.1 Menüs 6.5.2 Dashboard 6.5.3 Exportfunktionen 6.6 Visualisierungen 6.6.1 Netzwerkgraph 6.6.2 Segeldiagramm 6.6.3 Sankey Diagramm 7 Evaluation 7.1 Testdaten 7.2 Resultate der Visualisierungen 7.2.1 Networkgraph 7.2.2 Segeldiagramm 7.2.3 Sankey Diagramm 7.3 Zusammenfassung 8 Zusammenfassung & Aussicht 8.1 Zusammenfassung 8.2 Bewertung der erstellten LinkViz Anwendung 8.3 Rückblick auf Forschungsfragen 8.4 Ausblick Anhang Abbildungsverzeichnis Tabellenverzeichnis Abkürzungsverzeichnis Literaturverzeichnis

This dissertation describes the development of a requirements analysis methodology that takes into account the concept of operations and the hierarchical decomposition of aerospace systems. At the core of the methodology, the Analytic Network Process (ANP) is used to ensure the traceability between the qualitative and quantitative information present in the hierarchical model. The proposed methodology is implemented to the requirements definition of a hurricane tracker Unmanned Aerial Vehicle. Three research objectives are identified in this work; (1) improve the requirements mapping process by matching the stakeholder expectations with the concept of operations, systems and available resources; (2) reduce the epistemic uncertainty surrounding the requirements and requirements mapping; and (3) improve the requirements down-selection process by taking into account the level of importance of the criteria and the available resources. Several challenges are associated with the identification and definition of requirements. The complexity of the system implies that a large number of requirements are needed to define the systems. These requirements are defined early in the conceptual design, where the level of knowledge is relatively low and the level of uncertainty is large. The proposed methodology intends to increase the level of knowledge and reduce the level of uncertainty by guiding the design team through a structured process. To address these challenges, a new methodology is created to flow-down the requirements from the stakeholder expectations to the systems alternatives. A taxonomy of requirements is created to classify the information gathered during the problem definition. Subsequently, the operational and systems functions and measures of effectiveness are integrated to a hierarchical model to allow the traceability of the information. Monte Carlo methods are used to evaluate the variations of the hierarchical model elements and consequently reduce the epistemic uncertainty. The proposed methodology is applied to the design of a hurricane tracker Unmanned Aerial Vehicles to demonstrate the origin and impact of requirements on the concept of operations and systems alternatives. This research demonstrates that the hierarchical modeling methodology provides a traceable flow-down of the requirements from the problem definition to the systems alternatives phases of conceptual design.

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.

The Model Driven Development (MDD) promotes the use of models to generate software solutions, in which models are the primary development artifact. In recent years, studies in software engineering area (ES) have been intensified and several solutions, definitions, methods and structures are being generated. However, this paradigm, as it is considered by some authors, has not been effectively used, as the ES covers various aspects, and not everyone is prepared for MDD. The Requirements Engineering (RE) is highlighted in this scenario, since it comprises the initial phase of the development process and the product generated must meet the requirements set out in that time. Once the code ceases to be the focus of development in the context of MDD, it is necessary to identify whether the requirements defined at the beginning of the project while under transformation remain faithful as well as the allocated elements to each requirement at all stages and possible impacts in case of change. In this context, it is important to introduce the concepts of traceability requirements in MDD. Thus, this work presents the R2MDD, a framework which aims to monitor and track requirements for the transformation of models to the generation of source code. The R2MDD seeks to identify impacts, ensure the consistency of requirements and other characteristics, as well as generate information management level, benefiting all stakeholders. An experimental study was conducted with the assistance of Qualitas model at the University Hospital of the Federal University of Sergipe (HU - UFS) to assess the R2MDD, highlighting its advantages and limitations. / O Model Driven Development (MDD) promove o uso de modelos na geração de soluções de software, na qual os modelos são o artefato principal do desenvolvimento. Nos últimos anos, estudos na área de Engenharia de Software (ES) tem sido intensificados e diversas soluções, definições, métodos e estruturas estão sendo geradas. Entretanto, esse paradigma, como é considerado por alguns autores, ainda não é utilizado de forma efetiva, visto que a ES abrange diversos aspectos e nem todos estão preparados para o MDD. A Engenharia de Requisitos (ER) ganha destaque nesse cenário, pois compreende a fase inicial do processo de desenvolvimento e o produto gerado deve atender aos requisitos definidos nesse momento. Uma vez que o código deixa de ser o foco do desenvolvimento no contexto de MDD, surge a necessidade de identificar se os requisitos definidos no início do projeto, ao serem transformados, mantém-se fieis, bem como identificar os elementos alocados a cada requisito em todas as fases e possíveis impactos em caso de alteração. Nesse contexto, torna-se importante introduzir os conceitos da rastreabilidade de requisitos em MDD. Dessa forma, este trabalho apresenta o R2MDD, um framework que visa monitorar e rastrear requisitos durante as transformações de modelos até a geração de código fonte. O R2MDD busca identificar impactos, garantir a consistência dos requisitos e demais características, bem como gerar informações a nível gerencial, que beneficiam todos os stakeholders. Um caso exemplo foi realizado com o auxílio do modelo Qualitas no Hospital Universitário da Universidade Federal de Sergipe (HU – UFS) a fim de avaliar o R2MDD, destacar suas vantagens e identificar suas limitações.