Software Testing Standards: An In-Depth Analysis of the IEEE Standard

This report provides a comprehensive analysis of the IEEE standard in the context of software testing. It begins with an executive summary outlining the study's objective: to discuss and analyze the IEEE standard, which offers reference approaches for software testing implementation. The report c...Read More

Running head: SOFTWARE TESTING STANDARDS
Software Testing Standards
Name of the student
Name of the University
Author’s Note

1SOFTWARE TESTING STANDARDS
Executive Summary
The main aim of this study is to discuss and analyze the IEEE standard in the context of
software testing. The IEEE standard gives the reference approaches to implement the
software testing. This study discusses about the IEEE standard, copyright holders of the
standards, intent of the standard IEEE. There are some key terms of the IEEE application in
software testing are discussed in this study and relevant result of the application of this
standard. This report concludes that the IEEE standard is the refinement of the traditional
approaches and this will help in the great dealing to build the entirely new era of the testing
of softwares and the system.

2SOFTWARE TESTING STANDARDS
Table of Contents
Introduction................................................................................................................................3
IEEE Standard............................................................................................................................3
Copyright Holders for IEEE.......................................................................................................3
Intent or Scope of IEEE.............................................................................................................4
Key Terms of IEEE for its Application......................................................................................5
Result of the Application...........................................................................................................5
Relevance to Software testing....................................................................................................6
Conclusion..................................................................................................................................7
References..................................................................................................................................8

3SOFTWARE TESTING STANDARDS
Introduction
Various groups and organizations in all around the world set and build up various
standards to improve the user experience and excellence of development of the software. The
testing standards of software are used in the development of software to increase the quality
of the software and the testing of the software of the organization. In this report, IEEE
standard is chosen for software testing and analysis. This study discusses about the IEEE
standard in the context of software testing. IEEE standard identifies the author’s right of the
qualified sponsors to hold the copyright on the behalf of the standard IEEE for testing of
software. The IEEE standard gives the reference approaches to implement the software
testing (Jorgensen, 2013). This study analyses the framework for the software testing to
enable the sharing of the work items.
IEEE Standard
IEEE stands for The Institute of Electrical and Electronics is the global organization
and association of the professionals working toward the implementation, development and
maintenance of the software testing (Pogliano et al., 2013). IEEE is one of the non-profit
organizations that is founded in the year 1963. It works towards standardizing, educating and
innovating software testing development in the industry. The key areas of IEEE of focus are
information technology, computer engineering, electrical, electronics and computer science
and the related disciplines. IEEE is widely known for the development of the standards for
the software programming and its testing.
Copyright Holders for IEEE
The author, who develops the standard related products, has different author
agreements, which addresses the copyright ownership for the developed services and

4SOFTWARE TESTING STANDARDS
products (Laplante, 2017). IEEE holds the copyright of IEEE itself. All professional,
educational and technical publications of the standard IEEE, except the newsletters but it
includes the e-Newsletters, Technical Council Newsletters and Society. These are the holders
of the copyright of IEEE. Prior to the publication by the standard IEEE, the authors or the
employers should transfer to the standard IEEE in the writing. For the individual papers, they
hold the copyright. This transfer is necessary for the publications except the public domain,
which is reprinted from the copyrighted publication. In return, of the transfer of the rights of
the authors, IEEE should grant the authors and the employers for making the copies and reuse
the materials under the terms that are approved by the BOD (Board of Directors). In case of
the conferences, which are jointly sponsored, IEEE recognizes the rights of another qualified
sponsor for holding the copyright and administering all the copyrights on the behalf of IEEE
and the authors (Smith & Kandel, 2018). Between the qualified sponsor and the IEEE
standard, the rights will be the subject of the written agreement. In case of conference, a
sponsor may hold the copyright to the standard of the IEEE. Under the terms that are
approved by PSPB, the permissions and licenses for republishing or copying the IEEE
materials may be granted.
Intent or Scope of IEEE
IEEE defines the consistent and efficient solution for keyword-driven testing. It
introduces the keyword-driven testing. IEEE standard provides a reference approaches for
implementing the keyword-driven software testing. IEEE defines the requirements on the
framework for the software testing for enabling the tester for sharing the work items such as
test specification, keywords, test cases and test data (Zuse, 2013). IEEE defines the tools
requirements, which supports the software testing (Leicht, Blohm & Leimeister, 2017). The
requirements of the tools can be applied to any kind of tool, which will support the keyword-
driven approach such as test management tools, test design and test automation. It defines the

5SOFTWARE TESTING STANDARDS
interfaces and the similar data or information exchange format to make sure that the tools
from different vendors vendors, who can exchange the data such as test data, test cases and
test result. It provides a definition of the level of the hierarchical keywords and it gives
advice of the usages of the hierarchical keywords. This consists of some of the keywords for
checking or navigating the value while using the flat structured keywords. IEEE provides the
initial list of the low level or generic technical keywords such as checkValue or inputData.
These types of keywords are used for specifying the test cases on the technical level and can
be combined for creating the business level keywords as needed.
Key Terms of IEEE for its Application
Softwares are becoming more pervasive in today’s world. It is not limited applications
to run on the mainframes, linked or not linked with the networks, micros or minis. Software
is present in any commercial appliance from cars to fridges and from personal assistant to
telephones. The hardware verification aspects are very essential to the software aspects. The
application of the IEEE standard is reflected in term of usages of the software and the system
and it reflects on the identified component collection or component, which is not restricted to
software (Vanfretti et al., 2013). It comprises with the software bases system. This analysis
included to the hardware components implies on the test analysis and the future test manager
for defining the software testing strategies and plans of the software testing (Chauhan &
Singh, 2014). The software testing strategies and plans will be needed to have the idea of the
specific environment on which the software will run. In this context, the standard IEEE can
be applied in the multiple environments and contexts of software development of any
organization such as insurance, banking, automotive or aerospace industry.

