“ Introduction to Software

Quality Assurance
”
Fundamental Concepts of SQA

QA Methodologies
In the fast-paced world of software development, ensuring quality is not a one-size-fits-all approach. Software Quality Assurance (SQA)
methodologies provide structured, strategic processes for testing and validating software. The choice of methodology depends on the
project’s complexity, scale, and industry requirements. By understanding the various QA methodologies, teams can select the most
appropriate approach to ensure a reliable, user-friendly product.
Fundamental Concepts of SQA

Waterfall vs. Agile Methodologies

These two methodologies represent different philosophies in how software is developed and delivered. Understanding the differences between
Waterfall and Agile is essential for tailoring QA practices to fit the project needs.

Waterfall Methodology
The Waterfall methodology is linear and sequential. It follows a strict path where each phase of development—requirements, design,
implementation, testing, and maintenance—must be completed before moving on to the next.

Key Characteristics of Waterfall:

Fixed Requirements: Once requirements are defined, they rarely change.
Phased Progress: Each phase must be fully completed before moving to the next.
Late Testing: Testing only occurs after the development is finished, which can delay issue discovery.
Example: For a large-scale government software project with clearly defined requirements and little room for change, Waterfall may be the preferred
method. Here, QA comes into play after the development is fully completed, performing end-to-end tests to ensure compliance.

Role of QA in Waterfall:
Test After Development: QA performs testing only after the entire application is built.
Thorough Documentation: Detailed test cases and documents are created during the early phases.
Limited Flexibility: Since changes are hard to implement, QA focuses on verifying the initial requirements.
Fundamental Concepts of SQA

Waterfall vs. Agile Methodologies

Agile Methodology
In contrast to Waterfall, Agile is iterative and flexible. Agile breaks the project down into smaller, manageable chunks called “sprints.” This allows
teams to respond quickly to changes and adjust as they go.

Key Characteristics of Agile:

Flexibility: Agile welcomes changes, even late in development.
Iterative Progress: Development is done in cycles, with each sprint delivering a working product.
Continuous Testing: QA is integrated throughout the development process, ensuring issues are caught early.
Example: An eCommerce website, where features and designs are subject to frequent change, benefits from Agile. QA is continuously testing features
during each sprint, ensuring every update is ready for deployment.

Role of QA in Agile:
Early and Ongoing Involvement: QA is involved from the very start of the project, working alongside developers in each sprint.
Testing in Sprints: QA tests smaller portions of the product in cycles, reducing the risk of larger defects later on.
Collaboration and Communication: QA works closely with the entire team, ensuring that quality is built into every stage.
Fundamental Concepts of SQA

Introduction to Scrum and Kanban

Within Agile, two popular frameworks guide how teams work: Scrum and Kanban. Both offer unique approaches to managing work, but they share
the same Agile mindset of adaptability and continuous improvement.

Scrum
Scrum is one of the most widely adopted Agile frameworks. It organizes work into fixed-length sprints, usually lasting two to four weeks. Teams
commit to completing a set of tasks within each sprint.
Key Components of Scrum:
Product Backlog: A prioritized list of features, bugs, and tasks that need to be worked on.
Sprint Planning: Teams meet to decide what tasks will be completed during the next sprint.
Daily Standups: Short daily meetings where team members discuss their progress, roadblocks, and next steps.
Sprint Review and Retrospective: After each sprint, teams review what was accomplished and discuss what can be improved.

Role of QA in Scrum:
Sprint Testing: QA ensures that every deliverable within a sprint is tested and meets quality standards.
Collaboration with Developers: QA and developers work closely throughout the sprint, offering quick feedback on issues.
Automation and Regression Testing: QA may use automated testing tools to ensure that new changes don’t break existing functionality.
Fundamental Concepts of SQA

Introduction to Scrum and Kanban

Kanban
Kanban is another Agile framework but is more focused on visualizing and optimizing the flow of work. Instead of working in fixed sprints, Kanban
allows for continuous delivery by moving tasks through a series of stages, typically represented on a board.
Key Components of Kanban:
Kanban Board: A visual representation of the work process, with columns representing stages like “To Do,” “In Progress,” and “Done.”
Work In Progress (WIP) Limits: The number of tasks allowed in each column is limited to avoid bottlenecks.
Continuous Flow: Unlike Scrum’s fixed sprints, tasks move through the board whenever they are ready.

Role of QA in Kanban:
Continuous Testing: QA is always testing tasks as they move from one stage to the next.
Reduced Bottlenecks: QA ensures that testing doesn’t become a bottleneck by continuously moving tasks through the pipeline.
Collaboration with Developers: Like Scrum, QA works hand-in-hand with the development team, offering real-time feedback.
Example: A mobile app development team using Kanban would allow tasks to be picked up and worked on as soon as they are ready, with QA
continuously testing features as they move through the pipeline.
Fundamental Concepts of SQA

The Role of QA in Different SDLC Models

QA’s role varies depending on the chosen SDLC model, but in every case, QA plays a vital role in ensuring software quality from start to finish.

Waterfall SDLC Model

In Waterfall, QA is heavily documentation-driven and focused on post-development testing. QA is responsible for validating that the final product
meets the initially specified requirements.

Agile SDLC Model

In Agile, QA’s role is more integrated and collaborative. Rather than waiting until development is finished, QA participates in every sprint. This means
testing happens early and often, allowing for quick feedback and adjustments.

V-Model
The V-Model is another variation of the Waterfall approach, where each phase of development corresponds to a testing phase. For every design
phase, there is a corresponding test planning phase, ensuring that QA activities align with the development lifecycle.
Example: In a V-Model project for a medical device software, QA would be involved in both planning test cases during the design phase and executing
those tests once the software is developed.

DevOps
DevOps emphasizes collaboration between development and operations teams to achieve faster delivery. QA’s role in DevOps is to ensure that
automation and continuous testing are in place, enabling seamless deployment and delivery of software.
Example: In a continuous delivery pipeline for a cloud-based SaaS product, QA engineers are responsible for automating tests to ensure that every
build can be deployed quickly and reliably.