Implicit requirements

Implicit requirements image
Implicit requirements are necessary yet may not always be documented. They are assumed to be understood and necessary. Although these requirements are available in documented format they are usually available outside the project context. 

Examples of implicit requirements:
  • Legal requirements: Ensuring the application is compliant with data protection and accessibility laws. Examples: ADA, GDPR, etc.
  • Regulatory standards: Industry-specific rules exist and any software built for that industry must comply with them. 
  • Marketing claims: If a marketing advertisement mentions "lightning-fast performance," it is expected to be delivered in the coming versions and releases too. 
  • User desires: Common user desires such as responsive design. 
Engineer Your System - Hands-On Virtual Workshop with Elisabeth Hendrickson image
Get 20% off with code MOTAVERSE! Happening on the 13th of March, from 9AM to 1PM PDT. A 4-hour online live deep dive into three core systems thinking tools for software development process improvement.
Explore MoT
TestBash Brighton 2025 image
Wed, 1 Oct
On the 1st & 2nd of October, 2025 we'll be back to Brighton for another TestBash: the largest software testing conference in the UK
MoT Foundation Certificate in Test Automation
Unlock the essential skills to transition into Test Automation through interactive, community-driven learning, backed by industry expertise
This Week in Testing
Debrief the week in Testing via a community radio show hosted by Simon Tomes and members of the community
Subscribe to our newsletter
We'll keep you up to date on all the testing trends.