MuleSoft Integration Architect Practice Test

From a user story perspective, you separate what the system must do from how the system must be when it does it. The first category is functional requirements, which cover the features, actions, inputs, outputs, and business rules the user story describes. The second category is non-functional requirements, which address quality attributes and constraints such as performance, security, reliability, usability, and maintainability. Together, these two kinds capture the full set of needs implied by a user story, with acceptance criteria often outlining the expected levels for both. The other groupings—focusing only on performance and security, or on hardware versus software, or on compliance and audit—don't represent the standard twofold split that emerges from translating a user story into concrete requirements.