Software Testing Standard Review: Analysis of ISO/IEEC 12207 Standard

This report presents an article review focusing on software testing standards, specifically the ISO/IEEC 12207 standard for software verification and validation. The review delves into the standard's scope, intent, and key terms, explaining its application within the software development life cycle, including acquisition, development, supply, operation, and maintenance. It addresses the standard's relevance to software testing, emphasizing its role in early error detection and risk management. The report also identifies commonalities and differences between the chosen standard and the research paper, highlighting the importance of standardized testing processes to ensure software quality and adherence to customer requirements. The conclusion underscores the necessity of software testing phases within the software development lifecycle and the benefits of standardized practices for both product quality and future development.

Running head: ARTICLE REVIEW - SOFTWARE TESTING
Article Review - Software Testing
Name of the Student
Name of the University
Author Note

1ARTICLE REVIEW - SOFTWARE TESTING
Table of Contents
Introduction................................................................................................................................2
Introduction to standards and a brief description of the research paper and chosen standard
................................................................................................................................................2
Responses to questions for the standard.................................................................................3
What is the standard name?................................................................................................3
Who holds the copyright for the standard?........................................................................3
Amongst the acknowledged contributors to the document, which universities were
involved (if any)?...............................................................................................................4
What is the scope or intent of the standard?......................................................................4
What are key terms and understandings needed for the standard to be understood and
applied?..............................................................................................................................4
In your own words, what does application of the standard result in? Or, in other words,
what does the standard do?................................................................................................5
Finally, what specific relevance to software testing is the standard?................................6
Listing and a discussion of commonalities and differences between the two documents.....6
Conclusion..................................................................................................................................7
References..................................................................................................................................8

2ARTICLE REVIEW - SOFTWARE TESTING
Introduction
Software Testing has been an extremely common phenomenon in the latest times in
both the phases of the technical advancement scenario and the business scenario as well. This
is an extremely common phenomenon where a software is brought to a quality assurance
checking before it is presented to the market and made available to the clients. This process
of software testing was not considered to be of much importance in the previous times and
therefore the end products presented to the customers were often listed as unsatisfactory as
per the complaints received from them (IEEE Computer Society, 1998). Then the idea of
software testing was presented to the business organizations and then it was introduced as a
mandatory step for every software development phase as it would be necessary for assuring
the quality of the software developed through the development life cycle including all the
stages of the developmental process. There are also proposed standardization methods
approved by universities and standardizations of the organizations that needs to be followed
to make sure that the quality assurance testing for the software are also specified and
standardized as a format. There are various formats specified for a software testing method
that needs to be discussed in this particular paper.
Introduction to standards and a brief description of the research paper and
chosen standard
This particular paper focuses on the Software verification and validation process that
helps in determining the development process of a product to confirm their fulfilment to find
out if they satisfy the requirements of their utility and the needs of the users. This verification
and validation standard is what is addressed throughout the software life cycle process
including the phases of supply, acquisition, operation, development and maintenance. The

3ARTICLE REVIEW - SOFTWARE TESTING
paper describe in an elaborate way on how the compatibility of a particular standard resides
within the life cycle models of a software production and development. The software
verification and validation process is applicable to various standards. The particular standard
chosen in this research paper is the ISO/IEEC 12207. This particular standard has been
chosen in this paper to be described. The description of the standard chosen for the software
verification and validation process also abide by the purpose that it service and why does the
software validation and verification process needs to have a particular standard to be
established and for analysing the quality of the product all the software that is being
developed throughout its life cycle.
The identified purpose of this particular standard lies between establishment of a
common Framework for the verification and validation of a software process, and bytes by
the entire life cycle process during the development phase. this life cycle phases includes
acquisition, development, supply, operation and maintenance processes. This particular
standard also helps in defining the verification and validation tasks that is required for the
analysis of both inputs and outputs.
Responses to questions for the standard
What is the standard name?
The chosen standard in this particular paper is clarified as software verification and
validation process standardized by ISO / IEEC 12207 (IEEE Computer Society, 1998).
Who holds the copyright for the standard?
The copyright of this particular standard is held by the Institute of Electrical and
Electronics Engineers Incorporations in the United States of America.

