OSI Layers: Test Plan Pennywise National Bank System (Research Paper Sample)

Instructions:

Application: Test Planning
You must organize software testing carefully. Ideally, a team other than the development team should do the testing to avoid making incorrect assumptions when translating requirements into design and code. The team that does the testing may or may not be aware of the specifics of your code. This should not affect their approach to testing. Your test plan should be the starting point for the testing phase and will be your main guide through this phase. It needs to include the features that will be tested, what features will not be tested, the roles and responsibilities of those involved in testing, details of the risks to development, specifics of the testing strategies and during which phases they will be applied, the tools to be used during testing, a schedule for testing, and a clear communication plan for test status and results.
For this Assignment, refer to the Pennywise National Bank system application from Unit 3. Write a test plan that corresponds with the Requirements Analysis document, UML Class Diagram and Design Pattern you developed. Create a 3 page test plan that includes the following sections:
Scope: Clearly defines what is “In Scope” (what will be tested) and what is “Out of Scope” (what will not be tested)
Roles and Responsibilities: Determines the tasks to be performed by the key stakeholders during testing
Testing Methodology: Defines what types of tests will be performed and during which phases they will be performed
Test Deliverables: What documents and materials will be generated during testing and the stakeholders to whom they will be provided
Resource Requirements: Lists the tools, services, and materials required to be in place for testing
Test Estimation and Schedule: Provides estimated dates for testing in each phase along with an estimate of when testing will be completed
Exit Criteria: A set of criteria that must be met to determine when to end testing
Communication Plan: Lists who will provide communication to stakeholders, the stakeholders to be informed, and the information to be included in the communications

source..

Content:

Test Plan - Pennywise National Bank System ApplicationAuthor’s Name:University Name:Course:Date:Test planScope The modules that will be tested during the testing operation include user interfaces, accounts authentication and databases. Additionally, the feasibility of each and every requirement will be tested so as to ascertain that the entire software development procedure and end product are in compliance with legal, technical and operational constraints among others feasibility tests. The network security won’t be tested notwithstanding its constituent essentiality in determining the perfection as well as effectiveness with which the final software deliverable will operate when integrated with other legacy systems in the organization’s network. Roles and responsibilities In the requirements elicitation and system analysis stages of the SDLC (Software Development Life Cycle), the system analysts will be held responsible for undertaking all the feasibility tests. This will include determining whether the application’s requirements conform to Pennywise Bank’s policies or not. In fact, the software will be gauged on its compliance with preset legal rules and laws which govern software development. Also, they will engage in assessing the validity of the anticipated software operations. Herein, the operations will be evaluated on the criterion of whether the problem in question will be sufficiently solved by the end deliverables or not. The system analysts will be granted the responsibility of alienating irrelevant requirements if their corresponding operations aren’t operationally feasible. Another role for this stakeholders will be conducting technical feasibility tests. This will involve deducing whether all the resources and technologies needed to develop the software are available or not. System analysts and requirements analysts will be accountable for ensuring that the software’s operations are socially feasible. This is concerned with examining the requirements and ascertaining that the SDLC’s end deliverables are acceptable by the society or end users. Finally, these stakeholders will be responsible for carrying out a cost-benefit analysis which verifies whether the software will bring forth more benefits to the organization than the cost utilized to develop it. The role of system designers will be to confirm that all the requirements specified in the requirements and system analysis documentations are well stated and transformed to implementable functionalities. Also, they will engage in testing whether the system’s physical designs for the user interfaces and database schemas encapsulate all of the end-users’ needs. This is done immediately after the system design phase. Programmers’ responsibilities include testing the executable code so as to ensure that it executes correctly without any bugs or errors and ensuring that all the requirements are satisfactorily met by the system. The testing will also focus on ensuring that the components of the graphical user interface are well displayed, easily readable and navigable without visual obstructions. The data structures will be tested to ensure that proper and error-free data entry is achieved. In fact, the security team will be given the role of testing the user authentication process so as to ensure that user’s private information such as passwords, and usernames is protected. Also, the team will verify the software’s databases to optimize security of information associated with user transactions such as cash deposits, changing pin numbers and funds withdrawals. This will be done within the implementation and integration stages of development. Testing methodologyThe types of test that will be conducted include the unit testing which will be concerned with testing specific units or modules of the software to ascertain that each gives the proper output for certain inputs. It will be done during the implementation phase of the SDLC. Additionally, feasibility test will be conducted in the requirements analysis and system analysis phases of development so as to ascertain whether all the requirements are implementable or not. In the design phase, usability testing will be conducted. This will check the user-friendliness level of the graphical user interface to ensure that users can easily know how to use or navigate the websites in order to access all its features without major hitches CITATION Reh12 \l 1033 (Zafar, 2012). Integration testing will also be done. It will be focused on checking whether different units or components of the software combine and cooperate/interact well with each other or not. Also, the software’s interaction with the availed hardware will be tested under this particular test. Integration testing will be conducted during and after the implementation phase of development. Acceptance testing will also be done to ensure that the end deliverables are deemed fit and of excellent quality to meet all the user requirements. Test deliverables...

Get the Whole Paper!

Not exactly what you need?

Do you need a custom essay? Order right now:

Order

OSI Layers: Test Plan Pennywise National Bank System (Research Paper Sample)

Other Topics: