International Workshop on Future Software Technology 2005/11/8 - 10 Two approaches in Empirical Software Engineering Kenichi Matsumoto Nara Institute of.

Slides:



Advertisements
Similar presentations
1 Accumulative Versioning File System Moraine and Its Application to Metrics Environment Mame Tetsuo Yamamoto * Makoto Matsushita * Katsuro Inoue *,**
Advertisements

Low Defect Potentials (< 1 per function point)
The Experience Factory May 2004 Leonardo Vaccaro.
Planning a measurement program What is a metrics plan? A metrics plan must describe the who, what, where, when, how, and why of metrics. It begins with.
A GOAL-BASED FRAMEWORK FOR SOFTWARE MEASUREMENT
Software metrics Selected key concepts. Introduction Motivation:  Management:  Appraisal  Assurance  Control  Improvement  Research:  Cause-effect.
Modeling and Validation Victor R. Basili University of Maryland 27 September 1999.
SE 325/425 Goal, Question, Metric Approach Autumn 2006
Gifts in the treasure chest of Methodology: A personal view Rolf Steyer Friedrich Schiller University Jena Institute of Psychology Department of Methodology.
An Approach to Measure Java Code Quality in Reuse Environment Aline Timóteo Advisor: Silvio Meira Co-advisor: Eduardo Almeida UFPE.
Building Knowledge-Driven DSS and Mining Data
Software Process and Product Metrics
DECISION SUPPORT FOR RE-PLANNING OF SOFTWARE PRODUCT RELEASES S. M. Didar-Al-Alam Dept. of Computer Science University of Calgary, Calgary, AB, Canada.
Approaches to ---Testing Software Some of us “hope” that our software works as opposed to “ensuring” that our software works? Why? Just foolish Lazy Believe.
Teachers Name : Suman Sarker Telecommunication Technology Subject Name : Computer Controller System & Robotics Subject Code : 6872 Semester :7th Department.
CEN 4935 Senior Software Engineering Project Joe Voelmle.
LÊ QU Ố C HUY ID: QLU OUTLINE  What is data mining ?  Major issues in data mining 2.
IWFST20051 A Research Framework for Empirical Software Engineering Collaboration and Its Application in a Software Development Project Yoshiki Mitani*,
Chapter 8 : Software Quality Assurance Juthawut Chantharamalee Curriculum of Computer Science Faculty of Science and Technology, Suan Dusit University.
University of Southern California Center for Systems and Software Engineering GQM, GQM+ Supannika Koolmanojwong CSCI577 Spring 2013 (C) USC-CSSE1.
ISESE2004 ymitani EASE/NAIST1 An Experimental Framework for Japanese Academic-Industry Collaboration in Empirical Software Engineering Research Yoshiki.
Software Engineering Laboratory, Department of Computer Science, Graduate School of Information Science and Technology, Osaka University 1 Refactoring.
SOFTWARE ENGINEERING1 Introduction. Software Software (IEEE): collection of programs, procedures, rules, and associated documentation and data SOFTWARE.
SYSE 802 John D. McGregor Module 8 Session 2 Platforms, Ecosystems, and Innovations.
Chapter 6 : Software Metrics
Evaluation of software engineering. Software engineering research : Research in SE aims to achieve two main goals: 1) To increase the knowledge about.
Workshop on Computer-Supported Knowledge Collaboration, Shanghai, July 7, Current Status of Software Industry in Japan.
Copyright © 2010 Nara Institute of Science and Technology / Osaka University Standardizing the Software Tag in Japan for Transparency of Development Profes.
Bayesian Graphical Models for Software Testing David A Wooff, Michael Goldstein, Frank P.A. Coolen Presented By Scott Young.
Department of Computer Science, Graduate School of Information Science & Technology, Osaka University A Method to Detect License Inconsistencies for Large-
Data-Driven Transaction Based Unit Tests Engin Yorgancıoğlu Volkan Sevinçok Turkey.
E 2 ESQuaReD Software Product Line Testing Part V : SPL-Driven Test Processes Myra CohenMatthew Dwyer Laboratory for Empirically-based Software Quality.
Thomas L. Gilchrist Testing Basics Set 4: Strategies & Metrics By Thomas L. Gilchrist, 2009.
Experimentation in Computer Science (Part 1). Outline  Empirical Strategies  Measurement  Experiment Process.
University of Southern California Center for Systems and Software Engineering Metrics Organizational Guidelines [1] ©USC-CSSE1 [1] Robert Grady, Practical.
CSE4002CMMI Capability Maturity Model Integration (CMMI) CMMI is replacing the well established CMM rating for software developers and systems engineers.
SEMINAR WEI GUO. Software Visualization in the Large.
EXAM REVIEW MIS2502 Data Analytics. Exam What Tool to Use? Evaluating Decision Trees Association Rules Clustering.
CS 3300 FALL 2015 Software Metrics. Some Quotes When you can measure what you are speaking about and express it in numbers, you know something about it;
SOFTWARE ENGINEERING1 Introduction. SOFTWARE ENGINEERING2 Software Q : If you have to write a 10,000 line program in C to solve a problem, how long will.
CS532 TERM PAPER MEASUREMENT IN SOFTWARE ENGINEERING NAVEEN KUMAR SOMA.
Bug Localization with Association Rule Mining Wujie Zheng
1 Software Engineering: A Practitioner’s Approach, 6/e Chapter 15a: Product Metrics for Software Software Engineering: A Practitioner’s Approach, 6/e Chapter.
Chapter 10 Database Management. Data and Information How are data and information related? p Fig Next processing data stored on disk Step.
Software Engineering Saeed Akhtar The University of Lahore.
Introduction The design, development and maintenance of concurrent software are difficult tasks. Truly effective support methodologies have yet to be developed.
Software Measurement: A Necessary Scientific Basis By Norman Fenton Presented by Siv Hilde Houmb Friday 1 November.
An Approach to Measure Java Code Quality in Reuse Environment Author: Aline Timóteo Professor: Silvio Meira UFPE – Federal University.
November 8-10, 2005 International Workshop on Future Software Technology (WFST2005) Introducing Empirical Software Engineering into Japanese Industry Naoki.
Graduate School of Information Science, Nara Institute of Science and Technology - Wed. 7 April 2004Profes 2004 Effort Estimation Based on Collaborative.
Department of Computer Science, Graduate School of Information Science & Technology, Osaka University Detection of License Inconsistencies in Free and.
Strategy for EASE Project Kenichi Matsumoto Nara Institute of Science and Technology (NAIST) EASE Project, Ministry of Education, Culture, Sports, Science.
A PRELIMINARY EMPIRICAL ASSESSMENT OF SIMILARITY FOR COMBINATORIAL INTERACTION TESTING OF SOFTWARE PRODUCT LINES Stefan Fischer Roberto E. Lopez-Herrejon.
1 Visual Computing Institute | Prof. Dr. Torsten W. Kuhlen Virtual Reality & Immersive Visualization Till Petersen-Krauß | GUI Testing | GUI.
Rick Selby Software Products, Northrop Grumman & Adjunct Faculty, University of Southern California Los Angeles, CA Candidate member Main empirical research.
PREPARED BY G.VIJAYA KUMAR ASST.PROFESSOR
Introduction Edited by Enas Naffar using the following textbooks: - A concise introduction to Software Engineering - Software Engineering for students-
Software Quality Assurance (SQA)
Introduction SOFTWARE ENGINEERING.
Datamining : Refers to extracting or mining knowledge from large amounts of data Applications : Market Analysis Fraud Detection Customer Retention Production.
Empirical Project Monitor and Results from 100 OSS Development Projects Masao Ohira Empirical Software Engineering Research Laboratory, Nara Institute.
Introduction Edited by Enas Naffar using the following textbooks: - A concise introduction to Software Engineering - Software Engineering for students-
Goal, Question, and Metrics
Data Analysis Empirical Distributions Industrial Engineering
The Software Aging and Rejuvenation Repository
Nature of Science Understandings for HS
Business Intelligence
Software Requirement and Specification
Metrics Organizational Guidelines [1]
Software Verification and Validation
Presentation transcript:

