Software Testing

This document explores a research paper on software testing procedures and standards. It discusses the chosen IEEE standard and compares it with other standards. The paper provides insights into different aspects of the standards, their application, and relevance to software testing. It also highlights the commonalities and differences between the chosen standard and the research paper. The conclusion emphasizes the importance of maintaining software quality through standardized testing procedures.

Running head: SOFTWARE TESTING
Software Testing
Name of the Student
Student ID:
Course ID:
Course Name:
Name of the University
Author Note:

1SOFTWARE TESTING
Table of Contents
Introduction......................................................................................................................................2
Brief description of the paper..........................................................................................................2
Chosen Standard..........................................................................................................................3
Reason behind choosing IEEE standard..................................................................................3
Questions for the standards..............................................................................................................3
Similarity and Differences...............................................................................................................5
Conclusion.......................................................................................................................................6
Reference.........................................................................................................................................7

2SOFTWARE TESTING
Introduction
The notable determination of the report is to focus on the research paper related to the
testing procedures of different types of software (Wichmann & Cox, 1992). The standard of the
testing procedures offered by the research paper from different perspectives will be evaluated in
this paper.
The extensive development in the field of information technology has resulted in the
growth of numerous innovative software and technologies. Most of the business organizations
use different categories of software each day. It can be said that the growth of a business can be
hugely on the Quality of Service (QoS) offered by the software. Maintaining the quality of
standard is one of the prime criteria of software testing (Vale et al., 2016). Standards can be
defined as the published documents which ensure the quality and the safety of the products such
as software. The software testing standards are accepted by every IT entity of the world as these
standards are there for improving the effectiveness of the product (Ratwani et al., 2015). It can
be also seen that more resources are required for software testing rather than the designing and
the development part.
Brief description of the paper
The paper is very much helpful to identify the different problems and strategies
associated with the software components testing standards. The different types of software
testing procedures in different industries have been introduced in the paper, along with that it
will also help in understanding the tools and techniques which are widely used in the software
testing purposes (Leon, 2015). Different aspects of testing procedures such as test effectiveness
ratios and LDRA have been stated in the paper as well. The factors determining the adequacy of

3SOFTWARE TESTING
the test are also mentioned in the paper along with the current practice of software testing (Khan
& Malik, 2017). The different types of testing standards such as BS5887, MOD00-55 and
D0178B has been presented in the paper in a professional manner (Garousi & Mäntylä, 2016).
The factors which can have an impact on the software testing procedure such as reference
software, data sets and modularity have been discussed in the paper as well (Fenton & Neil,
2018). The advantages of maintaining the standards and testing the numeric operations of
software testing have been presented in the paper as well.
Chosen Standard
The chosen standard of the paper is IEEE which will be compared with standard of the
research paper ANSI1/IEEE2 Standard 8293 and ANSI/IEEE Standard 1008.
Reason behind choosing IEEE standard
IEEE is an internationally accepted standard which can be applicable in any kinds of
industries. The application of the software is not only restricted to a country but are involved in
bigger projects where the software is accessed from human resources sitting thousands of miles
apart from each other.
Questions for the standards
Standard Name ANSI1/IEEE2 Standard
8293
ANSI/IEEE Standard 1008 IEEE
Copyright Institute of Electrical
and Electronics
Engineers Standards
Association holds the
copyright of this
standard (Felderer etal.,
2016).
Institute of Electrical and
Electronics Engineers
Standards Association
holds the copyright of
this standard as well.
Institute of
Electrical and
Electronics
Engineers
Standards
Association
have the
copyright of this
software.
Universities involved This standard is part of the This testing standard is not The authorization

4SOFTWARE TESTING
(if any) training syllabus of British
Computer Society and
International Software
Testing Quality Board of
Belgium.
applicable to any of the
educational institutions.
of this standard is
done by a
community.
Scope of the standard It is one of the most
important software test
documentation method.
It is the IEEE standard for
software unit testing
(Ammann & Offutt,
2016).
Maintaining
balance and
openness are the
prime
specification of
this standard.
Intent of the standard Maintaining the quality of
standard of documentation
after the testing is the
prime intent of this
software.
This standard is used in the
unit testing procedures of
websites and software.
Technologies with
one or more
potent claims is
the primary intent
of this standard.
Key terms and
understandings needed
to understand the
standard
The documents required
for thus standard are:
 Master test plan
 Anomaly report
 Level test log
 Level test
procedure
 Level test case.
 Level test design.
 Level test plan
 Level interim test
status report
 Level test report
 Master test report
The drawbacks of the
software testing unit
phases can be managed
with the help of this
standard.
IEEE patent
policy can be very
much important to
understand the
insights of this
standard.
Application of the
standard
This standard is applied in
most of the software
development organization
only.
This standard is widely
used in Information
Technology industry,
robotics,
telecommunication, home
automation and other
industries.
This application
can be
incorporated in a
wide range of
industries such as
IT, manufacturing
industry, and
information
assurance.
Functionality of the
standard
Software and system
testing procedures are
conducted with the help of
this standard.
Guidance and resource
information are the other
two objectives of this
standard along with the
usage of the software
testing.
Consensus and
fair procedures
are maintained by
this standard.
Specific relevance to
software testing
Eight different stages of
software testing can be
done with the help of this
standard.
The quality of the software
along with the
implementation of the
software considers this
standard.
The
standardization
process of IEE
can be divided
into seven basic

