Software traceability establishes a network of connections between diverse artifacts such as requirements, design, and code. However, given the cost and effort of creating and maintaining trace links manually, researchers have proposed automated approaches using information retrieval techniques. Current approaches focus almost entirely upon generating links between pairs of artifacts and have not leveraged the broader network of interconnected artifacts. In this paper we investigate the use of intermediate artifacts to enhance the accuracy of the generated trace links – focus- ing on paths consisting of source, target, and intermediate artifacts. We propose and evaluate combinations of techniques for computing semantic similarity, scaling scores across multiple paths, and aggregating results from multiple paths. We report results from five projects, including one large industrial project. We find that leverag- ing intermediate artifacts improves the accuracy of end-to-end trace retrieval across all datasets and accuracy metrics. After further analysis, we discover that leveraging intermediate artifacts is only helpful when a project’s artifacts share a common vocabulary, which tends to occur in refinement and decomposition hierarchies of artifacts. Given our hybrid approach that integrates both direct and transitive links, we observed little to no loss of accuracy when intermediate artifacts lacked a shared vocabulary with source or target artifacts.

The South African (SA) export fruit industry is vital to the SA economy, contributing about 20% (or 4 million tons) to agricultural production. As a one billion US dollar export industry in 2002, the country exports about 42% of its fresh fruit production (Shepherd 2003:2), contributing 75% of all farm income for fruit (Kriel 2002:4). The industry is well positioned with regard to its southern hemisphere competitors (Argentina, Australia, Chile and New Zealand) in terms of average growth in export volumes. However, the market requirements are constantly changing and competition is fierce due to the general oversupply of fruit in major markets. The limitations of the regulated environment eventually led to deregulation in August 1997 and to the phasing out of the statutory bodies. The new deregulated market structure radically changed the competitive profile of the industry by lifting the artificial barriers that existed for fruit exports. However, there was still a major barrier to performance – having the knowledge and ability to deal with export processes (S. Rigotti, personal communication, 13 June 2003 – Manager Information Systems, Capespan, P.O. Box 505, Bellville, South Africa, 7535). Exporters experienced a combination of problems. Few had proper systems, which meant that access to critical information was severely hampered. It was, for instance, difficult to record and verify the cost, quite often resulting in serious losses. Producer payments were inaccurate and late most of the time; sometimes payments only occurred during the harvesting of the next season. Data integrity on the supply chain was suspect, because of fragmented information channels and duplicated capturing at various points in the chain. The internal challenges were compounded by a difficult time in the markets. Strong competition, globalization and the effects of world-wide overproduction, caused prices to drop dramatically. Consequently many farmers and exporters incurred enormous debts and went bankrupt (Van der Ham, Becker and Guis 2002a; 2002b). In 2000, the third year after deregulation, the fruit export industry as a whole lost an estimated one billion rand in export earnings and declared itself in crisis (Mather 2003). SA's international image slipped because of all the negative consequences of deregulation (Symington 2003:5).

Purpose: An exploration into the application of pre-requirements specification traceability (pre-RST) practices in Information Systems (IS) projects within a retail setting. Research Design/methodology: A qualitative study in the interpretivist tradition applied within a single case study setting was selected. Findings: Awareness and value-perception emerged as the most significant challenge to overcome with recommendations for a well-considered organisational change management programme to address this. The potential impact on the trust relationship amongst requirements practitioners and participants is a factor to be addressed. More readily accessible requirements engineering guides that include pre-RST as a prominent aspect is required to raise awareness levels amongst practitioners. Practical implications: The research points to a need to raise awareness amongst practitioners through improved and more readily accessible requirements engineering guides that include pre-RST as a prominent aspect. It also highlights what to consider when embarking upon pre-RST, most prominently the need for carefully considered change management programme to tackle value-perception. Originality/value: Addressing the paucity in case study insights, this research provides an understanding of practice, awareness, value-perception and perceived challenges to pre-RST. Considerations for pre-RST implementation, including careful consideration for the trust relationship amongst requirements practitioners and participants is highlighted. Limitations: The case study was limited to eleven interviews in the retail industry and therefore may not be generalisable to other industries or general practice.

