Non-functional requirements
We’re simply going to ignore non-functional requirements
- Performance, ease of change, etc.
I’m not proud of this, but there is relatively little known about this issue
- Worthwhile concrete discussion: should an interface’s specification (documentation) specify the performance of the operations?
- Pro: Sure, it’s a key property (and people will find it out anyway)
- Con: No way, since I’m supposed to be able to change an implementation as long as it behaves the same