Ashworth College ATM Requirements Traceability Matrix Excel Task

ATM/Debit Card Requirements:1. Verification of the ‘ATM Card Insertion Slot’ is as per the specification
2. Verification of the ATM machine accepts card and PIN details
3. Verification of the error message by inserting a card incorrectly
4. Verification of the error message by inserting an invalid card (Expired Card)
5. Verification of the error message by entering an incorrect PIN
6. Verification of that the user is asked to enter the PIN after inserting a valid
ATM Card
7. Verification of that PIN is encrypted
8. Verification of that there is an action like blocking of card occurs when the
total no. of incorrect PIN attempts get surpassed
9. Verification of the user is allowed to do only one cash withdrawal
transaction per PIN request
10. Verification of the machine logs out of the user session immediately after
successful withdrawal
11. Verification of the message when there is no money in the ATM
12. Verification of the language selection functionality
a13. Verification of the cash withdrawal functionality by entering some valid
amount
14. Verification of the cash withdrawal functionality by entering an amount less
than 100
15. Verification of the cash withdrawal functionality by entering an amount
greater than the total available balance in the account.
16. Verification of the cash withdrawal functionality by entering an amount
greater than per day limit
17. Verification of the user is allowed to enter the amount again in case the
amount entered is not valid. A proper message should be displayed.
18. Verification of the ATM machine successfully takes out the money.
19. Verification of the ATM machine takes out the balance printout after the
withdrawal
20. Verification of the font of the text displayed in ATM screen
21. Verification of the text on the screen buttons visible clearly.
22. Verification of the functionality of all the buttons on the keypad
23. Verification of the text on the buttons visible clearly.
24. Verification of that touch of the ATM screen is smooth and operational
25. Verification of the user is allowed to choose different account types like
Savings, Current etc.,
26. Verification of the different combinations of operation and check if there
will be an electricity loss in the middle of the operation. If there is an electricity
loss in the middle of the transaction then the transaction should be marked as
null and the amount shouldn’t be disclosed to others.
27. Verification of the functionality of the cash dispenser
28. Verification of the functionality of the receipt printer
29. Verification of whether the printed data is correct or not in the receipt
30. Verification of how much time the system takes to log out.
ATM/Debit Card Requirements:
1. Verification of the ‘ATM Card Insertion Slot’ is as per the specification
2. Verification of the ATM machine accepts card and PIN details
3. Verification of the error message by inserting a card incorrectly
4. Verification of the error message by inserting an invalid card (Expired Card)
5. Verification of the error message by entering an incorrect PIN
6. Verification of that the user is asked to enter the PIN after inserting a valid
ATM Card
7. Verification of that PIN is encrypted
8. Verification of that there is an action like blocking of card occurs when the
total no. of incorrect PIN attempts get surpassed
9. Verification of the user is allowed to do only one cash withdrawal
transaction per PIN request
10. Verification of the machine logs out of the user session immediately after
successful withdrawal
11. Verification of the message when there is no money in the ATM
12. Verification of the language selection functionality
a13. Verification of the cash withdrawal functionality by entering some valid
amount
14. Verification of the cash withdrawal functionality by entering an amount less
than 100
15. Verification of the cash withdrawal functionality by entering an amount
greater than the total available balance in the account.
16. Verification of the cash withdrawal functionality by entering an amount
greater than per day limit
17. Verification of the user is allowed to enter the amount again in case the
amount entered is not valid. A proper message should be displayed.
18. Verification of the ATM machine successfully takes out the money.
19. Verification of the ATM machine takes out the balance printout after the
withdrawal
20. Verification of the font of the text displayed in ATM screen
21. Verification of the text on the screen buttons visible clearly.
22. Verification of the functionality of all the buttons on the keypad
23. Verification of the text on the buttons visible clearly.
24. Verification of that touch of the ATM screen is smooth and operational
25. Verification of the user is allowed to choose different account types like
Savings, Current etc.,
26. Verification of the different combinations of operation and check if there
will be an electricity loss in the middle of the operation. If there is an electricity
loss in the middle of the transaction then the transaction should be marked as
null and the amount shouldn’t be disclosed to others.
27. Verification of the functionality of the cash dispenser
28. Verification of the functionality of the receipt printer
29. Verification of whether the printed data is correct or not in the receipt
30. Verification of how much time the system takes to log out.
Business requirement document:
This is a site that aims at computerizing the loan system for XYZ bank. The following are the business targets that are to be ac
1. Loan process
2. Ease of use
3. Integration with the bank users list
Business requirement document:
This is a site that aims at computerizing the loan system for XYZ bank. The following are the business targets that are to be achieved via t
1. Loan process
The loan system must cater to both the existing and new users. For new users it should provide a way to apply
for loan.
The existing users should be able to access the loan information. The banker should be notified of the changes or
2. Ease of use
All the information should be easy to access. If the banker needs to make administrative changes, they should be
able to
3. Integration with the bank users list
The loan customers and the other bank customers list has to be merged but the identification of the loan
customers
are to be achieved via this:
Functional Specification Document: (FSD)
1 Loan Process
1.1 New users
1.2 Existing users
2. Ease of use
2.1 All the information should be accessible in less than 3 clicks for a user.
Functional Specification Document: (FSD)
1 Loan Process
1.1 New users
The new users can access the bank URL and when they click on the “Apply Loan” button they are going to be
displayed a
The new user needs to provide first name, last name, address, DOB, SSN and email address mandatorily.
The user can register or continue as a guest before entering the loan specific information.
If the user chooses to continue as guest, there will not be a prompt for password selection.
If the user chooses to register the user will be asked to choose a password.
1.2 Existing users
The existing users can be the ones who have applied for a loan and are waiting on confirmation or the ones that
already have the loan granted.
The users who are waiting will be displayed the information on in which stage the loan is at.
The loan as soon as being applied is in the stage of “Sent for review”.
2. Ease of use
2.1 All the information should be accessible in less than 3 clicks for a user.
Test scenario ID
TS_Loan_001
TS_Loan_002
TS_Loan_003
TS_Loan_004
TS_Loan_005
TS_Loan_006
TS_Loan_007
TS_Loan_008
TS_Loan_009
TS_Loan_010
TS_Loan_011
Test Objective/Test scenarios
Validate the “Apply Loan” feature as a new user
validate the “Apply Loan” feature as a already existing user
For a new user in the “Apply loan”, check the guest customer option and apply loan
For a new user in the “Apply loan”, check the Register option and apply loan
Login to the loan portal as an already a customer with a loan and check the information displayed
Check the Loan whose status is “Sent for review”
Check the Loan whose status is “Reviewed and approved”
Check the Loan whose status is “Reviewed and deleted”
Check for a visitor if the information on the site is accessible in less than 3 clicks or not
Check for a reigstered user if the information on the site is accessible in less than 3 clicks or not
Check for a banker if the information on the site is accessible in less than 3 clicks or not
BRD- Section
1- Loan Process
FSD- Section
1.1- New users
1.2- Existing users
2- Ease of use
2.1- Ease os use
Sample Requirements Traceability Matrix
Test scenario ID
TS_Loan_001- Validate the “Apply Loan” feature as a new user
TS_Loan_002- validate the “Apply Loan” feature as a already existing user
TS_Loan_003- For a new user in the “Apply loan”, check the guest customer option and
apply loan
TS_Loan_004 – For a new user in the “Apply loan”, check the Register option and apply
loan
TS_Loan_005- Login to the loan portal as an already a customer with a loan and check
the information displayed
TS_Loan_006-Check the Loan whose status is “Sent for review”
TS_Loan_007-Check the Loan whose status is “Reviewed and Accepted”
TS_Loan_008-Check the Loan whose status is “Reviewed and deleted”
TS_Loan_009-Check for a visitor if the information on the site is accessible in less than
3 clicks or not
TS_Loan_010-Check for a registered user if the information on the site is accessible in
less than 3 clicks or not
TS_Loan_011-Check for a banker if the information on the site is accessible in less than
3 clicks or not
Test case ID
TC_newuser_01
TC_newuser_02
TC_newuser_03
TC_newuser_04
TC_newuser_05
TC_newuser_06
TC_newuser_07
TC_newuser_08
TC_newuser_09
TC_Exist_User_01
TC_Exist_User_02
TC_Exist_User_03
TC_Exist_User_04
TC_EasyUse_01
TC_EasyUse_02
TC_EasyUse_03
Status
Passed
Passed
Failed
Passed
Blocked
Failed
Passed
Passed
Passed
Passed
Passed
Passed
Passed
Passed
Passed
Passed
Defects
Defect_01,
Defect_02
Defect_01
Defect_03
Business requirement document:
This is a site that aims at computerizing the loan system for XYZ bank. The following are the business targets that are to be ac
1. Loan process
2. Ease of use
3. Integration with the bank users list
Business requirement document:
This is a site that aims at computerizing the loan system for XYZ bank. The following are the business targets that are to be achieved via t
1. Loan process
The loan system must cater to both the existing and new users. For new users it should provide a way to apply
for loan.
The existing users should be able to access the loan information. The banker should be notified of the changes or
2. Ease of use
All the information should be easy to access. If the banker needs to make administrative changes, they should be
able to
3. Integration with the bank users list
The loan customers and the other bank customers list has to be merged but the identification of the loan
customers
are to be achieved via this:
Functional Specification Document: (FSD)
1 Loan Process
1.1 New users
1.2 Existing users
2. Ease of use
2.1 All the information should be accessible in less than 3 clicks for a user.
Functional Specification Document: (FSD)
1 Loan Process
1.1 New users
The new users can access the bank URL and when they click on the “Apply Loan” button they are going to be
displayed a
The new user needs to provide first name, last name, address, DOB, SSN and email address mandatorily.
The user can register or continue as a guest before entering the loan specific information.
If the user chooses to continue as guest, there will not be a prompt for password selection.
If the user chooses to register the user will be asked to choose a password.
1.2 Existing users
The existing users can be the ones who have applied for a loan and are waiting on confirmation or the ones that
already have the loan granted.
The users who are waiting will be displayed the information on in which stage the loan is at.
The loan as soon as being applied is in the stage of “Sent for review”.
2. Ease of use
2.1 All the information should be accessible in less than 3 clicks for a user.
Test scenario ID
TS_Loan_001
TS_Loan_002
TS_Loan_003
TS_Loan_004
TS_Loan_005
TS_Loan_006
TS_Loan_007
TS_Loan_008
TS_Loan_009
TS_Loan_010
TS_Loan_011
Test Objective/Test scenarios
Validate the “Apply Loan” feature as a new user
validate the “Apply Loan” feature as a already existing user
For a new user in the “Apply loan”, check the guest customer option and apply loan
For a new user in the “Apply loan”, check the Register option and apply loan
Login to the loan portal as an already a customer with a loan and check the information displayed
Check the Loan whose status is “Sent for review”
Check the Loan whose status is “Reviewed and approved”
Check the Loan whose status is “Reviewed and deleted”
Check for a visitor if the information on the site is accessible in less than 3 clicks or not
Check for a reigstered user if the information on the site is accessible in less than 3 clicks or not
Check for a banker if the information on the site is accessible in less than 3 clicks or not
BRD- Section
1- Loan Process
FSD- Section
1.1- New users
1.2- Existing users
2- Ease of use
2.1- Ease os use
Sample Requirements Traceability Matrix
Test scenario ID
TS_Loan_001- Validate the “Apply Loan” feature as a new user
TS_Loan_002- validate the “Apply Loan” feature as a already existing user
TS_Loan_003- For a new user in the “Apply loan”, check the guest customer option and
apply loan
TS_Loan_004 – For a new user in the “Apply loan”, check the Register option and apply
loan
TS_Loan_005- Login to the loan portal as an already a customer with a loan and check
the information displayed
TS_Loan_006-Check the Loan whose status is “Sent for review”
TS_Loan_007-Check the Loan whose status is “Reviewed and Accepted”
TS_Loan_008-Check the Loan whose status is “Reviewed and deleted”
TS_Loan_009-Check for a visitor if the information on the site is accessible in less than
3 clicks or not
TS_Loan_010-Check for a registered user if the information on the site is accessible in
less than 3 clicks or not
TS_Loan_011-Check for a banker if the information on the site is accessible in less than
3 clicks or not
Test case ID
TC_newuser_01
TC_newuser_02
TC_newuser_03
TC_newuser_04
TC_newuser_05
TC_newuser_06
TC_newuser_07
TC_newuser_08
TC_newuser_09
TC_Exist_User_01
TC_Exist_User_02
TC_Exist_User_03
TC_Exist_User_04
TC_EasyUse_01
TC_EasyUse_02
TC_EasyUse_03
Status
Passed
Passed
Failed
Passed
Blocked
Failed
Passed
Passed
Passed
Passed
Passed
Passed
Passed
Passed
Passed
Passed
Defects
Defect_01,
Defect_02
Defect_01
Defect_03
FAROOQ SYED RTM WORK SHEET
BRD – SECTION
REQ-ID
REQ-1
3.1.1
REQ-2
FSD-SECTION
FAROOQ SYED RTM WORK SHEET
TEST SCENARIO ID
TEST CASE ID
REQ-1 – VERIFICATION OF A ERROR MESSAGES BY ENTERING THE INCORRECT PIN.
TS-1 – WHEN ENTERING THE INCORRECT PIN.
EXPECTED
RESULT: YES, AN ERROR MESSAGE POPPED UP “YOU ENTERED AN INCORRECT PIN PLEASE
ENTER PIN.”.
TC_01
TS-1.2: WHEN WE ENTERING THE CORRECT PIN.
EXPECTED
RESULT: YES, IT PROCEEDED FOR FURTHER TRANSACTION AND ALLOWED USERS TO
ACCESS THEIR ACCOUNT.
TC_02
TS-1.3: WHEN WE SKIP TO ENTER THE PIN.
EXPECTED
RESULT: MACHINE SHOULD NOT ALLOW USER TO ACCESS THE ACCOUNT BY SKIPPING
THE PIN BUT HERE MACHINE IS ALLOWING USER TO PROCEED FOR FURTHER
TRANSACTION AND ACCESS THEIR ACCOUNT.
TC_03
REQ-2: VERIFICATION OF THE ERROR MESSAGE BY INSERTING A CARD IN CORRECTLY.
TS-2.1: WHEN INSERTING A CARD IN CORRECTLY.
EXPECTED
RESULT: AN ERROR MESSAGE SHOULD POP UP ” PLEASE ENTER THE CARD CORRECTLY,
BUT HERE AN ERROR MESSAGE IS NOT POPPING UP.
TS-2.2: WHEN INSERTING A CARD CORRECTLY.
EXPECTED RESULT: MACHINE SHOULD ACCEPT THE CARD AND ALLOW USERS TO ACCES
THEIR ACCOUNT. (TESTING IN PROGRESS).
TC_04
TC_05
STATUS
DEFECTS
PASSED
PASSED
FAILED
DEFECT_01
FAILED
DEFECT_02
IN PROGRESS