Continuous Productivity Assessment and Effort Prediction Based on Bayesian Analysis Seok Jun Yun and Dick B. Simmons Texas A&M University College Station,

Slides:



Advertisements
Similar presentations
Rating IT Quality : Software Project Management and Business Risk.
Advertisements

IBM Software Group ® Traceability From Need To Solution What, Why and How Tammy Lavi Alon Bar-Ner.
Web Development Engineering Processes Introduction to Web Development Outsourcing Processes.
Metrics for Process and Projects
Metrics for Process and Projects
Project Closure Report Basker George. Project Closure When does a project end? Does it end when the software has been delivered to customer & acceptance-tested?
Sixth Hour Lecture 10:30 – 11:20 am, September 9 Framework for a Software Management Process – Artifacts of the Process (Part II, Chapter 6 of Royce’ book)
Static Structure: Process Description
Rational Unified Process Software Engineering Lab. Summer 2006.
Ask Pete Acquired Software Knowledge Project - Estimation- Tool - Effort Presented to the NASA OSMA SAS ‘01 NASA IV&V Facility September 5-7, 2001 Tim.
Rational Tool Overview. Introduction Requirements-Driven Software Development with Rational Analyst Studio. Tafadzwa Nzara Analysis & Design Consultant.
RequisitePro (1) Copyright, 2001 © Jerzy R. Nawrocki Quality Management Lecture.
Rational Requisite Pro Usage at NYSDOT BA CoP
ICS Management Poor management is the downfall of many software projects Software project management is different from other engineering management.
Building Enterprise Applications Using Visual Studio ®.NET Enterprise Architect.
Metrics Project and Process Metrics. Why do we measure? Assessing project status Allows us to track risks Before they go critical Adjust workflow See.
Requirements Specification
Software Engineering II - Topic: Software Process Metrics and Project Metrics Instructor: Dr. Jerry Gao San Jose State University
A GOAL-BASED FRAMEWORK FOR SOFTWARE MEASUREMENT
University of Southern California Center for Systems and Software Engineering Assessing the IDPD Factor: Quality Management Platform Project Thomas Tan.
Effort in hours Duration Over Weeks Or Months Inception Launch Web Lifecycle Methodology Maintenance Phases Copyright Wonderlane Studios.
Software Engineering Institute Capability Maturity Model (CMM)
CSCI ClearQuest 1 Rational ClearQuest Michel Izygon - Jim Helm.
Overview of Change Management ClearQuest Overview for CORUG January, 2008.
What is Business Analysis Planning & Monitoring?
Module 3: Business Information Systems Chapter 11: Knowledge Management.
S/W Project Management
RUP Requirements RUP Artifacts and Deliverables
Selected Topics in Software Computing Distributed Software Development CVSQL Final Project Presentation.
Rational Unified Process
© VESP International Pty Limited To Contents Slide CLICK to advance slides/ bullet points within slides Integrated Master Planner An Overview.
Software Testing and Reliability Software Test Process
Rational Suite and CMM Level 2 Copyright, 2000 © Jerzy R. Nawrocki Requirements.
Test Organization and Management
Applications of OO System Engineering Methodology and Tools for Complex Systems9/11/2015 Application of Object Oriented Systems Engineering Methodology.
Testing – A Methodology of Science and Art. Agenda To show, A global Test Process which work Like a solution Black Box for an Software Implementation.
MEASUREMENT PLAN SOFTWARE MEASUREMENT & ANALYSIS Team Assignment 15
Chapter 3: Software Maintenance Process Omar Meqdadi SE 3860 Lecture 3 Department of Computer Science and Software Engineering University of Wisconsin-Platteville.
DBSQL 14-1 Copyright © Genetic Computer School 2009 Chapter 14 Microsoft SQL Server.
Software Measurement & Metrics
Software Project Management With Usage of Metrics Candaş BOZKURT - Tekin MENTEŞ Delta Aerospace May 21, 2004.
Software Metrics – part 2 Mehran Rezaei. Software Metrics Objectives – Provide State-of-art measurement of software products, processes and projects Why.
C6 Databases. 2 Traditional file environment Data Redundancy and Inconsistency: –Data redundancy: The presence of duplicate data in multiple data files.
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.
SWEN 5130 Requirements Engineering 1 Dr Jim Helm SWEN 5130 Requirements Engineering Requirements Management Under the CMM.
Introduction to SoDA Copyright, 2001 © Jerzy R. Nawrocki Requirements Engineering.
University of Southern California Center for Systems and Software Engineering Metrics Organizational Guidelines [1] ©USC-CSSE1 [1] Robert Grady, Practical.
CSCI 521 Final Exam Review. Why Establish a Standard Process? It is nearly impossible to have a high quality product without a high quality process. Standard.
RequisitePro (1) Copyright, 2001 © Jerzy R. Nawrocki Requirements Engineering.
Iterative Development Royce, “Successful Software Management Style: Steering and Balance”, IEEE Software sep/oct Sp8Jan22iterdev2.
Introduction to Requirements Eng. Copyright, 2001 © Jerzy R. Nawrocki Requirements.
Software Project Management (SEWPZG622) BITS-WIPRO Collaborative Programme: MS in Software Engineering SECOND SEMESTER /1/ "The content of this.
Yazd University, Electrical and Computer Engineering Department Course Title: Advanced Software Engineering By: Mohammad Ali Zare Chahooki The Rational.
Hussein Alhashimi. “If you can’t measure it, you can’t manage it” Tom DeMarco,
RIA to visualize the health of a project Team #4 Midterm presentation February 28,2008.
Ahmed Hassan Ghulam Murtaza Umar Farooq M Mannan Razzaq BSEF08A011 BSEF08A031 BSEF08A034 BSEF08A050.
Chapter 22 Metrics for Process and Projects Software Engineering: A Practitioner’s Approach 6 th Edition Roger S. Pressman.
Software Testing Process
Project Management Planning Nikolai Dushkov Sirma AI Ltd.
Project Planning Goal 1 - Estimates are documented for use in tracking and planning project. Goal 2 - Project Activities and commitments planned and documented.
Introduction to SoDA Copyright, 2001 © Jerzy R. Nawrocki Quality Management Lecture.
6/6/ SOFTWARE LIFE CYCLE OVERVIEW Professor Ron Kenett Tel Aviv University School of Engineering.
Managing Data Resources File Organization and databases for business information systems.
Building Enterprise Applications Using Visual Studio®
Chapter 33 Estimation for Software Projects
Identify the Risk of Not Doing BA
Why Do We Measure? assess the status of an ongoing project
Chapter 33 Estimation for Software Projects
Why Do We Measure? assess the status of an ongoing project
Presentation transcript:

