1_Interview_Prep_SDLC__Agile__STLC_Google_Docs_1_2

SDLC

SDLC

Software Development Life Cycle - The phases involved in building software or an application.

Agile

A software development methodology that emphasizes flexibility and collaboration.

STLC

Software Testing Life Cycle - The phases involved in testing software or an application.

Software Testing

The process of executing a program or application with the intent of finding software bugs/defects using functional and automation tools.

Requirement

The description of features and functionalities of the target system that conveys the expectations of users from the software product.

Test Plan

A document that outlines the approach, objectives, and scope of testing for a software project.

Test Estimation

The process of estimating the effort and resources required for testing a software project.

Test Schedule

A timeline that outlines when different testing activities will be performed during the software development life cycle.

Test Case Development

The process of designing and creating test cases, test scripts, and test data for testing a software application.

Test Environment Setup

The process of setting up the necessary hardware, software, and network configurations for testing a software application.

Test Closure Activity

The reporting and documentation activities that are performed at the end of the testing phase.

Regression Suite

A collection of test cases that are executed to ensure that new changes or bug fixes do not introduce new defects or break existing functionality.

Unittesting

The testing of individual modules or blocks of code during the development process.

Component Testing

The testing of standalone functionalities or components of a software application.

Integration Testing

The testing of the combined functionalities of a software application to ensure that they work together correctly.

System Testing

The end-to-end testing of a software application to ensure that it functions as expected from beginning to end.

Acceptance Testing

The testing of a software application by a user acceptance testing team or business analyst to ensure that it meets the requirements and is ready for release.

Black Box Testing

A testing technique where the tester only knows the expected behavior of the software and tests it from an end-user perspective.

Equivalence Class Partitioning

A software test design technique that involves dividing input values into valid and invalid partitions and selecting representative values from each partition as test data.

Boundary Value Analysis

A software test design technique that involves determining boundaries for input values and selecting values at the boundaries and just inside/outside of the boundaries as test data.

Cause-Effect Graphing

A software test design technique that involves identifying input conditions and output conditions, producing a Cause-Effect Graph, and generating test cases accordingly.

White Box Testing

A software testing method where the internal structure of the software is known to the tester and is tested accordingly.

Gray Box Testing

A testing method that combines elements of black box testing and white box testing, where the tester has partial knowledge of the internal structure of the software.

Functional Testing

A type of testing that focuses on testing the functionality of a software application to ensure that it meets the specified requirements.

Functional Testing

Testing the functions of a component or system to verify specific actions or functions of the code.

Non-functional Testing

Testing the performance of a system under a particular workload, such as testing concurrent user logins or transaction response time.

Unit Testing

Testing the smallest testable parts of an application, such as functions, classes, procedures, or interfaces, to eliminate bugs before further testing.

Component Testing

Testing each component of an application separately to find defects and verify the functioning of the software.

Integration Testing

Testing the system after integrating multiple components to ensure that it works fine when combined.

Acceptance Testing

Testing performed by the user or customer to determine if the system meets the specified requirements.

Regression Testing

Testing to ensure that new functionality or bug fixes do not break existing functionality.

Smoke Testing

Initial testing to check if the software is stable and ready for further testing.

Positive Testing

Testing the application with valid input to ensure it works as expected.

Negative Testing

Testing the application with invalid data or unexpected user behavior to check if it behaves as expected.

Verification

Evaluating software during development to determine if it satisfies the specified requirements.

Validation

Evaluating software at the end of the development process to check if it meets customer requirements.

Software Testing

Activity to detect and identify defects in the software as part of the Software Development Life Cycle (SDLC).

Software Testing Life Cycle (STLC)

Testing process with specific steps executed in a definite sequence to ensure quality goals are met.

Requirements Analysis

Analyzing and studying the requirements to identify the scope of testing and ensure testability.

Test Plan Creation

Creating a plan that describes the scope, approach, resources, schedule, and tasks for the testing process.

Test Case Creation

Creating documentation that outlines a set of actions executed to verify a particular feature or functionality of the software.

Test Scenario

Possible area to be tested in a user story, determining what to test before writing test cases.

Environment Setup

Setting up the test environment and test data for testing activities.

Test Execution

Carrying out testing based on the test plans and test cases, documenting results and logging defects.

SDLC

Software Development Life Cycle, a systematic process for developing software

Agile

A project management methodology that emphasizes collaboration, flexibility, and iterative development

STLC

