1. Software Development Lifecycle Models
1.1. SDLC & SW Testing
1.1.1. Characteristics of good testing
1.1.2. Sequential Development Model
1.1.3. Iterative & Incremental Development Model
1.1.3.1. Rational Unified Process
1.1.3.2. Spiral
1.1.3.3. Scrum
1.1.3.4. Kanban
1.2. SDLC Models in Context
2. Test Levels
2.1. Component Testing
2.1.1. Objectives
2.1.2. Test basis
2.1.3. Test objects
2.1.4. Defects & failures
2.1.5. Approaches & responsibilities
2.2. Integration Testing
2.2.1. Objectives
2.2.2. Test basis
2.2.3. Test objects
2.2.4. Defects & failures
2.2.5. Approaches & responsibilities
2.2.6. Types of integration Testing
2.2.6.1. Component Integration Testing
2.2.6.2. System Integration Testing
2.2.7. Approaches
2.2.7.1. Top-down Testing
2.2.7.2. Bottom-up Testing
2.2.7.3. Big-bang Testing
2.3. System Testing
2.3.1. Objectives
2.3.2. Test basis
2.3.3. Test objects
2.3.4. Defects & failures
2.3.5. Approaches & responsibilities
2.4. Acceptance Testing
2.4.1. Objectives
2.4.2. Common Forms of Acceptance Testing
2.4.2.1. 1. User acceptance testing
2.4.2.2. 2. Operational acceptance testing
2.4.2.3. 3. Contractual and regulatory acceptance testing
2.4.2.4. 4. Alpha & Beta Testing
2.4.3. Test basis
2.4.4. Test objects
2.4.5. Defects & failures
2.4.6. Approaches & responsibilities
3. Test Types
3.1. Functional Testing
3.2. Non-functional testing
3.2.1. (ISO/IEC 25010)
3.3. White-Box testing
3.4. Change-Related Testing
4. Maintenance Testing
4.1. Triggers for Maintenance
4.1.1. Modification of operational environment
4.1.2. Migration from one platform to another
4.1.2.1. require operational tests
4.1.2.2. require tests of data conversion
4.1.2.3. Retirement, requires testing of data migration or archiving
4.1.2.4. Testing restore/retrieve procedures after archiving for long retention periods
4.1.2.5. regression testing may be needed to ensure that any functionality that remains in service still works.