English 中文(简体)
COMPARISON - STLC and SDLC
  • 时间:2024-03-19 19:08:27

COMPARISON - STLC and SDLC


Previous Page Next Page  

在本章中,我们将理解STLC和SDLC之间比较的因素。 让我们考虑以下几点,从而比较STLC和SDLC。

    STLC是SDLC的一部分。 可以说,STLC是SDLC的一组子。

    STLC仅限于确保软件或产品质量的测试阶段。 SDLC在软件或产品的完整开发方面有着巨大和至关重要的作用。

    但是,STLC是SDLC的一个非常重要的阶段,最后产品或软件不能通过STLC程序释放。

    STLC也是释放后/更新周期的一部分,是SDLC的维护阶段,因为已知的缺陷已经固定下来,或者在软件中添加新的功能。

下表列出了按阶段分列的SDLC和STLC之间的比较因素:

Phase SDLC STLC
Requirement Gathering

    Business Analyst gathers requirements.

    Development team analyzes the requirements.

    After high level, the development team starts analyzing from the architecture and the design perspective.

    Testing team reviews and analyzes the SRD document.

    Identifies the testing requirements - Scope, Verification and Vapdation key points.

    Reviews the requirements for logical and functional relationship among various modules. This helps in the identification of gaps at an early stage.

Design

    The architecture of SDLC helps you develop a high-level and low-level design of the software based on the requirements.

    Business Analyst works on the mocker of UI design.

    Once the design is completed, it is signed off by the stakeholders.

    In STLC, either the Test Architect or a Test Lead usually plan the test strategy.

    Identifies the testing points.

    Resource allocation and timepnes are finapzed here.

Development

    Development team starts developing the software.

    Integrate with different systems.

    Once all integration is done, a ready to test software or product is provided.

    Testing team writes the test scenarios to vapdate the quapty of the product.

    Detailed test cases are written for all modules along with expected behaviour.

    The prerequisites and the entry and exit criteria of a test module are identified here.

Environment Set up

    Development team sets up a test environment with developed product to vapdate.

    The Test team confirms the environment set up based on the prerequisites.

    Performs smoke testing to make sure the environment is stable for the product to be tested.

Testing

    The actual testing is carried out in this phase. It includes unit testing, integration testing, system testing, defect retesting, regression testing, etc.

    The Development team fixes the bug reported, if any and sends it back to the tester for retesting.

    UAT testing performs here after getting sign off from SIT testing.

    System Integration testing starts based on the test cases.

    Defects reported, if any, get retested and fixed.

    Regression testing is performed here and the product is signed off once it meets the exit criteria.

Deployment/ Product Release

    Once sign-off is received from various testing team, apppcation is deployed in prod environment for real end users.

    Smoke and sanity testing in production environment is completed here as soon as product is deployed.

    Test reports and matrix preparation are done by testing team to analyze the product.

Maintenance

    It covers the post deployment supports, enhancement and updates, if any.

    In this phase, the maintaining of test cases, regression suits and automation scripts take place based on the enhancement and updates.

Advertisements