Software Testing Life Cycle, a systematic process for testing software

RTM

Requirements Traceability Matrix, a document that maps requirements to test cases

Test cases

Detailed steps and conditions to be followed in order to test a specific functionality of a software application

Defect reports

Documentation of issues or bugs found during testing

Test Cycle Closure

The final phase of the testing process where test reports and defect reports are generated

Jira

A popular project management tool used for issue tracking and project management

Defect

An issue or bug in a software application where the actual result does not match the expected result

Defect Life Cycle (DLC)

The systematic process for dealing with defects, from identification to closure

New

The initial status of a defect when it is reported by the tester

Assigned

The status of a defect when it is assigned to the development team for resolution

Open

The status of a defect when the developer starts analyzing and working on the fix

Fixed

The status of a defect when the developer has made the necessary code changes and verified the fix

Re-test

The status of a defect when the tester retests the code to check if the fix is successful

Reopen

The status of a defect when the bug persists even after the developer has fixed it

Closed

The status of a defect when it is resolved and no longer exists

Rejected

The status of a defect when the developer determines that it is not a valid defect

Duplicate

The status of a defect when it is a repeated issue or corresponds to the same concept as another bug

Not a bug

The status of a defect when it does not affect the functionality of the application

Deferred

The status of a defect when it is not of high priority and is expected to be fixed in a future release

Severity

The degree of impact a defect has on the development or operation of a software application

Priority

The order in which defects should be fixed based on their importance and urgency

Planning Poker

A card-based agile technique used for planning and estimation in which team members privately select cards with values to denote story points or ideal days

Waterfall Methodology

A traditional project management approach where a project is divided into sequential phases and each phase must be completed before moving on to the next

Agile Methodology

A project management approach that involves breaking a project into stages and emphasizing collaboration, continuous improvement, and iteration

Scrum

An agile process that focuses on delivering the highest business value in the shortest time through rapid inspection and adaptation

SDLC

Software Development Life Cycle, a process used to develop software applications.

Agile

An iterative and flexible approach to software development that emphasizes collaboration and adaptability.

STLC

Software Testing Life Cycle, a process used to test software applications.

Scrum

A framework within Agile that emphasizes teamwork, collaboration, and iterative development.

Kanban

Another Agile framework that focuses on visualizing work, limiting work in progress, and optimizing flow.

Extreme Programming (XP)

An Agile framework that emphasizes continuous feedback, frequent releases, and close collaboration.

Adaptive Project Framework (APF)

An Agile framework that focuses on adapting to changing requirements and delivering value incrementally.

Product Owner

The role in Scrum responsible for defining product features, prioritizing work, and ensuring profitability.

Scrum Master

The role in Scrum responsible for facilitating the Scrum process, removing impediments, and ensuring the team is productive.

Scrum Development Team

A group of individuals who work together to create and test incremental releases of a product.

Product Backlog

A list of work that needs to be done in a project, prioritized by the Product Owner.

Sprint Backlog

Tasks that a Scrum team needs to complete within a specific sprint.

Burnout Chart

A visual representation of the amount of work remaining in a project over time.

Sprint Planning

A meeting where the team discusses and decides what can be accomplished in the next sprint.

Daily Scrum

A daily meeting where the team provides updates on their progress and discusses any blockers or impediments.

Sprint Review

A meeting at the end of a sprint where the team demonstrates the new functionalities of the product.

Sprint Retro

A meeting after the sprint review where the team reflects on what went well, what went wrong, and how to improve.

Epic

A large user story that cannot be completed in one sprint and represents a significant portion of a project.

Feature

Multiple user stories that are grouped together to form a standalone component of an application.

User Story

A short, simple description of a minimum shippable product from the perspective of the end-user.

Acceptance Criteria

Statements that define the requirements for a user story and determine when it is considered "done."

Rat Hole

A situation in a meeting where the team gets into excessive argument and wastes time.

Parking Lot Item

A valid problem or issue raised in a meeting that is not immediately addressed but can be discussed later.

Velocity

The number of story points delivered in a sprint, used to measure the team's productivity.

Capacity

The total number of available hours for a sprint, taking into account holidays and PTO.

Sprint Grooming

A meeting where the team gives estimates for the tasks in the sprint backlog.

SDLC

Stands for Software Development Life Cycle, a process used to develop software applications.

Agile

An iterative and flexible approach to software development that emphasizes collaboration and adaptability.

STLC

Stands for Software Testing Life Cycle, a process used to test software applications.