Integration of Software Testing in Agile Development

Running head: SOFTWARE TESTING
SOFTWARE TESTING
Name of Student
Name of University
Author’s Note

1SOFTWARE TESTING
Introduction
The standard chosen for this particular assignment is AS/NZS ISO/IEC/IEEE 29119
Software Testing. The main purpose of this standard series is defining a set of various standards
for the purpose of software testing which is internationally agreed, this standard can be used by
organizations during performing the process of testing, and it can be used by various
organizations of any size and irrespective of the services provided by them (Chen, Chen and
Chen 2018). The part ISO/IEC/IEEE 29119-2 of the standard does not refer to a process for test
design as well as implementation, it refers to a set of techniques that would be used within the
ISO/ICE/IEEE 29119-2.
Responses to the questions for standard
The name of the standard is AS/NZS ISO/IEC/IEEE 29119 Software Testing.
The copyright for the standard is hold by the Joint Standards Australia/ Standards New
Zealand Committee IT- 015, Software and Systems Engineering.
Amongst all the acknowledged contributors to the document, the universities that were
involved NAVSEA, ASQ; KOMBIT, IMBUS, IBM Research, Janaagraha, Planit Testing,
Software Testing Alliances (Laplante 2017).
The standard provides an international standard which defines the techniques of software
testing design which can be utilized within the test design as well as implementation processes
that has been defined in ISO/IEC/IEEE 29112-2 (Mall 2018). This particular part of the standard
does not prescribe the process for test design as well as implementation. The main intent of this
standard is to describe a particular series of technique which has a wide acceptance in the
industry of software testing.

2SOFTWARE TESTING
The application of standard results in helping organizations to carry out the process of
testing. There are various techniques that can be used by organizations; these techniques follow
the test design as well as process of implementation which is defined in the ISO/IEC/IEEE
29119-2
The key terms and understanding that are needed for the standard to be understood as
well as applied include systems, objects, software items, classes, design specifications, user
guides and requirements documentations (Beyer 2019). The aspect which requires to be
understood include the fact that a test condition is a particular testable aspect of a particular test
team like function, feature, transaction, quality attribute and structural element which is
identified as a basic step for testing. This has to be achieved by discussing with various
stakeholders whose attributes are to be tested.
The relevance of software testing to the standard
The IEEE Std 29119 is a specific set of standards that is agreed upon internationally, its
purpose was to support the process of software testing. IEEE Std 29119 has five parts that have
different operations and features (Garousi and Mäntylä 2016). The five parts are as follows
 IEEE Std 29119-1: concepts and definitions
 IEEE Std 29119-2: processes of testing
 IEEE Std 29119-3: documentation of testing
 IEEE Std 29119-4: techniques of testing
 IEEE Std 29119-5: keyword driven testing
IEEE Std 29119 is actually intended for the purpose of replacing the existing standards
for software testing. The previously used standards for software testing are IEEE 829 test