|Overview: Missing Requirements|
A perceived defect that is the result of lacking requirements.
What are Missing Requirements?
John Spacey, updated on August 15, 2017
Missing requirements, or requirements shortfall, is a perceived defect that is the result of lacking functional, behavior or non-functional requirements. The term defect is typically defined as a non-conformance to requirements. Therefore, a missing requirement is typically rejected as a defect according to quality assurance best practices. As such, missing requirements are handled as change requests.It is common for missing requirements to be non-functional or behavioral. This is due to a tendency for business units to focus on business rules over other concerns such as design, user interactions, security and operational characteristics.
Business AnalysisThis is the complete list of articles we have written about business analysis.
If you enjoyed this page, please consider bookmarking Simplicable.
A list of business analysis techniques and deliverables. The common types and formats of requirements.
The difference between business analysis and business architecture.
A few examples of common process gaps.
A definition of best in class with examples.The common types of data analysis.
Common types of technical feasibility.
The common types of requirements elicitation.A definition of requirements management with examples.
The common types of specification. A list of common project risks. A list of basic project management techniques.
A definition of workaround with examples.
A list of project branding techniques.An overview of project stakeholder management with examples. A definition of action plan with examples.
The primary types of cost overrun.The definition of document control with examples.
A guide to project oversight.
A definition of design driven development with examples.
TrendingThe most popular articles on Simplicable in the past day.
Recent posts or updates on Simplicable. Site Map