Software Verification and Validation

Slides:



Advertisements
Similar presentations
Software Quality Assurance Plan
Advertisements

By: MSMZ. Objective After completing this chapter, you will be able to: Explain 2 contract review stage List the objective of each stage of the contract.
1.Quality-“a characteristic or attribute of something.” As an attribute of an item, quality refers to measurable characteristics— things we are able to.
Systems Analysis, Prototyping and Iteration Systems Analysis.
PERTEMUAN - 2 SOFTWARE QUALITY. OBJECTIVES After completing this chapter, you will be able to: ■ Define software, software quality and software quality.
These slides are designed to accompany Software Engineering: A Practitioner’s Approach, 6/e (McGraw-Hill 2005). Slides copyright 2005 by Roger Pressman.1.
©2003 Prentice Hall Business Publishing, Cost Accounting 11/e, Horngren/Datar/Foster Strategy, Balanced Scorecard, and Strategic Profitability Analysis.
CS 501: Software Engineering Fall 2000 Lecture 14 System Architecture I Data Intensive Systems.
Strategy, Balanced Scorecard, and Strategic Profitability Analysis
OHT 1.1 Galin, SQA from theory to implementation © Pearson Education Limited 2004 The uniqueness of software quality assurance The environments for which.
1 CS 501 Spring 2005 CS 501: Software Engineering Lecture 26 Delivering the System.
Software Quality Assurance
Chapter 1 The Uniqueness of Software Quality Assurance
ERP Enterprise Resource Planning. What is ERP? Software programs that help to manage company-wide business processes, using a common database and shared.
Development and Quality Plans
Chapter 1 The Uniqueness of Software Quality Assurance.
SE513 Software Quality Assurance Lecture04: Contract Review Galin, SQA from Theory to Education Limited 2004.
OHT 3.1 Galin, SQA from theory to implementation © Pearson Education Limited 2004 Software Quality assurance (SQA) SWE 333 Dr Khalid Alnafjan
How To Apply Quality Management
Galin, SQA from theory to implementation © Pearson Education Limited 2004 Review objectives Formal design reviews (FDRs) Participants Preparations The.
S oftware Q uality A ssurance Part One Reviews and Inspections.
Software Quality Assurance Activities
CMSC 345 Fall 2000 Unit Testing. The testing process.
From Research Prototype to Production
SE513 Software Quality Control Lecture01: Introduction to Software Quality Assurance Galin, SQA from Theory to Education Limited.
Project Tracking. Questions... Why should we track a project that is underway? What aspects of a project need tracking?
©Ian Sommerville 2000Software Engineering, 6th edition. Chapter 23Slide 1 Chapter 23 Software Cost Estimation.
This chapter is extracted from Sommerville’s slides. Text book chapter
Quality Activity Matrix Presented by Sandra Toalston President, SanSeek 1.
1 IT Zone Hi Tech Tuesday, February 13, 2002 Software Quality Assurance in the Real World Renee’ E. Jones QA Team Lead The MEDSTAT Group.
OHT 1.1 Galin, SQA from theory to implementation © Pearson Education Limited 2004 The uniqueness of software quality assurance The environments for which.
Chapter 3 Project Management Chapter 3 Project Management Organising, planning and scheduling software projects.
1 CS 501 Spring 2002 CS 501: Software Engineering Lecture 24 Delivering the System.
Improving Design #1 Reduce complexity - narrow-down the project scope - optimize underlying process - eliminate unneeded parts # 2 Find and eliminate redundancies.
Chap 4. Project Management - Organising, planning and scheduling
Project Management. Introduction  Project management process goes alongside the system development process Process management process made up of three.
Operational and Postimplementation
OHT 1.1 Galin, SQA from theory to implementation © Pearson Education Limited 2004 The uniqueness of software quality assurance The environments for which.
1 Object-Oriented Analysis and Design with the Unified Process Figure 13-1 Implementation discipline activities.
 Software Testing Software Testing  Characteristics of Testable Software Characteristics of Testable Software  A Testing Life Cycle A Testing Life.
