NFR Patterns and Abilities

Non-functional requirements describe how software should behave, not only what features it contains. These patterns are both how we build and how we work.

Patterns

• NeoLibrary

• Self Service

• Know Your Customer

• Share Everywhere

• Educate, Educate, Educate

• All Pillars of Observability: logs, metrics and traces

• Dynamic Dashboards and Living Notebooks

• Ambient Findability

• Transformations Are All You Need

• Event Driven, Content Powered, Influencer Amplified Programs

• Blueprints, Diagrams, Canvases and 1 Pagers

• AI First

• APIs

• Headless

• Transparent Layers

• Cloud

• SOMOCLO: Social, Mobile, Cloud

Abilities

• Usability

• Observability

• Localizability

• Extensibility

• Composability

• Scalability

• Integratability

• Reliability

• Testability

• Probability

• Transformability, including multilingual, multicurrency and multitimezone operation

• Datastore independence

• LLM independence

These lists overlap by design. Observability appears once because it is both a design pattern and an ability.