6SOFTWARE TESTING STANDARDS
Result of the Application
The standard IEEE for software testing defines the internationally agreed set of the
IEEE standards for the testing of the software that is used by any organization while
executing the software testing. The IEEE standard facilitates the usages of the other
standards of IEEE by introducing the vocabulary and the concepts on the build-in standards
and is also provides the examples of the application in the practice. The standard IEEE
provides the information, guidance, context and the starting point of the application of this
standard. The standard IEEE defines the format of the documentation of the testing and it
approaches the requirements of constructing quality, identifying, analysing and validation of
the testing process with the quality metrics of the software. This provides the entire guidance
for the software validation and verification plans.
Relevance to Software testing
IEEE 829-2008 is known as Standard 829, which is used for System and Software
testing (Vasanthapriyan et al., 2017). It is the IEEE standard, which specifies the form of the
document set for the use of eight stages of system testing and software testing. Each of the
stage produces their own type of various documents. The standard IEEE specifies the format
of the documents of the software testing. The standard does not stipulate whether the standard
needs to produce or need not any criteria about the proper content of the documents of the
software testing. This is the matter of judgement.
The documents for the testing are:
 MTP: MTP stands for Master Test Plan. MTP provides the entire testing of the
software management and planning of test of the documents of the software for the
multiple level tests (Elnasr, Rashad & Aly, 2014). This can be done either in one or
multiple projects.

7SOFTWARE TESTING STANDARDS
 LTP: LTP stands for Level Test Plan. The aim of LTP is to give resources, scope and
approaches and make the scheduling of the software testing activities for the specific
level of software testing (Wang et al., 2016). The items are tested, the tasks of testing
are performed, the features are tested, the personnel are responsible for each testing
task and risks of association with the testing needs to be identified.
 LTD: LTD stands for Level Test design. Level Test Design provides the information
of the test and the information of the expected result and the criteria of test pass.
 LTC: LTC stands for Level test Case. Level Test Case specifies the testing of the
program to use in the execution of the testing, which is identified in Level Test
Desiign.
 LTPr: LTPr stands for Level Test procedure. LTPr provides the details of the
execution of the software test, precondition of the set-up and the required steps of the
testing.
 LTL: LTL stands for Level Test Log. LTL provides the chronological test record of
the test details of the testing of the tests such as recording of the test case, order of the
test, programmer of the test.
 AR: AR stands for Anomaly Report. Anomaly report provides the documentation of
any event, which occurs in the process of software testing and it requires investigation
(Ghaith et al., 2013).
Conclusion
The standard IEEE for software testing is the widely accepted testing standard. It acts
as the blueprint to carry out the activities of software testing. This can be concluded by this
study that IEEE as a software-testing standard sets the benchmark and it is accepted by the
organization. The standard will prove for being the turning point of the present of the
organization’s work. This can be analysed that the standard IEEE is the refinement of the

8SOFTWARE TESTING STANDARDS
traditional approaches and this will help in the great dealing to build the entirely new era of
the testing of softwares. To the international community of testing, the IEEE standard is very
essential deliverables, which is the result of the joint effort by various testing organizations,
which come up with the consistent and coherent set of the documentation, which fits the
multiple contexts of the system and software testing.

9SOFTWARE TESTING STANDARDS
References
Chauhan, R. K., & Singh, I. (2014). Latest research and development on software testing
techniques and tools. International Journal of Current Engineering and
Technology, 4(4), 2347-5161.
Elnasr, O. M. A., Rashad, M. Z., & Aly, G. M. (2014). Towards a Framework Empowering
Software Testing Process for Better Quality. International Journal of Computer
Applications, 975, 8887.
Ghaith, S., Wang, M., Perry, P., & Murphy, J. (2013, March). Profile-based, load-
independent anomaly detection and analysis in performance regression testing of
software systems. In 2013 17th European Conference on Software Maintenance and
Reengineering (pp. 379-383). IEEE.
Jorgensen, P. C. (2013). Software testing: a craftsman's approach. Auerbach Publications.
Laplante, P. A. (2017). Requirements engineering for software and systems. Auerbach
Publications.
Leicht, N., Blohm, I., & Leimeister, J. M. (2017). Leveraging the power of the crowd for
software testing. IEEE Software, 34(2), 62-69.
Pogliano, U., Braun, J. P., Voljč, B., & Lapuh, R. (2013). Software platform for PMU
algorithm testing. IEEE Transactions on Instrumentation and Measurement, 62(6),
1400-1406.
Smith, S., & Kandel, A. (2018). Verification and validation of rule-based expert systems.
CRC Press.

10SOFTWARE TESTING STANDARDS
Vanfretti, L., Aarstrand, V. H., Almas, M. S., Perić, V. S., & Gjerde, J. O. (2013, June). A
software development toolkit for real-time synchrophasor applications. In 2013 IEEE
Grenoble Conference (pp. 1-6). IEEE.
Vasanthapriyan, S., Tian, J., Zhao, D., Xiong, S., & Xiang, J. (2017). An Ontology-based
Knowledge Management System for Software Testing. In SEKE (pp. 230-235).
Wang, J., Wang, S., Cui, Q., & Wang, Q. (2016, September). Local-based active
classification of test report to assist crowdsourced testing. In 2016 31st IEEE/ACM
International Conference on Automated Software Engineering (ASE) (pp. 190-201).
IEEE.
Zuse, H. (2013). A framework of software measurement. Walter de Gruyter.