requirements traceability
Traceability is how you demonstrated that requirements were allocated, implemented, and tested.
It’s how to demenstrate that various disparate documents have connections to each other.
Traceability ensures that we accounted for everything and that nothing is forgotten.
Traceability is not an easy task.
It's a many-to-many-to-many relationship between documents and it has to be human-readable.
Current tools on the market (such as
JAMA and
DOORS)
manage documents by storing them in a database running on a server.
Most of the documents that are part of your project will need to be maintained in DOORS.
Once DOORS is adopted, a company often becomes completely wed to those processes.
Often companies adopt freindly-looking programs like JAMA, only to realize that it isn't a longevity product line.
Entering Requirements through a a proprietary tool is an accomplishable task, but…
- how are different file formats (such as software source code) traced?
- how are non-requirements (such as tests or reports) traced?
- what if you are tracing to an industry document that is in a weird format?
Some systems force you to create a proxy document or to import a copy so that it can be managed in the module and traced.
Now you have to maintain the source document and the proxy document in DOORS.
Another problem is trying to export printable documents from the DOORS modules.
A lot of intuitive information can be lost in formatting and these systems are not
WYSIWYG
when the document is maintained in a database then exported to something printable.
Carma traces files in any format, without using a database.
Carma works by creating a project file that groups files together in a hierarchal order.
The hierarchy helps establish groups of dependencies.
For example, if High-Level Requirements need a High-Level Test, then all that's needed is to add the tests under the requirements and to link them in Carma.
#Uplinks, #CrossLinks, and #DownLinks all you to see which items are connected.
Carma works by creating a project file that groups files together in a hierarchal order.
The hierarchy helps establish groups of dependencies.
For example, if High-Level Requirements need a High-Level Test, then all that's needed is to add the tests under the requirements and to link them in Carma.
#Uplinks, #CrossLinks, and #DownLinks all you to see which items are connected.
- it's your data -
Uses your files in your formats. Open Source Inputs with Open Source Outputs.
Documents are added to the project and they are parsed by Carma using custom algorithms.
You choose the format and develop documents using any tool you want - Carma doesn't get in the way of that.
Stitch together Word Files, Excel, Text Files, Software Source Code, pdf, xml, json, python.
Trace anything with a file path. Carma works great with existing document control systems, such as
Subversion
- Parses Word, Excel, txt, source code, python, -nearly anything with a file path
- Extracts requirements from documents regardless of the formatting (id's, or context, or table cells)
- Extracts source code functions for most any programming language
- Automatically builds a list of recommended connections based on Well Known Names, attributes and id's
- Tracts changes in files providing and instant Change-Impact-Analysis
- Enables cross-links to be inserted into Word Documents so that bookmarks for references are navigable between documents
- Provides publishable html outputs to host dynamic documents on the web