Evaluating ANSI/IEEE Standards 8293 and 1008

This report evaluates ANSI/IEEE Standards 8293 and 1008, discussing their specifications, differences, and commonalities. It also explores the relevance of software testing and the consequences of deploying these standards.

Running head: EVAUATING ANSI1/IEEE2 STANDARD 8293 AND ANSI/IEEE STANDARD 1008
Evauating ANSI1/IEEE2 Standard 8293 and ANSI/IEEE Standard 1008
Name of the student:
Name of the university:
Author Note

1EVAUATING ANSI1/IEEE2 STANDARD 8293 AND ANSI/IEEE STANDARD 1008
Executive summary
The standards refer to different published documents. These are found to set different types of
specifications. It has included various processes designed to assure that the products, services and
systems are protected. Further, they are highly reliable and performing in the manner they are
intended in a consistent manner. In this report, an introduction is given evaluating various standards
along with the discussing on the chosen standards. After that, different questions related to the
standards are evaluated. At last, a discussion is made and different commonalities are listed are in
the study. This also involves the differences that have been fund while analyzing the documents.

2EVAUATING ANSI1/IEEE2 STANDARD 8293 AND ANSI/IEEE STANDARD 1008
Table of Contents
1. Introduction:......................................................................................................................................3
2. Discussion on standards and research paper and the standards:........................................................3
2.1. Discussion on the standards:.......................................................................................................3
2.2. Assessing the research paper:.....................................................................................................4
2.3. Evaluating the standards:............................................................................................................4
2.3.1. ANSI/IEEE Std 829:1983:...................................................................................................4
2.3.2. ANSI/IEEE Std 1008:1987:.................................................................................................4
3. Responses to various questions for the above standards:..................................................................5
3.1. Standard names:..........................................................................................................................5
3.2. Holding of the copyright of the standards:.................................................................................5
3.3. Universities involved:.................................................................................................................5
3.4. Intent and scope of the standard:................................................................................................5
3.5. Key terms and different understanding required for the standard to be applied and understood:
...........................................................................................................................................................6
3.6. Consequences of deploying the standards:.................................................................................7
3.7. Relevance of software testing:....................................................................................................7
4. Discussing and listing the commonalities and differences between the two:....................................7
5. Conclusion:........................................................................................................................................8
6. References:........................................................................................................................................9

3EVAUATING ANSI1/IEEE2 STANDARD 8293 AND ANSI/IEEE STANDARD 1008
1. Introduction:
The standards are the published documents that are found to be setting out various
specifications. This also involved different procedures that are designed for assuring that the
systems, services and products are secured, dependable and constantly performing the way they are
expected to be. Further, they are found to be deploying the common language defining security and
quality criteria.
In the following study, an introduction is provided with various standards with a concise
demonstration of the standard chosen. Then, various queries regarding the standards are discussed.
Lastly, a discussion and listing of various commonalities and various differences taking place
between the documents are evaluated.
2. Discussion on standards and research paper and the standards:
2.1. Discussion on the standards:
The IEEE-SA or “The Institute of Electrical and Electronics Engineers Standards
Association” is the organization under the IEEE. This creates worldwide standards under a wider
range of industries. This involves information technology, telecommunication and many more. The
ANSI or the “American National Standards Institute” is the popular non-profit organization (Sneed
& Seidl, 2017). This overseas the developing of the standards of consensus for personnel,
systems, processes, services and products at the United States. They are also found to be
coordinating the standards U.S. along with various international standards such that the America
products are utilized throughout the globe (Jambak et al., 2017).

4EVAUATING ANSI1/IEEE2 STANDARD 8293 AND ANSI/IEEE STANDARD 1008
2.2. Assessing the research paper:
It is already understood that there are various national and international standards relating
mainly to the testing of software. These standards have been formalizing the best practices of the
industries. These are found to be agreed upon by different experts at the sectors where the standards
are applicable. The present research paper is the analysis of the chosen standards. Thus the research
is helping to develop the skills of comprehension and research. Besides, it is useful for the effective
understanding of standards of professional industries regarding the testing of software. Lastly, the
values of different methods and processes utilized in the business are appreciated through the
research. This is helpful for evaluating and testing the systems of the software.
2.3. Evaluating the standards:
Wichmann and M. G. (1992), has identified has a couple of standards from the ANSI/IEEE
regarding testing. They are discussed hereafter.
2.3.1. ANSI/IEEE Std 829:1983:
This is standard for the test documentation of software. The document is about 50 pages
long. Here, eight of them has the primary texts. However, the residual has been the explanatory and
example material. Here, the scope has been roughly the completeness of the checklist. This is
particularly for the documentation. Further, this consists of direct importance to the study (Pröll &
Bauer, 2018). This is because this has been controlling the documentation instead of nature and the
context tests.
2.3.2. ANSI/IEEE Std 1008:1987:
This standard is intended for the unit testing of the software. Its primary text is about 25
pages longer. This consists of the scope of the standard approach for the unit testing of the software.

