Working in an architecture roles I was asking the team that was developing a component to add some logging at certain points. For this I was offered and NFR document to fill in.

Does logging fit as a Non functional Requirement or could they go somewhere else. in oneway a NFR document is convienent for a boiler plate requirement but its functional in that actions trigger logs.

  • 2
    I can see it both ways. While I think it's a functional requirement, in that it actually specifies functionality, that functionality does not contribute directly to any user story or use case. Jan 30, 2017 at 3:30
  • To add to the comment by @RobertHarvey, it can be seen as a non-functional requirement because it is something that needs to be kept in mind for every future story you implement (i.e. it probably ends up in the definition-of-done). Jan 30, 2017 at 17:31

1 Answer 1


That depends on the scope of your application. If you have some legal liability to provide a thorough logging of calculations, user-interactions with the software etc, you need the logging to fulfill your functional requirements.

On the other hand, if you're talking about logging to provide your developers, sysadmins and/or operations a means of debugging and monitoring, then it may not be an actual requirement. In that case, you will have a somewhat pure non-functional requirement.

  • Was the pun in "pure non-functional" requirement intended?
    – Mael
    Jan 30, 2017 at 11:34
  • As I have to ask you 'what pun' - nope. ;)
    – mhr
    Jan 30, 2017 at 11:39
  • I thought it was a twist on "pure" and "functional" as in "purely functional programming language".
    – Mael
    Jan 30, 2017 at 12:12

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.