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. 
Explore MoT
AI-driven testing in practice: from requirements to reliable automation image
See where AI genuinely helps, where it doesn’t, and how testers can stay firmly in control
MoT Software Testing Essentials Certificate image
Boost your career in software testing with the MoT Software Testing Essentials Certificate. Learn essential skills, from basic testing techniques to advanced risk analysis, crafted by industry experts.
Into The Motaverse image
Into the MoTaverse is a podcast by Ministry of Testing, hosted by Rosie Sherry, exploring the people, insights, and systems shaping quality in modern software teams.
Subscribe to our newsletter