In the paper “New Results on Frame-Proof Codes and Traceability Schemes” by Reihaneh Safavi-Naini and Yejing Wang [IEEE Trans. Inform. Theory, vol. 47, no. 7, pp. 3029– 3033, Nov. 2001], there are lower bounds for the maximal number of codewords in binary frame-proof codes and decoders in traceability schemes. There are also existence proofs using a construction of binary frame-proof codes and ...

Food safety is a widely concerned problem in current world. Traceability technology is an effective measure to solve the problem. This paper describes the study of the traceability of grain and oil products. Include the study contents, and a system we developed for traceability of grain and oil products, and the demonstration of the study. The system we developed was used in Luhua group and som...

Software artefact traceability is widely recognised as an important factor for the effective development and maintenance of a software system. Unfortunately, the lack of automatic or semi-automatic supports makes the task of maintaining links among software artefacts a tedious and time consuming one. For this reason, often traceability information becomes out of date or it is completely absent ...

The great variety of traceability systems in the German food industry makes it difficult to describe them coherently and to distinguish them clearly one from another. Therefore a classification system or typology is needed to facilitate their description and analysis. This study suggests an approach to extract distinguishing aspects from a detailed description of traceability systems for pork. ...

Traceability ensures that software artifacts of subsequent phases of the development cycle are consistent. Few works have so far addressed the problem of automatically recovering traceability links between object-oriented (OO) design and code entities. Such a recovery process is required whenever there is no explicit support of traceability from the development process. The recovered informatio...

In this paper, we introduce a domain-specific component-based approach with traceability of concerns. It is based on the separation of concerns, which is a long well known fundamental principle of software engineering but some time neglected in practice. Our approach is included in the V-based development process prescribed by the CENELEC EN-50128 standard of railway control and protection syst...

Traceability is the only means to ensure that the source code of a system is consistent with its requirements and that all and only the specified requirements have been implemented. During software maintenance and evolution, as developers add, remove, or modify features (including bugs), requirement traceability links become obsolete because developers do not/cannot devote effort to update them...

This report contains the proceedings of the Third ECMDA Traceability Workshop, arranged in Haifa, Israel 2007 together with ECMDA 2007 conference. The papers within target various aspects of traceability in model-driven development.

When a system evolves, while the source code is changed documentation and traceability links are barely ever updated: maintaining traceability information between software artifacts is a costly and tedious activity frequently sacrificed during development and maintenance due to market pressure. This paper presents a new method to recovery traceability links between high level and low level arti...

Traceability links enable the possibility to trace the evolution of a project from the earliest requirements engineering phase over the design and implementation to the test phases of a project. Having a link between the artifacts resulting from these phases, a requirement can be traced to, e.g., the test report, which tested the code implementing the requirement. However, as the artifacts evol...