Page 1 of 2 12 LastLast
Results 1 to 20 of 21

Thread: Difference between SDLC & STLC

  1. #1
    Junior Member
    Join Date
    Sep 2006
    Answers
    6

    testing life cycle

    plz some body provide me
    pictorial representation of testing life cycle and explanation

    regards
    whizen


  2. #2
    Expert Member
    Join Date
    Jan 2007
    Answers
    141

    Re: testing life cycle

    Hi,

    This link give you discussion on testing life cycle.

    http://www.sqaforums.com/showflat.ph...38&an=0&page=0

    Also go through the file attached.you can see the Pictorial representation of testing life cycle.

    Regards,
    Sridevichitthu

    Attached Images Attached Images

  3. #3
    Junior Member
    Join Date
    Jan 2007
    Answers
    11

    Re: testing life cycle

    1.Test Planning : The test plan describes how the Test Strategy is implemented.A project plan for testing. Defines what is to be tested, how it is to be tested what is needed for testing etc..

    2.Test Specification:Test preparation, Build test cases, Cross-reference and classify test cases.

    3.Test Execution:Test execution check list then we are ready to run the tests.

    4.Test Recording:The test itself either passes or fails,we record the test results

    5.Checking for Test Completion:Have we fulfilled the Test Exit Criteria?
    Used to determine when to stop this phase of testing.


  4. #4
    Junior Member
    Join Date
    Dec 2006
    Answers
    20

    Re: Testing Life Cycle

    1. Requirements stage 2. Test plan 3. Test design. 4. Design reviews 5. Code reviews 6. Test cases preparation. 7. Test execution 8. Test reports. 9. Bugs reporting 10. Reworking on patches. 11. Release to production. ************************** the steps in the testing process are as follows. 1. Requirement analysis - testing should begin in the requirements phase of the software life cycle (sdlc). The actual requirement should be understand clearly with the help of requirement specification documents, functional specification documents, design specification documents, use case documents etc. During the requirement analysis the following should be considered. -are the definitions and descriptions of the required capabilities precise? -is there clear delineation between the system and its environment? -can the requirements be realized in practice? -can the requirements be tested effectively? 2. Test planning - during this phase test strategy, test plan, test bed will be created. A test plan is a systematic approach in testing a system or software. The plan should identify: -which aspects of the system should be tested? -criteria for success. -the methods and techniques to be used. -personnel responsible for the testing. -different test phase and test methodologies -manual and automation testing -defect mgmt, configuration mgmt, risk mgmt. Etc -evaluation & identification – test, defect tracking tools 3. Test environment setup - during this phase the required environment will be setup will be done. The following should also be taken in account. - network connectivity’s -all the software/ tools installation and configuration -coordination with vendors and others 4. Test design - during this phase -test scenarios will be identified. -test cases will be prepared. -test data and test scripts prepared. -test case reviews will be conducted. 5. Test automation in this phase the requirement for the automation will be identified. The tools that are to be used will be identified. Designing framework, scripting, script integration, review and approval will be undertaken in this phase. 6. Test execution and defect tracking testers execute the software based on the plans and tests and report any errors found to the development team. In this phase -test cases will be executed. -test scripts will be tested. -test results will be analyzed. -raised the defects and tracking for its closure. 7. Test reports once testing is completed, testers generate metrics and make final reports on their test effort and whether or not the software tested is ready for release. -test summary reports will be prepared -test metrics and process improvements made -build release -receiving acceptance

    Last edited by irinak; 03-29-2007 at 09:54 PM.

  5. #5
    Contributing Member
    Join Date
    Jan 2007
    Answers
    48

    Sdlc

    Why SDLC is required?


  6. #6
    Moderator
    Join Date
    Sep 2006
    Answers
    920

    Re: Sdlc

    SDLC is used for better software development.Manager can see the progress of project and time deadlines can be made when the project will be completed.

    Regards,
    Brijesh Jain
    ---------------------------------------------------------
    Connect with me on Skype: jainbrijesh
    Google Plus : jainbrijeshji

  7. #7
    Junior Member
    Join Date
    May 2007
    Answers
    11

    SDLC and STLc

    hi,

    can anybody tell me, how we map sdlc nad stlc. this question is asked to me in an interview. mapping of stlc with sdlc??????????


  8. #8
    What are the documents to be prepared during the following phases of SDLC?
    and who s preparing those documents during different phases?

    1.Requirement phase
    2. Design phase
    3.Coding
    4.Testing
    5.Maintainance

    Last edited by jainbrijesh; 06-06-2007 at 02:11 AM.

  9. #9

    Re: SDLC and STLc

    Hi
    Mapping with sdlc and stlc is done in V-Model.
    parllely the work will be done along with the development.


  10. #10
    Expert Member
    Join Date
    Nov 2006
    Answers
    518

    Re: documents to be prepared during the phases of SDLC?

    Hi,

    1) Requirement phase - BRS & SRS.
    2) Design phase - HLDD and LLDD.
    3) Coding - Psudo Docs, Flow Charts, Unit Test Cases Docs & their results.
    4) Testing - Strategy, Plan, Test Cases, Results, Defect Report.
    5) Maintainence - CCB Strategy & Plan, Impact Analysis Report, Change Status Report.

    This is as far as I could remember at this moment. There may be more and not all companies may be using all the documents listed above.

    Lack of WILL POWER has caused more failure than
    lack of INTELLIGENCE or ABILITY.

    -sutnarcha-

  11. #11
    bhushanbhangale
    Guest

    Smile Difference between SDLC & STLC

    Hi Friends, Please tell me difference between SDLC & STLC.


  12. #12
    Banned
    Join Date
    Oct 2007
    Answers
    173

    Re: Difference between SDLC & STLC

    hi dear,

    There is quite fade difference between these two:

    One is strictly assured for Quality Assurance process and Other comes under Quality Control process.

    As the name intended SDLC stands for Software Development Life Cycle
    1) Requirement Gathering 2)Analysis 3)Design 4)Coding 5)Testing and 6)Maintenance....


    STLC: 1)Test Planning 2)Test Development 3)Test Analysis 4)Test Scripting 5)Test Execution 6)Defect Reporting ..


    Hope i have answered your question appropriately. Please Revert back to me
    incase of queries..

    Freindly
    PRATAP M


  13. #13
    Junior Member
    Join Date
    Jun 2008
    Answers
    1

    Re: Difference between SDLC & STLC

    Quote Originally Posted by quality_quantity View Post
    hi dear,

    There is quite fade difference between these two:

    One is strictly assured for Quality Assurance process and Other comes under Quality Control process.

    As the name intended SDLC stands for Software Development Life Cycle
    1) Requirement Gathering 2)Analysis 3)Design 4)Coding 5)Testing and 6)Maintenance....


    STLC: 1)Test Planning 2)Test Development 3)Test Analysis 4)Test Scripting 5)Test Execution 6)Defect Reporting ..


    Hope i have answered your question appropriately. Please Revert back to me
    incase of queries..

    Freindly
    PRATAP M
    hi pratap,

    Hi, this is rashmi here . well i have a clear idea about SDLC terms what u have mentioned above , could u plz elaborate on STLC terms that is , Test Development , Test Analysis , Test Scripting , Test Execution , Defect Reporting ,..... plz give clear descriptions for the above ...

    Regards
    Rashmi .......


  14. #14
    Junior Member
    Join Date
    Jun 2007
    Answers
    3

    Re: Difference between SDLC & STLC

    Hi as per my understanding test planning where test plan is prepared by test lead i.e. Introduction,objective,focus,scope,what n what not to test,exit criterias,risks and contingencies etc. Test development preparing all the test related documents for instance clarification document. Test analysis system analyst will analyse the understanding document which is prepared by the tester n gives a clear document. Test scripting writing the test cases in terms of manual testing. Prepare test case documents. Test execution upon execution of the application based on testcases n other scenarios results are seen i.e pass or fail.these test results i.e. Pass/fail/regresss/to test are placed in test report. Results are analysed. Defect reporting based on valid report of test , bugs are tracked n reported as bug. Thanks any one could correct incase if any explaination sounds wrong. Strength is life weakness is death.


  15. #15
    Expert Member
    Join Date
    Jun 2007
    Answers
    260

    Re: Difference between SDLC & STLC


  16. #16
    Junior Member
    Join Date
    Jul 2008
    Answers
    22

    Re: Difference between SDLC & STLC

    SDLC is the process prepared and followed by the development team to work on the project in different phases which also includes STLC

    STLC is a process followed by the testing team to test the developed project STLC is prepared by the testing team


  17. #17
    Junior Member
    Join Date
    Sep 2008
    Answers
    3

    Re: Difference between SDLC & STLC

    As my point of u

    SDLC is nothing but a Sofrware Development Life Cycle

    SDLC is prepared at the time of requirement phase when requirements is come

    STLC is completely in testing phase

    when UCD and BRS Is developed the STLC Phase is come to picture


  18. #18

    Re: Difference between SDLC & STLC

    SDLC is software development life cycle.
    STLC is software testing life cycle.


  19. #19
    Contributing Member
    Join Date
    Dec 2007
    Answers
    42

    Re: Difference between SDLC & STLC

    SDLC and STLC

    Before going into any details. The first point which I want to emphasize is that STLC is a part of SDLC process. The SDLC(Software Development Life Cycle) process goes as follows:

    1. Requirement Phase
    2. Analysis Phase
    3. Design Phase
    4. Development Phase
    5. Testing Phase
    6. Deployment and maintenance phase

    Now, from the above the 5th phase of SDLC is that of testing phase. This is testing phase as a life cycle which is STLC(Software testing life cycle). Here are different phase of testing life cycle.

    1. Test Planning
    2. Test Development
    3. Test Execution
    4. Result Analysis
    5. Bug tracking
    6. Reporting

    Regards,
    Narin Kamuni


  20. #20
    Junior Member
    Join Date
    Sep 2009
    Answers
    2

    Re: Testing Life Cycle

    Quote Originally Posted by irinak View Post
    1. Requirements stage 2. Test plan 3. Test design. 4. Design reviews 5. Code reviews 6. Test cases preparation. 7. Test execution 8. Test reports. 9. Bugs reporting 10. Reworking on patches. 11. Release to production. ************************** the steps in the testing process are as follows. 1. Requirement analysis - testing should begin in the requirements phase of the software life cycle (sdlc). The actual requirement should be understand clearly with the help of requirement specification documents, functional specification documents, design specification documents, use case documents etc. During the requirement analysis the following should be considered. -are the definitions and descriptions of the required capabilities precise? -is there clear delineation between the system and its environment? -can the requirements be realized in practice? -can the requirements be tested effectively? 2. Test planning - during this phase test strategy, test plan, test bed will be created. A test plan is a systematic approach in testing a system or software. The plan should identify: -which aspects of the system should be tested? -criteria for success. -the methods and techniques to be used. -personnel responsible for the testing. -different test phase and test methodologies -manual and automation testing -defect mgmt, configuration mgmt, risk mgmt. Etc -evaluation & identification – test, defect tracking tools 3. Test environment setup - during this phase the required environment will be setup will be done. The following should also be taken in account. - network connectivity’s -all the software/ tools installation and configuration -coordination with vendors and others 4. Test design - during this phase -test scenarios will be identified. -test cases will be prepared. -test data and test scripts prepared. -test case reviews will be conducted. 5. Test automation in this phase the requirement for the automation will be identified. The tools that are to be used will be identified. Designing framework, scripting, script integration, review and approval will be undertaken in this phase. 6. Test execution and defect tracking testers execute the software based on the plans and tests and report any errors found to the development team. In this phase -test cases will be executed. -test scripts will be tested. -test results will be analyzed. -raised the defects and tracking for its closure. 7. Test reports once testing is completed, testers generate metrics and make final reports on their test effort and whether or not the software tested is ready for release. -test summary reports will be prepared -test metrics and process improvements made -build release -receiving acceptance
    Testing Life Cycle
    1. Requirements stage 2. Test plan 3. Test design. 4. Design reviews 5. Code reviews 6. Test cases preparation. 7. Test execution 8. Test reports. 9. Bugs reporting 10. Reworking on patches. 11. Release to production. ************************** the steps in the testing process are as follows. 1. Requirement analysis - testing should begin in the requirements phase of the software life cycle (sdlc). The actual requirement should be understand clearly with the help of requirement specification documents, functional specification documents, design specification documents, use case documents etc. During the requirement analysis the following should be considered. -are the definitions and descriptions of the required capabilities precise? -is there clear delineation between the system and its environment? -can the requirements be realized in practice? -can the requirements be tested effectively? 2. Test planning - during this phase test strategy, test plan, test bed will be created. A test plan is a systematic approach in testing a system or software. The plan should identify: -which aspects of the system should be tested? -criteria for success. -the methods and techniques to be used. -personnel responsible for the testing. -different test phase and test methodologies -manual and automation testing -defect mgmt, configuration mgmt, risk mgmt. Etc -evaluation & identification – test, defect tracking tools 3. Test environment setup - during this phase the required environment will be setup will be done. The following should also be taken in account. - network connectivity’s -all the software/ tools installation and configuration -coordination with vendors and others 4. Test design - during this phase -test scenarios will be identified. -test cases will be prepared. -test data and test scripts prepared. -test case reviews will be conducted. 5. Test automation in this phase the requirement for the automation will be identified. The tools that are to be used will be identified. Designing framework, scripting, script integration, review and approval will be undertaken in this phase. 6. Test execution and defect tracking testers execute the software based on the plans and tests and report any errors found to the development team. In this phase -test cases will be executed. -test scripts will be tested. -test results will be analyzed. -raised the defects and tracking for its closure. 7. Test reports once testing is completed, testers generate metrics and make final reports on their test effort and whether or not the software tested is ready for release. -test summary reports will be prepared -test metrics and process improvements made -build release -receiving acceptance


  21.  Sponsored Ads
    Ad


     
Page 1 of 2 12 LastLast

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  
About us
Applying for a job can be a stressful and frustrating experience, especially for someone who has never done it before. Considering that you are competing for the position with a at least a dozen other applicants, it is imperative that you thoroughly prepare for the job interview, in order to stand a good chance of getting hired. That's where GeekInterview can help.
Interact