MICRO PROJECT

Computer Engineering (CO)

Softwere Testing (ST)

Title of micro project :

Test cases for AMT

Roll.No. Name Branch

3162 Hritik Prajapati CO
3160 Deepak behera CO
3163 Jidnyasa Wagh CO
3164 Shwetang CO

Guide Name: Monal Malge

Plan:A

Title:
Test cases for AMT

1.0. Introduction:

An ATM, which stands for automated teller machine, is a specialized computer that makes it convenient to manage a
bank account holder’s funds. It allows a person to check account balances, withdraw or deposit money, print a
statement of account activities or transactions, and even purchase stamps.

2.0 Aims/Benefits of the micro-project

a) Great help with studies and in making a career choice.

b) Improves academic performance and interest.

c) To Support Self Directed Learning.

d) To help students develop teamwork and problem-solving skills.

e) To enhance the skills to ‘communicate effectively and skillfully at workplace’.

1. Action plan:

Sr.no. Details of activity Planned Start Planned finish Name of

date date responsible team
members
1 Discussion and finalization of hritik prajapati
the project title
2 Preparation of abstracts All
3 Literature review Jidnyasa wagh
4 Collection of data Deepak behera
5 Discussion and outline of Shwetang
content
6 Rough writing of the projects Hritik prajapati
contents
 7 Editing and proof reading of Deepak behera
the contents
8 Final completion of the All
project
9 Seminar presentation, viva- All
vice, assessment and
submission of report

2. Actual Resources Used:

Sr.no. Name of resource Specifications Qty. Remarks

Computer java 1 for 1 student
Open learning sources Internet 1 for 1 student

Plan: B

Title:

Test cases for ATM

Brief descriptionSoftware testing is any activity aimed at evaluating an attribute or capability of a programOr
system and determining that it meets its required results. Although crucial to software Quality and widely
deployed by programmers and testers, software testing still remains an Art, due to limited understanding of the
principles of software. The difficulty in software Testing stems from the complexity of software: we can not
completely test a program with Moderate complexity. Testing is more than just debugging. The purpose of
testing can be Quality assurance, verification and validation, or reliability estimation. Testing can be used As a
generic metric as well. Correctness testing and reliability testing are two major areas of Testing. Software testing
is a trade-off between budget, time and quality

A TEST CASE is a set of conditions or variables under which a tester will determine whether a

System under test satisfies requirements or works correctly.

The process of developing test cases can also help find problems in the requirements or design of

An application.

Test Case Specification :Using test plan as basis, the testing team designs test case specification which then becomes the
Basis for preparing individual test cases.

Following things need to be identified –

(1) The purpose of test.

(2) Items to be tested.
(3) Software and Hardware environment setup.
(4) Input data to be used.
(5) Steps to be executed.
(6) Expected Results.
(7) Actual Results
(8) Relationship of current test with other tests.
 A test case can have the following elements. Note, however, that a test management tool Is normally used by
companies and the format is determined by the tool used.

Test Suite ID The ID of the test suite to which this test case belongs.

Test Case ID The ID of the test case.

Test Case Summar The summary / objective of the test case.

Related Requirement The ID of the requirement this test case relates/traces to.

Prerequisites Any prerequisites or preconditions that must be fulfilled prior to executing the test.

Test Procedure. Step-by-step procedure to execute the test.

Test Data The test data, or links to the test data, that are to be used while conducting the test.

Expected Result The expected result of the test.

Actual Result The actual result of the test; to be filled after executing the test.

Status Pass or Fail. Other statuses can be ‘Not Executed’ if testing is not performed and

‘Blocked’ if testing is blocked.

Remarks Any comments on the test case or test execution.

Created By The name of the author of the test case.

Date of Creation. The date of creation of the test case.

Executed By The name of the person who executed the test.

Date of Execution The date of execution of the test.

Test Environment The environment (Hardware/Software/Network) in which the test was

Test Case For ATM

 Conclusion

ľhis papeí develops a model of AľM fees that captuíes the salient featuíes of the
Austíalian AľM maíket. In paíticulaí, vaíious AľM usage costs, often ignoíed in the
liteíatuíe, aíe explicitly incoípoíated into existing models and the numbeí of banks
modelled is incíeased to thíee fíom the usual two. ľhese contíibutions aíe impoítant foí a
numbeí of íeasons. Fiíst, including AľM usage costs in the model píovides the complexity
íequiíed to undeístand why, despite claims by the industíy that maintaining foíeign fees
was íequiíed to coveí own-bank píocessing costs, foíeign fees have mostly been
eliminated since the 2009 AľM íefoíms. Second, having thíee banks makes the model
moíe íealistic and píovides a mechanism wheíeby inteíchange fee neutíality is
maintained but foíeign and diíect fees no longeí need to move in lock-step with changes in
the inteíchange fee, matching the Austíalian expeíience.

Refeíences
(1) ATM Definition | Bankrate.com
(2) Wikipedia https://en.m.wikipedia.org › wiki Automated teller machine
(3) Technical publications of Software Testing.
(4) Tech-Neo publications of Software Testing.