{[ promptMessage ]}

Bookmark it

{[ promptMessage ]}

07-01-VerificationTestingPrinciples-notes

07-01-VerificationTestingPrinciples-notes - Outline What...

Info icon This preview shows pages 1–3. Sign up to view the full content.

View Full Document Right Arrow Icon
1 CSE 435: Software Engineering (slides adapted from Ghezzi et al & Stirewalt B. Cheng Verification (See related materials in textbook.) CSE 435: Software Engineering (slides adapted from Ghezzi et al & Stirewalt B. Cheng Outline What are the goals of verification? What are the main approaches to verification? – What kind of assurance do we get through testing? – How can testing be done systematically? – How can we remove defects (debugging)? What are the main approaches to software analysis? – informal vs. formal CSE 435: Software Engineering (slides adapted from Ghezzi et al & Stirewalt B. Cheng Need for verification Designers are fallible even if they are skilled and follow sound principles Everything must be verified, every required quality, process and products – even verification itself… Correctness: must have point of reference – Design is correct wrt requirements – Code is correct wrt design, requirements – Code correctness: does a program work as expected for a given set of inputs CSE 435: Software Engineering (slides adapted from Ghezzi et al & Stirewalt B. Cheng Properties of verification May not be binary (e.g., right, wrong) – severity of defect is important – some defects may be tolerated May be subjective or objective – e.g., usability Even implicit qualities should be verified – because requirements are often incomplete – e.g., robustness
Image of page 1

Info icon This preview has intentionally blurred sections. Sign up to view the full version.

View Full Document Right Arrow Icon
2 CSE 435: Software Engineering (slides adapted from Ghezzi et al & Stirewalt B. Cheng Approaches to verification Experiment with behavior of product – sample behaviors via testing – goal is to find "counterexamples" – dynamic technique Analyze product to deduce its adequacy – analytic study of properties – static technique CSE 435: Software Engineering (slides adapted from Ghezzi et al & Stirewalt B. Cheng Testing and lack of "continuity" Testing samples behaviors by examining "test cases" Impossible to extrapolate behavior of software from a finite set of test cases No continuity of behavior
Image of page 2
Image of page 3
This is the end of the preview. Sign up to access the rest of the document.

{[ snackBarMessage ]}

What students are saying

  • Left Quote Icon

    As a current student on this bumpy collegiate pathway, I stumbled upon Course Hero, where I can find study resources for nearly all my courses, get online help from tutors 24/7, and even share my old projects, papers, and lecture notes with other students.

    Student Picture

    Kiran Temple University Fox School of Business ‘17, Course Hero Intern

  • Left Quote Icon

    I cannot even describe how much Course Hero helped me this summer. It’s truly become something I can always rely on and help me. In the end, I was not only able to survive summer classes, but I was able to thrive thanks to Course Hero.

    Student Picture

    Dana University of Pennsylvania ‘17, Course Hero Intern

  • Left Quote Icon

    The ability to access any university’s resources through Course Hero proved invaluable in my case. I was behind on Tulane coursework and actually used UCLA’s materials to help me move forward and get everything together on time.

    Student Picture

    Jill Tulane University ‘16, Course Hero Intern