Software Testing: Pennywise National Bank - Research Paper Example

Software Testing Software Testing Introduction Software testing involves an investigation carried out to provide the users with information about the products quality. Through its investigation, the business form will be able to appreciate and understand all the risks associated with the software. In general, the tests involve validation of if the software meets the required design, it works as expected and can be implemented owing the same original characteristics besides satisfying the users’ needs. Owing that video game software is different from banking software; each software should be tested towards its target audience. We are dealing with the banking system from Pennywise National Bank. Therefore, experimental design is the best method of testing software (Basili and Selby, 1987). Scope According to Gelperin and Hetzel (1988), we are going to deal with phase models and life cycle models. In the phase models, we have a demonstration and destruction phases. Demonstration ensures that the software satisfies all its specifications. Destruction involves detection of the implemented faults that may lead to errors during the software functioning. In the life cycle models, we have an evaluation and the prevention stages. In the evaluation, one detects requirements, design and implements faults. In prevention, requirements, design and implementation faults are prevented. Review of software requirements is not considered as testing. Prevention testing involves analysis and review besides improvement of the software specifications and design. Moreover, the code is improved before test execution (Gelperin and Hetzel, 1988). We are going to test the coding, structural and functional properties of our software. Code reading will be tested using the stepwise subtraction. The structural testing will be done using 1005 statement coverage criteria. Finally, the functional testing will be done using equivalence partitioning and analysis of the boundary value (Basili and Selby, 1987). Roles and responsibilities The primary goals of testing are; to demonstrate that some parts of the software specifications are functional and meet their tasks, to detect faults and finally to prevent faults. Formerly constructive approach was being used in testing yielding unsatisfactory results in that it contained tests that the software could pass. Currently, the demonstration strategy is being used. Tests always are hypothesized that the software is not perfect in its specifications in that it can not lack even a single fault. A set of test T is built and applied to the software. In the long run, at least a single fault may be identified. However, before the software is fully satisfactory, its degree is estimated as follows; every requirement is tested at least once to determine if the test set satisfies necessary conditions, determination if the test set satisfies the conditions connected to a particular fault and finally insertion of different faults to test if the software can detect them (Burnstein, Suwannasart and Carlson, 1996). Testing Methodology Testing is the most critical component in software development (Burnstein et al., 1996). It is one of the most expensive and challenging stage but its verification yields high quality software. It involves testing of the structural, coding and functional properties of the software. In the test maturity model, the following components will be proposed; first, a set of levels that clearly define the stages of software maturity (Burnstein et al., 1996). Movement from lower to the upper level will mean that lower practices will be in place. Secondly, asset of maturity goals for each level will be set with the exception of level 1. The organization will focus on the goals, activities, tasks and responsibilities that will be needed to be adhered to. Finally, an assessment model is to be set. The model will compose of a mature goal-related question that seeks go assess the test process of maturity. Moreover, there will be a training program for all the evaluation team to conduct the maturity assessment. Finally, there will be an application assessment to the organization to allow it on the basis of the questionnaires and interview data obtained (Burnstein et al., 1996). Four sources are to serve as the principal inputs. They are the Capability Maturity Model (CMM), Gelperin and Hetzel Evolutionary Testing Model, current industrial testing practices and Beziers Progressive Tester’s Mental Model. The CMM is a comprehensive process of evaluation and improvement. The stage has several levels arranged in a hierarchy form. Each level provides a foundation to progression of the next level. All the levels in the CMM have an internal structure with the exception of level 1 which has key areas organized into common features (Burnstein et al., 1996). In the evolutionary stages of testing, the pattern of testing processes is documented over the years. In our case, we re going to apply the Gelperin and Hetzel as the base for level differentiation. In their model, test goals and phases are documented since 1950s to around 1990s. The model involves review activities to support test planning, test design and evaluation f the product. The current industrial practices are very important in that they will help us determine the best and worst environments to test our product. A mature testing organization should have adequate skills, ability and the individual attitudes (Burnstein et al., 1996). The V-model and testing maturity requires widening of the testing activity. During testing, reviews, audits, walk-through and inspections are considered to be part of the product verification and validation. The practices are incorporated in the software life cycle. On completion of coding, execution-based activities such as unit and integration, reviews and audits of the actual test plan should be performed before actual execution (Burnstein et al., 1996). Test Deliverables Our software is to be applied in the banking system. Therefore, during our test, we are going to perform some banking activities with consideration of security purposes. All banking services will be performed in testing of our product. Since the software will nit have been fully approved and then virtual information or automation system may be used. The software’s efficiency in results production will gauge its efficiency (Burnstein et al., 1996). Resource requirements The assessment model will require the following resources. A questionnaire that will contain questions designed to test the level of testing maturity. The questions should relate to the goals and processes at each level. Second will be an assessment procedure that will give the assessment team guidelines on whom to be interviewed and where to get the data from. Moreover, guidelines on how to organize analyze and interpret it. A reporting mechanism will guide on how the results and the recommendations form the test process can be disseminated with identification of high priorities. The team selection and training procedure is always carried out by a trained assessment team on assessment. The program contains instructions on the interviewing techniques, internal structure of the levels AND an in-depth of the assessment procedure. Hardware to be used will also be tested for compatibility. The framework of the levels will involve a framework of goals, sub goals, tasks and responsibilities (Burnstein et al., 1996). The general requirements of the model development are; the model should be acceptable to the software developers, agree with the software engineering principles and practices. It must allow for step-wise phases that follow the natural process evolution. Moreover, there should be a support mechanism the process assessment and improvement (Burnstein et al., 1996). Test estimation and schedule The TMM framework will, therefore, have to follow the following levels. Level 1 which is termed as the initial stage or the debugging oriented period. Level 2 also known as the phase definition has demonstration and destruction-oriented. Level 3 contains the integration stage. Levels 4 and 5 reflect and shows the trends and practices discussed in the evaluation oriented duration (Burnstein et al., 1996). Exit criteria Once the faults in the software are fully detected, then the testing can be terminated. Moreover, if errors are detected at an early stage, then new software needs to be designed. Provided that the coding is corrects besides the functional and structural features, then the little faults in the security among others can be rectified before the software is released for use (Burnstein et al., 1996). Communication plan Once the experts are through with the testing, through their consultant leader they will forward their results to the customer who is the bank manager. The manager and his team may have a visit to the consultant firm for elaboration of the obtained results. The message in the report will either to quit the software and design a new one if several faults are noted, its modification or approval of the software for usage (Burnstein et al., 1996). References Basili, V. and Selby, R. (1987). Comparing the Effectiveness of Software Testing Strategies. IEEE Transactions on software engineering, 13 (12), 1278-1298 Burnstein, I., Suwannasart, T. and Carlson C. (1996). Developing a testing maturity model: part 1. New York: Cross Talk Publication. Gelperin, D and Hetzel, B. 1988. The Growth of Software Testing. Communications of the ACM, 31 (6), pp. 687-694. Read More