International Workshop on Future Software Technology 2005/11/ Two approaches in Empirical Software Engineering Kenichi Matsumoto Nara Institute of Science and Technology

2 International Workshop on Future Software Technology 2005/11/ Two approaches Goal-driven Approach (GDA) Goal is prescribed and empirical data is collected to achieve such specific goal. Model to clarify relationship between the goal and data is needed. GQM Model, ISO Measurement Information Model Data-driven Approach (DDA) By using large amount of stored data, the relationship among software product, process, and resource is revealed. Visualization and data mining techniques are needed. Project Visualization, Association Analysis

3 International Workshop on Future Software Technology 2005/11/ Goal/Question/Metric (GQM) Model V. R. Basili and D. M. Weiss: A methodology for collecting valid software engineering data, IEEE Transactions on Software Engineering, Vol.SE-10, No.6, pp , Question to evaluate Goal Data set to answer Question Measurement Goal

4 International Workshop on Future Software Technology 2005/11/ Association Analysis Useful method for discovering interesting relationships hidden in large data sets. The uncovered relationships can be represented in the form of association rules; X -> Y: “60% of bug reports have “Change Request” class” -> “the requirements are unstable” The strength of an association rule can be measured in terms of its support and confidence. Support: how often a rule is applicable to a given data set. Confidence: Conditional probability P(Y|X).

5 International Workshop on Future Software Technology 2005/11/ Integration of Two Approaches Data-driven Goal-driven ISO MI Model GQM Model Association Analysis Visualization Case-Based Reasoning Conventional metrics Multi-Dimensional Scaling Integrated Empirical Approach in SE Threshold, Rule, Scale, … Analysis Model Values New metrics

6 International Workshop on Future Software Technology 2005/11/ GQM with Association Rules Model (Question) if ( FCM > 1.0 and (LCC/LOC > 5%) and (60% of bug reports have “Change Request” class ) then the requirements are unstable Metric FCM: Cumulative number of changed files / total number of files currently in the system. LCC: the number of lines of code changed. LOC: the number of lines of code. Replace them with "Association Rules” discovered in data sets collected in your project or organization