|
|
 |
Information and Communications
Technology Qualifications
| Back to list of Prescriptions
| Prescription: QA600 (QA200)Quality Assurance |
| Aim of Module | Students will gain an understanding of the role of quality assurance in business computing.
|
| Credits | 7
|
| Student Learning hours | 70
|
| Content Revised | 2000
|
| Prescription Expiry Date | Nov 2005
|
LEARNING OUTCOMES
The Student Will
| | | | | A | 1 | Critically evaluate the reasons for software quality assurance and validation and explain where it can be applied in the software development process. | | | | | A | 2 | Critically evaluate the types of SQA reviews and the kinds of SQA organisation. | | | | | A | 3 | Distinguish between the different types of testing and testing strategies. | | | | | A | 4 | Design test cases, create a test implementation plan, and conduct a full SQA test project for a module/application package. | | |
CONTENT
| | | | > | The origins and application of quality, quality control and quality assurance, including such other aspects as: | | | | - Total Quality Management | | | | - Dr W. Edwards Deming | | | | - guidelines for implementing a Quality Management System | | | | - quality system standards/objectives of standards | | | | - an overview of the ISO 9000 Standards, particularly as to how they apply to the software industry | | | | - the role of quality assurance in the software development life cycle | | |
|
top
| | | | > | The principles and practices of software quality assurance, including such other aspects as: | | | | - generally accepted principles of good software | | | | - quality assurance and validation techniques and organisation | | | | - software measurement techniques (function points or metrics) | | | | - planning for and the various plans involved in software reviewing | | | | - code review guidelines | | | | - an in-depth look at review procedures, including formal and informal reviews, self management and peer reviews | | |
|
top
| | | | > | The principles and practices of software testing and testing strategies, including such other aspects as: | | | | - the difference between testing to specification and testing to code | | | | - the difference between testing “on-the-fly” and testing to plan | | | | - myths about testing | | | | - testing axioms | | | | - items traditionally done badly | | | | - terms and techniques and Bug Classification | | | | - the principles of proof of error | | | | - the principles of “good enough” software, including Ed Yourdan’s theory of operational capability | | |
|
top
| | | | > | For a module of code or an application package, students will carry out a full software quality assurance programme, including: | | | | - design test cases and develop data and expected results for all conditions | | | | - create a test implementation plan | | | | - conduct a full test with detailed results, including, for the application package, testing “on-the-fly” and testing to planned test cases. | | | | - detailed results are also to include proof and classification of errors
|
top
|
|
