Implicit and Explicit requirements

Implicit and Explicit requirements

Explicit Requirements​ :  
● The Things business analyst Wrote Down. 
● These are the requirements explicitly stated or mentioned by the customer. 
● Explicit requirements are most commonly found in documents communicated by stakeholders to the development team.  
● This is the simplest type and the easiest to test. 
● The development team might take the form of an elaborate design specification, a set of acceptance criteria. 
● Explicit requirements in the form of claims that is, communications to end-users about things the software can do.  

Implicit Requirements​ : 
● The Things client Will Expect 
● These are the requirements that are not explicitly stated by the customer, but implied or derived from the requirement stated by the customer. 
● These are all the things that users are going to expect that were not captured explicitly. 
● Examples include performance, usability, availability, and security. 
● Implicit requirements are sometimes called ​nonfunctional​ requirements. 
● It’s certainly possible to capture business expectations about any of those nonfunctional areas explicitly, at which point they can be treated like any other explicit requirement.