ASSIGHNMENT NO 1

Submitted by:
Muhammad Maqbool Ahmad (SP21-BSE-043)

Submitted to :
Sir iftikhar azam niaz

Submission Date:
17– October – 2022
Recharge Protal

Modules:
1. Login System.

2. Recharge account.

3. Subscribe Offer.

4. Transfer Money.

5. Transaction (Deposit and Withdraw).

6. Logout.

7. Managing System.

Scope:

The online mobile recharge system is beneficial to both the admins and users. Using the online
application, the admin can add new operators, tariff plans, offers and update or modify the
existing tariff plans. It helps the users in creating their account, and then recharging the
mobiles phones at any time.

Proposed Solution:
We are developing recharge portal system so when it is developed we can easily create account
or remove if you have one .We can also make request to recharge account, transfer money
and use transactions by using internet .
 1. Login Page

Login
 Use Case ID: UC-1.1
Use Case Name: Login

Actors: User (Primary Actor)

System admin (Secondary Actor)
Preconditions: 1. User must have registered account to login.

Post conditions: 1. After successful login, user will be able to avail all services of this application.

Normal Flow:

1. User select login option.

2. User enters id and password.
3. User clicks on submit button.
4. System validates if user is registered or not.
5. If validation goes well then user is logged in.
Alternative
Flows: 4a. In step 4 of the normal flow, if the user is not registered
1. System will ask user to create account
[Alternative 2. Process is terminated.
Flow 1 – Not
Registered]

Exceptions:
2a. In step 2 of the normal flow, if the user enters invalid id and or password.

1. Message to user to re-enter id and password.

2. System also provides extended facility if user forgot password, if user selects
forget password option then system will assist user to create new password.
3. User enters correct id and password
4. Use Case resumes on step 3 of normal flow.
Includes: It includes two processes:

1. Enter id and password.

2. Submit and validate entered id, password.

Quality This response time of this process should be a second or less.

Requirements

Create Account

Use Case ID: UC-1.2

 Use Case Name: Create Account

Actors: User (Primary Actor)

System admin (Secondary Actor)
Preconditions: 1. User must have opened the application.

Post conditions: 1. After account creation, new user will be logged in automatically and can use all
features of this application.

Normal Flow:

1. User select create account option.

2. User enters all required credentials.
3. User clicks on submit button.
4. System validates if user has entered all credentials in correct format.
5. If verification goes well then user is logged in.
6. The new registered user is saved in user’s table (database).
Alternative
Flows: 4a. In step 2 of the normal flow, if the user enter id which has been already
registered to some other user
[Alternative
Flow 1 – Already 1. System will ask user to enter unique id.
Registered] 2. Process resumes on step 3 of normal flow.
Exceptions:
2a. In step 2 of the normal flow, if the user enters credentials in wrong format

1. Message to user to re-enter id and password.

2. User enter credentials in correct format
3. Process resumes on step 3 of normal flow.
Includes: It includes three processes:

1. Enter credentials.
2. Verify credentials.
3. Update user’s table.

Quality This response time of this process should be a second or less.

Requirements

Delete Account

Use Case ID: UC-1.3

Use Case Name: Delete Account

Actors: User (Primary Actor)

 System admin (Secondary Actor)
Preconditions: 1. User must have opened the application.

Post conditions: 1. After account creation, new user will be logged in automatically and can use all
features of this application.

Normal Flow:

1. User select delete account option.

2. User enters the id.
3. User clicks on submit button.
4. System validates if user has entered id present in the system.
5. If verification goes well then user is deleted.
Alternative
Flows: 4a. In step 2 of the normal flow, if the user enter id which is not in the system.

[Alternative 1. System will ask user to enter id present in the system.

Flow 1 – Already 2. Process resumes on step 3 of normal flow.
Registered]

Exceptions:
2a. In step 2 of the normal flow, if the user enters id in wrong format

1. Message to user to re-enter id in correct form.

2. User ID credentials in correct format.
3. Process resumes on step 3 of normal flow.
Includes: It includes three processes:

1. Search ID.
2. Confirm the deletion.

Quality This response time of this process should be a second or less.

Requirements

2. Recharge Account
Recharge

Use Case ID: UC-2.1

Use Case Name: Recharge

Actors: User (Primary Actor)

