Implicit requirements are expectations or assumptions that are not voiced by the client but are critical for the successful implementation of the system. The analyst identifies them through business context analysis, process modeling, clarifying questions, and analysis of similar systems. It is important to validate such requirements with the client to avoid misunderstandings and risks. Using techniques such as interviews, observation, and documentation analysis helps make implicit requirements explicit and document them in the specification.