3 Functional requirements
Who uses the application and how much. Estimates are fine – just leave open what you don’t know.
Visitors per month Not decided yet under 10,000 10,000–100,000 100,000–1 million 1–10 million over 10 million Personalised content Not decided yet hardly any – almost everything can be cached login area, search, forms shop, portal, many logged-in users Whatever cannot be cached needs computing power for every visitor. Editors in the back end Not decided yet 1–5 6–20 21–100 over 100 Websites or tenants Not decided yet one 2–5 6–20 over 20 Agents in total Not decided yet 1–10 11–50 51–200 over 200 Tickets or cases per month Not decided yet under 1,000 1,000–10,000 10,000–100,000 over 100,000 Channels Users in total Not decided yet 1–50 51–250 251–1,000 1,001–5,000 over 5,000 Concurrent video or office sessions Not decided yet none up to 10 11–50 over 50 Video conferences and co-editing need the most power. Followers or members Not decided yet under 1,000 1,000–10,000 10,000–100,000 over 100,000 Active users per month Not decided yet under 100 100–1,000 1,000–10,000 over 10,000 Contacts or recipients Not decided yet under 10,000 10,000–100,000 100,000–1 million over 1 million Sign-in Not decided yet accounts in the application itself LDAP / Active Directory single sign-on (SAML, OpenID Connect)
4 Non-functional requirements
How resilient, available and secure the environment needs to be, and the framework of your project.
Performance and load Concurrent visitors at peak Not decided yet under 50 50–500 500–5,000 over 5,000 Agents logged in at the same time Not decided yet 1–10 11–50 51–200 over 200 Users active at the same time Not decided yet under 25 25–100 101–500 over 500 Traffic per month Not decided yet under 100 GB 100 GB–1 TB 1–10 TB over 10 TB Amount of media and files Not decided yet under 50 GB 50–500 GB 500 GB–5 TB over 5 TB Load peaks Not decided yet evenly over the day during business hours with campaigns, seasons or deadlines Growth over the next 12 months Not decided yet hardly any up to twice as much more than twice as much
Operations and security Required availability Not decided yet 99.5% 99.9% 99.95% or more Support hours Not decided yet business hours on working days extended, also evenings and weekends around the clock (24/7) Requirements and certifications
Project Starting point Not decided yet new setup migration of an existing system Desired start Not decided yet as soon as possible in 1–3 months in 3–6 months later Procurement Not decided yet direct order tender or public procurement procedure