Achieving end to-end bidirectional traceability in complex software projects
•Download as PPTX, PDF•
0 likes•432 views
End-to-end traceability is not only beneficial in terms of process improvement, product quality and efficiency of development; it’s also a requirement in many (safety-critical) industries. Thus, establishing links between artifacts, and ensuring transparency & process visibility could facilitate compliance audits, making it important for developers in various highly regulated sectors. Watch this webinar recording to learn about the three layers of traceability, and to see how you can ensure complete bidirectional traceability throughout the development lifecycle, even across projects.
Recommended
Recommended
More Related Content
What's hot
What's hot (20)
Similar to Achieving end to-end bidirectional traceability in complex software projects
Similar to Achieving end to-end bidirectional traceability in complex software projects (20)
More from Intland Software GmbH
More from Intland Software GmbH (20)
Recently uploaded
Recently uploaded (20)
Achieving end to-end bidirectional traceability in complex software projects
- 1. Achieving End-to-End Bidirectional Traceability in Complex Software Projects Peter Haller 08 July 2015
- 2. 2 Intland Software Webinar info • Live demonstration will be followed by a Q&A session • Webinar recording will be • available at http://intland.com/webinars/ • Sign up for our upcoming webinars
- 3. 3 Agenda • Introduction Intland Software • Introduction to traceability • Three layers of traceability • Live demo – Staying on the top of processes using codeBeamer & the Traceability Browser
- 4. 4 • Founded in 1998 • Headquarter in Stuttgart, Germany • Office in Silicon Valley, USA • Partners in Korea & Taiwan • Development, consulting and services in Germany • Provider of an ALM tool with three main modules: • Requirements Management • Development Management • QA & Test Management Introduction Intland Software
- 6. 6 • Establish traceability between all artifacts in the lifecycle such as requirements, specifications, test cases, bugs and code • Show relationships between artifacts • Provide audit trail on all artifacts in the lifecycle Introduction to traceability Benefits of traceability Traceability is important to:
- 7. 7 End-to-end Traceability A practical example Release 1 Release2
- 10. Thank you for your attention! Any questions? Webinar: Agile, V-Model / Waterfall and Hybrid Development Date: 15 July 2015 Time: 4:00 PM (CET) / 10:00 AM (EST)
Editor's Notes
- When organizations fail to deliver quality software on time and on budget, it is typically not because any individual is dysfunctional, but because the entire team or organization is misaligned. End-to-end visibility enables organizations to proactively steer projects to success based on real-time information. Traceability is the ability to gain an end-to-end view across your project lifecycle. When your software is delivered to the customer, you should be able to identify all the activities associated with the software. You should be able to state with confidence that the software includes this specific requirement, included in this software build, validated by this test case and with this test result. Anything less and you really don’t know what you are delivering and whether what you are delivering will meet your quality requirements. End-to-end lifecycle traceability is a prerequisite for meaningful insight into project status, issues and risks. For example, the question, “Are we ready to release?” requires knowledge that can only be gathered by correlating requirements, code, build, and test information-data that potentially resides in four different repositories. The ideal environment will allow teams to easily link related assets and maintain those linkages as assets evolve.
- Traceability isn’t simply one of those “nice to have” capabilities in the software development lifecycle. Traceability helps you understand what everyone else on the team is doing. For example, while the requirements analyst knows very well what requirements he has written, he still needs to know whether a given requirement will be addressed during a specific development iteration and, if so, which one. Or he wants to know if the implementation of that requirement has been tested and with what result. It is important to understand how requirements, test and development are linked by projects and tasks. We can differentiate 3 dimensions of traceability: Artifact traceability (also referred to as horizontal traceability) is tracing each individual product requirement into the analysis and design, construction, testing and validation, releases etc. The purpose of artifact traceability is to ensure that each requirement is going through all the necessary phases of the development lifecycle. In software and hardware engineering contexts, you always have to make sure you have a transparent view of how your requirements are being covered by test cases to provide proper validation. This kind of tracing may employ forward tracing and backward tracing. Forward tracing is used when the tracing follows subsequent steps in a development path, such as forward from requirements to the design code. Backward tracing means the opposite, following the steps backward such as code through design to requirements. codeBeamer offers forward and backward traceability: bi-directional traceability can be enforced at any point in the project. Historical traceability (also referred to as vertical traceability) is ensured on each and every item, letting you browse and control all changes on every singe artifact. Previous versions and changes can be reviewed, along with all the relevant details of these changes (who made the chances, when, and what exactly was changed). Project Traceability means that all the details of the entire process and work history are stored and can be assessed any time. It basically means total transparency of your projects. In the codeBeamer this kind of traceability can be enforced with baselines and it spans the vertical and horizontal traceability of any item or even entire projects.
- Live demo. Manage multiple projects at the same time. As codeBeamer is a browser based system it can be access from anywhere with an internet connection and can be used in Chrome, Firefox and Internet Explorer as well. But, before we get started with the live demonstration I have a couple of questions that I would like to ask.