Software verification and Validation

Slides:



Advertisements
Similar presentations
Project Estimation: Metrics and Measurement
Advertisements

Metrics. A Good Manager Measures measurement What do we use as a basis? size? size? function? function? project metrics process metrics process product.
Chapter 4 Software Process and Project Metrics
These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 6/e and are provided with permission by.
These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 6/e and are provided with permission by.
Metrics for Process and Projects
Metrics for Process and Projects
1 These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 5/e and are provided with permission by.
Project Change Management
Software Quality Metrics
Software Engineering II - Topic: Software Process Metrics and Project Metrics Instructor: Dr. Jerry Gao San Jose State University
Software Process and Product Metrics
Page 1 COCOMO Model The original COCOMO model was first published by Barry Boehm in 1981 at CSE Center for Software Engineering. This is an acronym derived.
OHT 21.1 Galin, SQA from theory to implementation © Pearson Education Limited 2004 Software Quality assurance (SQA) SWE 333 Dr Khalid Alnafjan
1 SOFTWARE MAINTENANCE. 2 Software Maintenance Software maintenance is often considered to be an unpleasant, time consuming, expensive and unrewarding.
Managing the development and purchase of information systems (Part 1)
Cmpe 589 Spring Software Quality Metrics Product  product attributes –Size, complexity, design features, performance, quality level Process  Used.
Software Quality Assurance Activities
Software System Engineering: A tutorial
Software Estimation and Function Point Analysis Presented by Craig Myers MBA 731 November 12, 2007.
Software Engineering Software Process and Project Metrics.
Chapter 6 : Software Metrics
Galin, SQA from Theory to Implementation
These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 6/e and are provided with permission by.
Software Engineering Modern Approaches Eric Braude and Michael Bernstein 1.
Prof. Mohamed Batouche “If you can’t measure it, you can’t manage it” Tom DeMarco,
Software Project Management Lecture # 3. Outline Chapter 22- “Metrics for Process & Projects”  Measurement  Measures  Metrics  Software Metrics Process.
Software Quality Metrics
OHT 21.1 Galin, SQA from theory to implementation © Pearson Education Limited 2004 Software Quality assurance (SQA) SWE 333 Dr Khalid Alnafjan
Software Metrics – part 2 Mehran Rezaei. Software Metrics Objectives – Provide State-of-art measurement of software products, processes and projects Why.
Lecture 4 Software Metrics
OHT 21.1 Galin, SQA from theory to implementation © Pearson Education Limited 2004 Objectives of quality measurement Classification of software quality.
1 Chapter 3 1.Quality Management, 2.Software Cost Estimation 3.Process Improvement.
Chapter 3: Software Project Management Metrics
SOFTWARE PROCESS AND PROJECT METRICS. Topic Covered  Metrics in the process and project domains  Process, project and measurement  Process Metrics.
A Metrics Program. Advantages of Collecting Software Quality Metrics Objective assessments as to whether quality requirements are being met can be made.
Lesson 1: Examining Professional Project Management Topic 1A: Identify Project Management Processes.
Business Analysis. Business Analysis Concepts Enterprise Analysis ► Identify business opportunities ► Understand the business strategy ► Identify Business.
Hussein Alhashimi. “If you can’t measure it, you can’t manage it” Tom DeMarco,
Chapter 22 Metrics for Process and Projects Software Engineering: A Practitioner’s Approach 6 th Edition Roger S. Pressman.
1 These slides are designed to accompany Software Engineering: A Practitioner’s Approach, 7/e (McGraw-Hill 2009). Slides copyright 2009 by Roger Pressman.
These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 6/e and are provided with permission by.
SwCDR (Peer) Review 1 UCB MAVEN Particles and Fields Flight Software Critical Design Review Peter R. Harvey.
M ANAGKEMENT COMPONENTS OF SOFTWARE QUALITY. S OFTWARE QUALITY METRICS Chapter 21.
Configuration Management
Software Quality Control and Quality Assurance: Introduction
Software Metrics 1.
Software quality metrics
Chapter 11: Software Configuration Management
Software Verification and Validation
Configuration Management
Software Engineering (CSI 321)
IEEE Std 1074: Standard for Software Lifecycle
د. حنان الداقيز خريف /28/2016 Software Quality Assurance ضمان جودة البرمجيات ITSE421 5 – The components of the SQA.
Why Do We Measure? assess the status of an ongoing project
BASIC DEFINITIONS Errors : An error is a mistake, misconception, or misunderstanding on the part of a software developer. In the category of developer.
Software Metrics “How do we measure the software?”
Why Do We Measure? assess the status of an ongoing project
Chapter 25 Process and Project Metrics
Chapter 11: Software Configuration Management
Software metrics.
Why Do We Measure? assess the status of an ongoing project
Chapter # 7 Software Quality Metrics
Metrics for process and Projects
Why Do We Measure? assess the status of an ongoing project
Chapter 32 Process and Project Metrics
Metrics for Process and Projects
Software Reviews.
Presentation transcript:

Software verification and Validation

