This core concept refers to how requirements are traced, prioritized, and maintained to ensure that a need is met.

Let's look at an example to bring this concept of need into the real world:

If we continue with the example of the change request for the electricity supply charges review process, you will also capture the details of this change request as part of your requirements traceability activities. You will, therefore, know in future why the approved requirement was changed and what the new requirement entails. This change request may also have an impact on the priorities associated with the affected requirements.

This example illustrates how the core concept of need is implemented during Requirements Life Cycle Management by tracing changes to requirements, carefully maintaining the requirements, and considering a potential change in priority to deliver the requirements that meet the business needs.