Plausible and adaptive requirement traceability structures (original) (raw)
Related papers
Rule-based generation of requirements traceability relations
Journal of Systems and Software, 2004
The support for traceability between requirement specifications has been recognised as an important task in the development life-cycle of software systems. In this paper, we present a rule-based approach to support the automatic generation of traceability relations between documents which specify requirement statements and use cases (expressed in structured forms of natural language), and analysis object models for software systems. The generation of such relations is based on traceability rules of two different types of traceability rules. More specifically, we use requirement-to-object-model rules to trace the requirements and use case specification documents to an analysis object model, and inter-requirements traceability rules to trace requirement and use case specification documents to each other. By deploying such rules, our approach can generate four different types of traceability relations. To implement and demonstrate our approach, we have implemented a traceability prototype system. This system assumes requirement and use case specification documents and analysis object models represented in XML. It also uses traceability rules are also represented in an XML-based rule markup language that we have developed for this purpose. This XML-based representation framework makes it easier to deploy our prototype in settings characterised by the use of heterogeneous software engineering and requirements management tools. The developed prototype has been used in a series of experiments that we have conducted to evaluate our approach. The results of these experiments have provided encouraging initial evidence about the plausibility of our approach and are discussed in the paper.
Requirement Traceability: A Model-Based Approach
2020
Abstract-Requirements tractability remains challenging, particularly in the prevalence of code centric approaches. Similarly, within the emerging model centric paradigm, requirements traceability is addressed only to a limited extent. To facilitate such traceability, we call for representing requirements as first class entities in the emerging paradigm of model-oriented programming. This has the objective of enabling software developers, modelers, and business analysts to manipulate requirements entities as textual model and code elements. To illustrate the feasibility of such an approach, we propose a Requirement-Oriented Modeling and Programming Language (ROMPL) that demonstrates how modeling abstractions can be utilized to manage the behavior and relationships of key requirements entities.
Modeling Functional Requirements to Support Traceability Analysis
2006 IEEE International Symposium on Industrial Electronics, 2006
Traceability analysis is a technique that enables the verification of software requirements within the software life cycle. Within a context where there is a lack of common understanding of what must be traced, a number of methods have been proposed to implement software requirements traceability analysis, many of these methods dealing with software requirements expressed in natural language. This paper provides a graphical model to visualize software functional requirements that facilitates identifying functional traceability links. An application of the proposed model is illustrated through a case study taken from a process control system.
Model for Enhancing Requirements Traceability and Analysis
International Journal of Advanced Computer Science and Applications, 2010
Software quality has been a challenge since the inception of computer software. Software requirements gathering, analysis, and specification; are viewed by many as the principle cause of many of the software complex problems. Requirements traceability is one of the most important and challenging tasks in ensuring clear and concise requirements. Requirements need to be specified and traced throughout the software life cycle in order to produce quality requirements. This paper describes a preliminary model to be used by software engineers to trace and verify requirements at the initial phase. This model is designed to be adaptable to requirement changes and to assess its impact.
2007
Requirements traceability is the ability to follow the life of a requirement i.e. from its origin, to its refinement and inclusion in the requirement specification document, and from there to its subsequent deployment in coding, testing and validation. Pre-Requirement Traceability is concerned with requirement's life before its inclusion in the requirement specification, while Post-Requirement Traceability is concerned with the requirement's life after its inclusion in the requirement specification.
An analysis of the requirements traceability problem
1994
Abstract Investigates and discusses the underlying nature of the requirements traceability problem. Our work is based on empirical studies, involving over 100 practitioners, and an evaluation of current support. We introduce the distinction between pre-requirements specification (pre-RS) traceability and post-requirements specification (post-RS) traceability to demonstrate why an all-encompassing solution to the problem is unlikely, and to provide a framework through which to understand its multifaceted nature.
Tracing software requirements artifacts
2003
Abstract The support for traceability between requirement specifications has been recognised as an important task in the development life-cycle of software systems. In this paper we present an approach for automatic generation and maintenance of bi-directional traceability relations between commercial and functional requirements expressed in natural language, and requirement object models.
Towards Identification and Recognition of Trace Associations in Software Requirements Traceability
In the field of Software Engineering, Requirements Traceability is becoming a dynamic area of research. Producing numerous artifacts is crucial activity to maintain and yield high quality software. These artifacts are created and generated throughout the lifetime of software development, and are highly interrelated where the impact of any change in either artifact imparts changes on all the relevant product outcomes. This research focuses on the identification of inherent relationships that occur and became existent in the software requirements engineering activity due to which new and hidden traces among the artifacts including those to be self-created or generated at a later juncture can be discovered as a Post-RS 1 activity. This results in the reduction of traces to be found at a later development period and offers faster identification and realization of traces among innumerable artifacts. As a consequence of this scheme, the complexity of generating traces among artifacts is reduced and the overall quality of the software improves.
Towards a framework for improving requirement traceability
Ingenieria e Investigación
Muchos trabajos de trazabilidad de requisitos están focalizados en aspectos de programación en vez de la identificación, análisis y modelamiento de todas las informaciones trazables de un proyecto de software. Este artículo trata del desarrollo de un marco de trabajo para mejorar la trazabilidad de requisitos de software. El marco de trabajo consiste en la clasificación de las informaciones trazables; la definición y uso de tipos de relaciones entre las informaciones trazables; un conjunto de directrices para elaborar un modelo de trazabilidad de requisitos en un proyecto de software y el desarrollo de la herramienta MyMT (My Management Tool) para apoyar el desarrollo de un modelo de trazabilidad de requisitos. Un sistema universitario de administración de biblioteca es empleado para ilustrar la aplicación del marco de trabajo.
The role of traceability in requirements engineering
Software documentation is usually expressed in natural languages contains much useful information. Therefore establishing the traceability links between documentation and source code can be very helpful for software engineering management. Suchas requirement traceability, impact analysis, and software reuse, currently. Therecovery of traceability links is mostly based on information retrieval techniques, for instance, probabilistic model, vector space model, and latent semantic indexing. Previous work treats both documentation and source code as plain text files. The quality of retrieved links can be improved by imposing additional structure using that they are software engineering documents. In this paper, we present four enhanced strategies to improve traditional LSI method based on the special characteristics of documentation experimental results show that the first three enhanced strategies can increase the precision of retrieved links by 5%∼16%, while the fourth strategy is about 13%.