Software Testing Standard
VerifiedAdded on 2023/01/23
|10
|1944
|37
AI Summary
This report discusses the ISO/IEC/IEEE 29119 software testing standard, including its scope, key terms, application, and relevance in software testing. It also compares it with other testing standards and discusses a specific document on integrating the standard with Agile development.
Contribute Materials
Your contribution can guide someone’s learning journey. Share your
documents today.
Running head: SOFTWARE TESTING STANDARD
SOFTWARE TESTING STANDARD
Name of the Student
Name of the University
Author note
SOFTWARE TESTING STANDARD
Name of the Student
Name of the University
Author note
Secure Best Marks with AI Grader
Need help grading? Try our AI Grader for instant feedback on your assignments.
SOFTWARE TESTING STANDARD
Table of Contents
Introduction......................................................................................................................................3
Response to the questions................................................................................................................3
Standard name.............................................................................................................................3
Copyright of the standard............................................................................................................3
Which university was included?..................................................................................................4
Scope of the standard...................................................................................................................4
Key terms.....................................................................................................................................4
Application of the standard..........................................................................................................5
Relevance in software testing the standard..................................................................................5
Discussion regarding the chosen paper............................................................................................6
Listing of differences.......................................................................................................................6
Conclusion.......................................................................................................................................8
Bibliography....................................................................................................................................9
Table of Contents
Introduction......................................................................................................................................3
Response to the questions................................................................................................................3
Standard name.............................................................................................................................3
Copyright of the standard............................................................................................................3
Which university was included?..................................................................................................4
Scope of the standard...................................................................................................................4
Key terms.....................................................................................................................................4
Application of the standard..........................................................................................................5
Relevance in software testing the standard..................................................................................5
Discussion regarding the chosen paper............................................................................................6
Listing of differences.......................................................................................................................6
Conclusion.......................................................................................................................................8
Bibliography....................................................................................................................................9
SOFTWARE TESTING STANDARD
Chosen Document
Chen, N., Chen, E. W., & Chen, I. S. (2018). Integrating Software Testing Standard
ISO/IEC/IEEE 29119 to Agile Development. In Proceedings of the International
Conference on Software Engineering Research and Practice (SERP) (pp. 89-95). The
Steering Committee of The World Congress in Computer Science, Computer Engineering
and Applied Computing (WorldComp).
Reference Document
Wichmann, B. A., & Cox, M. G. (1992). Problems and strategies for software component testing
standards. Software Testing, Verification and Reliability, 2(4), 167-185.
Chosen Document
Chen, N., Chen, E. W., & Chen, I. S. (2018). Integrating Software Testing Standard
ISO/IEC/IEEE 29119 to Agile Development. In Proceedings of the International
Conference on Software Engineering Research and Practice (SERP) (pp. 89-95). The
Steering Committee of The World Congress in Computer Science, Computer Engineering
and Applied Computing (WorldComp).
Reference Document
Wichmann, B. A., & Cox, M. G. (1992). Problems and strategies for software component testing
standards. Software Testing, Verification and Reliability, 2(4), 167-185.
SOFTWARE TESTING STANDARD
Introduction
Testing standards have been gaining importance in the regular testing process. the main
aspect that is taken int consideration includes proper testing of the software as per the selection
of the standard. This is one of the main reasons that the acceptance of the standards has been
very high. The testing standard that is chosen for commencing of the report is ISO/IEC/IEEE
29119. This report will discuss about the selection of the standard and hence few questions
regarding copyright of the standard and the inclusion of the standard setting will also be
discussed. Scope of the standard will also be discussed in the report. the key terms that are
important in understanding the processing of the standard will also be stated in the report. the
main application of the standard will also be discussed in the report. the relevancy of the
software testing method will also be stated in the report. listing of differences as per the sample
paper provided against the paper that is chosen for completing the report will also be stated in the
report.
Response to the questions
Standard name
The standard that is chosen for completion of the report is ISO/IEC/IEEE 29119. This
standard is bifurcated 5 different software testing standards. The standards are namely
ISO/IEC/IEEE 29119-1:2013, Part 1: Concepts and definitions, ISO/IEC/IEEE 29119-2:2013,
Part 2: Test processes, ISO/IEC/IEEE 29119-3:2013, Part 3: Test documentation and
ISO/IEC/IEEE 29119-4:2015, Part 4: Test techniques.
Copyright of the standard
The copyright is provided to the IEEE.
Introduction
Testing standards have been gaining importance in the regular testing process. the main
aspect that is taken int consideration includes proper testing of the software as per the selection
of the standard. This is one of the main reasons that the acceptance of the standards has been
very high. The testing standard that is chosen for commencing of the report is ISO/IEC/IEEE
29119. This report will discuss about the selection of the standard and hence few questions
regarding copyright of the standard and the inclusion of the standard setting will also be
discussed. Scope of the standard will also be discussed in the report. the key terms that are
important in understanding the processing of the standard will also be stated in the report. the
main application of the standard will also be discussed in the report. the relevancy of the
software testing method will also be stated in the report. listing of differences as per the sample
paper provided against the paper that is chosen for completing the report will also be stated in the
report.
Response to the questions
Standard name
The standard that is chosen for completion of the report is ISO/IEC/IEEE 29119. This
standard is bifurcated 5 different software testing standards. The standards are namely
ISO/IEC/IEEE 29119-1:2013, Part 1: Concepts and definitions, ISO/IEC/IEEE 29119-2:2013,
Part 2: Test processes, ISO/IEC/IEEE 29119-3:2013, Part 3: Test documentation and
ISO/IEC/IEEE 29119-4:2015, Part 4: Test techniques.
Copyright of the standard
The copyright is provided to the IEEE.
Secure Best Marks with AI Grader
Need help grading? Try our AI Grader for instant feedback on your assignments.
SOFTWARE TESTING STANDARD
Which university was included?
No University students were involved in developing of the standards
Scope of the standard
The scope of ISO/IEC/IEEE 29119 is to perform efficient and consistent solutions for the
key word driven testing process. the main aspect that is taken into consideration is that the
introductory keywords are taken into concern for performing the testing scenes proper defining
of the framework of the keyword driven testing will ensure that the engineers will be having a
proper understanding of the work items. The main aspect that affects includes test cases, test data
and key words as per the completion of the specification. Defining of the minimum requirement
of the tools that re required for fully utilizing the key word testing.
Key terms
The key terms that are required for performing of the testing process includes test
automation, test design, test management tools. These key terms are related with the functional
process of the interface defining and performing an exchange of the data format that will ensure
that the tolls of the different vendors will be capable of exchanging of their data. Another set of
key terms includes test cases, test data and test result. These key terms are associated with the
processing of the defining of the different level of hierarchy of the of keywords which will
ensure proper management of the hierarchical keywords for enhancing the vivid usage of the
terms. Proper definition of the usage of keywords as per the different structural keywords. This
also helps in defining the specificity of the keywords. The keywords for navigation or analyzing
a special prospect includes proper management of the provisioning of the generic suggestion of
technical keywords that are of low level. This insists the fact that the management of the entire
scenario will help in better execution of the task with the help of keywords namely, ‘inputData’
Which university was included?
No University students were involved in developing of the standards
Scope of the standard
The scope of ISO/IEC/IEEE 29119 is to perform efficient and consistent solutions for the
key word driven testing process. the main aspect that is taken into consideration is that the
introductory keywords are taken into concern for performing the testing scenes proper defining
of the framework of the keyword driven testing will ensure that the engineers will be having a
proper understanding of the work items. The main aspect that affects includes test cases, test data
and key words as per the completion of the specification. Defining of the minimum requirement
of the tools that re required for fully utilizing the key word testing.
Key terms
The key terms that are required for performing of the testing process includes test
automation, test design, test management tools. These key terms are related with the functional
process of the interface defining and performing an exchange of the data format that will ensure
that the tolls of the different vendors will be capable of exchanging of their data. Another set of
key terms includes test cases, test data and test result. These key terms are associated with the
processing of the defining of the different level of hierarchy of the of keywords which will
ensure proper management of the hierarchical keywords for enhancing the vivid usage of the
terms. Proper definition of the usage of keywords as per the different structural keywords. This
also helps in defining the specificity of the keywords. The keywords for navigation or analyzing
a special prospect includes proper management of the provisioning of the generic suggestion of
technical keywords that are of low level. This insists the fact that the management of the entire
scenario will help in better execution of the task with the help of keywords namely, ‘inputData’
SOFTWARE TESTING STANDARD
and ‘checkValue’. Hence creation of low-level keywords can be performed and hence different
terminologies will get affected in a positive manner.
Application of the standard
The main purpose of the ISO/IEC/IEEE 29119 testing standard is to define the set of data
that are associated to the functional progression of the internationally agreed standard set which
is considered valid for performing software testing processes. This standard finds its application
in software testing process, notwithstanding any bar for any business organization and hence all
the business organizations can use the same for their testing process. the main application of the
ISO/IEC/IEEE 29119 is that the testing process that is used in the standard is modular in nature
and hence the management of the project testing process gets performed in a better manner as the
testing processes are performed with the help of keyword testing process. this standard finds its
usage in all the testing processes that implements the keyword driven testing process. test
automation is also considered as a main aspect of the testing standard application.
Relevance in software testing the standard
The relevance of this testing standard is very high. The main reason of high relevance of
the ISO/IEC/IEEE 29119 is that the entire ISO/IEC/IEEE 29119 testing customary is
compartmentalized in smaller parts and hence the main issue that is present is that the functional
process will get better. The terminologies that are used in the processing of the testing process is
also very efficient. Usage of keyword driven has been very proficient making the relevancy of
the entire testing standard high.
and ‘checkValue’. Hence creation of low-level keywords can be performed and hence different
terminologies will get affected in a positive manner.
Application of the standard
The main purpose of the ISO/IEC/IEEE 29119 testing standard is to define the set of data
that are associated to the functional progression of the internationally agreed standard set which
is considered valid for performing software testing processes. This standard finds its application
in software testing process, notwithstanding any bar for any business organization and hence all
the business organizations can use the same for their testing process. the main application of the
ISO/IEC/IEEE 29119 is that the testing process that is used in the standard is modular in nature
and hence the management of the project testing process gets performed in a better manner as the
testing processes are performed with the help of keyword testing process. this standard finds its
usage in all the testing processes that implements the keyword driven testing process. test
automation is also considered as a main aspect of the testing standard application.
Relevance in software testing the standard
The relevance of this testing standard is very high. The main reason of high relevance of
the ISO/IEC/IEEE 29119 is that the entire ISO/IEC/IEEE 29119 testing customary is
compartmentalized in smaller parts and hence the main issue that is present is that the functional
process will get better. The terminologies that are used in the processing of the testing process is
also very efficient. Usage of keyword driven has been very proficient making the relevancy of
the entire testing standard high.
SOFTWARE TESTING STANDARD
Discussion regarding the chosen paper
The paper that is chosen for completion of the report is written by Ning Chen, Ethan W.
Chen and Ian S. Chen, who are from the department of computer science, California State
University, which is located in California, USA. This document is highly linked with the chosen
standard ISO/IEC/IEEE 29119. This document is mainly concerned with the integration of the
testing standard ISO/IEC/IEEE 29119 with the Agile development process. this document states
the reasons why ISO/IEC/IEEE 29119 replaces the older version of testing standard namely,
IEEE Std 829. The document discusses about the issues that are present in integrating the Agile
terminology with the testing standard. The mechanism that is required for the processing of the
Agile technology in the testing standard is stated inn the document. Test maturity model
integration is also one of the main concerns of the document. The main aspect that is taken inti
consideration includes the processing of the tailored conformance technology that will benefit
the functional process.
Listing of differences
The main difference in between the two documents is that the document that is chosen for
this report and the provided reference document is that the main concern of the chosen document
is concerned with the processing of the IEEE standard 29119. Whereas the refence document
that is provided as a reference discusses about several testing standards. The testing standards
that are used in the provided document are concerned with the testing standards namely BS
58887, MOD 00-55, IEEE, D0178B (draft), IEC/ WG9, IEC/ Nuclear and ITSEC.
The document that is chosen for completion of the report provides a vivid description of
the functional process of the IEEE standard 29119. The different parts of the testing standard are
also well stated in the document. Whereas the main focus of the reference document is
Discussion regarding the chosen paper
The paper that is chosen for completion of the report is written by Ning Chen, Ethan W.
Chen and Ian S. Chen, who are from the department of computer science, California State
University, which is located in California, USA. This document is highly linked with the chosen
standard ISO/IEC/IEEE 29119. This document is mainly concerned with the integration of the
testing standard ISO/IEC/IEEE 29119 with the Agile development process. this document states
the reasons why ISO/IEC/IEEE 29119 replaces the older version of testing standard namely,
IEEE Std 829. The document discusses about the issues that are present in integrating the Agile
terminology with the testing standard. The mechanism that is required for the processing of the
Agile technology in the testing standard is stated inn the document. Test maturity model
integration is also one of the main concerns of the document. The main aspect that is taken inti
consideration includes the processing of the tailored conformance technology that will benefit
the functional process.
Listing of differences
The main difference in between the two documents is that the document that is chosen for
this report and the provided reference document is that the main concern of the chosen document
is concerned with the processing of the IEEE standard 29119. Whereas the refence document
that is provided as a reference discusses about several testing standards. The testing standards
that are used in the provided document are concerned with the testing standards namely BS
58887, MOD 00-55, IEEE, D0178B (draft), IEC/ WG9, IEC/ Nuclear and ITSEC.
The document that is chosen for completion of the report provides a vivid description of
the functional process of the IEEE standard 29119. The different parts of the testing standard are
also well stated in the document. Whereas the main focus of the reference document is
Paraphrase This Document
Need a fresh take? Get an instant paraphrase of this document with our AI Paraphraser
SOFTWARE TESTING STANDARD
diversified to more than one testing standard this makes document incapable of providing a vivid
description of the functional process of the different testing standards.
Integration of Agile in the processing of the IEEE standard 29119 testing standard
processes are stated in the document that is chosen for the completion of the report. different
methods, namely sprints in Scrum is well defined as a process of integrating Agile process in the
system. Whereas in case of the reference document that is provided no process of integration of
the Agile terminology is stated and hence the entire document stays as a basic definitive
document that helps in understanding the basic features of several outdated testing standards that
are no longer in use.
The document that is chosen includes the fact that no prior history of the testing standards
are stated, the sole concentration of the document has been on the IEEE standard 29119, this will
lead to the fact that a novice will find it difficult to cope up with the document and will not be
aware of the steps that led to the usage of the IEEE standard 29119. Whereas in case of the
reference document proper definition of different testing standards are provided along with a
precise description of their working process.
In the document that is chosen for completion of the report provides a proper
understanding of the Tailored Conformance at TMMi Level 2 functional process. process of the
testing area as per the test policy and strategy phase, Test monitoring, Test planning and
controlling, test designing and performance and test situation are also well described. Nothing as
such is present in the reference document.
diversified to more than one testing standard this makes document incapable of providing a vivid
description of the functional process of the different testing standards.
Integration of Agile in the processing of the IEEE standard 29119 testing standard
processes are stated in the document that is chosen for the completion of the report. different
methods, namely sprints in Scrum is well defined as a process of integrating Agile process in the
system. Whereas in case of the reference document that is provided no process of integration of
the Agile terminology is stated and hence the entire document stays as a basic definitive
document that helps in understanding the basic features of several outdated testing standards that
are no longer in use.
The document that is chosen includes the fact that no prior history of the testing standards
are stated, the sole concentration of the document has been on the IEEE standard 29119, this will
lead to the fact that a novice will find it difficult to cope up with the document and will not be
aware of the steps that led to the usage of the IEEE standard 29119. Whereas in case of the
reference document proper definition of different testing standards are provided along with a
precise description of their working process.
In the document that is chosen for completion of the report provides a proper
understanding of the Tailored Conformance at TMMi Level 2 functional process. process of the
testing area as per the test policy and strategy phase, Test monitoring, Test planning and
controlling, test designing and performance and test situation are also well described. Nothing as
such is present in the reference document.
SOFTWARE TESTING STANDARD
Conclusion
From the above discussion it can be stated that the functional process of the IEEE
standard 29119 have been highly accepted by the global mass in the corporate software
engineering phases. The major stages that are stated in the report includes providing concepts
and definition of the concepts of the IEEE standard 29119. Different life cycle models are also
well defined. The main concern of the document is to integrate the Agile method in the testing
standard in instruction to surge the competence of the standard. Usage of the TMMi for the
implementation of the IEEE standard 29119 testing standard are stated in the document.
Conclusion
From the above discussion it can be stated that the functional process of the IEEE
standard 29119 have been highly accepted by the global mass in the corporate software
engineering phases. The major stages that are stated in the report includes providing concepts
and definition of the concepts of the IEEE standard 29119. Different life cycle models are also
well defined. The main concern of the document is to integrate the Agile method in the testing
standard in instruction to surge the competence of the standard. Usage of the TMMi for the
implementation of the IEEE standard 29119 testing standard are stated in the document.
SOFTWARE TESTING STANDARD
Bibliography
Chen, N., Chen, E. W., & Chen, I. S. (2018). Integrating Software Testing Standard
ISO/IEC/IEEE 29119 to Agile Development. In Proceedings of the International
Conference on Software Engineering Research and Practice (SERP) (pp. 89-95). The
Steering Committee of The World Congress in Computer Science, Computer Engineering
and Applied Computing (WorldComp).
Wichmann, B. A., & Cox, M. G. (1992). Problems and strategies for software component testing
standards. Software Testing, Verification and Reliability, 2(4), 167-185.
Bibliography
Chen, N., Chen, E. W., & Chen, I. S. (2018). Integrating Software Testing Standard
ISO/IEC/IEEE 29119 to Agile Development. In Proceedings of the International
Conference on Software Engineering Research and Practice (SERP) (pp. 89-95). The
Steering Committee of The World Congress in Computer Science, Computer Engineering
and Applied Computing (WorldComp).
Wichmann, B. A., & Cox, M. G. (1992). Problems and strategies for software component testing
standards. Software Testing, Verification and Reliability, 2(4), 167-185.
1 out of 10
Related Documents
Your All-in-One AI-Powered Toolkit for Academic Success.
+13062052269
info@desklib.com
Available 24*7 on WhatsApp / Email
Unlock your academic potential
© 2024 | Zucol Services PVT LTD | All rights reserved.