Bi-Directional Requirements Traceability, Software Re-use and Iterative Development Practices

EMBEDDEDLIVELOGO website 414x180px.jpg

Author: Andrew Banks, LDRA

When requirements are managed well, traceability is established between development phases confirming that each is a complete implementation of its predecessor - and no more than that.

While this is a laudable principle, changes of requirements or code made to correct problems identified during test tend to put such ideals into disarray. Despite good intentions, many projects fall into a pattern of disjointed software development in which requirements, design, implementation, and testing artefacts are produced from isolated development phases. Such isolation results in tenuous links between requirements, the development stages, and/or the development teams.

This presentation will discuss these issues and explain how best practices and tools drastically reduce defects. It will explore how to connect the artefacts of the software development, what advantages transparency and traceability provide and how teams can best balance tools, process and domain expertise.

It will go on to outline how the next-generation automated management and requirements traceability tools and techniques can create relationships between requirements, code, static and dynamic analysis results, and tests. It will demonstrate how linking these elements enables the entire software development cycle becomes traceable, making it easy for teams to identify problems and implement solutions faster and more cost effectively.

Agile for Embedded - Tues 25th September 11.20 - 11.45

Sponsored by

LDRA block.png




Andrew Banks is a Field Applications Engineer at LDRA with more than 25 years’ experience of high-integrity real-time/embedded software development.

A Chartered Fellow of the British Computer Society, he graduated from the University of Lancaster in 1989, and has spent most of his career within the aerospace, defence and automotive sectors.

Andrew is committed to standards development - he has been involved with MISRA since 2007 and has been Chairman of the MISRA C Working Group since early 2013; he is the Chairman of the BSI “Software Testing” Working Group; and an active participant of other BSI, ISO, IET and SCSC work, including the recent revision of ISO 26262.