Software Testing Standards | Report

Running head: SOFTWARE TESTING STANDARDS
1
Software Testing Standards
Name
University
Date:

SOFTWARE TESTING STANDARDS
2
Part A: ISO/IEC 29119
Concept and Definition
Software testing is a fundamental stage in the process of developing a product. The
ISO/IEC 29119 is a software standard released in 2013, which defines the documentation,
vocabulary, process, and techniques within a software development cycle (García, Meléndez, &
Dávila, 2018). Software testing processes have from a general phase of debugging to one that
considers bug-free products with mismatched logic and product improvement. Some of the
modern trends found in the ISO/IEC 29119 include the agile and mobile testing, automation
testing, test factories, and the context-driven testing . One of the reason for the standardization of
software testing techniques is to enable the universal usage, especially for small companies and
organizations that do not have the means to develop internal testing equipment. The
standardization enables them to employ workers who are already familiar with the processes,
thus enabling quicker and cheaper software development and life cycle management.
Test Processes
A process model is a framework of activities, processes, ad artifacts that enable proper
communication and collaboration of product testing (Eira, et al., 2016). An organization or
company’s rate of maturity in the development of software products is measured by the level of
implementation of the ISO/IEC 29119 framework in its day-to-day operations. In the second
standard part of the ISO/IEC 29119 model relates to the generic processes that are part of the
software development cycle. It can be applied to organizations of any kind of product or size.
Numerous standards have been defined in this model. Therefore, a project manager chooses the
parts that are applicable to the different sections. The described approach is referred to as the
adapted compliance. The alternative is fully implement all standards in a process model called

SOFTWARE TESTING STANDARDS
3
the full compliance counterpart. The ISO/IEC 29119 has 8 processes split into 89 base practices
and 50 artifacts (Ali & Yue, 2015). Its levels are divided into five based on their capabilities:
Managed, Performed, Predictable, Established, and Innovating. The ISO/IEC 29119 may be seen
as a continuous process model with two major classifications: architectural, and assessment
based.
Test Documentation
The test documentation is defined under the ISO/IEC 29119-3:2013, which was
published in the year 2013. It includes the definition of test templates and test documentation
examples that are internationally accepted (Kasurinen, 2010). The organization of the documents
reflects the overall test process in accordance with the process adaptation defined by the test
processes phase (section 2 i.e. ISO/IEC 29119-2). The documentation phase contains annexes A,
B, C, D to S, and T. A contains the document contents, B shows the mappings of ISO/IEC 29119
section 2. C provides an example-based approach, while D-S have template application case
examples. Annex T maps the standards to the currently applied standards. The crucial purpose of
the documentation section is to provide a dynamic testing mechanism that is functional for both
automated and manual testing procedures, whether scripted or unscripted.
Test Techniques
The software testing techniques are defined under the ISO/IEC 29119-4 standard, which
provides the standard test methods and their sample implementations. The project administrator
decides the level of applicability of the testing techniques to present or planned projects within
the company (ISO Software and systems engineering, 2013). Three kinds of techniques are
defined: Specification-based, structure-based, and the experienced based models. They entail an
array of methods that enable a team of testing professionals to determine the stability of a