Requirements

Functional

Functional requirements are features that allow the system to function as it was intended. Put another way, if the functional requirements are not met, the system will not work. Functional requirements are product features and focus on user requirements.

• MUST allow creating army lists AKA rosters

• MUST be usable on mobile

  • We know a lot if not most of the usage of BS is mobile

• MUST work with all BSData created by existing tooling

• MUST be able to gather data from data sources, eg Gallery

Non-functional

While functional requirements define what the system does or must not do, non-functional requirements specify how the system should do it. Non-functional requirements do not affect the basic functionality of the system (hence the name, non-functional requirements). Even if the non-functional requirements are not met, the system will still perform its basic purpose.

• MUST follow rules and guidelines of both Apple App store and Google Play store

• MUST be client based, with minimal calls home

  • We'll not be able to do server-hosting for the traffic the community generates. client-side, static website/PWA

• MUST be independent of data

  • We'll need to keep the same data-app separation BS does. client-side data management

• SHOULD have translations for non English users

• SHOULD look good

• SHOULD be performant on all devices

• COULD offload some tasks to server side

---

Fluffy text from https://qracorp.com/functional-vs-non-functional-requirements/