Telecommunication Company (Secondary Actor)
Preconditions: 1. User must be logged in.

Post conditions: 1. After this, the target account will be recharged.

Normal Flow: 1. List of networks is shown

2. User selects the network of number to be recharged.
3. User then enters the phone number.
4. System then validates the phone number by communicating with particular
telecommunication company.
5. System then ask the user to enter amount within the range of 50 – 5000.
6. System then validate the entered amount.
7. User then click on recharge button.
8. System then checks the current balance.
9. System then update the current balance.
10. Then the entered phone number is recharged.
Alternative 5a- If user enters the amount greater than 5000 or less than 50
Flows 1. Prompt the user to enter amount again.
2. Process resumes on step 6 of normal flow.
 [Alternative
Flow 1 – Amount
not in Range]

[Alternative 8a- If system detect that entered amount is not account balance
Flow 2 – 1. Tells user to deposit money or enter amount according to current balance.
Insufficient 2. Process resumes on step 5 of normal flow.
Balance

Exceptions: 4a- If system detects the invalid or unregistered phone number

1. Prompt the user to enter phone number again.
2. Process resumes on step 4 pf normal flow.
5a- If user enters the amount in wrong format
1. Prompt the user to enter amount again.
2. Process resumes on step 6 of normal flow.
Includes: It includes:
1. Check Balance.
2. Update Balance.
3. Validate Phone Number.
4. Update Network Account
Quality This response time of this process should be a second or less.
Requirements

3. Subscription
Subscribe Offer

Use Case ID: UC-3.1

Use Case Name: Subscribe Offer

Actors: User (Primary Actor)

Telecommunication Company (Secondary Actor)
 Preconditions: 1. User must be logged in.

Post conditions: 1. After this, selected offer will be subscribed to the target account.

Normal Flow: 1. List of networks is shown

2. User selects the network of number to be recharged.
3. User then enters the phone number.
4. System then validates the phone number by communicating with particular
telecommunication company.
5. List of offers is shown.
6. User then selects an offer
7. System then checks the current balance.
8. System then update the current balance.
9. Then the offer is subscribed to target phone number.
[Alternative 7a- If system detect that offer price is not in account balance
Flow 1 – 3. Tells user to deposit money or select offer according to current balance.
Insufficient 4. Process resumes on step 5 of normal flow.
Balance

Exceptions: 4a- If system detects the invalid or unregistered phone number

1. Prompt the user to enter phone number again.
2. Process resumes on step 4 pf normal flow.

Includes: It includes:
5. Check Balance.
6. Update Balance.
7. Validate Phone Number.
8. Update Network Account
Quality This response time of this process should be a second or less.
Requirements

4. Transfer Amount
Transfer Amount

Use Case ID: UC-4.1

Use Case Name: Transfer Amount

Actors: User (Primary Actor)

Preconditions: 1. User must be logged in.

Post conditions: 1. After this, given amount will be transferred to given user.
Normal Flow: 1. System asks user to enter id of user to which amount is to be transferred
2. System validates the given user.
3. User then enters amount (Amount must be in range of 1 to 40, 000 per day).
4. System then validates the given amount.
5. System then checks the current balance.
6. System then update the current balance.
7. Then the amount is transferred.
[Alternative 4a- If system detect that offer entered amount is not in account balance
Flow 1 – 1. Tells user to deposit money or select offer according to current balance.
Insufficient 2. Process resumes on step 3 of normal flow.
Balance

Flow 2 – Limit 4a- If system detects that the limit of amount to be transferred is exceeded
Exceed 1. Tells user that money cannot be transferred till next day.
2. Terminates Process.
Exceptions: 2a- If system detects the invalid or unregistered id of user
1. Prompt the user to enter id again.
2. Process resumes on step 2 pf normal flow.

3a- If user enters the amount in wrong format

1. Prompt the user to enter amount again.
2. Process resumes on step 4 of normal flow.

Includes: It includes:
1. Check Balance.
2. Update Balance.
3. Validate User.
4. Get User id.
Quality This response time of this process should be a second or less.
Requirements

5. Transaction
Deposit Money

Use Case ID: UC-5.1

Use Case Name: Deposit Money

Actors: User (Primary Actor)

Franchise Cashier (Secondary Actor)
 Preconditions: 1. User must have registered account.

Post conditions: 1. After this, given amount will be deposited to user’s account.

Normal Flow: 1. User go to franchise and give amount to be deposited to cashier (maximum of
100000)
2. Cashier validate the user
3. Then amount is deposited to user’s account.
Alternative 2a- If the user is not registered
Flows 1. Cashier ask the user to create account first.
2. Process is terminated.
Flow 1 –
Insufficient
Balance

Flow 2 – Limit 1a- If the user give more than 100000 to deposit
Exceed 1. User is asked to deposit allowed amount.
2. User accepts this.
3. Process resumes on step 2 of normal flow.

1b- - If the user give more than 100000 to deposit

1. User is asked to deposit allowed amount.
2. User declines.
3. Process Terminated.

Exceptions:

Includes: It includes:
1. Validate User
Quality
Requirements

Withdraw Money

Use Case ID: UC-5.2

Use Case Name: Withdraw Money

Actors: User (Primary Actor)

 Franchise Cashier (Secondary Actor)
Preconditions: 2. User must have registered account.

Post conditions: 2. After this, amount will be withdrawn from user’s account.

Normal Flow: 4. User go to franchise and tell cashier to withdraw amount (maximum 50000).
5. Cashier validate the user
6. System checks the current balance
7. Then amount is deposited to user’s account.
Alternative 2a- If the user is not registered
Flows 3. Cashier ask the user to create account first.
4. Process is terminated.
Flow 1 –
Insufficient
Balance

Flow 2 – Limit 1a- If the user asks for more than 50000 to withdraw
Exceed 4. User is asked to lower the amount.
5. User accepts this.
6. Process resumes on step 7 of normal flow.

1b- If the user asks for more than 50000 to withdraw

4. User is asked to lower the amount.
5. User declines.
6. Process Terminated.

Exceptions:

Includes: It includes:
1. Validate user.
2. Check Balance.
Quality
Requirements

6. Log Out
Log Out

Use Case ID: UC-6.1

Use Case Name: Log Out

Actors: User (Primary Actor)

Preconditions: 1. User must be logged in

Post conditions: 1. User will be logged out.

Normal Flow: 1. User clicks on log out option.

2. System asks user to confirm logging out.
3. User is logged out.
 Alternative
Flows

Exceptions:

Includes: It includes:
2. Confirm Logging Out.
Quality
Requirements

Save Current User’s Data

Use Case ID: UC-6.2

Use Case Name: Save Current User’s Data

Actors: System Admin (Primary Actor)

Preconditions: 1. User confirms logging out.

Post conditions: 1 Before Logging out, user’s data will be saved.

Normal Flow: 1. User clicks on log out option.

2. System asks user to confirm logging out.
3. System saves user’s data in database before logging out.
4. User is logged out.
Alternative
Flows

Exceptions:

Includes:

Quality
Requirements
 7. Managing System

Add Operator

Use Case ID: UC-7.1

Use Case Name: Add Operator

Actors: System Admin (Primary Actor)

Preconditions:

Post conditions: 1. New operator (Telecommunication Company) will be added to application.

Normal Flow: 1. Admin will add operator name.

2. Now users can avail facilities of new operator.
Alternative
Flows

Exceptions:
 Includes:

Quality
Requirements

Add Offer

Use Case ID: UC-7.2

Use Case Name: Add Offer

Actors: System Admin (Primary Actor)

Preconditions:

Post conditions: 2. New offer of available offers will be added

Normal Flow: 3. Admin will add offer.

4. Now users can subscribe that offer.
Alternative
Flows

Exceptions:

Includes:

Quality
Requirements

Modify Offer

Use Case ID: UC-7.3

Use Case Name: Modify Offer

Actors: System Admin (Primary Actor)

Preconditions:

Post conditions: 1. Selected offer will be modified.

Normal Flow: 1. Admin will select offer.

2. Admin will modify offer (remove or update).
Alternative
 Flows

Exceptions:

Includes:

Quality
Requirements

Record and Save User’s Activity

Use Case ID: UC-7.4

Use Case Name: Record and Save User’s Activity

Actors: System Admin (Primary Actor)

Preconditions: 1. User has performed any activity.

Post conditions: 1. Performed activity will be saved in database.

Normal Flow: 1. User perform any function.

2. Admin will save and keep record of that activity.
Alternative
Flows

Exceptions:

Includes:

Quality
Requirements