In this module, you will get a clear overview of the Waterfall methodology within the Software Development Life Cycle (SDLC). We will begin by an overview of the six common approaches such as Waterfall, Agile, DevOps/DevSecOps, Lean, Iterative, and Spiral. We will then walk through the Waterfall phases, from initiation and requirements to design, construction, testing, and deployment. We will also highlight key deliverables such as the Business Requirements Document (BRD), Functional Specification Document (FSD), Technical Specification Document (TSD), the Traceability Matrix, RACI Chart, and Test Plan and test scenarios/cases, while also reviewing the main testing layers, build process, and tools for test and defect management. We will then look at the advantages and disadvantages of Waterfall methodology.

Agile processes represent a transformative approach to software development and project management that emphasizes iterative development, customer collaboration, and adaptive planning over traditional rigid methodologies. Born from the Agile Manifesto of 2001, these processes prioritize individuals and interactions, working software, customer collaboration, and responding to change through core frameworks like Scrum, Kanban, and Extreme Programming (XP), which focus on delivering value through short development cycles called sprints, continuous feedback loops, and cross-functional team collaboration. Scaled Agile Framework (SAFe) extends the Agile principles to address the complexities of large-scale software development across multiple teams and business units by providing a structured approach that incorporates elements like Agile Release Trains (ARTs), Program Increments (PIs), and portfolio-level planning to coordinate work across dozens or even hundreds of development teams.

In this module, you will be introduced to the Automation Testing Fundamentals. We will review the automation strategy, automation frameworks, the benefits of automation testing, and how it helps to speed up the testing process. We will also review some of the automation tools that are in the market today. Next, this module will discuss DevOps. This set of practices and philosophies represents a cultural and operational shift that bridges the traditional gap between development and operations teams, emphasizing collaboration, automation, and continuous integration and delivery (CI/CD). DevOps methodology enables organizations to deploy software more frequently and reliably by automating testing, building, and deployment processes while fostering shared responsibility for application performance and stability. DevSecOps extends the DevOps philosophy by integrating security practices throughout the entire software development lifecycle, rather than treating security as a final gate before deployment. This "shift-left" approach embeds security considerations into every stage of development, from code writing and testing to deployment and monitoring, ensuring vulnerabilities are identified and addressed early when they're less costly to fix. We will also discuss the microservices architecture that goes with DevOps and DevSecOps.

Application security and cybersecurity testing represent critical disciplines in modern software development and organizational risk management. As applications become increasingly complex and interconnected, they present expanding attack surfaces that malicious actors can exploit to compromise sensitive data, disrupt operations, or gain unauthorized system access. This field encompasses systematic approaches to identifying, analyzing, and mitigating security vulnerabilities throughout the software development lifecycle, from initial design through deployment and ongoing maintenance. Cybersecurity testing, on the other hand, employs various methodologies including static code analysis, dynamic application security testing, penetration testing, and threat modeling to evaluate application resilience. These approaches range from automated scanning tools that identify known vulnerability patterns to manual testing techniques that simulate real-world attack scenarios.

In today's diverse digital landscape, users access web applications through an ever-expanding array of browsers, devices, and operating systems. From Chrome and Firefox on desktop computers to Safari on iPhones and Samsung Internet on Android devices, each platform interprets and renders web content differently. What appears perfectly formatted and functional in one environment may display broken layouts, missing features, or critical errors in another. This reality makes cross browser testing and mobile testing essential components of any comprehensive quality assurance strategy. Meanwhile, mobile testing extends beyond simple responsive design checks to encompass touch interactions, device-specific features, network conditions, and the unique constraints of mobile hardware. Together, these testing approaches ensure that applications deliver consistent, reliable experiences regardless of how users choose to access them. Organizations that prioritize comprehensive cross browser and mobile testing strategies position themselves to capture the full breadth of their potential audience while minimizing the costly technical debt that emerges from platform-specific bugs discovered post-launch.

This module explores the principles, methodologies, and tools for ensuring software applications meet performance, scalability, and reliability requirements. We will touch upon various types of performance tests and their differences under the Performance Engineering umbrella.