Okuzeka
Software Engineering vocabulary · Agile and Team Workflow

Requirement

Meaning in software engineering, with examples

/rɪˈkwaɪərmənt/nounCore term

In software engineering, requirement means: Something the software must do, or a condition it must meet, as agreed with users, clients or the product team.

In Turkish: gereksinim, ihtiyaç, isterler

How it is used

Usually plural. Teams gather, clarify, change and document requirements. 'Functional requirements' describe what the system does; 'non-functional requirements' cover speed, security and reliability.

Example sentences

  1. The requirements changed twice during the sprint, so we lost a few days.

  2. Before I start, can we clarify the requirements for the export format?

Common collocations

  • gather requirements
  • clarify the requirements
  • meet the requirements
  • non-functional requirements
  • user storyA short description of a feature from the user's point of view, often written as 'As a [type of user], I want [goal] so that [reason]'.
  • featureA piece of functionality that users can see or use, such as a search bar, dark mode or the option to export a report.
  • out of scopeNot part of the work that was agreed for a project, sprint or ticket, so it will not be done now, even if it is a good idea.
  • estimateTo judge roughly how much time or effort a task will take before you start it. As a noun, 'an estimate' is that rough figure.

This word in other fields

The same English word can have a different meaning in another field:

More terms: Agile and Team Workflow

Practise with graded reading

Reading at the right level is the fastest way to make new words stick. Pick free English books by level: