Tailoring Traceability Information to Business Needs

Arkley, Paul; Riddle, Steve; Brookes, Tom

doi:10.1109/re.2006.63

Cited by 17 publications

(26 citation statements)

References 3 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…It should also be noted that a good safety case is useful in defence of any litigation. Competitive Advantage: Traceability reduces production costs [15,17] through reuse, error avoidance etc. Traceability also allows for impact analyses (case studies [6,[13][14][15][16]and general literature [9,26,27]) which in turn allows for cost estimation of any change to a system.…”

Section: Resultsmentioning

confidence: 99%

“…Traceability improves the ability to develop realistic cost proposals and gain competitive advantage in building similar systems due to "savings from using [a] lessons learned database of critical issues and rationale" [2]. Productivity and Quality gains: Traceability helps facilitate productivity and quality gains [13,[15][16][17]19]. Reuse of 'proven' artefacts from design, code or test stage ensure productivity gains as these artefacts don't have to be reproduced, saving both time and effort.…”

Section: Resultsmentioning

confidence: 99%

“…This may be because of regulations; therefore linking requirements to sources can help avoid conflict and rework. Requirements validation: Process conformance will be facilitated through traceability as requirements validation [25] will be ensured and the product will satisfy customer requirements [14,15,17,19]. While unidirectional forward tracing facilitates requirements validation, the reverse of this(tracing from code to design and onto requirements) helps mitigate the risk of 'gold-plating' i.e.…”

Section: Resultsmentioning

confidence: 99%

“…23 engineers (4 Systems Engineers, 7 Subsystem Engineers, and 12 Design Verification Engineers) responded directly to the survey regarding their experiences with traceability. Arkley and Riddle: 2006 [15] observed a project, conducted at BAE SYSTEMS Electronics and Integrated Solutions (E&IS) (Plymouth, UK) that developed a requirements traceability system which is integral to their development process. The E&IS operating group of companies designs, develops and manufactures a wide range of electronic systems and subsystems for both military and commercial applications.…”

Section: Research Methodsologymentioning

confidence: 99%

“…Traceability helps project leaders identify the relevant stakeholders [6,15] to involve when drawing out requirements and makes the requirements negotiation stage easier as backward tracing links requirements to their origin. Rationale for decisions: Many critical decisions are taken during the SDLC and the rationale for these decisions [13,14] can be lost unless they are documented and traced to the corresponding artefacts.…”

Section: Identification Of Stakeholdersmentioning

confidence: 99%

See 4 more Smart Citations

Traceability-Why Do It?

Regan

McCaffery

McDaid

et al. 2012

Communications in Computer and Information Science

View full text Add to dashboard Cite

Abstract. Traceability of software artifacts, from requirements to design and through implementation and quality assurance, has long been promoted by the research and expert practitioner communities. However, evidence indicates that, with the exception of those operating in the safety critical domain, few software companies choose to implement traceability processes, in the most part due to cost and complexity issues. This paper presents a review of traceability literature including the implementation of traceability in real organizations. Through both analyzing case studies and research published by leading traceability researchers, this paper synthesizes the motivations of the organizations for implementing traceability. Given the importance of traceability in the regulated domain of safety critical software, the paper compares the motivations and benefits for organizations operating inside and outside of this domain. Finally, based on an analysis of the disparate case studies, the paper re-assesses the value of traceability motivators for more widespread adoption by firms outside of the safety critical sector.

show abstract

Section: Resultsmentioning

confidence: 99%

Section: Resultsmentioning

confidence: 99%

Section: Resultsmentioning

confidence: 99%

Section: Research Methodsologymentioning

confidence: 99%

Section: Identification Of Stakeholdersmentioning

confidence: 99%

See 3 more Smart Citations

Traceability-Why Do It?

Regan

McCaffery

McDaid

et al. 2012

Communications in Computer and Information Science

View full text Add to dashboard Cite

show abstract

3.2.2 Traceable Engineering of Fault‐Tolerant SoSs

Andrews

Ingram

Payne

et al. 2014

INCOSE International Symp

View full text Add to dashboard Cite

Abstract. Systems of systems (SoSs) are characterised by a challenging combination of continuous evolution, emergent behaviour and distributed, autonomous and independent constituents. The development of SoSs that can tolerate faults and harmful events is hampered by these and other complexities. Currently there is little in the way of methods or tools to help SoS developers to design fault-tolerant SoSs. In this paper we present a structured approach for capturing requirements for a fault-tolerant SoS and a fault modelling architectural framework (FMAF) that supports disciplined and reusable development of fault-tolerant architectures. We also provide a traceable mapping of the fault-tolerant requirements into SoS architectural designs. Finally we apply our techniques to a real-world SoS case study.

show abstract