Scribd
Upload
36 views13 pages

Mirpur University of Science and Technology: Deparment Software Engineering

This document contains lecture notes on software verification and validation. It discusses the adverse effects of faulty software such as deaths, injuries, and financial losses. It then defines software testing as an investigation to provide quality information about software. The lecture covers basic testing, validation, and verification. It also includes in-class activities asking students about their development, customer, and management experiences as they relate to software quality assurance.

Uploaded by

ahsan
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
36 views13 pages

Mirpur University of Science and Technology: Deparment Software Engineering

This document contains lecture notes on software verification and validation. It discusses the adverse effects of faulty software such as deaths, injuries, and financial losses. It then defines software testing as an investigation to provide quality information about software. The lecture covers basic testing, validation, and verification. It also includes in-class activities asking students about their development, customer, and management experiences as they relate to software quality assurance.

Uploaded by

ahsan
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 13

MIRPUR UNIVERSITY OF SCIENCE AND TECHNOLOGY

DEPARMENT OF SOFTWARE ENGINEERING


INTRODUCTION TO SOFTWARE VERIFICATION AND
VALIDATION (cont.)
(lecture # 2)

Maryum Hamdani
(Lecturer)

Date: April 23, 2020


LECTURE CONTENTS

1. Adverse Effects

2. What is Software Testing

3. Basic Testing

SE-362 Software Verification and Validation 3


Adverse Effects of Faulty Software

• Communications: Loss or corruption of communication


media, non delivery of data.

• Space Applications: Lost lives, launch delays.

• Defense and Warfare: Misidentification of friend or foe.

SE-362 Software Verification and Validation 4


Adverse Effects of Faulty Software (Cont’d)

• Transportation: Deaths, delays, sudden acceleration,


inability to brake.

• Safety-critical Applications: Death, injuries.

• Electric Power: Death, injuries, power outages, long-


term health hazards (radiation).

SE-362 Software Verification and Validation 5


Adverse Effects of Faulty Software (Cont’d)

• Money Management: Fraud, violation of privacy, shutdown of


stock exchanges and banks, negative interest rates.
• Control of Elections: Wrong results (intentional or non-
intentional).
• Control of Jails: Technology-aided escape attempts and
successes, accidental release of inmates, failures in software
controlled locks.
• Law Enforcement: False arrests and imprisonments.

SE-362 Software Verification and Validation 6


In class activity #1
(take 5 to 10 mins to answer these questions)

• Your experience as a developer


• What programming experience do you have? (e.g.
course project, internship ... Etc.)
• What language did you use?
• What level of quality you think it had?
• How did you assure it’s quality?

SE-362 Software Verification and Validation 7


In class activity #2
(take 5 to 10 mins to answer these questions)

• Your experience as a customer


• What software do you use and think it is a good
software?
• Why do you think it’s good?
• Looks good, fast, accurate … etc.
• How did you measure it’s goodness?
• Can you compare it to other similar software?

SE-362 Software Verification and Validation 8


In class activity #3
(take 5 to 10 mins to answer these questions)

• Your experience in management


• Did you work in a team for developing a software
before? What was it?
• What was your role in the team?
• Was there any team member responsible for QA?
• How did you divide QA tasks amongst team members?
• What can you do to enhance management of your team
with regards to QA activities?

SE-362 Software Verification and Validation 9


Software testing

• Software testing is an investigation conducted to


provide stakeholders with information about the quality
of the software product or service under test.
• Testing Includes
• Basic testing
• Validation
• Verification

SE-362 Software Verification and Validation 10


Basic testing
• Correctness and completeness
• Free from Faults and Errors
• Causing close to zero Failures
• Software testing can be conducted as soon as executable
software (even if partially complete) exists.

SE-362 Software Verification and Validation 11


Basic testing
• The overall approach to software development often determines
when and how testing is conducted.
• For example, in a phased process, most testing occurs after system
requirements have been defined and then implemented in testable
programs. In contrast, under an agile approach, requirements,
programming, and testing are often done concurrently.

SE-362 Software Verification and Validation 12


REFERENCES

Software Quality Engineering: Testing, Quality Assurance, and


Quantifiable Improvement, Jeff Tian, John-Wiley & sons, 2005

SE-362 Software Verification and Validation 13

You might also like