tion Sem 1 2020/2021 (page 31 of 34) e@Uniten Checklist for Requirements Specification Reviews C1: Do any requirements conflict with or duplicate other requirements? C2: Is each requirement uniquely and correctly identified? C3: Are all requirements actually requirements, not design or implementation The requirement specification under review looks as follows: Functional Requirement 1 ID: FRI Title: Download mobile application Description: A user should be able to download the mobile application through an application store. The application should be free to download. Functional Requirement 2 ID: FR3 Title: User registration Description: Given that a user has downloaded the mobile application, the user should be able to register through the mobile application. The user must provide username, password, and e-mail address. The user data should be kept in the MySQL relational database in a table UserData" with columns user_id," "username," "password," and "email, where user_id is the primary key. Functional Requirement 3 ID: FR3 Title: User logging Description: Given that a user is registered the user should be able to log in to the application with his/her username and password. Functional Requirement 3 ID: FR3 Title: User payment Description: User should be able to make payment when the mobile application completely downloads from the application store. Based on the given checklist, identify and explain the violations for each of the requirements. hp