STQA - Assignment 2

1) Define BVA.
➔ BVA (Boundary Value Analysis) is a software testing technique in
which tests are designed to include representatives of boundary values
in the input domain. Errors often occur at the boundaries of input
ranges rather than within the ranges.

2) Define Equivalence Class Partitioning.

➔ Equivalence Class Partitioning (ECP) is a black-box testing technique
that divides input data into partitions or classes. Test cases are
designed to cover each class, reducing the number of test cases while
ensuring adequate coverage.

3) Describe testing layers in detail.

➔ The main testing layers include:
1) Unit Testing – Testing individual component or modules.
2) Integration Testing – Testing interaction between integrated
modules.
3) System Testing – Testing the complete system as a whole.
4) Acceptance Testing – Validating the system against business
requirements.

4) List out issues in object oriented testing.

➔ Issues in Object-Oriented Testing include:
- Encapsulation makes it hard to access private data.
- Inheritance may cause redundant tests.
- Polymorphism increases complexity in designing test cases.
- Dynamic binding complicates test execution and verification.
5) Describe Cyclomatic complexity.
➔ Cyclomatic Complexity is a software metric used to measure the
complexity of a program by counting the number of linearly
independent paths. It helps in determining the minimum number
of test cases required for complete path coverage.

6) Difference between Alpha testing and Beta Testing.

➔ Alpha Testing: Conducted by internal developers and testers at
the developer’s site, before release.

Beta Testing: Conducted by actual users in the real environment,

after Alpha testing but before final release.

7) Define Security Testing.

➔ Security Testing is a process to identify vulnerabilities, threats, and
risks in a software application to prevent malicious attacks. It ensures
that data and resources are protected from unauthorized access and
breaches.

8) Explain Fault based testing.

➔ Fault-based Testing is a technique in which test cases are designed
with the assumption that specific types of faults may be present in the
system. Its goal is to uncover these faults and ensure robustness of the
system.
 STQA – Assignment 3
1. What is Client-Server Testing? Explain with types.
• Definition:
Client-Server Testing is performed on applications that follow a two-tier architecture
(Client ↔ Server).
The client sends requests and the server processes and returns responses. Testing ensures
correct communication, performance, and functionality.
• Types:
1. Application Functionality Testing – Verifies business logic, features, and
correctness.
2. Server Side Testing – Checks database, queries, deadlocks, and response.
3. Client Side Testing – Validates GUI, usability, and client software.
4. Database Testing – Validates CRUD (Create, Read, Update, Delete) and
transactions.
5. Performance Testing – Load, stress, concurrency, and scalability.
6. Security Testing – Authentication, authorization, and data protection.

2. What is Web-based Testing?

• Definition:
Web-based testing is performed on applications deployed over the internet or intranet
(three-tier architecture: Browser ↔ Server ↔ Database).
• Focus: Functionality, UI, database, compatibility, and performance.
• Examples: Testing login systems, online shopping carts, payment gateways.

3. What is Multiplatform Independent Testing?

• Definition:
Testing an application across different platforms (OS, browsers, devices) to ensure
portability and consistency.
• Examples:
o Testing a website on Windows, Linux, Mac.
o Testing a mobile app on Android & iOS.
o Testing on browsers (Chrome, Firefox, Edge, Safari).
4. Explain STLC (Software Testing Life Cycle).
• Definition: STLC defines the process followed to perform software testing in a systematic
way.
• Stages & Roles:
1. Requirement Analysis → QA team studies requirements.
2. Test Planning → Define strategy, tools, resources.
3. Test Case Design → Prepare test cases, test data.
4. Environment Setup → Hardware/software configuration.
5. Test Execution → Run tests, log defects.
6. Defect Reporting & Tracking → Fix + retest.
7. Test Closure → Final reports, metrics.
• Advantages: Structured, improves quality, early defect detection.
• Disadvantages: Time-consuming, costly if requirements change frequently.

5. What is Software Quality Assurance (SQA) and Software Quality

