1. What is SDLC?

- SDLC (Software Development Life Cycle)

- Is a process in which software is developed and deployed.

- Aims to produce a high-quality software that meet customer expectations within lowest cost and
shortest time possible.
2. How many stages are in the SDLC? What are they? Who will join these stages?

There are 6 main stages in SDLC:

Stage 1: Planning and Requirement analysis

- Is the most important stage in SDLC

- Plan for the quality assurance requirement, identify the risk of the project

- Who will join: Project management (PM), BA, Sales department, Domain expects, Customer

Stage 2: Defining requirements

- Define and document the requirement -> get customer’s approval

- Output: SRS (Software Requirement Specification) document, which is used during the project life cycle

- Who will join: PM & BA, Customer

Stage 3: Designing

- This stage comes out the best detailed architecture of product base on SRS document

- Output: DDS (Design Document Specification)

- Who will join: Designer, BA, customer

Stage 4: Development

- In this stage, product is built base on document

- Who will join: Developer, Tester, BA

Stage 5: Testing

- Test the product or modules base on testcase scenario.

- Who will join: Tester, developer, BA, customer

Stage 6: Deployment and Maintenance

- When the product is ready to deploy, it is release in the market

- Maintain base on customer requirement

- Who will join: PM & BA, Customer, User

 3. What is STLC?

- STLC (Software Testing Life Cycle)

- Is series of steps to ensure the quality of product goals are met.

4. How many stages are in STLC?

5. What is the main content and purpose of each stage?

There are 6 major phases in STLC:

Phase 1: Requirement analysis

- Analyze the requirement base on document, identify the feasibility of software testing
- Aims to: prevent bugs occurring in early stage as possible

Phase 2: Test Planning

- Tester leader create the plan, test strategy and possible risks
- Estimate the time, cost and schedule
- Aims to: identify the product activities, resources, scope, acceptance criteria, and delivery timelines

Phase 3: Test case development

- Write test case according to the criteria in the project specification document
- Prepare test data
- Aims to: cover all possible test cases to ensure the modules are met in the project

Phase 4: Test Environment setup

- Define test environment based on software testing conditions

- Aims to: setup environment and be ready for testing

Phase 5: Test Execution

- Perform software testing, evaluate test results, report software defects

- Aims to: find out defect list and give developer to fix until all bugs are successfully fixed

Phase 6: Test Cycle closure

- Summarize, report the results of testing

- Aims to: archive experience for the better future project