Project 2 Quarter 8 ATM SYSTEM

Huỳnh Thủy Ngân NIIT Cần Thơ PROJECT ON ATM SYSTEM Developed by Name: Huỳnh Thủy Ngân ATM System Page 1 Huỳnh Thủy Ngân NIIT Cần Thơ ATM SYSTEM Batch Code : B120011 Start Date : 8 th Jun 2012 End Date : 18 th Jun 2012 Name of the Coordinator : Phạm Tiến Phúc Name of the Developer : Huỳnh Thủy Ngân Date of Submission : 20 th Jun 2012 ATM System Page 2 Huỳnh Thủy Ngân NIIT Cần Thơ NIIT CERTIFICATE This is to certify that this report, titled ATM System, embodies the original work done by Huỳnh Thủy Ngân in partial of their course requirement at NIIT. Coordinator: Phạm Tiến Phúc ATM System Page 3 Huỳnh Thủy Ngân NIIT Cần Thơ ACKNOWLEDGEMENT We have benefited a lot from the feedback and suggestions given to us by Mr. Phạm Tiến Phúc and other faculty members, and the machine room coordinator. ATM System Page 4 Huỳnh Thủy Ngân NIIT Cần Thơ SYSTEM ANALYSIS System Summary: The ATM system have following features: - Cash withdrawal - Cash deposit - Transaction summary - Changing the PIN - Check deposit - Fund transfer within the same bank On the basic of these features, prepare a white paper for testing the ATM system. The white paper should present the general requirements of an ATM system and discuss the following points: - Test environment that needs to be set up to test an ATM system. - Testing techniques that need to be adopted to test an ATM system. - Testing tools that need to be acquired to test an ATM system. - Risk involved in testing an ATM system - Typical components of a test plan that need to be developed for an ATM system. - Test metrics that need to be gathered while testing an ATM system. One of the best ways to guarantee long term performance is through rigorous, standardized testing at both the component and system levels. Testing systems check whether ATM equipment meets their design specifications, confirm that products from different manufacturers can work together, measure performance against traffic contracts, and provide assurances that the underlying physical resources are operating correctly. ATM System Page 5 Huỳnh Thủy Ngân NIIT Cần Thơ IDEAL TEST ENVIRONMENT FOR ATM SYSTEM FUNCTION TEST ENVIRONMENT Server/device types Machine name Hardware specification Software specification Client application and Database Server MSDNFTEST01 750 MHz 256 MB of RAM, 19-GB HD Intel EtherPro 10/100 NIC * Windows 2000 Advanced Server * Windows 2000 SP1 Server* SQL Server 2000 * SOAP Toolkit End-user machines Various 700 MHZ 64 MB RAM, 10 GB HD * Windows 2000 Professional * Internet Explorer 5.0 or later/Netscape browsers SYSTEM TEST ENVIRONMENT Server/device types Machine name Hardware specification Software specification Web server MSDNIIS01 933 MHz 256 MB of RAM, 70-GB HD Intel EtherPro 10/100 NIC * Windows 2000 Advanced Server Web server MSDNIIS02 933 MHz 256 MB of RAM, 70-GB HD Intel EtherPro 10/100 NIC * Windows 2000 Advanced Server Database server MSDNSQL01 700 MHz 256 of MB RAM, 29-GB HD Intel EtherPro 10/100 NIC * Windows 2000 SP1 Server* SQL Server 2000 * SOAP Toolkit Client application server MSDNCLIENTAP0 1 750 MHz 256 MB of RAM, 19-GB HD Intel EtherPro 10/100 NIC * Windows 2000 Advanced Server End-user machines Various 700 MHZ 64 MB RAM, 10 GB HD * Windows 2000 Professional * Internet Explorer 5.0 or later/Netscape browsers ATM System Page 6 Huỳnh Thủy Ngân NIIT Cần Thơ INDIVIDUAL PROJECT SCHEDULE S. No. Activity Description Time 1 Analyze the given case study to identify the requirements 2 Hrs 2 Research for relevant information. Prepare a rationale for recommendations made in the solution 2 Hrs 3 Prepare the white paper after appropriate study. 2 Hrs 4 Prepare the white paper after appropriate study. Submit the white paper to the faculty. 2 Hrs 5 Present the white paper in class. Answer viva-voice related to the white paper. 2 Hrs ATM System Page 7 Huỳnh Thủy Ngân NIIT Cần Thơ METHODOLOGY APPROACH PROCESS OVERVIEW General Testing Guidelines The steps in this testing plan are to ensure a smooth transition of code from a development environment to its production usage. The general approach in most recommended testing plans have been considered. Combined, all of them emphasize a standard approach to testing with the following steps: usability testing, unit testing, integration testing, function testing, system testing, acceptance testing and regression testing. Testing starts with the developer and the customer verifying (usability testing) the interface early in development. The developer develops the code to support the requirements and exercises it (unit test). After this, the interfaces between modules is tested (integration testing), and then independent testing against requirements (functional) is conducted. Exercising all components in a production like environment (system testing) with final testing by the customer (acceptance testing) completes most of the process. This also takes into consideration the need to retest software in the event of ongoing fixes (regression testing). Early Development of Test Cases Test cases are developed early in the process. To complement the Extreme Programming paradigm, which is discussed below, use cases will be developed early in development. These describe the use of a system by an “actor” and form the basis for both design and test cases. Extreme Programming The most common method of software development is the waterfall method, which specifies a phased approach to software development – including plan, design, code, test, and release cycles. If a project is canceled during coding or earlier, it’s probable that no working code was developed, and the entire project will yield no tangible results. ATM System Page 8 Huỳnh Thủy Ngân NIIT Cần Thơ METHODOLOGY APPROACH PROCESS OVERVIEW XP processes also include pair-up design sessions and code sessions; this ensures all code that is created is viewed by two people. After the software is created, it may be re-factored, and then tested on a single “continuous integration” machine. After copying the code, developers run a full suite of the “test first” unit tests. If the code passes all tests, the developers can check in the code and the unit test. XP unit tests and building are covered in more detail under “unit tests”, below. Essentially, stories allow coders to begin development early, and an on-site customer ensures that the software that is created actually meets the customer’s need. “Getting to the code” early transforms expenses into working software; because of the priorities, it’s possible for the customer to cancel the project at 25% of schedule and actually get working software that fulfils the most important 25% of the business need. Extreme Programming also uses the concept of “Project Velocity” to measure the cost, time, and relative late/early-ness of the project. In addition to a project-level function point analysis, Smart Savings also asked it’s developers to measure the effort involved in creating the software in Extreme Programming units (XPU). By dividing the XPUs by the typical development speed (XPU’s developed per week on previous projects) the team produced a man-month estimate for development of the ATM project; this estimate, along with function points and risk-adjusted estimates, was used to create the $350,00 bid for the ATM Project. (Note: The deviation from “book” XP of working for a fixed price was a concession to the customer made to win the contract. The customer insisted on this concession to minimize uncertainty.) The XP method practiced by Smart Savings Co. feeds directly into the testing phase of the project. Although “book” XP does not include a testing phase, this concept has not exactly been embraced by the business community. As a result, Smart Savings Co. typically includes a testing phase in it’s software projects similar to the testing phase advocated by Donaldson/Siegel in their book Successful Software Development. ATM System Page 9 Huỳnh Thủy Ngân NIIT Cần Thơ METHODOLOGY APPROACH DEFINITIONS Common Terminology Term Definition Acceptance Testing Formalized testing by the customer to determine completion of the product prior to delivery and payment of services. Base Line The version of the source code currently in production. This is sometimes referred to as the “gold” copy of the software currently in production. Black Box Testing Testing software for its basic functionality without specifically exercising known pieces of code. Defect An instance of where the software does not meet the requirement. Function Testing Formalized testing of modules for their functionality based on the requirements document. Glass Box Testing White Box Testing Both terms are a form of testing where internal coding knowledge is used to determine testing. System Testing Formalized testing where the system is exercised under conditions similar to a regular production environment. Integration Testing Testing modules together to ensure the interfaces are compatible and meet requirements. System Testing Formalized testing where the system is exercised under conditions similar to a regular production environment. Test Case A specific set of steps to be followed to exercise a specific aspect of software. The steps include how to setup, how to provide the input and the expected output. Unit Testing Testing performed on a specific module by the developer. Use Case A story about the use of the system XP Extreme programming. ATM System Page 10 [...]... releases is recommended to be the following Processor: Pentium III-650MHZ Operating System: Windows 20 00 – Server Memory: 25 6 MB Hard Drive: At least 2. 5 Gig free on the installation drive Software: Full Net System Development Kit (SDK) Code is to be compile ATM System Page 18 Huỳnh Thủy Ngân NIIT Cần Thơ FUNCTION TEST PLAN ATM System Page 19 Huỳnh Thủy Ngân NIIT Cần Thơ Participants Under the extreme programming... customer Briefly, the eleven testing areas are listed below in priority SYSTEM TEST PLAN ATM System Page 21 Huỳnh Thủy Ngân NIIT Cần Thơ Actual Order Of Testing Summary and Budget Breakout Cycle Category 1 Configuration % Budget 2% 2 Installability 5% 3 Security 5% 4 Compatibility 10% 5 6 Reliability/Availab 18% ility Recovery 15% 7 8 9 Serviceability Load/Stress Volume 10% 10% 10% 10 11 Performance Human... associated with that aspect comes under the CM budget SYSTEM TEST PLAN ATM System Page 20 Huỳnh Thủy Ngân NIIT Cần Thơ Approach General System testing is intended to exercise the system within an environment that resembles a production environment as much as reasonably possible It is impossible to test for all conditions Prioritization As implied above, system testing is a high cost activity Due to that... our configuration management area not being a fully mature area process wise, assumptions about previous builds will not be made in the case of multiple regression tests ATM System Page 28 Huỳnh Thủy Ngân NIIT Cần Thơ PROJECT ON ATM SYSTEM ... customer acknowledges system acceptance in writing During execution of the acceptance test, the customer may document operational procedures and receive additional operational training from the SMART SAVINGS Project Engineers in order to train operational staff before going into production ERROR MANAGEMENT ATM System Page 26 Huỳnh Thủy Ngân NIIT Cần Thơ This section applies only to function, system and acceptance... Aid from Compuware Migration of Code Code moved into system test should be considered production ready from the standpoint of configuration management That is, it should not be recompiled when moved from the function test environment This is an established base line for the MicroSoft Intermediate Language (IL) code SYSTEM TEST PLAN ATM System Page 23 Huỳnh Thủy Ngân NIIT Cần Thơ Estimated Cost/Percentage... Thủy Ngân NIIT Cần Thơ Estimated Cost/Percentage of Budget According to Steve McConnell, Software Project Manager's Survival Guide, 20 % of the development budget is typically spent on Systems Testing Based on this, the total budget for testing against the project budget is estimated at $70,000 Approvals Since system testing is crucial to ensuring a quality product to customer, all managers must review... tester 4 Contracts with the customer, vendors, and contract companies forbids those agencies from recruiting until after the project is complete ATM System Page 12 Huỳnh Thủy Ngân NIIT Cần Thơ RISK ANALYSIS Risk Customer Changes requirements during Development, Unit Test or System Test Code shipped to customer fails to meet quality standards Description: Mitigation: Description: After coding begins,... developer ATM System Page 27 Huỳnh Thủy Ngân NIIT Cần Thơ REGRESSION TESTING General Regression testing is done anytime changes have been made to existing code The goal is to ensure that code that previously worked has not been adversely affected with the change Approach Due to the expense of testing, it is not desired to retest the entire system Instead, existing test cases that reflect areas of the system. .. Part of volume testing is covered under reliability and availability Budgeted according to the priority analysis Human factors should have been heavily scrutinized early in development SYSTEM TEST PLAN ATM System Page 22 Huỳnh Thủy Ngân NIIT Cần Thơ Note On Security Testing It is strongly advised that additional funding should be considered to procure third party support for security testing Testing . Thơ PROJECT ON ATM SYSTEM Developed by Name: Huỳnh Thủy Ngân ATM System Page 1 Huỳnh Thủy Ngân NIIT Cần Thơ ATM SYSTEM Batch Code : B 120 011 Start Date : 8 th Jun 20 12 End Date : 18 th Jun 20 12 Name. ATM system. - Testing tools that need to be acquired to test an ATM system. - Risk involved in testing an ATM system - Typical components of a test plan that need to be developed for an ATM system. -. 20 12 End Date : 18 th Jun 20 12 Name of the Coordinator : Phạm Tiến Phúc Name of the Developer : Huỳnh Thủy Ngân Date of Submission : 20 th Jun 20 12 ATM System Page 2 Huỳnh Thủy Ngân NIIT Cần Thơ NIIT CERTIFICATE This