👷🚧🏗️👷‍♂️👷‍♀️ This page is under construction. 👷🚧🏗️👷‍♂️👷‍♀️

Non-Functional Design

Do we understand the non-functional needs of the service, are we creating a solution which can meet those need and be flexible, without over engineering?

NF01	Observability: Solutions MUST incorporate workload observability, understand service health, and respond to events
NF02	Appropriate: Technology choices MUST be appropriate to the problem and non-functional needs i.e. we are as equally aware of over engineering as we are to under engineering.
NF03	Performance: An overall volume and performance model MUST exist and includes business-realistic exceptional scenarios.
NF04	Sustainability: Methods to measure sustainability to establish baseline and show improvement SHOULD be defined.
NF05	Auditing: Audit & logging requirements MUST be defined and solutions can support them, as defined in NF05.
NF06	Disaster Recovery: There MUST be clear requirements (commensurate with service levels) around DR & BC (and a pragmatic approach taken with regards DR/BC events planned for)
NF07	Accessibility & UX: The architecture MUST support the ability to maximise the UX and supports accessibility needs and legislation.