Completing the Loop: Linking Software Features to Failures 20 July 2004 Copyright © 2004, Mountain State Information Systems, Inc. All rights reserved.

Slides:



Advertisements
Similar presentations
PRINCIPLES OF A CALIBRATION MANAGEMENT SYSTEM
Advertisements

Radiopharmaceutical Production
Chapter 4 Quality Assurance in Context
Copyright  2002, Medical Present Value, Inc. All rights reserved. Copyright © 2010 Texas Education Agency. All rights reserved. TEA confidential and proprietary.
© 2005 by Prentice Hall Appendix 2 Automated Tools for Systems Development Modern Systems Analysis and Design Fourth Edition Jeffrey A. Hoffer Joey F.
Introduction Wilson Rosa, AFCAA CSSE Annual Research Review March 8, 2010.
University of Southern California Center for Software Engineering CSE USC USC-CSE Annual Research Review COQUALMO Update John D. Powell March 11, 2002.
200209–CSSA0001 – 16/27/ :25 PM CSSA Cepeda Systems & Software Analysis, Inc. GENERIC.
1 Software Testing and Quality Assurance Lecture 30 – Testing Systems.
I n t e g r i t y - S e r v i c e - E x c e l l e n c e Business & Enterprise Systems Introduction to Hewlett Packard (HP) Application Lifecycle Management.
© 2013 IBM Corporation Information Management Discovering the Value of IBM InfoSphere Information Analyzer IBM Software Group 1Discovering the Value of.
Copyright © 2006 by The McGraw-Hill Companies, Inc. All rights reserved. McGraw-Hill Technology Education Copyright © 2006 by The McGraw-Hill Companies,
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 8 Slide 1 Tools of Software Development l 2 types of tools used by software engineers:
Copyright 2002 Prentice-Hall, Inc. Modern Systems Analysis and Design Third Edition Jeffrey A. Hoffer Joey F. George Joseph S. Valacich Chapter 18 Maintaining.
Copyright © 2013 by The McGraw-Hill Companies, Inc. All rights reserved.McGraw-Hill/Irwin.
CSCI ClearQuest 1 Rational ClearQuest Michel Izygon - Jim Helm.
Data Integration Project. MoSTEMWINS Data Projects Strategy 1 -- Develop and Implement a statewide data system in support of tracking student performance.
Complete and Integrated Lifecycle Management. Challenges 1.
S T A M © 2000, KPA Ltd. Software Trouble Assessment Matrix Software Trouble Assessment Matrix *This presentation is extracted from SOFTWARE PROCESS QUALITY:
Appendix 2 Automated Tools for Systems Development © 2006 ITT Educational Services Inc. SE350 System Analysis for Software Engineers: Unit 2 Slide 1.
The Data Attribution Abdul Saboor PhD Research Student Model Base Development and Software Quality Assurance Research Group Freie.
CEDS Standard Update.
Copyright © IBM Corp., All rights reserved; made available under the EPL v1.0 | March 20, 2008 | Short Talk Standards based systems management: An.
- 1 - Roadmap to Re-aligning the Customer Master with Oracle's TCA Northern California OAUG March 7, 2005.
Standardization of the Continental Divide National Scenic Trail (CDNST) Data Management Kerry Shakarjian University of Denver Department of Geography Masters.
T. Dawson, TASC 9/11/13 Use of a Technical Reference in NASA IV&V.
1 Copyright ©2004 TAC. 2 T-WorMS Adding Sanity to Your Process Jamie L. Mitchell CTO TAC.
Quality Assurance Program Presenter: Erin Mustain 1.
SAS_08_Preventing_Eliminating_SWfaults_Goseva-Popstojanova Preventing and Eliminating Software Faults through the Life Cycle PI: Katerina Goseva-Popstojanova.
Certification and Accreditation CS Phase-1: Definition Atif Sultanuddin Raja Chawat Raja Chawat.
NASA Software Productivity Consortium Affiliation NASA Office of Safety and Mission Assurance Software Assurance Symposium September 5, 2001 Cynthia Calhoun.
Johnson Space Center SAS05_CodeSurfer_Infusion_JSC_Markovich S&MA Directorate Can CodeSurfer Increase Code Inspection Efficiency? A Research Infusion Project.
Georgia Institute of Technology CS 4320 Fall 2003.
JLab Software Assurance Program A Risk Based Approach to Software Management.
“Guidance on the Selection and Appraisal of Geospatial Content of Enduring Value, April 2014 Draft” groups-subcommittees/hdwg/index_html.
SAS ‘05 Reducing Software Security Risk through an Integrated Approach David P. Gilliam, John D. Powell Jet Propulsion Laboratory, California Institute.
Development of Methodologies for Independent Verification and Validation of Neural Networks NAG OSMA-F001-UNCLASS Methods and Procedures.
Slide 1 Product Line Studio TM Features used for “Customization of Documents”
ANKITHA CHOWDARY GARAPATI
Cmpe 589 Spring 2006 Lecture 2. Software Engineering Definition –A strategy for producing high quality software.
CASE (Computer-Aided Software Engineering) Tools Software that is used to support software process activities. Provides software process support by:- –
– 1Texas Nodal Texas Nodal ICCP Business Case By Jeyant Tamby, ERCOT.
第 11 組 MIS 報告. Phases of any information system ~ recognition of a business problem or opportunity ~ recognition of a business problem or opportunity.
Copyright 2010, The World Bank Group. All Rights Reserved. Recommended Tabulations and Dissemination Section B.
SAS_08_Full Life-cycle Defect Management_inspections & tests_Shull 09/2008 Executive Briefing 1© 2008 Fraunhofer USA Inc. Dr. Forrest Shull (PI) Ms. Sally.
TRAC Software for creation of supplier contract risk profile
Completing the Loop: Linking Software Features to Failures 31 July 2003 Copyright © 2003, Mountain State Information Systems, Inc. All rights reserved.
Contents 1 Description of 1 Description of Initiative Initiative 3 Defining Inspection 3 Defining Inspection Perspectives Perspectives 2 Overview of 2.
IV&V Facility Research and Development of Deployable IV&V Methods for FPGA Applications Northrop Grumman, KeyLogic Systems, Mountain State Information.
Glenn Research Center at Lewis Field Software Assurance of Web-based Applications SAWbA Tim Kurtz SAIC/GRC Software Assurance Symposium 2004.
CI R1 LCO Review Panel Preliminary Report. General Comments –Provide clear definition of the goals of the phase (e.g. inception), the scope, etc. in order.
Location Guide & Text Me a Call Number integration to Primo Presented By Dhanushka Samarakoon Marjorie Devlin.
CEDS: Why? What is CEDS? voluntarycommon A national collaborative effort to develop voluntary, common data standards for a key set of education data.
Configuration Control (Aliases: change control, change management )
CASE Tools and their Effect on Software Quality
CASE (Computer-Aided Software Engineering) Tools
Common Education Data Standards 1 Improving Programs through Data-Driven Decisions: The Journey From Critical Questions to Data Visualization.
1 CASE Computer Aided Software Engineering. 2 What is CASE ? A good workshop for any craftsperson has three primary characteristics 1.A collection of.
Software Project Configuration Management
Definition CASE tools are software systems that are intended to provide automated support for routine activities in the software process such as editing.
Chapter 18 Maintaining Information Systems
Operations Event Report Enhancement
IEEE Std 1074: Standard for Software Lifecycle
EIN 6133 Enterprise Engineering
Tools of Software Development
Michael Morris Syzygy Technologies, Inc.
CVE.
Overview Activities from additional UP disciplines are needed to bring a system into being Implementation Testing Deployment Configuration and change management.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 8 Slide 1 Tools of Software Development l 2 types of tools used by software engineers:
Radiopharmaceutical Production
Presentation transcript:

