IEEE 829 Standard: Testing Plan For Online Backstage Management System

The IEEE 829 Standard prescribes a set of documents that cover the various stages of testing,including:
Master Test Plan (MTP): provides an overall test planning and test management document for multiple levels of test
Level Test Plan (LTP): provides for each level of testing, the scope, approach, resources, and schedule of the testing activities. It lists items being tested, the features to be tested, the tasks to be performed, the personnel responsible for each task, and the associated risk(s) need to be identified.

Analysis the details test cases and the expected results as well as test pass criteria.specifies the test data for use in running the test cases identified in the Level Test Design.Commence your assignment task by reading the case study documents for the Online Backstage
Management System. The documents are:
• Software Requirements Specification (SRS)
• Software Architecture Design Document (SADD)
• Administrator documentation
• User documentation 

Main purpose of the test

A test plan is created for the testing the online backstage management system and different testing strategy is used for the preparation of the project test plan. The unit is described and the integration of the system with the different levels is important for testing of the system. A traceability matrix is created for recording the test results. The main purpose of the software testing is to test the functionality of the system and resolve the errors for increasing the efficiency of the system.

The functionality of the system is required to be analyzed and tested for reviewing the test case of the system

1. The prerequisite of the task and the data that exists for the advancement of the undertaking.
2. Analysis of the business prerequisite and the exchange that are required to be fundamentally tried.
3. Strategies and the sorts of testing is required to be chosen for the usage of the testing design
4. A testing plan is required to be set up for the correct working of the testing design and help to build up a quality final result.

The report is set up to go about as a base stage for testing the online backstage administration framework. The principle destinations of the task is to investigate that the project meets the prerequisite of the undertaking and the archive should go about as a rule for the testing group for testing the usefulness of the framework that are installed as a practical module. The test archive likewise assesses the nature of the last form item and diminish the quantity of blunders in the framework.

In this area the diverse degree for the advancement of the online backstage administration framework are examined regarding the in scope and the out extension things.

The fundamental extent of the testing design is that the product is tried in a PC with intel i5 3^rd generation processor and 4 GB Ram. The accompanying tests are done, for example, unit testing, framework incorporation testing, framework testing and lastly acknowledgment testing. For playing out each of the test one week time is taken and along these lines the aggregate testing technique proceeds for 1 month. For proceeding with the test the following areas are tested and are listed below:

• The login approval of the administrator
• Adding or erasing new client for the framework
• Controlling diverse nodes
• Real time update of the profile of the client
• Add or erasure of the nodes

The execution of the product relies upon the equipment and the stage where it runs and along these lines it is out of extent of the undertaking. The group of PCs where the product is focused to run is additionally kept out of degree for testing the product.

The accompanying table is made for appointing roles and duty to the assets associated with testing of the product application "Online Backstage administration System".

a. Test Plan design

There are distinctive sorts of test designs, for example, master test design, testing level particular test design and testing sort particular test design. A project scope is required to be created for including the risk associated with the development of the project and the test is done during the preparation of the test plan. The testing level particular test design is taken after for the readiness of the test report of the online backstage administration framework.

1. Unit Testing-The test is done to check the rationale of the program which is contrasted and the structure of the program and the learning of the testing group. As a client, unit testing is not something you will discover in a last outcome it's a sort of testing performed in the midst of the coding stage. The testing group can just discover that a potential designer that is utilized uses unit testing in the midst of the progression stage to ensure your thing has diminished steady bugs.
2. Integration Testing-The whole framework is considered for testing and the usefulness of the framework is tried by the proposed plan and the detail of the undertaking. The distinctive segments and the modules made for adding usefulness to the online backstage administration framework is required to be coordinated and tried for appropriate working of the entire framework. The framework mix testing is required to be done on different stage with the end goal that the readied application should chip away at all stages.
3. Business necessity-The test is done to check the prerequisite of the client and meet the business necessity and increment the productivity of the online backstage administration framework. The product item created is required to be broke down as indicated by the business necessity and diverse criteria for playing out the test is required to be produced for testing the usefulness of the framework. The experiment is required to be outlined and the aftereffects of the test is required to be checked for following and dealing with the deformities of the last programming item.
4. User acknowledgment testing-The test is required to be performed by a gathering of cordial client and the destinations of this testing is that the client desire is required to be met. It is the last period of the testing and it is performed before propelling the product in the market. The principle focus for playing out the client acknowledgment testing is approval of the conclusion to end stream of the business. The client acknowledgment test condition is isolated from the ordinary test condition and the members of the client acknowledgment testing are the customer and the focused on end clients.

Main objectives of the test

The previously mentioned tests are performed by making an experiment. The experiments are created and appeared in the table underneath:

The test case is defined in the above table and the following table is created for adding the description of the test case and the use case along with the results.

Conclusion

For the making of the test design distinctive advances are required to be taken after, for example, the depiction of the test plan which is additionally separated into portrayal of the test strategy and depiction of the experiment. The subsequent stage is the execution of the testing and putting away the occurrence of the report and make a test log. The last advance is the making of a synopsis test report. The principle objectives of the report are to fulfill necessities that are portrayed in the test design and introduce a quantifiable, reasonable and repeatable testing technique. The different usefulness of the segments of the present variant of the product are assessed and the mistakes happening in the framework are settled for advancement of a quality programming item.

Böhme, M., & Paul, S. (2016). A probabilistic analysis of the efficiency of automated software testing. IEEE Transactions on Software Engineering, 42(4), 345-360.

Considine, C., Crowley, S., Gardner, G., Shannon, C., Kwinn, M. J., Henderson, S. J., & Santamaria, P. (2016, April). Architecting a development and testing plan for the Army's common operating environment: Applying agile systems of systems development to army network acquisition. In Systems Conference (SysCon), 2016 Annual IEEE (pp. 1-6). IEEE.

Hass, A. M. (2014). Guide to advanced software testing. Artech House.

Jorgensen, P. C. (2016). Software testing: a craftsman’s approach. CRC press.

Lewis, W. E. (2016). Software testing and continuous quality improvement. CRC press.

Lewis, W. E. (2016). Software testing and continuous quality improvement. CRC press.

Mathur, A. P. (2013). Foundations of Software Testing, 2/e. Pearson Education India.

opencodez. (2017). 4 steps to create Requirement Traceability Matrix (RTM) - Free Sample to download - opencodez. [online] Available at: https://www.opencodez.com/software-testing/create-requirement-traceability-matrix-rtm-free-sample-download.htm [Accessed 26 Sep. 2017].

Schultz, J. L. (2015). Software Testing Guide to Ensure Effective and Efficient Health Information Technology Testing (Doctoral dissertation, The College of St. Scholastica).

Sharma, C., Sabharwal, S., & Sibal, R. (2014). A survey on software testing techniques using genetic algorithm. arXiv preprint arXiv:1411.1154.

Sharma, C., Sabharwal, S., & Sibal, R. (2014). A survey on software testing techniques using genetic algorithm. arXiv preprint arXiv:1411.1154.

Traceability matrix – Scripting Logic. (2017). Scriptinglogic.com. Retrieved 26 September 2017, from https://scriptinglogic.com/software-testing/manual-testing/traceability-matrix/