Lesson 2 - SDLC and Development Approaches

SDLC

Software developmrnt life cycle

SDLC

is a prcoess that produces software with the highest quality and lowest cost in the shortest time possible

Software two main components

The Server side (backend). A software system's client side (front end).

Server-side

consists of the server, database, and applications that power the front end but are not visible to the user. It handles business logic, data storage, and server side functions.

Client-side

is what users actually see and interact with like browser or application interface, from buttons and inputs to layouts and navigation

Modern software design

in the past apps were built as one big piece, inside one big block. If something needed to be changed or fixed, it could affect the whole system, which was inefficient and made developement harder. Just like a lego set.

Phases of SDLC

Planning > Design > Development > Testing > Deployment > Maintenance

Planning - SDLC

first stage of SDLC. The project team outlines a project's objectives, scope, and deliverables. This phase is critical in ensuring the project is well-defined and aligned with business goals and requirements.

Design - SDLC

the project team transforms the requirements and project goals into a detailed design. This phase creates a blueprint for the software including a detailed specification of how the system should work, how it should look, and how it should interat with users and other systems

Development - SDLC

the implementation or development of the software, which involves the actual coding process.

Testing - SDLC

the QA team tests the software against the requirements. Once a bug is found, testers inform the developers who will fix the issue and create a new version of the sofware.

Deployment - SDLC

Once the product is tested and ready to be deployed, it is formally released in the appropriate market. Project managers collect all sign-offs > release engineers prepare software builds > release engineers deploy software to end users > QA performs sanity checks once build is deployed > users perform beta-testing once build is deployed.

Maintenance - SDLC

The final stage, the software is now developed, tested, and implemented. The main goal is to keep the software operational and up-date with the changing user requirements. Ex. software upgrades, bug fixes, and improvements.

At which stage of the SDLC does a QA specialist typically begin their work

Design stage

Waterfall approach

is a six step process that cannot be skipped. Must go in the ordered flow to complete the process. A new phase starts when the previous phase is completed

Agile approach

adaptive planning, stages can be skipped in the development process. this approach is iterative and adaptive, focusing on continuous feedback and rapid adjustments throughout the developement process.

Stages of Waterfall Approach

Requirements > Design > Implementation > Testing > Deployment > Maintenance

Stages of Agile Approach

Requirements > Design > Develop > Test > Deploy > Review

Downside of Agile

constant collaboration and frequent reassessments, predicting project timelines and budgets can be difficult, no strict controlls so projects can grow larger, not a good documentation method

Downside of Waterfall

new phase only starts when the previous phase is completed(no phase overlap), users have minimal interaction with the project and cannot provide feedback during development, assumes that all customer requirments can completely and correctly defined at the beginning of the project.

Agile Scrum Framework

provides a structure for teams to manage and execute projects. Focuses on iterative developmeny, collaboration, and adaptability to change, allowing teams to deliver value in short cycles called sprints. Sprints usually last 2-4 weeks.

How Scrum works

1. Product Backlog Creation > 2. Sprint planning and creating sprint backlog > 3. Working on a sprint > 4. Testing and product demonstration > 5. Retrospective and planning the next sprint

Agile Release Planning

are incremental releases of a product.Each sprint should end with a new product version, which stakeholders can then review. This a not always a product release to the general public.