5EVAUATING ANSI1/IEEE2 STANDARD 8293 AND ANSI/IEEE STANDARD 1008
Nevertheless, its date, the activity never considers the tasks of classifying various forms related to
white-box testing (Pibida & Bunting, 2017). Above all, the query that the testing is the unit is done
with conformity for the standard is never actually denoted. However, the standard has been seen just
as the principle instead of the actual standard.
3. Responses to various questions for the above standards:
3.1. Standard names:
The name of the standards is ANSI/IEEE Std 829 and ANSI/IEEE Std 1008:1987.
3.2. Holding of the copyright of the standards:
“The Institute of Electrical and Electronics Engineers Standards Association” and “American
National Standards Institute” are found to be holding the copyrights of these standards.
3.3. Universities involved:
Amongst the various acknowledged contributors to the document, the IEEE-SEC or the
“IEEE Standards Education Committee” is involved here. This is a joint committee of IEEE-EAB
and IEEE-SA.
3.4. Intent and scope of the standard:
The IEEE standards assure that the implements have been utilizing the essential patented
technology of the standards. A vital element of the patent policy of IEEE includes FRAND
commitment. This the voluntary contractual commitment. This signifies the patent holders having
patented technology. This has adopted the standards of IEEE (Beebe, 2019). This is intended to be
accepted as the sufficient compensation of a non-discriminatory, reasonable and fair royalty for
using the third-party. On the other hand, the ANSI accredits the standards. These are created by
various representatives of various standards, consumer groups and government agencies,

6EVAUATING ANSI1/IEEE2 STANDARD 8293 AND ANSI/IEEE STANDARD 1008
organizations and so on. It assures that the performances and characteristics of the products remain
constant. This helps the people to use similar terms and definitions and the products get tested in a
similar manner (Stepanova, 2019). Further, the ANSI is also found to be accrediting the business that
conducts the personal certifications and productions as per the internal standards.
3.5. Key terms and different understanding required for the standard to be applied and
understood:
Securing sponsorships:
The sponsoring organizations have been in supervising and coordinating the development of
standards from starting to finish.
Project authorization:
In order to achieve the authorization of the project, PAR or Project Authorization Request is
to be submitted.
Drafting standard:
The working team must prepare the drafts as the suggested standard.
Balloting:
The department of the IEEE standard has been sending the invitation to the ballot for the
people who have been expressing the interest in the standard of the subject matter.
Final vote:
Every member of the IEEE-SA standards boards has been placing the ultimate vote over the
standard document submitted. At various cases, the external members are invited for voting. They
have been considering most of the votes of the board of standards. This is to achieve the ultimate

7EVAUATING ANSI1/IEEE2 STANDARD 8293 AND ANSI/IEEE STANDARD 1008
approval of the standard. Commonly, as the RevCom makes any recommendation of the approval,
the bard of the standards has been voting has been approving the standard (Sneed & Prentner, 2016).
3.6. Consequences of deploying the standards:
The standards help in testing the “look and feel” of the system. It is able to include the
environment and others. Further, it is useful in testing performances. Having complicated current
architectures, the performance analysis is complicated. Then, there is testing of concurrent and real-
time systems. It needs particular measures like various in-circuit emulators (Basem & Ali, 2017).
3.7. Relevance of software testing:
First of all, it is helpful for usability testing. This is to check as the user interface has been
using and analysed. This is concerned particularly to the use of the deployment. It is not a type of
testing that is automated. Then there is accessibility testing. Lastly, there is security testing
(Leszczyna, 2018). This is vital for the software that the confidential processing of data for
preventing the intrusion of systems through hackers. The standards help in the type of testing that is
conducted for analysing the degree for which the test team, information and related data are secured
(Rust, Flood & McCaffery, 2016). This happens as the unauthorized systems and persons can never
use, modify or read. Here the unauthorized systems and persons have never been denying access to
that.
4. Discussing and listing the commonalities and differences between the two:
For the documents, the subjective nature of information testing is undertaken from the side
most of the suppliers. Moreover, the repeatable tests have been clearly identifying the outcomes
underlying the process of testing (Koh, 2016). Both, of them, are simple in specifying the test that
has been completely uneconomic. Here, there is a broad range of software. The approach of testing

