SlideShare a Scribd company logo
Testing & Evaluating Software Solutions Testing and Evaluation of Software Solutions
What is Testing? Testing is a process that checks to see whether the solution meets the design specifications and is free from errors. This chapter is concerned with more advanced testing techniques that prepare the product for release on the software market. Testing & Evaluation of Software Solutions Testing the Software Solutions Reporting on the testing process
What is Testing? Testing is done throughout the entire software development cycle: Defining & Understanding the problem Planning & Design of Software Solutions Implementation of Software Solutions Feasibility Study Desk Checking Algorithms` Debugging Tools
Comparison against original design specifications The firsts step of testing a solution is to ensure that the program that you have created meets the design specifications outlined during the ‘defining & understanding the problem’ stage. Design Specifications  – are a list of criteria that must be met in the end product. These specifications are no different to the specifications that you would have for buying a new car.
Comparison against original design specifications Outline a list of criteria that you would use for purchasing a car?
Comparison against original design specifications The following guidelines are used to ensure you have created measurable specifications: Clarify any vague terms (e.g. ‘most’, ‘some’ and ‘usually’) Avoid use of vague verbs (e.g. ‘processed’, ‘eliminated’ and ‘handled’) as they may be interpreted in more that one way. Calculations should be accompanied by examples.
Comparison against original design specifications The following guidelines are used to ensure you have created measurable specifications: Don not use incomplete statements such as ‘e.t.c’ and ‘so on’. Ensure the specification can be physically measured. Incorporate pictures and diagrams to show structure.
Comparison against original design specifications Design specifications are often referred to as your ‘objectives’. The aim of the project is to implement and solve each objective. Objectives are written in such a way that a pass or fail can be allocated to them.
Comparison against original design specifications Identify a tool that could be implemented to test the successful completion of objectives.
Comparison against original design specifications Each objective is tested and if faults are encountered then the aspect of the product that failed is altered until the objective is realised. This is why it is important to test your solution continually throughout the development process.
Testing Hierarchy Testing Alpha Beta White-Box Black-Box Live Data Module Program System Large Files Response Times Volume Data
Broad Categories of Testing Alpha Testing Testing by the personnel within the software development company. Beta Testing Testing of the final solution by a limited number of users outside the company in real world conditions.
What is Black-Box Testing? Often referred to as ‘functional testing’ as it checks the inputs against expected and actual outputs. Does not identify the source of the problem but rather to identify that a problem exists. Once the problem has been identified it is necessary to move to ‘white-box’ testing to find and correct the error.
Black-Box Procedures 1.  Range (Boundary) Checking Tests the upper and lower ranges of inputted data. E.g. Numbers that may cause errors. 2.  Equivalence Partitioning Testing the validation procedures of input fields. E.g. Inputting 22a for the age field.
What is White-Box Testing? Is called ‘structural testing’ as it concentrates on processes involved in the program rather than input-output. This helps with the generation of test data as an explicit knowledge of the internal workings of the item being tested is needed.
White-Box Procedures 1. Statement Coverage Testing Test data would be chosen to test each statement in a module. E.g. A flag (Test true and false) 2. Decision Condition Testing Test data selected to test each decision. E.g. Testing selection and repetition statements.
Generating relevant test data for complex solutions Often the process of generating test data is a expensive and time-consuming event due to the large numbers of variables used within a solution. For this reason developers use a wide range of procedure given the situation which are organised into two main techniques: Black-Box Testing White-Box Testing
Black-Box - Question 1 Create a set of boundary (Range) test data items for an egg sorting machine. The machine works as follows: “ Eggs are graded as ‘SMALL’ if they weigh less than 50 grams, ‘MEDIUM’ if their weight is from 50 grams to less than 60 grams., ‘LARGE’ if their weight is from 60 grams to less than 70 grams and ‘EXTRA LARGE’ if their weight is 70 grams or more.”
Answers 49 50 59 60 69 70 71 Small Medium Large Extra Large
White-Box - Question 2 Create a set of test data for the module below employing the ‘statement coverage’ method? BEGIN Get Wage Get Tax CaseWhere Wage <$20,000 :  Module A <$40,000 :  Module B Otherwise :  Module C EndCase IF Tax = True THEN Module D ELSE Module E END
Answers $19,999, True $19,999, False $39,999, True $39,999, False $40,001, True $40,001, False
White-Box - Question 3 Create a set of test data for the module below employing the ‘Decision coverage’ method? BEGIN Get Wage Get Tax CaseWhere Wage <$20,000 :  Module A <$40,000 :  Module B Otherwise :  Module C EndCase IF Tax = True THEN Module D ELSE Module E END
Levels of Testing There are various levels of testing a system. Each is progressive and must be undertaken to ensure success. Testing will commence at the lowest level. 3. System Testing 2. Program Testing 1. Module Testing
Module (Unit) Testing Each individual module is tested to make sure that it is free from errors. Treats the modules as stand-alone applications that do not require any other components of the program to function. Normally, the use of libraries of code ensures that most modules used are appropriate.
Module (Unit) Testing Identify the tool that is used to substitute the mainline of the program so that the module can be tested.
Program Testing Ensures that all the modules work correctly together. This level concentrates on the interface and the relationship of each module to the main program. Uses both bottom-up and top-down testing of the program to ensure that the program meets the criteria set out in the design specifications.
System Testing Involves testing the program in environments outside development. Different processors, operating systems, software configurations and peripheral devices may cause errors to occur. This testing is done by those outside the development team.
The System 0110011001010101110011 Identify the names of the five (5) elements in a computer system.
Question 4 PaintPro is a new graphic manipulation software that allows users to scan images or input saved images and modify them via a variety of different filters. Identify what area system testing would concentrate and the reasons why.
Question 4 - Answer Software If scanned images are to be inputted the program must be able to collaborate with appropriate scanner drivers.
Use of Live Test Data Live test data is real test data that the program will work with. Up to this point the program has been tested with data created by the development team for the purpose of finding errors. Like testing a new car on a test track. Results will be obtained regarding how the car performs within the environment in which it will be used.
Use of Live Test Data
Use of Live Test Data For most products live test data should be created to test each of the following conditions: Large file sizes Mix of transaction times Response times Volume data Interfaces between modules Comparison with program test data
Large File Sizes During testing small data files are used. It is appropriate to test the program with large data sets to highlight problems with data access. For example a program that is created process transactions within a video store will now have to process 10,000 customers and access a video stock list of 15,000 videos.
Large File Sizes The limits of the program need to be tested to reveal any inefficiencies such as: Slow processing times. Slow network transfer rates. Effect on other users or programs.
Question 5 Identify TWO different types of errors that could be found when testing large file sizes.
Mix of Transaction Types Highlighting any errors that may occur during transactions being completed. This may include: Multiple users using the program. Manipulation of data in different ways.
Response Times Are the times required to complete a process. Any processes that are likely to take more than one second should provide user feedback. Both heavy and light loads should be checked.
Volume Data Stress testing to see how the program performs with volumes of data beyond normal expectations is a way of checking efficiency and robustness. Multiple users or a large number of processes occurring simultaneously may be required. CASE tools can also be used.
Question 6 Banking software programs are faced with a multitude of customers trying to access records continuously because of the introduction of online-banking, EFTPOS and ATM’s. Identify the areas that you would target regarding live testing such a system.
Question 6 - Answer Large File Sizes – Trying to see the maximum withdrawals, deposits ect. Mix of transaction types – Changing different applications i.e. BPAY, EFTPOS, different computers. Response Times – Measure the time taken on different Internet Connections. Volume Test Data – 50+ users accessing one account.
Interfaces Between Modules In this section we are interested in testing the performance of interfaces that connect modules and programs. Tests should examine the accuracy of data being passed as well as response times and the ability to cope with large volumes of data.
Comparison with test data This involves the use of test data that checks the expected outputs of processing. Because the outputs are already known, this testing process ensures the final product is able to perform processing correctly.
Benching Marking Bench marking is the process of evaluating a product through a series of tests to meet a standard of excellence. This process involves comparing competitors products to measure quality assurance.
Question 7 Identify the areas that a company may employee in which to base its benchmarking tests. i.e. Overall Performance.
Question 7 - Answer Overall Performance Quality Usability Robustness Maintainability Productivity
Quality Assurance The quality of a product is measured against how well the product meets or exceeds users’ expectations. The following factors are considered: Correctness:  Does it do what it is supposed to do? Reliability: Does it do it all the time? Efficiency: Does it do it the best way possible? Useability: Is it designed for the end-user. Flexibility: Can it be modified?
Quality Assurance Portability: Will it work with other hardware? Re-useability: Can it be used again? Integrity: Is it secure? It is used to assure customers of the quality of the product. Employs a set of measurable standards set out by the ISO (International Standards Organisation)
Question 8  A software application has been written to control the operation of a digital video camera. The camera performs all the usual video camera functions and some new ones. For example, the camera can be set to commence filming once it detects movement. This is useful for wildlife photographers. Describe the types of tests that could be conducted by The quality assurance company to determine reliability, efficiency and useability of this product.
Question 8 - Answers Reliability – Beta test using live test data to test how the camera performs under large volumes of data. i.e multiple animals or long sequences. Efficiency – Benchmarking could take place by giving a competitors product to compare. Useability – Beta testing and surveying users regrading useability of the camera and its functions.

More Related Content

PPT
The art of system and solution testing
PPT
Reporting On The Testing Process
PDF
What is Test Matrix?
PPT
Testing Framework
PPTX
Testing and types of Testing
PPTX
Types of testing
PPTX
Regression testing
PPT
Rob Baarda - Are Real Test Metrics Predictive for the Future?
The art of system and solution testing
Reporting On The Testing Process
What is Test Matrix?
Testing Framework
Testing and types of Testing
Types of testing
Regression testing
Rob Baarda - Are Real Test Metrics Predictive for the Future?

What's hot (19)

PPTX
Testing strategies
PPTX
H testing and debugging
PPT
want to contact me login to www.stqa.org
PPTX
Software testing fundamentals
PDF
4. The Software Development Process - Testing
PPTX
Importance of Software testing in SDLC and Agile
PPT
Testing Types And Models
PPT
Test Levels & Techniques
PPT
'Model Based Test Design' by Mattias Armholt
PPT
Lesson 3...PPT 2
PDF
C.V, Narayanan - Open Source Tools for Test Management - EuroSTAR 2010
PPTX
T19 performance testing effort - estimation or guesstimation revised
PPTX
risk based testing and regression testing
PPT
Software testing strategies
PPT
Testing
PDF
Introduction to automation testing
PPT
Manual testing concepts course 1
PPT
Software Testing 101
PDF
Software testing methods, levels and types
Testing strategies
H testing and debugging
want to contact me login to www.stqa.org
Software testing fundamentals
4. The Software Development Process - Testing
Importance of Software testing in SDLC and Agile
Testing Types And Models
Test Levels & Techniques
'Model Based Test Design' by Mattias Armholt
Lesson 3...PPT 2
C.V, Narayanan - Open Source Tools for Test Management - EuroSTAR 2010
T19 performance testing effort - estimation or guesstimation revised
risk based testing and regression testing
Software testing strategies
Testing
Introduction to automation testing
Manual testing concepts course 1
Software Testing 101
Software testing methods, levels and types
Ad

Viewers also liked (20)

PDF
6. The Software Development Process - Evaluation
PPT
Evaluation question 4 software used
PPTX
Software Evaluation
DOC
Df dtutorial
PPT
Evaluation A Software
PPTX
Software Evaluation Assignment
PPTX
Evaluation, software and hardware
DOC
Df dtutorial
PPT
Software Selection & Evaluation
PDF
Software Testing Interview Q&A – part 1
DOC
Multiplateform testing
PPTX
Intro to Unit Testing with test Driven Development
PDF
Fundamentals of Testing 2
PDF
Software project management
PDF
Software Testing and Quality Assurance Assignment 2
DOCX
Some Commonly Asked Question For Software Testing
DOCX
Fresher interview question for software testing (QA) manual + basic automation
DOC
Manual Testing.
PPTX
Gosecure Software Testing
PPTX
Software testing - basics
6. The Software Development Process - Evaluation
Evaluation question 4 software used
Software Evaluation
Df dtutorial
Evaluation A Software
Software Evaluation Assignment
Evaluation, software and hardware
Df dtutorial
Software Selection & Evaluation
Software Testing Interview Q&A – part 1
Multiplateform testing
Intro to Unit Testing with test Driven Development
Fundamentals of Testing 2
Software project management
Software Testing and Quality Assurance Assignment 2
Some Commonly Asked Question For Software Testing
Fresher interview question for software testing (QA) manual + basic automation
Manual Testing.
Gosecure Software Testing
Software testing - basics
Ad

Similar to Testing Software Solutions (20)

PPT
12 sdd lesson testing and evaluating
PPT
Sdd Testing & Evaluating
PPTX
PPTX
dynamic testing for polytechnic students
PPT
Defect Testing in Software Engineering SE20
PPT
Software Testing
PPT
Types of Software Testing
PPT
ISTQB, ISEB Lecture Notes
PPT
Testing
PPT
AutoTest.ppt
PPT
AutoTest.ppt
PPT
AutoTest.ppt
PPT
ISTQB / ISEB Foundation Exam Practice -1
PPT
SE-Testing.ppt
PPTX
Black box software testing
PPT
Software Engineering Lec 10 -software testing--
PPTX
SWE-6 TESTING.pptx
PPT
&lt;p>Software Testing&lt;/p>
12 sdd lesson testing and evaluating
Sdd Testing & Evaluating
dynamic testing for polytechnic students
Defect Testing in Software Engineering SE20
Software Testing
Types of Software Testing
ISTQB, ISEB Lecture Notes
Testing
AutoTest.ppt
AutoTest.ppt
AutoTest.ppt
ISTQB / ISEB Foundation Exam Practice -1
SE-Testing.ppt
Black box software testing
Software Engineering Lec 10 -software testing--
SWE-6 TESTING.pptx
&lt;p>Software Testing&lt;/p>

More from gavhays (18)

PPT
Data types
PPT
End user development
PPT
Representation Of Data
PPT
N301 Designing Circuits
PPT
Integer Representation
PPT
Binary Arithmetic
PPT
Understanding Flip Flops
PPT
Programming Hardware Devices
PPT
Plp
PPT
Electronic Circuits
PPT
Boolean Algebra
PPT
Sdd Maintenance Of Software Solutions
PPT
Sdd Documentation
PPT
S D D Program Development Tools
PPT
SDD Translation
PPT
The Role Of The Cpu
PPT
Sdd Syntax Descriptions
PPT
Interface Design
Data types
End user development
Representation Of Data
N301 Designing Circuits
Integer Representation
Binary Arithmetic
Understanding Flip Flops
Programming Hardware Devices
Plp
Electronic Circuits
Boolean Algebra
Sdd Maintenance Of Software Solutions
Sdd Documentation
S D D Program Development Tools
SDD Translation
The Role Of The Cpu
Sdd Syntax Descriptions
Interface Design

Recently uploaded (20)

PPTX
Effective Security Operations Center (SOC) A Modern, Strategic, and Threat-In...
PDF
Unlocking AI with Model Context Protocol (MCP)
PDF
The Rise and Fall of 3GPP – Time for a Sabbatical?
PPTX
Big Data Technologies - Introduction.pptx
PDF
Blue Purple Modern Animated Computer Science Presentation.pdf.pdf
PPTX
PA Analog/Digital System: The Backbone of Modern Surveillance and Communication
PDF
Modernizing your data center with Dell and AMD
PDF
Agricultural_Statistics_at_a_Glance_2022_0.pdf
PPT
“AI and Expert System Decision Support & Business Intelligence Systems”
PDF
Electronic commerce courselecture one. Pdf
PPTX
Digital-Transformation-Roadmap-for-Companies.pptx
PDF
KodekX | Application Modernization Development
PDF
NewMind AI Monthly Chronicles - July 2025
PDF
Approach and Philosophy of On baking technology
PDF
Machine learning based COVID-19 study performance prediction
PDF
Peak of Data & AI Encore- AI for Metadata and Smarter Workflows
PDF
CIFDAQ's Market Insight: SEC Turns Pro Crypto
PPTX
Detection-First SIEM: Rule Types, Dashboards, and Threat-Informed Strategy
PPT
Teaching material agriculture food technology
PDF
Spectral efficient network and resource selection model in 5G networks
Effective Security Operations Center (SOC) A Modern, Strategic, and Threat-In...
Unlocking AI with Model Context Protocol (MCP)
The Rise and Fall of 3GPP – Time for a Sabbatical?
Big Data Technologies - Introduction.pptx
Blue Purple Modern Animated Computer Science Presentation.pdf.pdf
PA Analog/Digital System: The Backbone of Modern Surveillance and Communication
Modernizing your data center with Dell and AMD
Agricultural_Statistics_at_a_Glance_2022_0.pdf
“AI and Expert System Decision Support & Business Intelligence Systems”
Electronic commerce courselecture one. Pdf
Digital-Transformation-Roadmap-for-Companies.pptx
KodekX | Application Modernization Development
NewMind AI Monthly Chronicles - July 2025
Approach and Philosophy of On baking technology
Machine learning based COVID-19 study performance prediction
Peak of Data & AI Encore- AI for Metadata and Smarter Workflows
CIFDAQ's Market Insight: SEC Turns Pro Crypto
Detection-First SIEM: Rule Types, Dashboards, and Threat-Informed Strategy
Teaching material agriculture food technology
Spectral efficient network and resource selection model in 5G networks

Testing Software Solutions

  • 1. Testing & Evaluating Software Solutions Testing and Evaluation of Software Solutions
  • 2. What is Testing? Testing is a process that checks to see whether the solution meets the design specifications and is free from errors. This chapter is concerned with more advanced testing techniques that prepare the product for release on the software market. Testing & Evaluation of Software Solutions Testing the Software Solutions Reporting on the testing process
  • 3. What is Testing? Testing is done throughout the entire software development cycle: Defining & Understanding the problem Planning & Design of Software Solutions Implementation of Software Solutions Feasibility Study Desk Checking Algorithms` Debugging Tools
  • 4. Comparison against original design specifications The firsts step of testing a solution is to ensure that the program that you have created meets the design specifications outlined during the ‘defining & understanding the problem’ stage. Design Specifications – are a list of criteria that must be met in the end product. These specifications are no different to the specifications that you would have for buying a new car.
  • 5. Comparison against original design specifications Outline a list of criteria that you would use for purchasing a car?
  • 6. Comparison against original design specifications The following guidelines are used to ensure you have created measurable specifications: Clarify any vague terms (e.g. ‘most’, ‘some’ and ‘usually’) Avoid use of vague verbs (e.g. ‘processed’, ‘eliminated’ and ‘handled’) as they may be interpreted in more that one way. Calculations should be accompanied by examples.
  • 7. Comparison against original design specifications The following guidelines are used to ensure you have created measurable specifications: Don not use incomplete statements such as ‘e.t.c’ and ‘so on’. Ensure the specification can be physically measured. Incorporate pictures and diagrams to show structure.
  • 8. Comparison against original design specifications Design specifications are often referred to as your ‘objectives’. The aim of the project is to implement and solve each objective. Objectives are written in such a way that a pass or fail can be allocated to them.
  • 9. Comparison against original design specifications Identify a tool that could be implemented to test the successful completion of objectives.
  • 10. Comparison against original design specifications Each objective is tested and if faults are encountered then the aspect of the product that failed is altered until the objective is realised. This is why it is important to test your solution continually throughout the development process.
  • 11. Testing Hierarchy Testing Alpha Beta White-Box Black-Box Live Data Module Program System Large Files Response Times Volume Data
  • 12. Broad Categories of Testing Alpha Testing Testing by the personnel within the software development company. Beta Testing Testing of the final solution by a limited number of users outside the company in real world conditions.
  • 13. What is Black-Box Testing? Often referred to as ‘functional testing’ as it checks the inputs against expected and actual outputs. Does not identify the source of the problem but rather to identify that a problem exists. Once the problem has been identified it is necessary to move to ‘white-box’ testing to find and correct the error.
  • 14. Black-Box Procedures 1. Range (Boundary) Checking Tests the upper and lower ranges of inputted data. E.g. Numbers that may cause errors. 2. Equivalence Partitioning Testing the validation procedures of input fields. E.g. Inputting 22a for the age field.
  • 15. What is White-Box Testing? Is called ‘structural testing’ as it concentrates on processes involved in the program rather than input-output. This helps with the generation of test data as an explicit knowledge of the internal workings of the item being tested is needed.
  • 16. White-Box Procedures 1. Statement Coverage Testing Test data would be chosen to test each statement in a module. E.g. A flag (Test true and false) 2. Decision Condition Testing Test data selected to test each decision. E.g. Testing selection and repetition statements.
  • 17. Generating relevant test data for complex solutions Often the process of generating test data is a expensive and time-consuming event due to the large numbers of variables used within a solution. For this reason developers use a wide range of procedure given the situation which are organised into two main techniques: Black-Box Testing White-Box Testing
  • 18. Black-Box - Question 1 Create a set of boundary (Range) test data items for an egg sorting machine. The machine works as follows: “ Eggs are graded as ‘SMALL’ if they weigh less than 50 grams, ‘MEDIUM’ if their weight is from 50 grams to less than 60 grams., ‘LARGE’ if their weight is from 60 grams to less than 70 grams and ‘EXTRA LARGE’ if their weight is 70 grams or more.”
  • 19. Answers 49 50 59 60 69 70 71 Small Medium Large Extra Large
  • 20. White-Box - Question 2 Create a set of test data for the module below employing the ‘statement coverage’ method? BEGIN Get Wage Get Tax CaseWhere Wage <$20,000 : Module A <$40,000 : Module B Otherwise : Module C EndCase IF Tax = True THEN Module D ELSE Module E END
  • 21. Answers $19,999, True $19,999, False $39,999, True $39,999, False $40,001, True $40,001, False
  • 22. White-Box - Question 3 Create a set of test data for the module below employing the ‘Decision coverage’ method? BEGIN Get Wage Get Tax CaseWhere Wage <$20,000 : Module A <$40,000 : Module B Otherwise : Module C EndCase IF Tax = True THEN Module D ELSE Module E END
  • 23. Levels of Testing There are various levels of testing a system. Each is progressive and must be undertaken to ensure success. Testing will commence at the lowest level. 3. System Testing 2. Program Testing 1. Module Testing
  • 24. Module (Unit) Testing Each individual module is tested to make sure that it is free from errors. Treats the modules as stand-alone applications that do not require any other components of the program to function. Normally, the use of libraries of code ensures that most modules used are appropriate.
  • 25. Module (Unit) Testing Identify the tool that is used to substitute the mainline of the program so that the module can be tested.
  • 26. Program Testing Ensures that all the modules work correctly together. This level concentrates on the interface and the relationship of each module to the main program. Uses both bottom-up and top-down testing of the program to ensure that the program meets the criteria set out in the design specifications.
  • 27. System Testing Involves testing the program in environments outside development. Different processors, operating systems, software configurations and peripheral devices may cause errors to occur. This testing is done by those outside the development team.
  • 28. The System 0110011001010101110011 Identify the names of the five (5) elements in a computer system.
  • 29. Question 4 PaintPro is a new graphic manipulation software that allows users to scan images or input saved images and modify them via a variety of different filters. Identify what area system testing would concentrate and the reasons why.
  • 30. Question 4 - Answer Software If scanned images are to be inputted the program must be able to collaborate with appropriate scanner drivers.
  • 31. Use of Live Test Data Live test data is real test data that the program will work with. Up to this point the program has been tested with data created by the development team for the purpose of finding errors. Like testing a new car on a test track. Results will be obtained regarding how the car performs within the environment in which it will be used.
  • 32. Use of Live Test Data
  • 33. Use of Live Test Data For most products live test data should be created to test each of the following conditions: Large file sizes Mix of transaction times Response times Volume data Interfaces between modules Comparison with program test data
  • 34. Large File Sizes During testing small data files are used. It is appropriate to test the program with large data sets to highlight problems with data access. For example a program that is created process transactions within a video store will now have to process 10,000 customers and access a video stock list of 15,000 videos.
  • 35. Large File Sizes The limits of the program need to be tested to reveal any inefficiencies such as: Slow processing times. Slow network transfer rates. Effect on other users or programs.
  • 36. Question 5 Identify TWO different types of errors that could be found when testing large file sizes.
  • 37. Mix of Transaction Types Highlighting any errors that may occur during transactions being completed. This may include: Multiple users using the program. Manipulation of data in different ways.
  • 38. Response Times Are the times required to complete a process. Any processes that are likely to take more than one second should provide user feedback. Both heavy and light loads should be checked.
  • 39. Volume Data Stress testing to see how the program performs with volumes of data beyond normal expectations is a way of checking efficiency and robustness. Multiple users or a large number of processes occurring simultaneously may be required. CASE tools can also be used.
  • 40. Question 6 Banking software programs are faced with a multitude of customers trying to access records continuously because of the introduction of online-banking, EFTPOS and ATM’s. Identify the areas that you would target regarding live testing such a system.
  • 41. Question 6 - Answer Large File Sizes – Trying to see the maximum withdrawals, deposits ect. Mix of transaction types – Changing different applications i.e. BPAY, EFTPOS, different computers. Response Times – Measure the time taken on different Internet Connections. Volume Test Data – 50+ users accessing one account.
  • 42. Interfaces Between Modules In this section we are interested in testing the performance of interfaces that connect modules and programs. Tests should examine the accuracy of data being passed as well as response times and the ability to cope with large volumes of data.
  • 43. Comparison with test data This involves the use of test data that checks the expected outputs of processing. Because the outputs are already known, this testing process ensures the final product is able to perform processing correctly.
  • 44. Benching Marking Bench marking is the process of evaluating a product through a series of tests to meet a standard of excellence. This process involves comparing competitors products to measure quality assurance.
  • 45. Question 7 Identify the areas that a company may employee in which to base its benchmarking tests. i.e. Overall Performance.
  • 46. Question 7 - Answer Overall Performance Quality Usability Robustness Maintainability Productivity
  • 47. Quality Assurance The quality of a product is measured against how well the product meets or exceeds users’ expectations. The following factors are considered: Correctness: Does it do what it is supposed to do? Reliability: Does it do it all the time? Efficiency: Does it do it the best way possible? Useability: Is it designed for the end-user. Flexibility: Can it be modified?
  • 48. Quality Assurance Portability: Will it work with other hardware? Re-useability: Can it be used again? Integrity: Is it secure? It is used to assure customers of the quality of the product. Employs a set of measurable standards set out by the ISO (International Standards Organisation)
  • 49. Question 8 A software application has been written to control the operation of a digital video camera. The camera performs all the usual video camera functions and some new ones. For example, the camera can be set to commence filming once it detects movement. This is useful for wildlife photographers. Describe the types of tests that could be conducted by The quality assurance company to determine reliability, efficiency and useability of this product.
  • 50. Question 8 - Answers Reliability – Beta test using live test data to test how the camera performs under large volumes of data. i.e multiple animals or long sequences. Efficiency – Benchmarking could take place by giving a competitors product to compare. Useability – Beta testing and surveying users regrading useability of the camera and its functions.