CS532 TERM PAPER MEASUREMENT IN SOFTWARE ENGINEERING NAVEEN KUMAR SOMA.

Slides:



Advertisements
Similar presentations
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 27 Slide 1 Quality Management.
Advertisements

Process Database and Process Capability Baseline
W5HH Principle As applied to Software Projects
Software Quality Metrics
Software Engineering II - Topic: Software Process Metrics and Project Metrics Instructor: Dr. Jerry Gao San Jose State University
8/28/2005ECEN5543 Req Elicitation1 Targets of Requirements Engineering ECEN 5543 SW Engineering of Standalone Programs University of Colorado, Boulder.
Software Metrics II Speaker: Jerry Gao Ph.D. San Jose State University URL: Sept., 2001.
Project Management Metrics.
WM Software Process & Quality Generic Processes - Slide #1  P. Sorenson SPiCE Reference Model - how to read Chapter 5 Capability Levels (process.
These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 6/e and are provided with permission by.
Name of Student Name of Instructor Date Submitted:
Software Process and Product Metrics
Project Tracking and Scheduling Infsy 570 Dr. R. Ocker.
Software Verification and Validation (V&V) By Roger U. Fujii Presented by Donovan Faustino.
Capability Maturity Model
The Importance and Value of Process Improvement. Rationale for Process Improvement Establishing an attitude and culture of quality improvement and continuous.
Chapter : Software Process
S T A M © 2000, KPA Ltd. Software Trouble Assessment Matrix Software Trouble Assessment Matrix *This presentation is extracted from SOFTWARE PROCESS QUALITY:
Performance Measurement and Analysis for Health Organizations
VTT-STUK assessment method for safety evaluation of safety-critical computer based systems - application in BE-SECBS project.
Software System Engineering: A tutorial
Business Analysis and Essential Competencies
Chapter 6 : Software Metrics
Software Engineering Lecture # 17
Evaluating a Research Report
What is a Business Analyst? A Business Analyst is someone who works as a liaison among stakeholders in order to elicit, analyze, communicate and validate.
Software Project Management With Usage of Metrics Candaş BOZKURT - Tekin MENTEŞ Delta Aerospace May 21, 2004.
1 Chapter 23 Estimation for Software Projects. 2 Software Project Planning The overall goal of project planning is to establish a pragmatic strategy for.
® IBM Software Group © 2006 IBM Corporation PRJ480 Mastering the Management of Iterative Development v2 Module 6: Phase Management -Transition.
Software Engineering Spring (C) Vasudeva VarmaClass of 32 CS3600: Software Engineering: Process and Product* *Most of the Content drawn.
Software Project Management Lecture # 3. Outline Chapter 22- “Metrics for Process & Projects”  Measurement  Measures  Metrics  Software Metrics Process.
Company LOGO Team assignment 03 Team 04 K15T02. Members… 1.Hoàng Thị Kim Dâng 2.Thái Thanh Nhã 3.Trần Thị Mộng Hà 4.Trần Tiễn Hưng 5.Chu Thị Thu Hương.
CS Process Improvement CMM Hans Van Vliet, Software Engineering, Principles and Practice, 3 rd edition, John Wiley & Sons, Chapter 6. W. Humphrey,
Process Improvement. It is not necessary to change. Survival is not mandatory. »W. Edwards Deming Both change and stability are fundamental to process.
Enabling Reuse-Based Software Development of Large-Scale Systems IEEE Transactions on Software Engineering, Volume 31, Issue 6, June 2005 Richard W. Selby,
Chapter 3: Software Project Management Metrics
Cmpe 589 Spring 2006 Lecture 2. Software Engineering Definition –A strategy for producing high quality software.
SP_IRS Introduction to Research in Special and Inclusive Education(Autumn 2015) Lecture 1: Introduction Lecturer: Mr. S. Kumar.
CSc 461/561 Information Systems Engineering Lecture 5 – Software Metrics.
Ch-1 Introduction The processes used for executing a software project have major effect on quality of s/w produced and productivity achieved in project…
Project Management Cross lifecycle Activity
CSC480 Software Engineering Lecture 8-9 September 20, 2002.
CHAPTER 2 Research Methods in Industrial/Organizational Psychology
A Metrics Program. Advantages of Collecting Software Quality Metrics Objective assessments as to whether quality requirements are being met can be made.
MODEL-BASED SOFTWARE ARCHITECTURES.  Models of software are used in an increasing number of projects to handle the complexity of application domains.
1 Software Engineering: A Practitioner’s Approach, 6/e Chapter 15a: Product Metrics for Software Software Engineering: A Practitioner’s Approach, 6/e Chapter.
Recall The Team Skills 1. Analyzing the Problem (with 5 steps) 2. Understanding User and Stakeholder Needs 3. Defining the System A Use Case Primer Organizing.
Hussein Alhashimi. “If you can’t measure it, you can’t manage it” Tom DeMarco,
Software Measurement Measuring software indicators: metrics and methods Jalote-2002,
Requirements Analysis
Software Measurement: A Necessary Scientific Basis By Norman Fenton Presented by Siv Hilde Houmb Friday 1 November.
Search Engine Optimization © HiTech Institute. All rights reserved. Slide 1 Click to edit Master title style What is Business Analysis Body of Knowledge?
Books Visualizing Data by Ben Fry Data Structures and Problem Solving Using C++, 2 nd edition by Mark Allen Weiss MATLAB for Engineers, 3 rd edition by.
Capability Maturity Model. CS460 - Senior Design Project I (AY2004)2 Immature Organisations Software processes are often rigorously followed. Organisation.
Information Technology Project Management, Seventh Edition.
© 2008 Thomson South-Western. All Rights Reserved Slides by JOHN LOUCKS St. Edward’s University.
Module 4: Effect of Agile on the DoD Program Office TLO: Given a DoD program involved in software development using Agile philosophy methodologies, the.
CS 577b: Software Engineering II
CS4311 Spring 2011 Process Improvement Dr
Software Engineering (CSI 321)
CHAPTER 2 Research Methods in Industrial/Organizational Psychology
Software Engineering: A Practitioner’s Approach, 6/e Chapter 23 Estimation for Software Projects copyright © 1996, 2001, 2005 R.S. Pressman & Associates,
Software Engineering Experimentation
Software Engineering I
Software metrics.
Measurement What is it and why do it? 2/23/2019
Software Engineering: A Practitioner’s Approach, 6/e Chapter 23 Estimation for Software Projects copyright © 1996, 2001, 2005 R.S. Pressman & Associates,
Goal-Driven Continuous Risk Management
Goal-Driven Software Measurement
Chapter 26 Estimation for Software Projects.
Presentation transcript:

