How deeply does a systems analyst participate in non-functional requirements — performance, fault tolerance, monitoring, security?

A systems analyst participates in non-functional requirements at the level of gathering, analyzing, and formalizing requirements, as well as coordinating their implementation. Specifically:

• Performance: the analyst gathers requirements regarding response time, throughput, load, and helps define acceptance criteria.
• Reliability: participates in defining requirements for redundancy, recovery after failures, and availability levels (SLA).
• Monitoring: formulates requirements for logging, metrics, and alerts for timely problem detection.
• Security: gathers requirements for authentication, authorization, data encryption, and compliance with standards.

Although the technical implementation and testing of these requirements are usually the responsibility of developers and engineers, the systems analyst plays a key role in understanding business goals, formalizing requirements, and ensuring their consistency with the system's functional aspects.