A non-functional requirement (NFR) is realized by the architecture and the implementation. The balance can vary. Sometimes the architecture does the most part, e.g. by providing a real-time OS and fixed priorities for critical threads; sometimes the implementation, e.g. by following coding conventions scrupulously to ensure code maintainability. And sometimes the balance is off.
Continue reading When architecture should helpTag Archives: nfr
NFRs and constraints
Architecture is about refining the understanding. Concepts become clearer over time, which means they are reworked, redefined as the understanding progresses. In this direction, it is beneficial to distinguish between constraints and other non-functional requirements. Continue reading NFRs and constraints