You are designing test cases based on the following use case:
Use case: logging in to the online banking system
1. The user opens the banking application.
2. The system displays the login page.
3. The user enters their username and password.
4. The user clicks the “Login” button.
5. The system verifies the username and password in the database.
6. The system starts the multi-factor authentication (MFA) procedure.
7. The user undergoes MFA verification.
8. The system logs the user in and redirects them to the welcome screen.

Alternative flows -
3A - the user clicks the “Forgot Password” button. The system sends an e-mail with a link to reset the password and returns to step 2
5A - incorrect password. The system displays the message “Incorrect password”, and after closing the window with the message, it returns to step 3

Exceptions -
2A - system unavailable due to maintenance work. The system displays the message “Maintenance work in progress; try later” and the login process ends
7A - MFA verification error. The system displays the message “MFA verification failed" and the login process ends
The test strategy requires that coverage of the main scenario, alternative flows, and exceptions is achieved for each use case. The strategy allows testing multiple alternative flows within a single test case. Each exception must be tested with a separate test case, but a test case can contain alternative flows.
What is the MINIMUM number of test cases that will achieve this coverage?