If you can’t measure it, you can’t manage it Tom DeMarco, 1982

What to measure Process Measure the efficacy of processes. What works, what doesn't. Project Assess the status of projects. Track risk. Identify problem areas. Adjust work flow. Product Measure predefined product attributes

What to measure Process Measure the efficacy of processes. What works, what doesn't. Code quality Programmer productivity Software engineer productivity Requirements, design, testing and all other tasks done by software engineers Software Maintainability Usability And all other quality factors Management Cost estimation Schedule estimation, Duration, time Staffing

Process Metrics Process metrics are measures of the software development process, such as Overall development time Type of methodology used Process metrics are collected across all projects and over long periods of time. Their intent is to provide indicators that lead to long-term software process improvement.

Project Metrics Project Metrics are the measures of Software Project and are used to monitor and control the project. Project metrics usually show how project manager is able to estimate schedule and cost They enable a software project manager to: Minimize the development time by making the adjustments necessary to avoid delays and potential problems and risks. Assess product cost on an ongoing basis & modify the technical approach to improve cost estimation.

Product metrics Product metrics are measures of the software product at any stage of its development, from requirements to installed system. Product metrics may measure: How easy is the software to use How easy is the user to maintain The quality of software documentation And more ..

Why do we measure? Determine quality of piece of software or documentation Determine the quality work of people such software engineers, programmers, database admin, and most importantly MANAGERS Improve quality of a product/project/ process

Why Do We Measure? To assess the benefits derived from new software engineering methods and tools To close the gap of any problems (E.g training) To help justify requests for new tools or additional training

Examples of Metrics Usage Measure estimation skills of project managers (Schedule/ Budget) Measure software engineers requirements/analysis/design skills Measure Programmers work quality Measure testing quality And much more …

IEEE definitions of software quality metrics A quantitative measure of the degree to which an item possesses a given quality attribute. A function whose inputs are software data and whose output is a single numerical value that can be interpreted as the degree to which the software possesses a given quality attribute.

Main objectives of software quality metrics Facilitate management control, planning and managerial intervention. Based on: Deviations of actual from planned performance Deviations of actual timetable and budget performance from planned. Identify situations for development or maintenance process improvement (preventive or corrective actions). Based on: Accumulation of metrics information regarding the performance of teams, units, etc.

Error density metrics CED DED WCED WDED WCEF WDEF Code Name Calculation formula CED Code Error Density NCE CED = ----------- KLOC DED Development Error Density NDE DED = ----------- WCED Weighted Code Error Density WCE WCDE = --------- WDED Weighted Development Error Density WDE WDED = --------- WCEF Weighted Code Errors per Function Point WCEF = ---------- NFP WDEF Weighted Development Errors per Function Point WDEF = ---------- NCE = The number of code errors detected by code inspections and testing. NDE = total number of development (design and code) errors) detected in the development process. WCE = weighted total code errors detected by code inspections and testing. WDE = total weighted development (design and code) errors detected in development process.

Error severity metrics Code Name Calculation formula ASCE Average Severity of Code Errors WCE ASCE = ----------- NCE ASDE Average Severity of Development Errors WDE ASDE = ----------- NDE NCE = The number of code errors detected by code inspections and testing. NDE = total number of development (design and code) errors detected in the development process. WCE = weighted total code errors detected by code inspections and testing. WDE = total weighted development (design and code) errors detected in development process.

Software process timetable metrics Code Name Calculation formula TTO Time Table Observance MSOT TTO = ----------- MS ADMC Average Delay of Milestone Completion TCDAM ADMC = ----------- MSOT = Milestones completed on time. MS = Total number of milestones. TCDAM = Total Completion Delays (days, weeks, etc.) for all milestones.

Error removal effectiveness metrics Code Name Calculation formula DERE Development Errors Removal Effectiveness NDE DERE = ---------------- NDE + NYF DWERE Development Weighted Errors Removal Effectiveness WDE DWERE = ------------------ WDE+WYF NDE = total number of development (design and code) errors) detected in the development process. WCE = weighted total code errors detected by code inspections and testing. WDE = total weighted development (design and code) errors detected in development process. NYF = number software failures detected during a year of maintenance service. WYF = weighted number of software failures detected during a year of maintenance service.

HD calls density metrics Code Name Calculation Formula HDD HD calls density NHYC HDD = -------------- KLMC WHDD Weighted HD calls density WHYC WHYC = ------------ NHYC = the number of HD calls during a year of service. KLMC = Thousands of lines of maintained software code. WHYC = weighted HD calls received during one year of service. NMFP = number of function points to be maintained.

Severity of HD calls metrics Code Name Calculation Formula ASHC Average severity of HD calls WHYC ASHC = -------------- NHYC NHYC = the number of HD calls during a year of service. WHYC = weighted HD calls received during one year of service.

HD success metrics Code Name Calculation Formula HDS HD service success NHYOT HDS = -------------- NHYC NHYNOT = Number of yearly HD calls completed on time during one year of service. NHYC = the number of HD calls during a year of service.

Summary Metrics Importance Product/Process metrics