| ▲ | hgomersall 2 hours ago | |||||||
I don't necessarily disagree, but can you give an example of a non functional requirement that influences the design? | ||||||||
| ▲ | Jtsummers 2 hours ago | parent [-] | |||||||
I always find the distinction between the two fuzzy (because many non-functional requirements can be argued to be functional requirements) but the list here is useful for the discussion: https://en.wikipedia.org/wiki/Non-functional_requirement Take things like "capacity". When building a system, you may have a functional requirement like "User can retrieve imagery data if authorized" (that is the function of the system). A non-functional requirement might be how many concurrent users the system can handle at a time. This will influence your design because different system architectures/designs will support different levels of usage, even though the usage (the task of getting imagery to analyze or whatever) is the same whether it handles one user at a time or one million. | ||||||||
| ||||||||