Completing the Loop: Linking Software Features to Failures 20 July 2004 Copyright © 2004, Mountain State Information Systems, Inc. All rights reserved. MOUNTAIN STATE INFORMATION SYSTEMS, INC. Paul Garnett Keith Lesch Chad Freeman

Copyright © 2004, Mountain State Information Systems, Inc. All rights reserved. MOUNTAIN STATE INFORMATION SYSTEMS, INC. Initial Problem Little consistency among IV&V Facility issue repository data Do software features predict software failures and defects?

Copyright © 2004, Mountain State Information Systems, Inc. All rights reserved. MOUNTAIN STATE INFORMATION SYSTEMS, INC. Evolution of Problem Statement Linker Project Successfully Set the Stage for Addressing the Problem of Little Consistency Among IV&V Facility Issue Repository Data (Linker is a computer program developed by MSIS that allows users to generate reports of PITS issue data across multiple projects) Other Work has Addressed Linking Features to Failures in Code

Copyright © 2004, Mountain State Information Systems, Inc. All rights reserved. MOUNTAIN STATE INFORMATION SYSTEMS, INC. Current Problem Little consistency among IV&V Facility issue repository data PITS data fields inconsistent across projects Reporting and analysis differ across multiple projects Are there consistent measures that can be applied across NASA centers and projects to determine when NASA software assurance efforts on a project have been effective?