Continuous Productivity Assessment and Effort Prediction Based on Bayesian Analysis Seok Jun Yun and Dick B. Simmons Texas A&M University College Station, TX {sjy3806,

Overview PAMPA 2 Knowledge Base (KB) Productivity Productivity Attributes Gather Attributes from CASE Tools Compute Productivity Use Bayesian approach to adjust Productivity Prediction Use Expert System to advise Manager

Pampa II Knowledge Base Dick B. Simmons Texas A&M University College Station, TX

Organization Project ProjectList Supplier SoftwareProduct * 1 ProjectVersion * * * * Plan Customer * SLCModelList SLCModel * 1 View [Productivity, Organization, Process, Project Dominator, Plan and WBS Gannt, Plann and WBS Activity Network,Feature Status, Project Design, Testing, Documentation]

Plan Process Activity * * * InitialMilestone FinalMilestone Criteria * * * * Risk

Supplier COTSRunFile ReusableSourceFile * *

Organization Salary Individual * * * 1.. * member {subset} 1.. * Process Activity * * InitialMilestone FinalMilestone * WorkBreakdownStructure Criteria * * * * Risk 1 manager

Feature SoftwareProduct Version VAndVTestUsabilityTestSubsystem Artifact Usability Chunk Volume Defect * * * * * * * * * * * * Structure Rework Problem Change * *

Customer

Organization Project ProjectList Salary Supplier Feature SoftwareProduct COTSRunFile ReusableSourceFile Version VAndVTestUsabilityTestSubsystem Artifact Usability authors runs Chunk Individual Volume is located in Defect is related to * 1 ProjectVersion * 1 owns * * * * * * 1.. * * 1.. * member1 manager {subset} * * * * * * * * * * * * ** * ** * * 1.. * Plan Customer * Structure Process Activity * * * InitialMilestone FinalMilestone * WorkBreakdownStructure Rework Criteria * * * * * authors * ** * * * SLCModelList SLCModel * Risk 1 Problem Change * * View [Productivity, Organization, Process, Project Dominator, Plan and WBS Gannt, Plann and WBS Activity Network,Feature Status, Project Design, Testing, Documentation]

Productivity

Software Productivity Model Before 2000 Customer and Corporate Needs Complexity of Problem Constraints of Environment VALUE QualityQuantityReusability Defects Size Lines of Source FunctionsObject Points Difficulty COST PeopleCalendar Time (Opportunity) Capital Engineering Months

Software Productivity Model After 2000 Customer and Corporate Needs Complexity of Problem Constraints of Environment VALUE QualityQuantityReusability Defects Size Lines of Source Functions Difficulty COST PeopleCalendar Time (Opportunity) Capital $’s HLCs (High Level Chunks) Object Points

Estimate uncertainty

Object Points Function Points Source lines of Code HLCs

Productivity Attributes

Productivity Prediction where a is the units of Volume, m is the number of the Volume estimating model, and n is the number of the effort estimating model. Productivity m,n is expression in a per person month. For example if a = KNCSS, then the units of productivity would be KNCSS per person month. Productivity m,n = Volume a,m Effort n

Productivity Prediction where a is the units of Volume, m is the number of the Volume estimating model, and n is the number of the effort estimating model. Salary is expressed $’s per month $Productivity m,n is expression in a per $. For example if a = KNCSS, then the units of productivity would be KNCSS per person month. $Productivity m,n = Volume a,m Effort n x Salary

Gather Attributes from CASE Tools

Organization Project ProjectList Salary Supplier Feature SoftwareProduct COTSRunFile ReusableSourceFile Version VAndVTestUsabilityTestSubsystem Artifact Usability authors runs Chunk Individual Volume is located in Defect is related to * 1 ProjectVersion * 1 owns * * * * * * 1.. * * 1.. * member1 manager {subset} * * * * * * * * * * * * ** * ** * * 1.. * Plan Customer * Structure Process Activity * * * InitialMilestone FinalMilestone * WorkBreakdownStructure Rework Criteria * * * * * authors * ** * * * SLCModelList SLCModel * Risk 1 Problem Change * * CASE TOOLS JESS Metric Center Rational ClearCase Rational ClearQuest Rational Test Studio CostXpert Crystal Report Writer MS SQL Server Rational RequisitePro SLIM SoDA MS Project Rational Rose DBMS Attribute Gatherer Design Tool View [Productivity, Organization, Process, Project Dominator, Plan and WBS Gannt, Plann and WBS Activity Network,Feature Status, Project Design, Testing, Documentation]

Compute Productivity

Organization Project ProjectList Salary Supplier Feature SoftwareProduct COTSRunFile ReusableSourceFile Version VAndVTestUsabilityTestSubsystem Artifact Usability authors runs Chunk Individual Volume is located in Defect is related to * 1 ProjectVersion * 1 owns * * * * * * 1.. * * 1.. * member1 manager {subset} * * * * * * * * * * * * ** * ** * * 1.. * Plan Customer * Structure Process Activity * * * InitialMilestone FinalMilestone * WorkBreakdownStructure Rework Criteria * * * * * authors * ** * * * SLCModelList SLCModel * Risk 1 Problem Change * * View [Productivity, Organization, Process, Project Dominator, Plan and WBS Gannt, Plann and WBS Activity Network,Feature Status, Project Design, Testing, Documentation] Effort Salary Volume

Use Bayesian approach to adjust Productivity Prediction Equation

Use Expert System to Advise Manager

Organization Project ProjectList Salary Supplier Feature SoftwareProduct COTSRunFile ReusableSourceFile Version VAndVTestUsabilityTestSubsystem Artifact Usability authors runs Chunk Individual Volume is located in Defect is related to * 1 ProjectVersion * 1 owns * * * * * * 1.. * * 1.. * member1 manager {subset} * * * * * * * * * * * * ** * ** * * 1.. * Plan Customer * Structure Process Activity * * * InitialMilestone FinalMilestone * WorkBreakdownStructure Rework Criteria * * * * * authors * ** * * * SLCModelList SLCModel * Risk 1 Problem Change * * View [Productivity, Organization, Process, Project Dominator, Plan and WBS Gannt, Plann and WBS Activity Network,Feature Status, Project Design, Testing, Documentation] Facts

Inference Engine Knowledge Elicitation from Manager Rules and Facts Generator Milestone & Risk Criteria (Rules and Initial Facts) Facts Action Response Data Collection Subsystem Plan Tracking Intelligent Agent

Summary Continuous productivity measurement Continuous productivity model calibration Expert Advisor Optimize cost across a geographically distributed labor force