1 Chapter 1 The Software Quality Challenge. 2 The uniqueness of software quality assurance  DO you think that there is a bug-free software?  Can software.
Chapter 1 Outline - The uniqueness of software quality assurance - The environments for which SQA methods are developed.
P RE - PROJECT P RE - PROJECT SOFTWARE QUALITY COMPONENTS Dr. Ahmad F. Shubita.
10-1 McGraw-Hill/Irwin Copyright © 2007 by The McGraw-Hill Companies, Inc. All rights reserved.
Chapter 1 the uniqueness of software quality assurance Dr. AlaaEddin Almabhouh.
Chapter 3 Project Management Parts of this presentation is extracted from Ian Sommerville’s slides located at
Software Quality Assurance
Group mambers: Maira Naseer (BCS ).
Software Engineering (CSI 321)
Chapter 1 The Uniqueness of Software Quality Assurance
The Development Process of Web Applications
Software Verification and Validation
Software Verification and Validation
Principles of Information Systems Eighth Edition
TQS - Teste e Qualidade de Software (Software Testing and Quality) Introduction To Software Testing Concepts João Pascoal.
Chapter Outline Innovation, Technological Change, and Competition
Assistant Professor of Computer Science Washington State University
The Software Quality Challenge
Different Types of Testing
Succeeding as a Systems Analysts
Quality Quality is “a characteristic or attribute of something.”
Design and Implementation
Operational and Postimplementation
Software Testing and Maintenance Maintenance and Evolution Overview
Chapter 13 Quality Management
Chapter # 1 Overview of Software Quality Assurance
Software Cost Estimation
Software Quality assurance SQA – SWE 333
Test Cases, Test Suites and Test Case management systems
Overview Activities from additional UP disciplines are needed to bring a system into being Implementation Testing Deployment Configuration and change management.
Presentation transcript:

Software Verification and Validation Lecture-01

We want to be able to: 1. Identify the unique characteristics of software as a product and as process that justify separate treatment of its quality issues. 2. Recognize the characteristics of the software environment where professional software develepment and maintenance take place

The uniqueness / differences between a Software Product and an Industrial Product High complexity The potential ways in which a software product can be used with different data / data paths reflecting different incoming data is almost infinite. Manner in which industrial products can be used are usually well-defined. Think about software: every loop with different values of data reflects a different opportunity to see software fail.

The uniqueness / differences between a Software Product and an Industrial Product Invisibility of the product In an industrial product, missing parts are obvious. Something missing? Easily identified. Not so in software products. May not be noticeable for years – if at all!

The uniqueness / differences between a Software Product and an Industrial Product Opportunities to detect defects (“bugs”)?? Consider: Product Development Product Planning Product Manufacturing

The uniqueness / differences between a Software Product and an Industrial Product Product Development: Industrial: Designers and quality assurance (QA) staff check and test the product prototype, in order to detect its defects. Computer Software: once prototype and system testing are concluded, product is ready for development.

The uniqueness / differences between a Software Product and an Industrial Product Product Production Planning: Industrial: Often need new tooling approaches, assembly lines, new manufacturing processes. Results in additional ‘looks’ at products One could say that there is a better chance to discover defects Computer Software: Not required for the software production process Manufacturing of software copies and printing of software manuals are conducted automatically. No real chance to discover additional defects.

The uniqueness / differences between a Software Product and an Industrial Product Product Manufacturing: Industrial: Usually defects uncovered here; easily fixed. Typical burn-in problems; another view of product; stabilizes. These represent additional opportunities to discover defects. Computer Software: We merely copyright, print copies of software and manuals No real chance for additional quality views No real chance for discovering additional defects

SQA Environment Being Contracted: Professional software development is almost always contracted. A defined list of functional requirements that the developed software and its maintenance need to fulfil Budget Time schedule

SQA Environment Subject to Customer-Supplier Relationship In professional software development, there is a constant oversight between customer and developer. Changes will occur; Criticisms will arise. Cooperation is critical to overall project success. Customer availability / relationship is essential and often problematic.

SQA Environment Required Teamwork We need teams due to Time required for development. Workload is too much for a single person A frequent variety of experts needed Database; networking; algorithms; … Wish to benefit from professional mutual support

SQA Environment Cooperation and Coordination with Other Software Teams Other software development teams in the same organization. Hardware development teams in the same organization. Software and hardware development teams of other suppliers. Customer software and hardware development teams that take part in the project’s development.

SQA Environment Interfaces with Other Systems Input interfaces, where other software systems transmit data to your software system. Output interfaces, where your software system transmits processed data to other software systems.

SQA Environment Need to Continue Project despite Team Changes Team members leave, are hired, fired, take unexpected vacations, transferred within the company, and more. Development must continue. Timeline will not change.

SQA Environment Need to continue Software Maintenance for an Extended Period Customers expect to continue utilizing software for a long period. SQA must address development, operations, and maintenance.

Summary Difference between software and industry product Unique characteristics of software Unique characteristics of SQA environment