le being cost optimized over all those performance points at the same time. What do we pick as functional and performance minimums and maximums? Who are the users of the network? Internal only or visitors and guests? Internal use only implies that the test environment can be greatly simplified: the breadth of connected device(s) (types) is very different as this changes the scope of feature development and test. What are the performance requirements? There is no need for wide bandwidth operation if the client does not support this. Sometimes, we really need to optimize for latency rather than bandwidth, and SO on. What are the applications running on the network and what are derived key performance indicators? Application definition. As we show elsewhere, industrial (5G URLLC) deployments are quite different from consumer (5G eMBB) ones with regards to throughput (industrial: less strict) as well as latency and reliability (industrial: stricter). Do we need to support local (edge) compute or only provide a wireless network/pipe without concern for other application presence? Do we need to colocate a core network or is this handled elsewhere? A well-defined application/use case allows the system architect to derive requirements from the elements discussed next rather than having to establish them individually. What are throughput and latency requirements? Throughput is defined as both single- user peak throughput and combined (network-level) aggregate performance over all users. The two numbers do not need to be the same and can have system-level impact (see our discussion on "Elephant Flows" later). The target user count includes definition of both connected users who are visible to the control plane of the system but are not transmitting or receiving data at all times (e.g., an idle phone) as well as active users who are defined as users that are actively transmitting and/or receiving data. What are the coverage requirements? Providing a 5G alternative to Wi-Fi coverage may require much be lenient RF coverage as