ARU's Bookstore Black Box Test Plan - Assignment Example

Task 01 Year Iota Eta Mu 0 -4000000 -1700000 -1200000 6000 1300000 0 2 260000 980000 400000 3 920000 600000 900000 4 1700000 100000 1000000 5 3700000 50000 700000 Net profit 2586000 1330000 1800000 Pay back 5 3 3 ROI % 12.93 15.6470588 30 NPV 370,072 841,872 924,420 IRR 12% 39% 30% The above table shows that the project Eta setup cost which it is 1700000 is more than the two others projects. We have the setup cost for Iota 4000000 and for Mu 1200000, according to the payback period we have for project Iota 5 years, for project Eta 3 years and for project Mu 3 years so the projects Eta and Mu have less payback period than the project Iota. Till now we have for project Mu less setup cost and good payback period ( setup cost 1200000 and 3 years payback). The net profit for project Iota is more than the two others which is 2586000 but according to payback the payback for this project is less than the two other projects. But after the calculation for net present value we have for project Mu 924,420, for project Eta 841,872 and for project Iota 370,072. To sum up due to above calculation project Mu is the recommended project because it has got less setup cost which is 1200000 and better payback period than the others which is 3 years and the net present value is much better than the other two project which is 924420 and project Iota has the high setup cost and late payback period and with low net present value. Task 2 The start date for project Kappa is 02/01/07 and according to network diagram the estimate duration is 16 weeks and the finish day for the project will be Monday 23/04/07. Task name Duration Start Finish Predecessors A Analyse Module1 6 weeks 2-1-07 10-2-07 B Analyse module 2 4 weeks 2-1-07 29-1-07 C Analyse module 3 5 weeks 2-1-07 5-2-07 D Implement module 3 3 weeks 6-2-07 26-2-07 C E Implement module 2 2 weeks 30-1-07 12-2-07 B F Implement module 1 8 weeks 11-2-07 7-4-07 A G Test Module 2 2 weeks 13-2-07 26-2-07 E H Test Module 3 3 weeks 27-2-07 19-3-07 D I Integrate modules 2 &3 3 weeks 20-3-07 9-4-07 G, H J Integrate modules 1 &3 2 weeks 8-4-07 21-4-07 A, F K Document module 1 1 week 22-4-07 28-4-07 J L System test 2 weeks 29-4-07 12-5-07 I, K Task 2 part 2 Due to underestimating the task A and task F the project would be finish later than the above estimated time which was 23/04/07. After the rescheduling the new finish day for the project Kappa would be on Monday 12/05/07 which would be 18 weeks When the plan of a project will rescheduling it would directly affect the cost and benefits of the project because the project would be finish later than the estimated time and it needs more work to do on it than the original plan so the main cost which is programmer cost will directly affect the benefit. According to I chart the project completes on 23-4-07 and by the new schedule the project will end on 9-5-07 This results in more than 2 weeks of delay and the marketing strategies also needed to be changed. The deadline mentioned to the customers about the supply of software need to be changed or the time duration between the completion of the project and the delivery of the product to the customer need to be decreased. If the cost based changes are concerned, the company has to pay for the programming and development costs for a period of 2 weeks more. This increases the expenditure on the product by 12.5 percent. The cost effectiveness of the product also decreases by that extent. If the company want to market it at the same price decided before rescheduling, there is a need of supplying for more customers initially as the supply to more number of customers will increaser profitability on same cost price. The increase of time in the production can be tolerated as no release of competitor's products is sited. This gives the company time to make the product bug free and to increase the functional performance. Due to increase in the production time, the marketing manager may object due to the delay in release of the product into the market. They can be addressed and the company can convince him giving him a product that is free of bugs. One of the concerns that can be considered in the coming tasks due to the increase of production time is the cost effectiveness. There is a chance of objection that can be from the finance manager. As the increase of production time ensures the application's functional performance, he can be convinced by the proposal to increase the price of the product. As this is the product that is available on networking, the increase of price for offering the services will be very little as the increase of the price can be shared on all the products offered by this application network. In the functions of the test it is observed that the cost of the books vary from 0.01 to 99.99. As the products are books the increase of the price of the product can be supported by the brand name of the firm. Task 3 ARU's bookstore black box test plan The test outlines the test for the bookstore part of ARU website. (HTML/XML data file) 1. Test objects ARU's bookstore's HTML file ARU's bookstore's XML data file 2. Features and Functions to be Tested Test No. Priority Description 01 Low The Web page is understandable 02 Low Ha user friendly colour 03 High The Web Page is compatible with major web browser. 04 High Books details are correct 05 High Books price are up to date 06 High The ISBN match the books 07 High The book must have a title 08 High The book must have at least 1 author and no more than 5 09 High The book must have a price of at least 0.01 but no more 99.99 10 High The book will have an image associated with it but the image is not used in this application 11 High The webpage is easy to navigate 12 High The webpage has security 13 High The webpage has the required document 14 High It easy to use 15 High Performance High Loading fast Part B) The above black box test plan covered tests for missing or incorrect function and the errors it might have but with white box test we can ensure that all modules works fine by testing the entire path inside them and their logical decision. This is because the white box strategy code deals with the internal logical structure of the code. This testing is necessary because the product needs the coverage of written code, branches, paths, statements and internal logic of the code. The coding logic, internal working of the code need to be tested. The unit, statement and the chunk manufactured can be tested. In white box testing the internal coding structure is prerequisite. The input data needed to be given should be selected according to the priority observed in the black box testing. The white box testing will optimise the code and can help in deleting the extra lines of code if present in hidden form. The disadvantages are the person who performs need the knowledge of code and internal structure. A skilled tester who charged at par with the programmer has been appointed to conduct the white box testing. . This increases the project cost and affects the cost effectiveness negatively. The absence of skilled person for the white box testing may result in errors, problems and even the failure of the application. The test that is carried out by developer checks the particular module for the fineness in the working. The capacity, the working speed, clarity and user friendliness need to be tested using white box method. The unit test will be done at the basic level and for a particular functionality of the module. The functionality test will reveal the merits and de merits of the product. In this test both static and dynamic analysis are tested. The testing did not find and possible defect in the code. The execution of the code and analysis of the output were also tested and found to be error free. Every statement of the application execution was tested. This assured that the statements can be executed without any side effects on the system. For this purpose, the execution of the statement for at least once was tested. As the software application cannot be written in the continuous mode of coding, the need of branch out the code has arisen. This performed the particular functionalities and the context of the branching. This testing about the branch coverage helped the validating of the branches in the code and made sure that the branching of the code did not lead to the abnormal behaviour of the software. The abnormal behaviour also is capable of affecting the performance and the speed of the application. The sophisticated testing techniques used in the testing of the application assured that the application is bug free. One more testing that made the application bug free is mutation testing. This was done after fixing the particular bug defect. As a result the mutation test ensured that the bug defect was removed and the fixing has been perfect. The test helped in finding out the code and the strategy of the coding and developed the functionality effectively. The functional testing that is involved in both black and white box testing dealt with the code in order to check the functional performance of the system. This integrated the increments of the application and enhanced the performance. The newly added codes to the application were embedded into the older ones and this resulted in higher performance of the application. The performance load testing did not find any errors and the particular code that is responsible for that managed resources and performed well. 1 Recommendation: The recommendation in this case is that the black box and white box testing are necessary to ensure the functionality. Though the white box testing is more costly than the black box, this is the one that ensures the qualities expressed in black box to be true when it delivers on real grounds. The black box testing has been done on the experimental grounds and there is no testing done on the codes and the statements in the program of the application. The white box testing done on the application ensures the enhanced functional performance. In the course of increase of functional performance, there is a chance of eliminating ignored bugs in the program. At the end of recommendation of this task, it is advised to conduct the white box testing with a specialist so that the testing can increase functional performance. For this the skilled person should be aware of the programming along with the testing tools. Task 4 The main problem in ARU case study is that the product hasn't got enough specification and if they decide to reach the main goal which is a product with the required specification (bug free product) and in the estimated time would be impossible. The products have bug on them and the project manager to be able to solve that problem should extend the deadline for the project which needs more cost which are the costs of staff (programmer, tester, etc) and also equipment and also there is no guarantee that they would be able to make a bug free product. The above process would take time (making bug free product) and the project manager should see if he extend the project time and make a bug free product, the ready product would be successful in the market in the time it would arrive or not because there is lots of product which are designed for specific time ( for example if program designed to work with windows XP and it became ready when everybody using windows vista that product wouldn't have the benefit which it might have at its actual deadline). In this case finance manager main consideration is to not spend more money to make the product better and without bug because it would directly affect the benefits. If they send the product as it is they would save the extra cost that they wanted to spend to make the product better. And in this case the product would be in market on time and they would be able later on to offer the customers with patches and updated for the product. The marketing manager's concern is due to the delay in the release of the product in the market and the concerns about the bugs in the product. This concern was before the black box testing and the application resulted in exhibiting the bugs. After the black box testing the performance was tested and after that the marketing manger did not test the product and he did not know about the bug free capacity of the application. If the marketing manager is not convinced with the quality of the product and if he emphasises on the timely release of the product, it can be done as follows. Task name Duration Start Finish Predecessors A Analyse Module1 3 weeks By doubling the personnel as this requires no predecessor 2-1-07 22-1-07 B Analyse module 2 4 weeks 2-1-07 29-1-07 C Analyse module 3 5 weeks 2-1-07 5-2-07 D Implement module 3 3 weeks 2-1-07 26-2-07 C E Implement module 2 2 weeks 30-1-07 12-2-07 B F Implement module 1 4 weeks This also can be done by doubling the personnel as this requires a predecessor A that also requires the doubling of personnel 23-1-07 9-2-07 A G Test Module 2 2 weeks 13-2-07 26-2-07 E H Test Module 3 3 weeks 27-2-07 19-3-07 D I Integrate modules 2 &3 3 weeks 20-3-07 19-4-07 G, H J Integrate modules 1 &3 2 weeks 9-2-07 22-2-07 A, F K Document module 1 1 week 23-2-07 1-3-07 J L System test 2 weeks 2-3-07 15-3-07 I, K This changes in timings of the production of the application by increasing the personnel can address the concerns of the marketing manager to release the product in time. Along with black box test, the white box was also implemented and this delayed the process of release of the product into the market. One of the concerns of the marketing manager; the bugs in the application has been solved after conducting the black and white box testing. The main concern of the finance manager is the increase of the cost due to the delay of the release of the product into the market. This increased the expenditure and decreased cost effective ness. The timely release of the product has been disturbed. This resulted in finance manager to object for the extra cost that will be incurred to make the product bug free. As in the task 2 and 3 the enhancement of production time and the white box testing has been done, one of the objections of the finance manager has been removed. The cost incurred due to increased production time is the main concern of the finance manager. This cost can be considered as a compulsion to make the product bug free. By complying to this the marketing manager's concern about the bugs in the product has been addressed. In conclusion there would be a high risk if the project manager decides to extend the project time that the market in the time the product is ready needs it and also they could make the product bug free. Therefore the finance manager can be convinced by increasing the cost of services offered by the application and the cost of the product. This will balance the decrease of the cost effectiveness. When there is any competitor's product is set to release in time into the market, the extension of the production time can be reduced by increase of the personnel working on the project. As the situation given for the assignment hints at no such product the marketing manager can be convinced. The increase of production time or the increase of personnel to control the increaser of the production time is a concern of the finance manager. This concern of the finance manager can be addressed by making him know about the increase of revenues by increase of costs of services and the sales of products. The increase of costs of the products can be supported by the fact that it will be bug free and the extension increases the functional performance. References 1. Nilesh Parekh, 2005, software testing - white box testing strategy, buzzle.com, http://www.buzzle.com/editorials/4-10-2005-68350.asp Read More