International Telemetering Conference Proceedings / October 25-28, 1999 / Riviera Hotel and Convention Center, Las Vegas, Nevada / Standards lead to the creation of requirements listings and test verification matrices allow developer and acquirer to assure themselves and each other that the requested system is actually what is being constructed. Further, in the intricacy of the software test description, traceability of test process to the requirement under test is mandated so the acceptance test process can be accomplished in an efficient manner. In the view of the logistician, the maintainability of the software and the repair of fond faults is primary, while these statistics can be gathered by the producer to ultimately enhance the Capability Maturity Module (CMM) rating of the vendor.

Made available in DSpace on 2014-06-12T15:50:44Z (GMT). No. of bitstreams: 2 arquivo1986_1.pdf: 7023849 bytes, checksum: ba0e9dc1eb31198972dbb6ceaf580dba (MD5) license.txt: 1748 bytes, checksum: 8a4605be74aa9ea9d79846c1fba20a33 (MD5) Previous issue date: 2008 / A engenharia de requisitos argumenta que, para o desenvolvimento de software complexo ser bem sucedido, é necessário que o processo de modelagem suporte mecanismos e ferramentas de rastreamento. Rastreabilidade de requisitos refere-se à habilidade de assegurar um alinhamento contínuo entre requisitos dos stakeholders e às várias saídas do processo de desenvolvimento de software. O processo de rastreamento de requisito descreve e segue a vida dos requisitos nas direções forward e backward (i.e. da sua origem, através do seu desenvolvimento e especificação, para sua subseqüente implementação e uso, e através de todos os períodos de refinamento e interação em qualquer uma dessas fases). Rastreamento de software é executado gerando, representando, armazenando e mantendo relações de rastreabilidade entre os artefatos de software tanto manualmente como automaticamente. Desenvolvedores de softwares têm usado agentes como uma forma de entender, modelar e desenvolver sistemas complexos mais naturalmente. Sistemas multiagentes (SMA) refletem a natureza descentralizada dos modernos sistemas distribuídos, dando suporte a situações dinâmicas e imprevisíveis nas quais se espera que o software opere atualmente, sendo apropriado para sistemas abertos nos quais seus componentes e padrões de interação mudam constantemente. O uso de agentes com uma maior dependência em conhecimento codificado, flexibilidade, adaptabilidade e autonomia, introduz novos desafios ao suporte de rastreamento de requisitos. As capacidades dos agentes e aspectos sociais devem ser consideradas. Uma contribuição neste campo é Tropos, um framework usado para modelar sistemas multiagentes. Ele faz uso das abstrações e conceitos das disciplinas organizacional e social para entender, modelar, analisar e projetar. Assim, Tropos fornece uma maior flexibilidade, e um conjunto de construtores de alto nível para tratar com um mundo operando mais nos princípios sociais do que nas regras mecanicistas. A flexibilidade, a adaptabilidade e a autonomia introduzidas pelos MAS apresentam novos desafios para as abordagens de rastreabilidade atuais. Nós advogamos que um modelo e um processo de rastreamento específico devem ser usados para tratar as necessidades específicas de um SMA de forma satisfatória. Nesta tese, nós propomos um Metamodelo de Rastreamento para facilitar a identificação das novas relações necessárias ao paradigma de agent system, the individual issues of each agent and their social aspects as well as the impact analysis when changes happen. The DBSitter-AS example will be used to illustrate how our proposal captures agent characteristics such as autonomy and cooperation

Traceability in the software industry is a topic which has been studied for a long time, but there still remain questions to be answered. This thesis looks into the state of software traceability in the software industry is today. It is also a case study in implementing traceability in a model-based testing process at a large automotive company. The thesis finds that while progress has been made in identifying the important aspects of traceability, there does not yet exist a clear consensus on general traceability models which can be used to implement traceability in an arbitrary company or project. Through a case study in implementing traceability in a model-based testing process, the thesis gives one example of how this could potentially be done.

