Services


An overview of software testing

Industries


Today’s automotive industry must deliver high levels of innovation and flexibility in shorter cycles, at the lowest cost and the highest quality. Software represents both significant opportunity for innovation as well as increased complexity and risk. Integrity reduces the overwhelming complexity of developing software intensive products, improves productivity and quality, streamlines compliance, and provides complete visibility throughout the product development life cycle. Automotive engineering organizations using Integrity have the capabilities they need to accelerate innovation, improve supply chain collaboration, diversify product offerings  and move products to market faster and more efficiently.

Triple V diagram

Due to our proven success, industry experience and technically superior solutions, leading global enterprises in the automotive engineering industry continue to make PTC a trusted partner in solving their most complex and critical software development challenges:

  • Automotive engineering companies are targeting software for 90% of product changes. Depending on the nature and technology of the system, the volume and velocity of engineering change driven from software is 10 to 100 times greater than from hardware, and traditional tools and integrations hinder communication andcollaboration, driving up costs and increasing the time required to move products into the market
  • Compliance to safety and environmental regulations and standards such as Automotive SPICE and ISO 26262 improves product and process quality, but can significantly drive up costs and impact time-to-market without effective management and a high degree of automation
  • Understanding release readiness across the isolated groups and systems in today’s global automotive development ecosystem is time consuming and error prone and risks making key decisions on data that is out-of-date and incomplete. This reduces productivity and can affect product quality
  • Consumer and regulatory pressure to develop higher quality and more sophisticated products is pushing development costs and time-to-market to unsustainable levels

Electronic Document Management

Reference: http://www.electronicdocumentmanagement.org.uk/

Testing Terminology


Definition:  Testing is a process in which the defects are identified, isolated (separated), subject (sending) for rectification and ensured that the product is defect free in order to produce a quality product in the end and hence customer satisfactoion.

Reliability:  The probability that software will not cause the failure of a system for a specified period of time under specified conditions

Defect:  The departure of a quality characteristic from its specified value that results in a product or service not satisfying its normal usage requirements

Fault :    A manifestation of an ERROR in software. Faults are also known colloquially as defaults or bugs.   A fault , if encourage, may cause a failure which is a deviation of the software from its intended purpose.

Error :   A human action that produces an incorrect result.

Quality :   The totality of the characteristics of an entity that bear on its ability     to satisfy stated or implied needs.

Testing and Risk : How much would you be willing to perform if the risk of failure were negligible? Alternatively, how much testing would you be willing to perform if a single defect could cost you your life’s savings, or, even more significantly, your life?

Testing and Quality:  Testing identifies faults whose removal increases the software quality by increasing the software’s potential reliability.

Testing  is the measurement of software quality.

We measure how closely we have achieved quality by testing the relevant factors such as correctness, reliability, usability, maintainability, reusability, testability etc.

Failure  – the act of a product not behaving as expected – the manifestation of a fault.

Validation – establishing the correspondence between the software and its specification – are we now building the correct product?  Also known as ‘black box’ testing.

Verification –  are  we now building the product  correctly? Also known as ‘white box testing’.

Test Case – the collection of inputs, predicted results and execution conditions for a single test

Pass/fail criteria – decision rules  used to determine whether  a product passes or fails a given test

Test suites – a collection of test cases necessary to “adequately” test a product

Test Plan– a document describing the scope, approach, resources and schedule of intended testing activity- identifies  features to be testing tasks, who will do each task, and any risks requiring contingency planning.

 
 

Software Testing Inside and Out

The separation of debugging from testing was intially introduced by Glenford J. Myers in 1979. Although his attention was on breakage testing ‘a successful test is one that finds a bug.’

Historically there has not been a generally accepted set of testing definations.