Software Design
Design for mlx.traceability
Since the sphinx documentation system is python based, and it allows for plugin development in seperate python packages, python was chosen. No limit should exist on the version of python or sphinx.
A directive name item is added to sphinx through the plugin that allows splitting the documentation into parts. The documentation parts are stored as objects of class TraceableItem. All TraceableItem objects are stored in a container class TraceableCollection.
A first argument to the item directive is used as a unique identifier for the documentation part. The identifier can be any string - not containing spaces.
To ensure uniqueness of the identifier, the TraceableCollection is used. When a TraceableItem will be added to the collection, its identifier is first checked to not appear in the collection yet. If it exists already, a warning is added to the documentation build log.
A second optional argument to the item directive is used as a brief description, or caption of the documentation part. This argument is allowed to have spaces. The caption is stored in the TraceableItem object.
The content of the item directive is used as the content of the documentation part. The caption is stored in the TraceableItem object. The content is forwarded through the sphinx parser. So other plugins and/or the native sphinx tool performs conversions from reStructuredText (rst) syntax to docutils nodes.
Attributes can be added to the documentation parts. Attributes have a key and an optional value. The set of attributes, their order and the validness of the attribute values are configurable.
Documentation parts can be linked to other documentation parts. The set of relations is configurable.
When a documentation part <A> is related to a documentation part <B> (forward relation), the reverse relation from documentation part <B> to documentation part <A> gets created automatically.
A list of documentation parts matching a certain query can be retrieved.
The plugin is able to calculate the coverage for a certain type of relation between documentation parts.
The relations between documentation parts can be queried, and an overview matrix can be generated.
The relations between documentation parts can be queried, and an overview tree can be generated.
An overview table of the attribute values for documentation parts can be generated.
The plugin has a directive that allows configurability of the order of items’ attributes.
Traceability matrix
Tree of design
Coverage to requirements and implementation
Trace design to requirements
Statistics: 14 out of 14 covered: 100%
Design |
Linked Requirements |
Linked Implementation |
---|---|---|
Design reverse coverage
Trace design to requirements
Statistics: 14 out of 14 covered: 100%
Design |
Linked Requirements |
---|---|
Implementation coverage
Trace design to implementation
Statistics: 1 out of 14 covered: 7%
Design |
Implementation |
---|---|