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. 
RiskStorming image
An educational tool to explore Risk Analysis and Quality Strategy building with the whole team.
Explore MoT
Castelo Branco Meetup image
Tue, 6 May
The Future of Testing in an Automated World: Embracing Continuous Learning and A
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. Early access available now at a discounted rate!
Leading with Quality
A one-day educational experience to help business lead with expanding quality engineering and testing practices.
This Week in Testing image
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.