The purpose of this thesis is to explore how to enable forward traceability of textile and fashion products at product level, using BC based traceability solutions. The study finds that within TC industry, forward traceability using available technologies (RFIDs, NFCs, QR codes ) is technically possible, however there could be impending regulatory, legal, technical implications of using these technologies. These implications may result in a slew of added compliance requirements, risk assessments and resources allocations from brands and retailers. As a result, this study uncovered that using QR codes with BC technology offers a suitable forward traceability solution which has the potential to set off most of the implications explored during this study. Moreover, to attain forward traceability at product levels, a complete mechanism involving readiness from customers, suppliers and all other stake holders is required. All these stake holders need to be connected to the central BC network, where data is protected and made tamper proof. Lastly, forward tracing at product levels is a futuristic concept, as TC industry is still majorly focused on the backward traceability, however this study finds that forward traceability at product levels may pave its way as a beneficial component of overall sustainability.

Incomplete and incorrect requirements might lead to sub-optimal software products, which might not satisfy customers’ needs and expectations. Software verification and validation is one way to ensure that the software products meets the customers’ expectations while delivering the correct functionality. In this direction, the establishment and the maintenance of traceability links between requirements and test cases have been appointed as promising technique towards a more efficient software verification and validation. Through the last decades, several methodologies supporting traceability have been proposed, where most of them realize traceability by implicitly exploiting existing documents and relations. Nevertheless, parts of the industry is reluctant to implement traceability within software development processes due to the intrinsic overhead it brings. This is especially true for all those light-weight, code-centric software development processes, such as scrum, which focus on the coding activities, trying to minimizing the administrative overhead. In fact, the lack of documentation finishes to hamper the establishment of those trace links which are the means by which traceability is realized. In this thesis, we propose a methodology which integrates traceability within a scrum development process minimizing the development effort and administrative overhead. More precisely we i) investigate the state-of-the-art of traceability in a scrum development process, ii) propose a methodology for supporting traceability in scrum and iii) evaluate such a methodology upon an industrial case study provided by Westermo.

Surface metrology has been widely used in manufacturing for many years. There has been a wide range of techniques applied for measuring surface topography. A photometric stereo technique is one of the best ways for the analysis of three-dimensional (3D) surface textural patterns. Many published works are concerned the developed approach for recovering the 3D profiles from surface normal. This research not only presents a methodology used to retrieve the profiles of surface roughness standards but also investigates the uncertainty estimation of textural measurement determined by the photometric stereo method. Various input quantities have been studied such as pixel error from recovered 3D surface textural patterns, the power of light source which involved with surface roughness average (Ra) value and the effect of room temperature. The surface roughness standards were utilized as the reference value. In term of increasing accuracy of the reference value, a contact method (stylus instrument) was used to calibrate them. Illumination angles of light source had some influence on the measurement results. A coordinate measuring machine (CMM) was used for holding the light source in order to study the effects of tilt and slant angles. The effect of tilt and slant angles were investigated. The results of these experiments successfully indicated that the angle used in photometric stereo method played an important role to the accuracy level of the roughness measurement results. The surface roughness specimen manufactured by a Computer Numerical Control (CNC) was applied to validate the capability of the photometric stereo system.

The maintenance of large-scale software systems without trace information between development artifacts is a challenging task. This thesis focuses on the problem of supporting software maintenance through a mechanism for establishing traceability relations between the system requirements and its code elements. The core of the proposed solution is a set of design rules that regulates the positional (e.g., package), structural (e.g., class), and behavioral (e.g., method) aspects of the system elements, thus establishing traceability between requirements and code. We identify several types of requirements each of which can be supported by design rules. We introduce a rule-based approach to software construction and demonstrate that such a process can support maintainability through two mechanisms: (a) traceability and (b) reduction of defect rate. We distinguish our work from traditional traceability approaches in that we regard traceability as an intrinsic structural property of software systems. This view of traceability is in contrast to traditional traceability approaches where traceability is achieved extrinsically through creating maps such as the traceability matrices or allocation tables. The approach presented in this thesis has been evaluated through conducting several empirical studies as well as building a proof-of-concept system. The results we obtained demonstrate the effectiveness and usefulness of our approach.