CIS 841 Verification and Validation Dr David A
- Slides: 16
CIS 841 – Verification and Validation Dr David A. Gustafson dag@cis. ksu. edu http: //www. cis. ksu. edu/~dag 841 f 06 intro 1 1
Goals u Prepare students to be software testers and researchers in software testing. In particular, students should understand the current state of the art in software testing, be able to read and evaluate current literature in software testing, and be able to plan an effective testing effort. 841 f 06 intro 1 2
Specific Goals of CIS 841 u understanding of software – faults, failures, errors, and testing u knowledge of “state-of-the-practice” and “state-of-the-art” (current articles) u understanding of issues, terminology, foundations, and techniques u learning to read the literature 841 f 06 intro 1 3
Conduct of Course u TU 9: 30 -10: 45 am u Discussions/Lectures u Homework u Exams u Read Syllabus u Read announcements 841 f 06 intro 1 4
Off Campus u Unless noted, due dates for off-campus students are the same as for on-campus students – contact me if this is a problem u For in class work, email as soon as possible but definitely before next class (on-campus) – Including today’s work u Turn in proctor information as soon as possible 841 f 06 intro 1 5
Active Learning u TTYP u Venn Diagrams u Classification u Definitions u 1 minute paper u Meta-cognition 841 f 06 intro 1 6
Exams cover u Lectures and Discussions u Homework u Articles and Readings u Postings on web u Pre. Lecture Quizzes 841 f 06 intro 1 7
Grading u two midterms (100 -150 pts) u one final (200 pts) u Prelecture quiz (4 -10 pts) u homework (10 -20 pts) – due beginning of class (10% off) u 6 main tasks (30 -100 pts) u Final paper (100 pts) u 90% of total points is an A, 80% is a B 841 f 06 intro 1 8
Grade Information u will be available on kstate online – Online. ksu. edu 841 f 06 intro 1 9
Availability of Lectures u world wide web – Powerpoint » Pre » Post – Tegrity video » Link from class web page below my webpage » www. cis. ksu. edu/~dag 841 f 06 intro 1 10
Articles u current information – sometimes unproven u different viewpoints u different styles, terminology, levels u little background information 841 f 06 intro 1 11
How do you read an article? u My approach – Read abstract – Check refs – Read conclusions – Only then, read paper 841 f 06 intro 1 12
TTYP 1 definitions u Define – Error – Fault – Failure domain 841 f 06 intro 1 13
TTYP 2 worst faults u What kind of fault is hardest to find? u Why? 841 f 06 intro 1 14
For Thursday, Aug 24 Write a correct program in C++ that has two numeric inputs, and a deterministic output. E. g. area Find 1) a fault that would be very easy to find, and 2) a fault that would be very hard to find. Estimate the number of the inputs that show each fault. (a fault would be a change to something in the correct version that would make it produce the wrong output for some inputs) Build a web page for 841 and post your program and the faults on that web page. Send me your url 841 f 06 intro 1 15
1 minute paper u What questions about testing would you like to answer? Or be answered? 841 f 06 intro 1 16
- Verification and validation
- Verification and validation
- Verification and validation
- Verification and validation plan
- Asme v&v 10
- Verification and validation
- Verification and validation
- Verification and validation plan
- Verification and validation
- A software verification and validation method. section 19
- Software verification and validation plan
- Is unit testing verification or validation
- Method verification vs validation
- Method verification vs validation
- 18004149025
- 841 x 1189
- 841*594