8EVAUATING ANSI1/IEEE2 STANDARD 8293 AND ANSI/IEEE STANDARD 1008
has been addressing the complicated software having less effect on most of the developers of
software. Moreover, they have possessed conceptual simplicity. There is an important issue for
ANSI/IEEE Std 829 because of the cost implications of greater test of different figures of metrics.
Moreover, they have conceptual simplicities (Talib, 2016). On the other hand, ANSI/IEEE Std 1008
can be used primarily for defining the testing. This is undertaken as the event takes place. Here, the
relative testing methods have been used necessity can be considered.
5. Conclusion:
The above study is helpful for evaluating the requirements of the software. This happens the
inputs for testing of the ultimate solution. Further, they have been critically analyzing and evaluating
the techniques and tools for supporting the process of testing. Further, the report has developed an
effective analysis to select and apply measures and models. These are used to test that are compliant
with suitable standards of the professional industry like IEEE and ACS. Then, they can critically
evaluate and assess the software requirements and suggested solutions. Apart from this, a complex
decision can be applied for making to choose the proper techniques of testing. Thus the study is
useful to document the professional level management, quality assurances, planning and testing of
documentation for the system of the software. Lastly, the investigation is helpful for efficient testing
tools for the software systems of various scales and levels of tests. Moreover, there are maintenance
and developments of plans to schedule the assurance of quality activities. This involves the testing of
software.

9EVAUATING ANSI1/IEEE2 STANDARD 8293 AND ANSI/IEEE STANDARD 1008
6. References:
Basem, A. M., & Ali, H. (2017). Data Distribution Service (DDS) based implementation of Smart
grid devices using ANSI C12. 19 standard. Procedia Computer Science, 110, 394-401.
Beebe, N. H. (2019). A Bibliography of Publications on Software Standards.
Jambak, M. I., Ahmad, H., Mohammed, M. A. H., Jumaat, S. A., & Sidik, M. A. B. (2017, August).
Evaluation of grounding system for AC substation using sub-ground (SG) software for
novice professionals: Interpretation based on IEEE Std. 80-1986. In 2017 International
Conference on Electrical Engineering and Computer Science (ICECOS) (pp. 321-327).
IEEE.
Koh, S. (2016). Cause-and-Effect Perspective on Software Quality. Journal of Information
Technology Applications & Management, 23(3), 71-86.
Leszczyna, R. (2018). Cybersecurity and privacy in standards for smart grids–A comprehensive
survey. Computer Standards & Interfaces, 56, 62-73.
Pibida, L. S., & Bunting, H. (2017). Validation Testing of ANSI/IEEE N42. 43 Standard
Requirements for Radiation Detection Backpacks| NIST (No. NIST Interagency/Internal
Report (NISTIR)-7476).
Pröll, R., & Bauer, B. (2018). Toward a Consistent and Strictly Model-Based Interpretation of the
ISO/IEC/IEEE 29119 for Early Testing Activities. In MODELSWARD (pp. 699-706).
Rust, P., Flood, D., & McCaffery, F. (2016). Creation of an IEC 62304 compliant software
development plan. Journal of Software: Evolution and Process, 28(11), 1005-1010.

10EVAUATING ANSI1/IEEE2 STANDARD 8293 AND ANSI/IEEE STANDARD 1008
Sneed, H. M., & Prentner, W. (2016, October). Analyzing Data on Software Evolution Processes. In
2016 Joint Conference of the International Workshop on Software Measurement and the
International Conference on Software Process and Product Measurement (IWSM-
MENSURA) (pp. 1-10). IEEE.
Sneed, H., & Seidl, R. (2017). Software Testdokumentation nach den IEEE und ISO Standards.
Softwaretechnik-Trends, 37(1).
Stepanova, V. (2019). Quality Control Approach in Developing Software Projects. International
Journal of Computer Science and Software Engineering, 8(1), 1-5.
Talib, M. A. (2016). Towards early software reliability prediction for computer forensic tools (case
study). SpringerPlus, 5(1), 827.