The use of requirements traceability for information systems development (ISD) projects is not very common in practice despite its often mentioned advantages in the literature. We conducted a case study in a large IT company to identify the factors that are relevant for the decision whether or not to adopt traceability in an ISD project. Five dominant factors emerged: development organization a...

Radio Frequency Identification (RFID) is an ubiquitous technology which may provide important improvements for the agri-food in different fields, e.g., supply chain management and alimentary security. As a consequence of local laws in many countries, which lay down that the traceability of food products is mandatory, industrial and academic research entities have been conducting studies on trac...

Traceability links can provide essential support for evolutionary development of software, beyond requirements engineering e.g. for reuse & design decisions, design and code comprehension, effort estimation, checks for completeness and project management. For maximum support, traceability links are required not only for large grained artifacts but for fine grained ones as well. The establishmen...

Recently, different methods and tools have been proposed to automate or semi-automate test-to-code traceability recovery. Among these, Slicing and Coupling based Test to Code trace Hunter (SCOTCH) exploits slicing and conceptual coupling to identify the classes tested by a JUnit test. However, until now the evaluation of testto-code traceability recovery methods has been limited to experiments ...

Creating traceability through the use of links between paragraphs of documents, or between objects in a requirements database, is a great step forward for many systems engineering organisations. It enables analysis of impact, coverage and derivation to be performed, and greatly improves the requirements management process. However, the semantics of the relationship induced by such links is very...

Several aspect-oriented approaches have been proposed to specify aspects at different phases in the software life cycle. Aspects can appear within a phase, be refined or mapped to other aspects in later phases, or even disappear. Tracing aspects is necessary to support understandability and maintainability of software systems. Although several approaches have been introduced to address traceabi...

Secret handshake allows two members in the same group to authenticate each other secretly. In previous works of secret handshake schemes, two types of anonymities against the group authority (GA) of a group G are discussed: 1)Even GA cannot identify members, namely nobody can identify them (No-Traceability), 2)Only GA can identify members (Traceability). In this paper, first the necessity of tr...

A thorough requirements analysis is indispensable for developing and implementing safety-critical software systems such as nuclear power plant (NPP) software systems because a single error in the requirements can generate serious software faults. However, it is very difficult to completely analyze system requirements. In this paper, an effective technique for the software requirements analysis ...

Pre-Requirement Speci cation traceability is the activity of capturing relations between requirements and their sources, in particular user needs. Requirements are formal technical speci cations in the solution space; needs are natural language expressions codifying user expectations in the problem space. Current traceability techniques are challenged by the complexity gap that results from the...

Requirements traceability can be expensive activities. Many researchers have addressed the problem of requirements traceability, especially to support software evolution activities. Yet, the evaluation results of those approaches show that most of them typically provide only limited supports to software evolution to perform requirements tracing and maintaining the established links. Based on th...