A nonfunctional requirement specifies the general properties and operational constraints an application must satisfy, rather than the functions it performs. In a spacecraft system, robustness, fault tolerance, continuous operation, ease of use, security, compatibility, performance, stability, extensibility, availability, capacity, and latency are nonfunctional requirements. section 1.2.1
Spacecraft control software
Manual and automatic control are functional requirements because they describe what the software does. Operating reliably around the clock, remaining secure, processing the required amount of data, and avoiding a rewrite as the system evolves are nonfunctional requirements that shape its design. section 1.2.1
Figure 1.4 Compromising between simplicity, goals, and requirements
Use the trade-off diagram to relate simplicity, goals, and requirements when choosing a design that remains maintainable. section 1.2.1





