Uploaded image for project: 'Qt Safe Renderer'
  1. Qt Safe Renderer
  2. QSR-768

Jira usage for requirement management in QSR 2.1

XMLWordPrintable

    • Icon: Task Task
    • Resolution: Done
    • Icon: P3: Somewhat important P3: Somewhat important
    • QSR 2.1
    • QSR 2.0
    • Documentation
    • None

      QSR requirement specification states:

      "From QSR 1.1 onwards, all QSR requirements derived from this document are available in the Jira system that is used for Qt bug and issue reporting [8]. The QSR Safety Plan [9] specifies the process for requirement handling."

      Known issues: Requirement linking. The requirements are only in the word document albeit the QSR 1.1 version suggests that requirements would be in Jira.

      • Test Rail can link the test cases to requirements, so Jira items can be tracked easily
        • Note that linking is bi-directional, so it is possible to see in the Jira what tests are linked to the Jira issues
      • When the requirements are not available as Jira items, there are some hiccups:
        • This prevents linking of the Jira requirement items and related tests properly.
      • In case that requirements would be in Jira in the future, there would be a need to separate the actual requirements and implementation tasks somehow.
        • By following the agreed data models and power use of the linking.
        • Also, the requirement versioning would need some thoughts. Basically it would be possible to replace also the requirement specification with Jira.

       

        No reviews matched the request. Check your Options in the drop-down menu of this sections header.

            tarjasundqvist Tarja Sundqvist
            assaarel Asmo Saarela (Inactive)
            Miao Luo Miao Luo
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved:

                There are no open Gerrit changes