In the functional standpoint, you will be reviewing the functional side of the solution:
- You know that the customer requires 10,000 hits, but what types of user will be using this website?
- You can see that it requires 10,000 hits, but the premise does not specify what the user will be doing with it.
- The premise states that they need the solution to be available during updates. By this, we assume that the application will be updated, but how?
To clarify the gaps in the functional standpoint, we can ask for the following information:
- What type of users will be using your application?
- What will your users be doing in your website?
- How often will this application be updated or maintained?
- Who will be maintaining and supporting this solution?
- Will this website be for internal company users or external users?
It is important to note that functional standpoint overlaps considerably with the business standpoint, as they are both trying to address similar problems.
Once we have gathered all the information, you can build a document summarizing the requirements of your solution; ensure that you go through it with the customer and that they agree to what is required to consider this solution complete.