Copyright © 2004, Mountain State Information Systems, Inc. All rights reserved. MOUNTAIN STATE INFORMATION SYSTEMS, INC. New Approach Use IV&V Facility as Pilot Project to Define Software Assurance Effectiveness Metrics Standardize defect reporting across IV&V Facility Refine PITS training Define and pilot software assurance effectiveness metrics at IV&V Facility Collaborate with Other Federal Agencies Record Results and Recommend Changes to NASA Software-Related Policies

Copyright © 2004, Mountain State Information Systems, Inc. All rights reserved. MOUNTAIN STATE INFORMATION SYSTEMS, INC. Importance/Benefits Positive NASA Project Impact Reports more meaningful Similar software assurance data collected across multiple projects More complete IV&V data per issue analyzable using ODC vs. “Everything is in the description field” More consistent use of PITS Positive NASA Software Assurance Impact Updated policies More accurate measurement of software assurance efforts

Copyright © 2004, Mountain State Information Systems, Inc. All rights reserved. MOUNTAIN STATE INFORMATION SYSTEMS, INC. Relevance to NASA Consistent Use of Software Assurance Metrics Across NASA Projects Linker Can Be Used to Support the Software Assurance Metrics Effectiveness Program ODC Can Be Used to Track Issues Across the Full Life-Cycle of NASA Projects PITS Standard Practices with Appropriate PITS Training IV&V Facility To Implement a Master Field Set for Issues Development of Linker translation layer Historical data to be mapped to master field set

Copyright © 2004, Mountain State Information Systems, Inc. All rights reserved. MOUNTAIN STATE INFORMATION SYSTEMS, INC. Accomplishments Completed Version 1 of the Linker Tool Imports PITS data across multiple projects ODC data Other data Creates intermediate data repository Reports PITS data across multiple projects Currently installed in the IV&V tools lab for use by NASA personnel Orthogonal Defect Classification Created master field set applying ODC to IV&V Implemented this field set on an IV&V pilot project Modified PITS for Automated Import of Field Set Started ODC Data Collection on Pilot Project

Copyright © 2004, Mountain State Information Systems, Inc. All rights reserved. MOUNTAIN STATE INFORMATION SYSTEMS, INC. Next Steps Contact Other Federal Agencies on Use and Definition of Software Assurance Metrics Establish IV&V Facility Metrics Effectiveness Program as a NASA Software Assurance Pilot Project Implement ODC Field Set on Additional IV&V Pilot Projects Modify Linker to Support the IV&V Facility Metrics Effectiveness Pilot Program