• snooggums@midwest.social
    link
    fedilink
    English
    arrow-up
    1
    arrow-down
    1
    ·
    5 months ago

    Requirements ≠ Documentation.

    They are part of documentation, but not all documentation.

    • vrek@programming.dev
      link
      fedilink
      English
      arrow-up
      1
      arrow-down
      1
      ·
      5 months ago

      The difference is in exact wording Agile: the software shall properly authticate a user within our active directory.

      Documention : user authentication will be provided by functions ”valisate username” as described in section 14,7 subsection 4, ”validate password” as described in section 16.2 and validate the correct pasword as described in section 23.4.Proper authication to the correct use group shall comply with the requirements in document 654689 section 64.7 subsection 17

      Yes there is a difference and one is better…

      • snooggums@midwest.social
        link
        fedilink
        English
        arrow-up
        2
        ·
        5 months ago

        So you started with the need to authenticate, which should be documented in the requirements. You know, the things that are required to happen.

        The details on HOW to authenticate are ALSO documentation. Not all documentation describes functionality.