Interactive Traceability Links Visualization using Hierarchical Trace Map

© 2019 IEEE. Traceability links between various software artifacts of a system aid software engineers in system comprehension, verification and change impact analysis. Establishing trace links between software artifacts manually is an error-prone and costly task. Recently, studies in automated traceability link recovery area have received broad attention in the software maintenance community aiming to overcome the challenges of manual trace links maintenance process. In these studies, the trace links results generated by an automated trace recovery approach are presented either in a bland textual matrix format (e.g., tabular format) or two-dimensional graphical formats (e.g. tree view, hierarchical leaf node). Therefore, it is challenging for software engineers to explore the inter-relationships between various artifacts at once (e.g., which test cases and source code files/methods are related to a particular requirement). In this position paper, we propose a hierarchical trace map visualization technique to explore inter-relationships between various artifacts at once naturally and intuitively

Visualization representation benefits of pre-requirement specification tractability

Representation of Pre-RST information is very useful using visualization elements for realization of benefits of requirements tractability This improves the practitioners motivation to maintain Pre-RST information during life cycle processes. Few researchers proposed visualization for post-RST due to which many benefits of requirements tractability cannot be realized. This paper proposed an important visualization representing Pre-RST information that demonstrate various benefits of requirements tractability. In order to evaluate empirically an experiment is conducted and textual representation of tractability information is obtained. In order to strengthen our claim a survey is conducted to compare textual representation of tractability information with proposed visualization and results are compiled

Requirements analysis process using role-based goal modeling

Requirements analysis is the process of analyzing the requirements of various stakeholders that represent the specification of system behavior. This must be stated precisely in order to proceed to the design phase. It is noted that the current process of requirements analysis is not sufficient for identifying and representing the existence of multiple stakeholders, which could lead to various conflicts and overlapping requirements. Furthermore, the involvement of various stakeholders normally leads to inconsistencies and misinterpretation of requirements. Therefore, this study is conducted to enhance goal modeling representation, namely role-based goal modeling. Role-based goal modeling highlights each stakeholder’s role identification in discovering the intentions and requirements of various stakeholders including the integration of data elements in order to determine the dependency of data when dealing with multiple stakeholders. An Integrated Plantation System was selected as a case study for this research with participation from different stakeholders. Besides that, the Integrated Learning Management System and NIMSAD approaches were used to evaluate the proposed method. From the result, it is found that role-based goal modeling showed improvement in deriving high feasibility (five goals) and high adequacy (one goal) requirements for implementation. The integration of data elements indicates high complexity when multiple stakeholders interact with the same data element. In sum, role-based goal modeling can facilitate the process of analyzing and prioritizing requirements from multiple stakeholders in the early stages of the development process

Tracing Requirements and Source Code During Software Development

Traceability supports the software development process in various ways, amongst others, change management, software maintenance and prevention of misunderstandings. Traceability links between requirements and code are vital to support these development activities, e.g., navigating from a requirement to its realization in the code, and vice versa. However, in practice, traceability links between requirements and code are often not created during development because this would require increased development effort. This reduces the possibilities for developers to use these links during development. To address this weakness, this thesis presents an approach that (semi-) automatically captures traceability links between requirements and code during development. We do this by using work items from project management that are typically stored in issue trackers. The presented approach consists of three parts. The first part comprises a TIM consisting of artifacts from three different areas, namely requirements engineering, project management, and code. The TIM also includes the traceability links between them. The second part presents three processes for capturing traceability links between requirements, work items, and code during development. The third part defines an algorithm that automatically infers traceability links between requirements and code based on the interlinked work items. The traceability approach is implemented as an extension to the model-based CASE tool UNICASE, which is called UNICASE Trace Client. Practitioners and researchers have discussed the practice of using work items to capture links between requirements and code, but there has been no systematic study of this practice. This thesis provides a first empirical study based on the application of the presented approach. The approach and its tool support are applied in three different software development projects conducted with undergraduate students. The feasibility and practicability of the presented approach and its tool support are evaluated. The feasibility results indicate that the approach creates correct traceability links between all artifacts with high precision and recall during development. At the same time the practicability results indicate that the subjects found the approach and its tool support easy to use. In a second empirical study we compare the presented approach with an existing technique for the automatic creation of traceability links between requirements and code. The results indicate the presented approach outperforms the existing technique in terms of the quality of the created traceability links

Maps of Lessons Learnt in Requirements Engineering

Both researchers and practitioners have emphasized the importance of learning from past experiences and its consequential impact on project time, cost, and quality. However, from the survey we conducted of requirements engineering (RE) practitioners, over 70\% of the respondents stated that they seldom use RE lessons in the RE process, though 85\% of these would use such lessons if readily available. Our observation, however, is that RE lessons are scattered, mainly implicitly, in the literature and practice, which obviously, does not help the situation. We, therefore, present ``maps” of RE lessons which would highlight weak (dark) and strong (bright) areas of RE (and hence RE theories). Such maps would thus be: (a) a driver for research to ``light up” the darker areas of RE and (b) a guide for practice to benefit from the brighter areas. To achieve this goal, we populated the maps with over 200 RE lessons elicited from literature and practice using a systematic literature review and survey. The results show that approximately 80\% of the elicited lessons are implicit and that approximately 70\% of the lessons deal with the elicitation, analysis, and specification RE phases only. The RE Lesson Maps, elicited lessons, and the results from populating the maps provide novel scientific groundings for lessons learnt in RE as this topic has not yet been systematically studied in the field

A Modelling Approach to Multi-Domain Traceability

Traceability is an important concern in projects that span different engineering domains. Traceability can also be mandated, exploited and man- aged across the engineering lifecycle, and may involve defining connections between heterogeneous models. As a result, traceability can be considered to be multi-domain. This thesis introduces the concept and challenges of multi-domain trace- ability and explains how it can be used to support typical traceability scenarios. It proposes a model-based approach to develop a traceability solution which effectively operates across multiple engineering domains. The approach introduced a collection of tasks and structures which address the identified challenges for a traceability solution in multi-domain projects. The proposed approach demonstrates that modelling principles and MDE techniques can help to address current challenges and consequently improve the effectiveness of a multi-domain traceability solution. A prototype of the required tooling to support the approach is implemented with EMF and atop Epsilon; it consists of an implementation of the proposed structures (models) and model management operations to sup- port traceability. Moreover, the approach is illustrated in the context of two safety-critical projects where multi-domain traceability is required to underpin certification arguments