5SOFTWARE TESTING
steps such as
securing
sponsorship,
requesting project
authorization,
drafting the
standard,
reviewing the
committee,
balloting, and the
final vote.
Table 1: Different aspects of the standards of the chosen paper
(Created by the author)
The following unit of the paper will be analysing this research paper with the chosen
standard.
Similarity and Differences
The below tables will be very much important to understand the similarity as well as the
differences between the research paper and the chosen standard which is IEEE.
Commonalities IEEE Standard of the research paper
 All these standards can be related to software testing (Dhiman, 2017).
 Identification of the limitations of the software is the area of concern for all these standards.
 Quality of the software can be maintained with the help of these standards.
 Monitoring of the activities of the software can be also done with the help of these standards.
Table 2: Commonalities of the standard with the chosen paper
(Created by the author)
Differences IEEE Research paper
 The prime difference between the two different types of standards is that the standardization
process of IEEE has seven steps unlike other standards which are maintained in the research
paper (Barr et al., 2015).
 IEEE authorization is done a community where as the authorization of the standards of the
paper are maintained by the International Software Testing Quality Board of Belgium and the

6SOFTWARE TESTING
British Computer Society.
 IEEE standards are more popular and are universally accepted (Abrahamsson et al., 2017).
 IEEE standards can be applied in both theories as well as in practical fields whereas
ANSI1/IEEE2 Standard 8293 cannot be applied in practical works.
 The drawback of the software and the websites can be managed with the help of ANSI1/IEEE2
Standard 8293 whereas the limitations of the software cannot be covered up in the IEEE
standard.
Table 3: Differences of the standard with the chosen paper
(Created by the author)
Conclusion
The paper helps in concluding the different types of standards which are supposed
to be maintained during the software testing procedures. The incremental growth of the
application of software has been presented in the paper in a professional manner. The research
paper which was selected for this paper was described briefly in the introductory parts of the
paper. The insights of the selected research paper is provided in the assignment. The standards
which are maintained in the selected research paper are ANSI/IEEE Standard 1008 and
ANSI1/IEEE2 Standard 8293. The chosen standard for evaluating these two stands is the IEEE standard.
Justification behind choosing the IEEE standard has been provided in the paper as well in order to
maintain the clarity of this paper. The paper helps in identifying the different aspects of the standards
which are discussed above such as their copyright holders, universities followed, scope of the standard,
intent of the standard, application of the standard, the functionality of the standard, and relevance to
software testing. The effectiveness of the paper is further maintained as it explains the key commonalities
between the selected standard and the standards maintained in the research paper. It can be concluded that
both these two standards can be applicable for identifying any kinds of flaws in software. The limitation
of the products can be determined by both these two universal standards. Both these standards can be
used in the software development corporations as it will help them to monitor the activities of the

7SOFTWARE TESTING
software using a set of rules which each of these standards have. The paper is also very much
beneficial for the readers of this document to understand the difference between with these two
standards such as the difference in authorization of standards where IEEE is authorized by
International Software Testing Quality Board of Belgium and British Computer Society and the
authorization of the standards used in this selected research paper is done by a community. The drawback
of the software can be covered-up according to the protocols of ANSI1/IEEE2 Standard 8293 which is
not possible in case of IEEE standards.

8SOFTWARE TESTING
Reference
Abrahamsson, P., Salo, O., Ronkainen, J., & Warsta, J. (2017). Agile software development
methods: Review and analysis. arXiv preprint arXiv:1709.08439.
Ammann, P., & Offutt, J. (2016). Introduction to software testing. Cambridge University Press.
Barr, E. T., Harman, M., McMinn, P., Shahbaz, M., & Yoo, S. (2015). The oracle problem in
software testing: A survey. IEEE transactions on software engineering, 41(5), 507-525.
Dhiman, S. (2017, February). Standards Driven Software Testing Best Practice. In Proceedings
of the 10th Innovations in Software Engineering Conference (pp. 214-214). ACM.
Felderer, M., Büchler, M., Johns, M., Brucker, A. D., Breu, R., & Pretschner, A. (2016). Security
testing: A survey. In Advances in Computers (Vol. 101, pp. 1-51). Elsevier.
Fenton, N. E., & Neil, M. (2018). Improving Software Testing with Causal Modeling. Analytic
Methods in Systems and Software Testing, 27-64.
Garousi, V., & Mäntylä, M. V. (2016). A systematic literature review of literature reviews in
software testing. Information and Software Technology, 80, 195-216.
Khan, H. H., & Malik, M. N. (2017). Software Standards and Software Failures: A Review With
the Perspective of Varying Situational Contexts. IEEE Access, 5, 17501-17513.
Leon, A. (2015). Software configuration management handbook. Artech House.
Ratwani, R. M., Benda, N. C., Hettinger, A. Z., & Fairbanks, R. J. (2015). Electronic health
record vendor adherence to usability certification requirements and testing standards.
Jama, 314(10), 1070-1071.

9SOFTWARE TESTING
Vale, T., Crnkovic, I., De Almeida, E. S., Neto, P. A. D. M. S., Cavalcanti, Y. C., & de Lemos
Meira, S. R. (2016). Twenty-eight years of component-based software engineering.
Journal of Systems and Software, 111, 128-148.
Wichmann, B. A., & Cox, M. G. (1992). Problems and strategies for software component testing
standards. Software Testing, Verification and Reliability, 2(4), 167-185.