4ARTICLE REVIEW - SOFTWARE TESTING
Amongst the acknowledged contributors to the document, which universities were
involved (if any)?
Other than the Institute of Electrical and Electronics Engineers Incorporations in the
United States of America, the other acknowledge contributors in this particular research
paper has been identified to be the Software Engineering Standards Committee that has
sponsored the research entirely to build up this particular article that is about to be reviewed
in this report.
What is the scope or intent of the standard?
The scope of intent of the standard is very clear according to the research paper that
has been presented in in explaining the field of application and the scope of this particular
standard for software verification and validation. any product for a software that has been
developed through several life cycle phases of a software development has to abide by certain
standards and laws that determines whether the particular software is following all the
standardized way of software development throughout its life cycle phases. The software
verification and validation standard determines all this process or phases of the software
development life cycle confirms every requirement required for that activity and the end
product of the software development phase has the capability of satisfying the user
requirements and the intended use of the software.
What are key terms and understandings needed for the standard to be understood and
applied?
there are several key terms identified in this particular research paper that needs to be
understood to implement them for the successful in the software testing phases during the
development of a software. The first and foremost identified key term in this research paper is

5ARTICLE REVIEW - SOFTWARE TESTING
identified to be reusable software. Reusable software is one that includes the usability of of a
software that can be formulated many a times with just one developmental phase.
The next three term defined in this paper has been the phases of a software
development, including accusation, supply, development, operation and maintenance. All
these include the software development process which needs to be analysed through the
standard presented in this paper so that it can be identified if the developmental phases are
carried out in accordance to the requirements of the customers and its usability.
With the understanding of all these key terms, it can be identified that a person going
through this research paper would be able to understand the need of this particular standard in
the phases of a software development process and how they can be implemented to make sure
that the development process is successfully and effectively following the correct procedures
so that it fulfils the requirement of the customers as well as its usability.
In your own words, what does application of the standard result in? Or, in other words,
what does the standard do?
As it has been hinted previously in the discussion above, it can be well understood
that this particular standard is utilised for software verification and validation methods that
analyses if a software development process is going through in accordance to all the
requirements needed for a proper fulfilment of all the customer needs and also its usability
standards. Verification of a software phase helps in facilitating the early detection of any
error that the software development phase may go through and it creates the window of
correcting it immediately. This particular standard also helps in the enhancement of the
management insight to initiate the process and product risk management. in addition to that,
the kind of support that up software life cycle process means for ensuring the compliance

6ARTICLE REVIEW - SOFTWARE TESTING
with problem performance, this standard makes sure that all the aspects of a software
development process are maintained including the budget requirements and the schedule.
Finally, what specific relevance to software testing is the standard?
The standard is essentially related to the software testing phase as only if a software
development phase is analysed throughout its life cycle collecting information about its
development at every step, then it would be easier to find out any error rather than finding it
right at the end where the development phase is completed. If the error is found after the
phase is completed, it would be an extremely difficult process to go back right at the point of
initiation and begin again. Instead of that if the analysis is done at every step of the software
testing process, the minimum amount of human error or any technical error can be detected to
be cleared out at first and then move on to the next phase. Therefore, the software V&V
standard is extremely relevant to the software testing process.
Listing and a discussion of commonalities and differences between the two
documents
The commonalities between the chosen IEEE Standard and the Research paper is that
both speaks about the process (Wichmann & Cox, 1992). However, the research paper and
the chosen standard are different from each other. Where the research paper speaks mostly
about the chosen standards, the IEEE standard speaks about the software verification and
validation procedure. The research paper only focuses on the utility of the chosen standard
and why there is a need to use them, whereas the standard speaks about what the standard can
ensure the customers and the organizations about the quality of the product, which in this
case is the software.
.

7ARTICLE REVIEW - SOFTWARE TESTING
Conclusion
Therefore, in conclusion, it can be said that the software development process has to
abide by a software testing phase as well, so that a proper standard is maintained during the
entire software development life cycle. standardization in a software testing phase is
maintained only to make sure that the developed software is a binding all the legal standards
as affiliated by various technical universities and institutions as the set standard of a software
according to its usability and customer requirements. The papers presented in this article
review essentially speaks about the software verification standard ISO / IEEC 12207 and the
software documentation face for the ANSI / IEEE Standard 829:1983. Where the former talks
about the verification and validation of a software done and every stage of of the software
development life cycle, the letter describes how the documentation face of every e testing
unit should be recorded to help the future development processes. The article review presents
The clear idea about the entire software testing standards followed by a comparison between
the two standards as well.

8ARTICLE REVIEW - SOFTWARE TESTING
References
IEEE Computer Society. (1998). IEEE Standard for Software. The Institute of Electrical and
Electronics Engineers, Inc.
Wichmann, B. A., & Cox, M. G. (1992). Problems and strategies for software component
testing standards. Software Testing, Verification and Reliability, 2(4), 167-185.