Verification And Validation

1,066 views
959 views

Published on

0 Comments
1 Like
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total views
1,066
On SlideShare
0
From Embeds
0
Number of Embeds
5
Actions
Shares
0
Downloads
35
Comments
0
Likes
1
Embeds 0
No embeds

No notes for slide

Verification And Validation

  1. 1. Group 3:<br />Johannes Bönner, Luka Hale, Paul Knulst<br />Christian Knutz, Tim Janssen<br />Verificationand Validation<br />
  2. 2. Do youhaveanyQuestions?<br />Pleaseaskthem after thepresentation!<br />
  3. 3. Content<br />Definition of validation and verification<br />Structure of a test plan<br />How to plan V&V<br />Methods of V&V<br />Why is V&V essential in software engineering<br />Questions<br />
  4. 4. We need verification and validation to…<br />…ensurethatthesoftwaresystemmeetstherequirementsofthecustomer<br />… ensurethatthesystemsperformanceisacceptable<br /> … find errorsandbugs in thesystembeforeitisdeliveredtothecustomer<br />
  5. 5. Validation vs. Verification<br />Validation:<br />Doesthe System reallymeettherequirementsandexpectaionsofthecustomer?<br />"Are we building the right product”.<br /><ul><li>Verification:
  6. 6. Doesthesystemmeetthefunctionaland non functionalrequirements?
  7. 7. "Are we building the product right”.</li></li></ul><li>Structureof a softwaretest plan<br />Is not a staticdocument, but envolvesduringthedevelopment<br />Hastocontain:<br />The testprocedure<br />Traceabilityofrequirements<br />Testedproducts<br />Schedulingoftests<br />Test recordingprocedures<br />Hard- andsoftwarerequirements<br />
  8. 8. Howto plan V&V?<br />V-Model<br />Desingingtestsforeverystageofthesoftwaredevelopement<br />Execute thetests in reverse order<br />Didwedevelopthesystemaswewantedto?<br />
  9. 9. Methodstoverifyandvalidatesoftwaresystems<br />White-Box-Testing (Integration tests)<br />The testerasaccsesstothesourcecode<br />The testerhasknowledgeoftheinnerfunctionalityofthesystem<br />Advantages:<br />Low costs<br />Support bydevelopingtools (like Unit-Test creation in Netbeans)<br />Disantvantages:<br />Nosystemrequirementsaretestes<br />Workflow errorscouldstayundetected<br />
  10. 10. Methodstoverifyandvalidatesoftwaresystems<br />Black-Box-Testing (Delivery-Tests)<br />The testerhasnoaccsesstothesourcecode<br />The testerhasnoknowledgeoftheinnerfunctionalityofthe System<br />Advantages:<br />Tests ifthesystemmeetsthegivenrequirements<br />Tests the hole system in workflowsituations<br />Disadvantages:<br />High costs<br />Novisibleresultslikeerrormessagesorthrownexceptions<br />
  11. 11. Methodstoverifyandvalidatesoftwaresystems<br />Software inspection<br />Goal: identifyingdefects<br />ImportantRoles:<br />Author<br />Moderator<br />Inspector<br />Reader<br />Recorder<br />
  12. 12. Methodstoverifyandvalidatesoftwaresystems<br />Automatedstaticanalysis<br />Code will not beexecuted<br />Helpsto find:<br />Unreachablesourcecode<br />Variables whichare not inizializied<br />Missingoverridestatements<br />Weknowthisbecauseofpluginslike checkstyle<br />
  13. 13. Whyis V&V so essential in sofwareengineering?<br />Makesitpossibleto find erroswhiledevelopingsoftware<br />Ensurethatthesoftwaremeetstheexpectationsofthecustomer<br />Ensurethat all functionsconformtotherequirements<br />
  14. 14. Howare V&V linkedtosoftwaredevelopementprocesses?<br />The developmentprocessand V&V arelinkedheavilybecause:<br />Itmakesiteasiertomeetthereqiurements<br />Ithelpstoreducecostsoftesting<br />Ithelpstoimprovethesoftwarequality<br />A goodexampleforthislinkingisthe V-Model wedescribedearlier<br />
  15. 15. Never testtobesurethatthesoftwarehasnodefects!!!Becausethatis just impossible<br />
  16. 16. Questions???<br />

×