Control (SQC)?
• SQA: Process-oriented. Ensures quality in processes, methodologies, standards followed
during development. (Prevention technique).
• SQC: Product-oriented. Ensures quality in the final product through inspection, reviews,
and testing. (Detection technique).

6. What is Software Review? List its types.

• Definition:
A process of examining a software product or process by peers or stakeholders to find
defects early.
• Types:
1. Informal Review – Peer-to-peer discussions.
2. Walkthroughs – Developer presents code/design to peers.
3. Technical Reviews – Experts evaluate technical content.
4. Inspections – Formal, structured defect detection.
7. What is FTR (Formal Technical Review)?
• Definition: A formal meeting-driven review process of software artifacts (requirements,
design, code) conducted by a team to ensure correctness and quality.
• Objectives:
o Identify defects early.
o Ensure compliance with standards.
o Improve team communication.

8. What is Software Reliability & Software Safety?

• Software Reliability: Probability that software will work without failure in a specified
environment for a specific time. (MTTF – Mean Time to Failure).
• Software Safety: Assurance that software will not cause hazardous conditions even in
case of failures (used in aviation, medical, defense).

9. Explain CMM (Capability Maturity Model).

• Definition: A model that defines maturity levels of software processes in an organization.
• Levels:
1. Initial – Ad hoc, chaotic.
2. Repeatable – Basic project management.
3. Defined – Standardized processes.
4. Managed – Measured & controlled processes.

5. Optimizing – Continuous process improvement.

10. Explain TQM (Total Quality Management).

• Definition: A management approach that focuses on continuous improvement of products,
processes, and services by involving everyone in the organization.
• Principles:
o Customer focus
o Continuous improvement
 o Employee involvement
o Process approach

11. Explain SPICE (ISO/IEC 15504).

• Definition: Software Process Improvement and Capability Determination (SPICE) – a
framework to assess and improve software development processes.
• Purpose: To evaluate capability maturity, similar to CMMI but more detailed.

12. What is Software Risk? List types.

• Definition: Possibility of an adverse outcome that may impact project success.
• Types:
1. Project Risk – Schedule, cost, resources.
2. Technical Risk – Technology failure, design issues.
3. Business Risk – Market changes, competition.

4. Operational Risk – Team skills, communication gaps.

13. What is RMMM Plan?

• Definition: Risk Mitigation, Monitoring, and Management Plan.
• Purpose: To identify risks, plan strategies to reduce their impact, monitor them, and take
corrective actions.

14. What is Software Configuration Management (SCM)?

• Definition: Process of systematically controlling changes in software to maintain integrity
and traceability.
• Activities:
o Version control
o Change control
o Build management
o Release management
15. Difference between SQA and SQC
Feature SQA SQC
Focus Process Product
Nature Preventive Detective
Performed by QA Team Testing Team
Example Process audits Testing, inspections

16. What is PDCA Concept in SQC?

• PDCA: A cycle for continuous improvement in quality.
1. Plan → Identify improvements.
2. Do → Implement changes.
3. Check → Monitor & measure results.

4. Act → Standardize and improve.

17. Draw McCall’s Quality Factors in a Diagram

McCall classified quality factors into 3 categories:
• Product Operation: Correctness, Reliability, Efficiency, Integrity, Usability.
• Product Revision: Maintainability, Flexibility, Testability.
• Product Transition: Portability, Reusability, Interoperability.
McCall’s Quality Model
Product Operation Product Revision Product Translate
Correctness Maintainability Portability
Reliability Flexibility Reusability
Efficiency Testability Interoperability
Integrity
Usability

18. What is Agile Testing?

• Definition:
Agile testing is a continuous testing process that follows Agile methodology. Testing is
done concurrently with development and focuses on customer satisfaction.
• Key Points:
o No separate testing phase.
o Continuous integration & regression testing.
o Uses Scrum/Kanban frameworks.
o Involves testers, developers, and customers closely.