A streamlined, cost-effective database approach to manage requirements traceability

Saiedian, Hossein; Kannenberg, Andrew; Morozov, Serhiy

doi:10.1007/s11219-011-9166-3

Cited by 4 publications

(10 citation statements)

References 12 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…H. Saiedian has proposed a cost effective tool for requirements traceability management. Though the tool takes more time to develop, it offers several advantages: lesser time in release, minimum bugs, and low cost as compared to other tools available in market [14]. Gea, J. M. has assessed the various tools available in market for requirement engineering process by conducting a survey of different vendors of the tools [2].…”

Section: Literature Reviewmentioning

confidence: 99%

“…However, it is to be informed that many of the tools suggested for implementation are only for research purposes and suffer from integration problems when implemented with commercial systems, and are very costly. Therefore, the use of such tools in industry would be very impractical [3,14].…”

Section: Tools and Support For Requirements Managementmentioning

confidence: 99%

“…H. Saiedian [14] Proposed a tool to trace the requirements to other requirements, design, source code and test cases. It has a database that keeps the information of the artifacts by their identifiers only, and a software wrapper to the database that has buttons and custom menu for human analysts to operate and manage it.…”

Section: Traceability Not Evaluatedmentioning

confidence: 99%

See 2 more Smart Citations

Software Change Management: A Note on Significance, Tools and Support

Siddique¹,

Siddique²

2020

IJCA

View full text Add to dashboard Cite

Requirements management is an essential part of software engineering. The changes occurring in the requirements of the software, if not handled properly, can lead to catastrophic failures. It is due to this reason that the proper management of requirements change is considered a critical part of software development. In this paper, a brief review on change management in requirements is presented. Moreover, general concepts of requirements change management are elaborated alongwith the information on related tools that are available for different aspects of requirements change management activities in the market. Last but not least, various tools proposed by different researchers on several categories of requirements change management are compared with each other. It has been observed that 'requirements traceability' tools are discussed more frequently in the literature than others, and find more support than other classes of requirements change management.

show abstract

Section: Literature Reviewmentioning

confidence: 99%

Section: Tools and Support For Requirements Managementmentioning

confidence: 99%

See 1 more Smart Citation

Software Change Management: A Note on Significance, Tools and Support

Siddique¹,

Siddique²

2020

IJCA

View full text Add to dashboard Cite

show abstract

“…In other traceability approaches, there exit some work related to different tools and methodologies for requirements traceability. Saiedian [26] stated that existing traceability tools focus primarily on requirements traceability or traceability among the various artifacts of a software product, however, there is still an open issue in end-to-end traceability. For instance, Sherba and Anderson [23] proposed a traceability, which has an evolution service that analyzes the changes to a set of relationships over time.…”

Section: Related Workmentioning

confidence: 99%

A Requirements-to-Implementation Mapping Tool for Requirements Traceability

García¹,

Paiva²

2016

JSW

View full text Add to dashboard Cite

Software quality is a major concern in software engineering, particularly when we are dealing with software services that must be available 24 hours a day, please the customer and be kept permanently. In software engineering, requirements management is one of the most important tasks that can influence the success of a software project. Maintain traceability information is a fundamental aspect in software engineering and can facilitate the process of software development and maintenance. This information can be used to support various activities such as analyzing the impact of changes and software verification and validation. However, traceability techniques are mainly used between requirements and software test cases. This paper presents a prototype of a tool that supports the mapping of functional requirements with the pages and HTML elements of a web site. This tool helps maintaining requirements traceability information updated and, ultimately, increasing the efficiency of requirements change management, which may contribute to the overall quality of the software service.

show abstract

“…Despite the vast body of knowledge that exists on traceability, traceability practices are far from being mature [17]. Over the years, RT in general and (semi-)automated RT in particular have been widely identified as problematic by the industry [18][19][20][21][22][23]. According to the NaPIRE (Naming the Pain in Requirements Engineering) survey, 32.4% (158 out of 488) of the respondents positioned 'missing traceability' in the top 15 requirements engineering (RE) challenges [24].…”

Section: Introductionmentioning

confidence: 99%

What have we learnt from the challenges of (semi‐) automated requirements traceability? A discussion on blockchain applicability

2021

View full text Add to dashboard Cite

Over the last 3 decades, researchers have attempted to shed light into the requirements traceability problem by introducing tracing tools, techniques, and methods with the vision of achieving ubiquitous traceability. Despite the technological advances, requirements traceability remains problematic for researchers and practitioners. This study aims to identify and investigate the main challenges in implementing (semi-)automated requirements traceability, as reported in the recent literature. A systematic literature review was carried out based on the guidelines for systematic literature reviews in software engineering, proposed by Kitchenham. We retrieved 4530 studies by searching five major bibliographic databases and selected 70 primary studies. These studies were analysed and classified according to the challenges they present and/or address. Twenty-one challenges were identified and were classified into five categories. Findings reveal that the most frequent challenges are technological challenges, in particular, low accuracy of traceability recovery methods. Findings also suggest that future research efforts should be devoted to the human facet of tracing, to explore traceability practices in organisational settings, and to develop traceability approaches that support agile and DevOps practices. Finally, it is recommended that researchers leverage blockchain technology as a suitable technical solution to ensure the trustworthiness of traceability information in interorganisational software projects.This is an open access article under the terms of the Creative Commons Attribution-NonCommercial-NoDerivs License, which permits use and distribution in any medium, provided the original work is properly cited, the use is non-commercial and no modifications or adaptations are made.

show abstract

A streamlined, cost-effective database approach to manage requirements traceability

Cited by 4 publications

References 12 publications

Software Change Management: A Note on Significance, Tools and Support

Software Change Management: A Note on Significance, Tools and Support

A Requirements-to-Implementation Mapping Tool for Requirements Traceability

What have we learnt from the challenges of (semi‐) automated requirements traceability? A discussion on blockchain applicability

Contact Info

Product

Resources

About