Tag Archives: Traceability

Traceability - Just Make it Simple.

May 15, 2008 – 2:25 pm

You hear a lot about “traceability’ in context to requirements management. It’s one of the primary benefits and reasons for buying a requirements management solution.
As the products we’re all building become more sophisticated as stand-alone software applications or embedded software within physical products, it’s common for development projects to consist of hundreds or thousands [...]

By Eric | Posted in Eric, Requirements Management | Also tagged , | Comments (1)

Cross Project Linking

January 31, 2007 – 11:50 am

Contour’s cross project linking allows a project to reference a requirement in a separate project.
Several clients had requested the ability to link requirements (or any items for that matter) across different projects. During analysis we realized that there were several possible implementations.
One option was to completely link an item from one project into another, such [...]

By Derwyn | Posted in Uncategorized | Also tagged , | Comments (0)

Impact Analysis

January 29, 2007 – 8:42 pm

With the release of Contour 1.3 users are able to see immediately the project artifacts – and team members working on those items that may be affected. This is one of the primary benefits or implementing project traceability.
For example, if I am a business analyst and I’m about to make a change to a [...]

By Eric | Posted in Uncategorized | Also tagged , | Comments (0)

Demystifying Traceability

January 9, 2007 – 9:22 pm

The latest release of Contour, our requirements management tool, incorporates some new features that got me thinking about traceability.
At Jama we use relationship and traceability interchangeably. To us the term “relationship” is much easier to understand than “directional trace” even though it may not be technically correct. (Contour can be set to use whatever [...]

By Eric | Posted in Uncategorized | Also tagged , | Comments (0)