Disclaimer: This is an example of a student written essay.
Click here for sample essays written by our professional writers.

Any opinions, findings, conclusions or recommendations expressed in this material are those of the authors and do not necessarily reflect the views of UKEssays.com.

Research on Software Testing and Standards

Paper Type: Free Essay Subject: Information Technology
Wordcount: 1801 words Published: 8th Feb 2020

Reference this


This Assignment is for understanding of the Software testing and Standard to analyze the relation between researches on the particular process used to make a standard. In this report, I will analyze the information about the standard which is named as “ANSI/IEEE 1008-1987” on the invention of “The SOFTWARE UNIT TESTING”.  This paper covers both the development of ANSI/IEEE 1008-1987 and compliance with the standard that has been finished.

Get Help With Your Essay

If you need assistance with writing your essay, our professional essay writing service is here to help!

Essay Writing Service

This standard’s major objective is to specify a standard approach to software unit checking out that can be used as a foundation for sound software engineering practice. A 2nd goal is to describe the software engineering principles and checking out assumptions on which this widespread approach is based. A 1/3 goal is to provide education and aid information to help with the implementation and utilization of the trendy unit checking out approach. The technique used to produce software program unit checking out consequences which are described via presenting a records of its development, displaying how initial chaotic improvement advanced with ride into a systematic process. This method was found to endure a robust resemblance to the software program engineering process, and borrowed methods from it, drawing especially from these that guide verification and validation. The understanding received from this development has to be relevant to many areas of standardization.

Analysis Report on the Standard – ANSI/IEEE 1008-1987

      Name of the standard and the copyright of the standard

The name of the standard is ANSI/IEEE 1008-1987 for Software Unit Testing. The copyright of this standard has been reserved by “The Institute of Electrical and Electronics Engineer Inc., 3 Park Avenue, New York, NY 10016-5997, USA”. (Approved on 11 December 1986 by IEEE-SA Standards Board and approved on 18 April 2003 by American National Standards Institute ).

      Participated Universities

There are four universities are acknowledged and involved in this research:

  • Boston University
  • Johns Hopkins University Applied Physics Laboratory
  • University of DC
  • University of Texas, Arlington

      Scope of the standard

Software unit testing is a method that consists of the performance of check planning, the acquisition of a check set, and the dimension of a take a look at unit against its requirements. Measuring entails the use of sample information to exercise the unit and the contrast of the unit’s true behavior with its required behavior as unique in the gadgets requirements documentation.

This general defines an integrated method to systematic and documented unit testing. The method uses unit format and unit implementation information, in addition to unit requirements, to decide the completeness of the testing. This standard requires the performance of each activity. For every mission inside an activity, this well-known requires both that the venture be performed, and that preceding outcomes be accessible and be reverified. This preferred also requires the preparation of two files specific in ANSI/IEEE standard 829-1983. These files are the Test Design Specification and the Test Summary Report. This well-known is applicable whether or not the unit tester is additionally the developer.

      Key terms and understandings needed for the standard

This area defines key phrases used in this standard wanted for the appreciation and implementation:

  1. Data characteristic: An inherent, per chance accidental, trait, quality, or property of data.
  2. Software feature: A software program attribute certain or implied by requirements documentation.
  3. Software test incident: Any task happening during the execution of a software program take a look at that requires investigation.
  4. Non-procedural programming language: A laptop programming language used to specific the parameters of a trouble instead than the steps in a answer.
  5. Procedural programming language: A computer programming language used to express the sequence of operations to be performed through a computer.
  6. Software characteristic: An inherent, perchance accidental, trait, quality, or property of software.
  7. Unit requirements documentation: Documentation that sets forth the functional, interface, performance, and design constraint requirements for the test unit.

      Result of this standard

The consequences of some basic check planning tasks follow to all trying out levels (for example, discover protection and privacy constraints). Such duties are not viewed a part of the unit testing process, although they directly have an effect on it. While the widespread identifies a want for failure analysis records and software fault correction, it does not specify a software debugging process. This trendy does not tackle different factors of a comprehensive unit verification and validation process, such as critiques (for example, walkthroughs, inspections), static analysis (for example, consistency checks, records drift analysis), or formal analysis (for example, proof of correctness, symbolic execution). This well-known does now not require the use of particular take a look at facilities or tools. This general does now not suggest any specific methodology for documentation control, configuration management, best assurance, or management of the testing process.


      Specific relevance to software testing

There are many facts that are identified in this standard, respectively which portrays the relevancy of ANSI/IEEE 1008-1987 for Software Unit Testing. This standard represents consensus on the definition of good software engineering practice. Some organizations use practices similar to the process specified here while others organize this work quite differently. In any case, it will involve considerable change for many organizations that choose to adopt it. This section species the activities involved in the unit testing process and describes the associated input, tasks, and output. When more than one unit is to be unit tested (for example, all those associated with a software project), the Plan activity should address the total set of test units and should not be repeated for each test unit. The other activities must be performed at least once for each unit. ANSI/IEEE Std 829-1983, IEEE Standard for Software Test Documentation, describes the basic information needs and results of software testing. This unit testing standard requires the use of the test design specification and test summary report specified in ANSI/IEEE Std 829-1983. This standard is one of a series aimed at establishing the norms of professional practice in software engineering. Any of the other software engineering standards in the series may be used in conjunction with it.

      Difference between the Research paper and Standard

Testing entails the size of behavior against requirements. Although one speaks informally of interface testing, kingdom testing, or even two requirement testing, what is supposed is measuring proper behavior related with an interface,  state, or requirement, against the corresponding required behavior. The degrees of venture checking out (for example, acceptance, system, integration, unit) are specified in challenge plans, verification and validation plans, or two typical take a look at plans. Also protected is the unit test planning records that is relevant to all units being examined (for example, completeness requirements, termination requirements, typical useful resource requirements).


Software unit testing is a product testing strategy by which singular units of source code, sets of one or more PC systems modules along  with the related control information, methodology, and working techniques are tried and tested to figure out if they are fit to be used or not. In other words, the unit tests check whether the software application is working fine and keeps on filling-in as the developer has proposed or planned. There are numerous particular subjects, for example, Test Driven Development (TDD) and the red-green-refactor advancement technique; however, it has been observed that these techniques jumble up the reason that underlies unit testing. Software unit testing can save your time as it can facilitate you to make huge and rapid changes for improvements in the code. You know that it works well for the code if you have run the unit tests properly. When you make any modifications in the code, you have to run the tests again to make sure that the behavior has not changed.


      Retrieved from 1008-1987 IEEE Standard for Software Unit Testing (Online): IEEE/IET Electronic Library (IEL) IEEE (Institute of Electrical and Electronics Engineers).

      Retrieved from https://ieeexplore-ieee-org.ezproxy.federation.edu.au/document/27763

      Retrieved from https://standards.globalspec.com/std/759325/ieee-1008

      Retrieved from https://webstore.ansi.org/Standards/IEEE/IEEE10081987R2009

      Unit Testing – Software Testing Fundamentals. (2019). Retrieved from http://softwaretestingfundamentals.com/unit-testing/


Cite This Work

To export a reference to this article please select a referencing stye below:

Reference Copied to Clipboard.
Reference Copied to Clipboard.
Reference Copied to Clipboard.
Reference Copied to Clipboard.
Reference Copied to Clipboard.
Reference Copied to Clipboard.
Reference Copied to Clipboard.

Related Services

View all

DMCA / Removal Request

If you are the original writer of this essay and no longer wish to have your work published on UKEssays.com then please: