4.1Use Cases
Following are the use cases:
· Register
· Login
· Feedback
· Rating
· Match Type Selection
· Venue Selection
· Opponent Selection
· Pitch Condition Selection
· Player Selection
· Player History
4.1.1 Register
Use case Register
Actors User
Description
This feature is considered as a significant feature of any Application where any new user get registered. Here certain fields are needed to be filled up, that includes Name, Email, Address, Password, Confirm Password and Phone Number. The data provided here will be entered in the Database and will authenticate the user when he will try to login again.
Pre-Condition
User must enter his credentials.
Post Condition
User record will be successfully stored in the Database.
Actor Action System Response
The user should start the application by Clicking the Icon of the Application.
The Software will display a splash screen following by an IDE which occupy multiple fields to be filled in. Also these fields needs to be filled with accuracy and here the user will set his login id and password for login anytime
User will input his Name/Surname The Software will store his name in Database
User will input his Email id The Software will store his email in Database
User will input his Address The Software will store his Address in Database
User will input his Password The Software will store his Password in Database
User will Re-enter his Password The Software will authenticate his Password
User will input his Phone Number.
The Software will store his phone number in Database
User will Press Register Button The record will be successfully Stored in database
Extensions
In case if password is not given correctly or user has not pressed Register button.
His record will went lame.
4.1.2 Login
Use case Login
Actors User
Description
This feature provides the User to Login the Application easily because he has already given his credentials and by the time of Login he will just give his email and password which will be authenticated from database and then the Application will be proceeded.
Pre Condition
The user will give his credentials.
Post Condition
Application will proceed to welcome screen.
Actor Action System Response
The user will enter His Email id The system will cross check his email from Database
The user will enter His Password The system will authenticate his Password from Database
The User will press Login Button The System will display Welcome Screen
Extensions
In case User has not given correct Email or Password he will not be able to Login and System
4.1.3 Feedback
Use case Feedback
Actors User
Description
This feature is the pivotal feature of the project. Where we can gather the user’s opinion that actually helps us in understanding the quality of our Application. Moreover by using feedbacks or reviews we can also modify our Application and we can introduce the modules that may be in accordance with the needs and demands of our users.
Pre-Condition
The User will give his feed back
Post Condition
The Software will store feedback in Database
Actor Action System Response
User will tap the hamburger icon on welcome screen The application will generate a pop-up with the options of Feedback as well as Rating.
User will tap Feedback option The feedback will be given and stored automatically.
4.1.4 Rating
Use case Rating
Actors User
Description
This feature is the pivotal feature of the project. Where we can gather the user’s opinion that actually helps us in understanding the quality of our Application. Moreover by using the statistics of Rating we can also modify our Application and we can introduce the modules that may be in accordance with the needs and demands of our users
Pre-Condition
The User will rate the Application
Post Condition
The Software will store that Rating in Database
Actor Action System Response
User will tap the hamburger icon on welcome screen The application will generate a pop-up with the options of Feedback as well as Rating
User will tap Rating option The Rating will be given and stored automatically.
4.1.5 Match Type Selection
Use case Match type selection
Actors User
Description
A pre-dominant feature of this Application is to select the Category of cricket Match. By tapping Match Type the user will be provided with three options i.e. ODI, Test Match and T-20. The user will click the desired type and proceed
Pre-Condition
User will select the desired Match Type.
Post Condition
The List of Players with be in Accordance with Selected Match Type.
Actor Action System Response
The use will click on Match type.
The Application will provide a scroll down of Type of Matches
The User will Select a Match Type The List of Players will be in accordance with selected Match Types.
4.1.6 Venue Selection
Use case Venue Selection
Actors User
Description
A pre-dominant feature of this Application is to select the Venue of cricket Match. By tapping Venue, the user will be provided with options of list of countries. The user will click the desired country and proceed
Pre-Condition
User will select the desired venue.
Post Condition
The List of Players with be in Accordance with Selected venue.
Actor Action System Response
The use will click on Select Venue.
The Application will provide a scroll down of List of countries
The User will Select a country The List of Players will be in accordance with selected country.
4.1.7 Opponent Selection
Use case Opponent Selection
Actors User
Description
A pre-dominant feature of this Application is to select the Opponent for cricket Match. By tapping Select Opponent, the user will be provided with options of list of countries. The user will click the desired country and proceed
Pre-Condition
User will select the desired opponent.
Post Condition
The List of Players with be in Accordance with Selected venue.
Actor Action System Response
The use will click on Select opponent.
The Application will provide a scroll down of List of countries.
The User will Select a country The List of Players will be in accordance with selected country.
4.1.8 Pitch Condition Selection
Use case Pitch Condition Selection
Actors User
Description
A pre-dominant feature of this Application is to select the Opponent for cricket Match. By tapping Select Opponent, the user will be provided with options of list of countries. The user will click the desired country and proceed
Pre-Condition
User will select the desired opponent.
Post Condition
The List of Players with be in Accordance with Selected venue.
Actor Action System Response
The use will click on Select opponent.
The Application will provide a scroll down of List of countries.
The User will Select a country The List of Players will be in accordance with selected country.
4.1.9 Player Selection
Use case Player Selection
Actors User
Description
Here, at this point of Application when we got a list of users that we eventually fetched out after providing multiple Filters of Match type, Venue, Opponent and Pitch condition. If user want to view the detailed information of any player he just simply have to tap the player and his history will be displayed including multiple information about him.
Pre-Condition
User will select the Player.
Post Condition
The history of relevant player will be flashed.
Actor Action System Response
The use will click on the Player.
The Application will provide the history and information about the player.
4.1.10 Player History
Use case Player history
Actors User
Description
Here, at this point of Application when we got a list of users that we eventually fetched out after providing multiple Filters of Match type, Venue, Opponent and Pitch condition. If user want to view the detailed information of any player he just simply have to tap the player and his history will be displayed including multiple information about him. Player history contains detailed data and statistics about the player.
Pre-Condition
The history of relevant player will be flashed.
Post Condition
The user can view the history
Actor Action System Response
The use will click on the Player.
The Application will provide the history and information about the player.
The user can view the data and statistics of the player.
4.2 Use Case
4.3Class Diagram
4.3Activity Diagram
4.4 Architecture Diagram