Software Testing - Verification VS Validation

Ғылым және технология

Subscribe to my channel TechvedasLearn for the latest update.
Software Testing - Verification VS Validation
Friends Verification and validation are independent procedures that are used together for checking that a product, service, or system meets its requirements and specifications. These are critical components of a quality management system.
In this video, let's try to understand the concept of Verification and Validation in an easy-to-understand manner.
#softwaretesting
#VerificationVSValidation
#DifferenceBetweenVerificationAndValidation
#WhatIsVerificationInSoftwareTesting
#WhatIsValidationInSoftwareTesting
#softwaretestingcourses
#softwaretester
#softwaredevelopmentlifecycle
#sdlc
Software Development Life Cycle:
• Waterfall Model for So...
Complete playlist link for Embedded System videos
• Embedded Systems Block...
Complete playlist link for Pointers in C
• Understanding Pointers...
Complete playlist link for Unified Modeling Language (UML) videos
• Unified Modeling Langu...
Complete playlist link for CAN Protocol
• CAN Protocol Tutorial ...
Contact- techvedas.learn@gmail.com

Пікірлер: 18

  • @TechVedas
    @TechVedas Жыл бұрын

    Software Development Life Cycle: kzread.info/dash/bejne/iaGpt7WEf7i8eKQ.html

  • @ibukuntemitopesamuel7603
    @ibukuntemitopesamuel7603 Жыл бұрын

    This guy has solved my 10 years old headache on V&V🤣🤣... Thank you!!

  • @QAToolBox
    @QAToolBox Жыл бұрын

    This is an EXCELLENT video! Thank you for sharing this information!

  • @TechVedas
    @TechVedas Жыл бұрын

    Complete playlist link for Unified Modeling Language (UML) videos kzread.info/dash/bejne/lZqumqWld8KngKw.html

  • @bennguyen1313
    @bennguyen1313Ай бұрын

    Are most big companies using the SCRUM / Kanban methodology (or framework) to satisfy the AGILE/Waterfall/V-Model philosophy (SDLC) ? I'd like to move away from a rapid-prototype environment to something more formal in order to develop high quality/safe products containing embedded software.. for ANY industry.. Aerospace (like Lockhead's SEAL Level X, Boeing , DDPMAS, DAL A to E etc) , Medical or Nuclear industries.. even Automtovie. I'd love to see a trivial project example that shows all the steps and outputs. For example, assuming I document the process on how the code is generated, what constitutes proof that it's safe? Static Analysis? Code Coverage - Statement (Level C), Decision (Level B), MCDC (Level A)? Who defines the unit tests? I imagine there are differences between the industries.. FAA : DO-178X , DO 331 , ARP4754A , ED-12C FDA : 13485 , ISO14971 , IEC 62304 , SaMD and DOE Nuclear : 414.1x, (Automotive : 26262) but what are the typical tools/software needed, and the typical document/artifacts in the various stages of the software life cycle? I saw a good video by CEMILAC Education Program "Airborne Software Development & Certification Process" and it's a bit overwhelming: Requirement Management - (IBM Ration) DOORS, JAMA, Xebrio, rmtoo florath , doorstop-dev / doorstop , reqview Static Structural Source Code Analysis - Parasoft, PolySpace, CodeSonar, horusec , SonarCloud, veracode PREFast, TBrun, LDRA Dynamic Analysis / Modified Condition/Decision Coverage (MC/DC) - VectorCAST, RapiTest Traceability Tools: Reqtify , Polarion , McCabe Configuration Management / Storage and Version Control System - Git, SourceSafe, Mercurial, MS TFS, ClearCase QA / ALM- Helix ALM for Managing Artifacts, Establishing Traceability, Documenting / Enforcing Processes, etc (I)V&V / Unit Test Automation - VectorCAST, LDRA Testbed , Mathworks Simulink DO Qualification Kit Continuous Integration / CD - Continuous Delivery/Deployment - Jenkins, Bamboo, or GitLab CI/CD And what is the general attitude towards open source software (ex. FreeRTOS) and code-generation tools (ex. ST's Cube MX)? Also, how do CPLD and FPGAs fit in to the embedded software picture.. since not exactly software nor hardware, since they are programmable devices written in an programming language like VHDL , (system) verilog , Amaranth HDL ? How would DO-254 apply to HDLs?

  • @nasiru25
    @nasiru256 ай бұрын

    Unit testing and integration testing is not for validation testing it's for verification

  • @arunasavyasachi5617
    @arunasavyasachi56176 ай бұрын

    Thank you so much 🙂

  • @atiyawarsi111
    @atiyawarsi111 Жыл бұрын

    Thnx a lot

  • @akhilkr100
    @akhilkr1004 ай бұрын

    Great

  • @vinajain959
    @vinajain959 Жыл бұрын

    How we solve software debugging code ? What is steps for to develop driver for new function ?

  • @vinajain959
    @vinajain959 Жыл бұрын

    If ADC driver is not working how we will debugg it ?

  • @khushinsavla
    @khushinsavla Жыл бұрын

    A bit enthusiastic while talking and a bit fast while talking 😅😅

  • @vinajain959
    @vinajain959 Жыл бұрын

    How will we write ADC driver ?

  • @valyrianchicken
    @valyrianchicken10 ай бұрын

    Watch at x1.5 speed, you are welcome.

  • @buvaneswaranamaresan2871

    @buvaneswaranamaresan2871

    8 ай бұрын

    X2😊

  • @bobolinho2004
    @bobolinho2004 Жыл бұрын

    This is incorrect. Verification is not static testing only. I agree that the foundation istqb sylabus lets place of interpretation. But to understand better verification vs validation start first with Test manager sylabus.

  • @bobolinho2004

    @bobolinho2004

    Жыл бұрын

    Best video I found so far on youtube describing it is kzread.info/dash/bejne/X2pnrLp-nNS2kbw.html&feature=share

Келесі