Hello,
I am writing a requirement for Data Transmission. The requirement says that the system must be able to transmit Data based on the "X" Standards
Then I will go to specify what is that "X" Standards mean for example, the first name should be Varchar and allows spaces and hyphens.
This is a Data Quality Requirement.
I am almost confident this is a Non-Functional Requirement because it relates to Data Consistency and Quality, however, because it involves Data Transmission Specification, could it be considered Functional?
I truly appreciate your inputs
OK, so this all rather depends on the information you have provided and my interpretation of it.
I am assuming that what you mean is that a system needs to be able to handle some data and handle it in a particular way.
If that's the case, then it is a functional requirement. My advice would be to make sure the requirement is very specific. What type of characters are input into the system and what is expected to come out - Alpha and numeric characters? Symbols? Put them all in a table and show what type it is , what goes in, what is expected to come out and when you have finished get it in writing that that is what you stakeholder wants. They have an annoying habit of changing their mind !!
If they also want requirements about how quickly the system should pass/create the data, then that is a non-functional requirement.
In short, if the requirement means something happens (or doesn't) because of it - then it is functional. If the requirement is purely about how fast or what impact it has (to quote two) then its Non-functional.
brought to you by enabling practitioners & organizations to achieve their goals using: