How easily the system can be changed if context/requirements change

Degree with which a solution is able to grow or evolve to handle increased amounts of work

Does our system support other (outdated) data formats, work with legacy systems?

How easily a solution or component can be modified to correct faults, improve performance or other attributes, or adapt to a changed environment.

Usability

Scalability

Security

Maintainability

True

False

Degree with which a solution is able to grow or evolve to handle increased amounts of work.

Ease with which a solution or component can be modified to correct faults, improve performance or other attributes, or adapt to a changed environment.

Degree to which the solution is operable and accessible when required for use, often expressed in terms of percent of time the solution is available.

Requirements dealing with local languages, laws, currencies, cultures, spellings, and other characteristics of users, which requires attention to the context.

Performance Efficiency

Usability

Compatibility

Portability

Scope, Timeline, Budget

User, Developer, Manager

Role, Action/Goal, Value/Benefit

Input, Process, Output

It describes more than one action.

It is too detailed for a high-level feature.

It lacks a “so that” part explaining the benefit.

It includes unnecessary technical details.

They cannot be used for agile development.

They focus too heavily on non-functional requirements.

They eliminate the need for team collaboration.

They require detailed acceptance criteria to avoid vagueness.

Ensuring alignment with technical requirements

Eliminating the need for supporting models

Prioritizing features based on user needs

Providing detailed system architecture

List of custom rules

Scenario, Given (precondition), When (trigger), Then (outcome)

User Roles, Stories, and Steps

Metrics, Timeline, and Process Flow