Skip to content

Create decision record: split needs and docs? #259

@AlexanderLanin

Description

@AlexanderLanin

Currently all needs (e.g. requirements) are scattered within docs. Any page could contain needs.

Within this ticket we want to investigate an alternative approach: is it feasible to have only a subset of pages have needs? The basic idea is, that if only a subset of rst files contain needs, then it will be much faster to analyze them for correct traceability.
On the other hand it might be simply impractical to do so. Or not worth the downsides, as traceability analysis is fast enough anyway.

As always, when we compare alternatives, we want to write a decision record.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    Status

    Draft

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions