1. 10.9.2015Dr Andy Brooks1 FOR0383 Software Quality Assurance Lecture 1 Introduction Forkröfur/prerequisite: FOR0283 Programming II Website: http://staff.unak.is/not/andy/SoftQualAssur0809/sqa.htm

2. FOR0383 Software Quality Assurance 10.9.2015Dr Andy Brooks2 Module description/Námslýsing This module aims to provide the student with knowledge, skills and critical thinking ability in software quality assurance at an introductory, undergraduate level. Incorrect computer software can be costly or even dangerous. Software quality assurance provides techniques which help towards the goal of developing correct software. The emphasis is on traditional software testing, but students will also be taught at least one other testing technique.

3. FOR0383 Software Quality Assurance 10.9.2015Dr Andy Brooks3 Module objectives/Námsmarkmið On completing this module a student should be able to: Describe selected case study successes and failures in software development. Design, execute, and report on the results of software tests at the method level. Design, execute, and report on the results of software tests at the requirements level. Design, conduct, and report on the results of formal technical reviews. Given a quality requirement, implement an appropriate software development process. Describe at least one other specialized software testing technique (e.g. testing with assertions, mutation testing).

4. FOR0383 assessment 10.9.2015Dr Andy Brooks4 The final examination is worth 60%. Students must obtain an overall passing grade, i.e. obtain at least 28,8% of the 60%. There will be 10 laboratory sessions each worth 2% giving a total of 20%. Students must obtain an overall passing grade, i.e. obtain at least 9,6% of the 20%. DO NOT LEAVE A LABORATORY SESSION WITHOUT CHECKING YOUR PARTICIPATION HAS BEEN RECORDED. There are 4 assignments each worth 5% giving a total of 20%. Students must obtain an overall passing grade, i.e. obtain at least 9,6% of the 20%. Please note “driving tests” may be used in assessing assignments.

5. 10.9.2015Dr Andy Brooks5 Ritstuldur/Plagiarism The copying and submission of someone else´s work is not tolerated. “Teachers are normally to exercise supervision to prevent violations of the prohibition against plagiarism and they are to direct complaints about such alleged incidents to the ethics committee.” Include on the front page of any assignment submission the following statement. Sign your name just below the statement to indicate your agreement. “This is all my own work. I have not knowingly allowed others to copy my work. This work has not been submitted for assessment in any other context."

6. 10.9.2015Dr Andy Brooks6 Recommended Textbook There is no recommended textbook for purchase for FOR0383 Software Quality Assurance. The website should contain all the materials you need.

7. 10.9.2015Dr Andy Brooks7 Incorrect software has caused deaths.

8. 10.9.2015Dr Andy Brooks8 “Testing is the process of executing a program with the intent of finding errors.”

9. 10.9.2015Dr Andy Brooks9

10. Regression Testing http://www.aptest.com/glossary.html 10.9.2015Dr Andy Brooks10 Regression Testing: Retesting a previously tested program following modification to ensure that faults have not been introduced or uncovered as a result of the changes made.

11. Release Candidate http://www.aptest.com/glossary.html 10.9.2015Dr Andy Brooks11 Release Candidate: A pre-release version, which contains the desired functionality of the final version, but which needs to be tested for bugs (which ideally should be removed before the final version is released).

12. Smoke Testing http://www.aptest.com/glossary.html 10.9.2015Dr Andy Brooks12 Smoke Testing: A quick-and-dirty test that the major functions of a piece of software work. Originated in the hardware testing practice of turning on a new piece of hardware for the first time and considering it a success if it does not catch on fire.

13. Static Testing http://www.aptest.com/glossary.html 10.9.2015Dr Andy Brooks13 Static Testing: Analysis of a program carried out without executing the program.

14. Stress Testing http://www.aptest.com/glossary.html 10.9.2015Dr Andy Brooks14 Stress Testing: Testing conducted to evaluate a system or component at or beyond the limits of its specified requirements to determine the load under which it fails and how. Often this is performance testing using a very high level of simulated load. performance testing

15. System Testing http://www.aptest.com/glossary.html 10.9.2015Dr Andy Brooks15 System Testing: Testing that attempts to discover defects that are properties of the entire system rather than of its individual components.

16. Test First Design http://www.aptest.com/glossary.html 10.9.2015Dr Andy Brooks16 Test First Design: Test-first design is one of the mandatory practices of Extreme Programming (XP). It requires that programmers do not write any production code until they have first written a unit test.

17. Test Plan http://www.aptest.com/glossary.html 10.9.2015Dr Andy Brooks17 Test Plan: A document describing the scope, approach, resources, and schedule of intended testing activities. It identifies test items, the features to be tested, the testing tasks, who will do each task, and any risks requiring contingency planning. Ref IEEE Std 829.

18. White Box Testing http://www.aptest.com/glossary.html 10.9.2015Dr Andy Brooks18 White Box Testing: Testing based on an analysis of internal workings and structure of a piece of software. Includes techniques such as Branch Testing and Path Testing. Also known as Structural Testing and Glass Box Testing. Contrast with Black Box Testing. Branch TestingPath Testing Structural TestingGlass Box TestingBlack Box Testing