ImpliedRequirements

Select and name chunks of functionality

Definition

Early in the requirements gathering process, the requirements are needed for delimiting scope and for estimation purposes.   Select and name chunks of required functionality that will act as placeholders for implied detailed requirements.

Source

Implied Requirements

Discussion

Early in the requirements gathering process, the requirements are needed for delimiting scope and for estimation purposes.   Detailed requirements are not needed until detailed estimates, detailed analysis or detailed design are needed.  If we are proceeding by IterativeDevelopment, then the requirements do not need to be detailed until needed for the iteration in which the functionality is to be developed.  This enables the process to benefit from feedback obtained from earlier iterations, and allows commencement of design before all requirements are detailed.  Without detailed requirements, detailed estimates cannot be made, so detailed schedules can only be accurate for a short period in advance.  However, long term rough estimates and work planning can be made by use of a WorkQueue.  A modern variant of Implied Requirements is the UserStory.