@crazybutable
That’s standard usage in dev circles, yup. And it’s reasonable to break software down that way. And yes, I realized it’s a term of art.
Still, it’s the word “requirements,” and the mindset it implies, that I object to. It sounds like “things teacher said you must do to get an A,” which isn’t even a good way to thinking about •school•, let alone software development.