CS532 TERM PAPER MEASUREMENT IN SOFTWARE ENGINEERING NAVEEN KUMAR SOMA

Introduction What is software measurement? GQM technique

We use software measures to derive A basis for estimates, A basis for estimates, To track project progress, To track project progress, To determine (relative) complexity, To determine (relative) complexity, To help us to understand when we have achieved a desired state of quality, To help us to understand when we have achieved a desired state of quality, To analyze To analyze To experimentally validate best practices To experimentally validate best practices

Goals of software measurement To predict the error-proneness of a system using software measures from its design phase. To extract quantitative features from the representation of a software design to enable us to predict the degree of maintainability of a software system. To extract quantifiable features from the representation of a software design to enable us to predict the amount of effort required to build the software described by that design.

Technical Areas Model Software Metrics Data

Reliability Simplicity S1.1S2.2S3.3

Reasons for Software Measurement Understanding Software Baseline models and relationships Baseline models and relationships Key process characteristics Key process characteristics Managing Software Project Planning and estimating Planning and estimating Tracking actual versus estimates Tracking actual versus estimates Validating models Validating models Guiding Process Improvement Understanding Understanding Assessing Assessing Packaging Packaging

Measurement Process and Different Models High Level Model High Level Model Detailed Model Detailed Model

HIGH LEVEL MODEL 1 First we should measure and design the measurement method 2The rules of the measurement method are applied to a software or piece of software 3The applications of the measurement method rules produce a result. 4 The measurement result is exploited in a quantitative or qualitative model.

High Level Model Design Application Analysis Exploitation

Detailed Model Design of Measurement method Design of Meta Model Concept to be measured Definition of numerical assignment rules

Detailed Model Definition Of objectives Concept to Be Measured Meta Model Numerical Assignment Rules

Validation Requirements Validation Frame Work

Conclusion Measurement is must for any product to become famous Output of measurement method will be context based Depends on how well the user analyses and uses the terms