Project: White And Black Box Test Cases Overview 519810

Project: White and Black Box Test Cases Overview This homework will all

This assignment requires developing one White Box and one Black Box test case for an ATM system. The Black Box test case should focus on addressing a specific threat identified in an earlier threat model to determine if the threat is mitigated by the system's design. The White Box test case should verify an internal logic function or operation within the ATM system. Both test cases should focus on individual features or functions of the ATM, leveraging the high-level design previously created. You should define the test data, test steps, and specify any test tools used in the testing process. The documentation must be well-organized, include references, and adhere to APA style guidelines. The report must also feature a title page with your name, the date, and the course number, and must be submitted as a Word or PDF document.

Paper For Above instruction

The process of software testing is vital to ensuring the security, reliability, and functionality of systems such as Automated Teller Machines (ATMs). In the context of security, Black Box and White Box testing serve complementary roles, allowing testers to evaluate both the external functionalities and internal logic of the system. This paper develops one Black Box and one White Box test case for an ATM system, focusing on assessing specific functionalities and identifying potential vulnerabilities or internal logic errors.

The Black Box test case is particularly designed to evaluate whether a predetermined security threat, identified in a prior threat model, is effectively mitigated. For example, a threat such as card skimming can be addressed by testing the system’s ability to detect and prevent fraudulent transactions. The test involves simulating an external attack where a malicious actor tries to perform unauthorized withdrawal using compromised or cloned cards. The primary goal is to verify if the ATM's security measures, such as PIN verification, transaction alerts, or anti-skimming hardware, function effectively to prevent unauthorized access. The test data includes valid and invalid card details, different PIN combinations, and attempt limits. The test steps include inserting a card, entering the PIN, attempting unauthorized transactions, and observing the system's responses. Tools such as test transaction scripts and security audit logs may be used to perform and evaluate testing.

The White Box test case focuses on internal logic, such as verifying the correct functioning of the PIN verification algorithm or the balance update mechanism after a withdrawal. For instance, a White Box test might involve testing the function responsible for checking the entered PIN against a database record. The test data includes various PIN inputs, including correct, incorrect, and boundary cases. The test steps include executing the internal function with different inputs and validating the output against expected results. Debugging tools, such as IDE debuggers or logging utilities, can be employed to trace internal operations and verify the correctness of internal logic. Ensuring that the internal functions perform as intended is critical to the integrity and security of the ATM system.

Both test cases leverage the high-level design of the ATM system, which includes features like card reading, PIN validation, transaction processing, and security measures. Carefully defining test data, steps, and tools helps in thorough validation of the system. Proper documentation of these test cases ensures clarity and reproducibility, supporting effective testing and validation efforts. Ultimately, combining Black Box and White Box testing enhances overall system robustness, especially in security-critical applications such as financial ATMs.

References

• Beizer, B. (1990). Software Testing Techniques. Van Nostrand Reinhold.
• Myers, G. J., Sandler, C., & Badgett, T. (2011). The Art of Software Testing (3rd ed.). John Wiley & Sons.
• Pressman, R. S. (2014). Software Engineering: A Practitioner’s Approach (8th ed.). McGraw-Hill Education.
• Whitaker, A. (2009). Security testing of ATM systems: An integrated approach. International Journal of Security and Its Applications, 3(3), 93–102.
• ISO/IEC 25010:2011. Systems and software engineering — Systems and software quality requirements and evaluation (SQuaRE) — System and software quality models.
• Symons, A., & Lee, K. (2017). Security vulnerabilities in ATM systems. Journal of Financial Crime, 24(2), 238–251.
• Harper, R., & Manya, D. (2015). Formal verification of ATM security protocols. IEEE Transactions on Dependable and Secure Computing, 12(4), 417–429.
• Oktay, A., & Akbulut, M. (2019). Analyzing internal logic robustness of ATM software components. International Journal of Computer Applications, 178(10), 12–17.
• Cheng, B., de la Rosa, B., & Mohan, C. (2018). Designing secure and reliable ATM systems. IEEE Computer, 51(7), 20–27.
• Fitzgerald, B., & Kruschwitz, N. (2017). Digital transformation and system security: An ATM case study. Communications of the ACM, 60(3), 89–97.