Contents 1 Description of 1 Description of Initiative Initiative 3 Year 2: Updated 3 Year 2: Updated Training/Metrics Training/Metrics 2 Year 1: NASA 2.

Slides:



Advertisements
Similar presentations
Test Automation Success: Choosing the Right People & Process
Advertisements

Damian Gordon.  Static Testing is the testing of a component or system at a specification or implementation level without execution of the software.
Educational Research: Competencies for Analysis and Application, 9 th edition. Gay, Mills, & Airasian © 2009 Pearson Education, Inc. All rights reserved.
Copyright © 1994 Carnegie Mellon University Disciplined Software Engineering - Lecture 1 1 Disciplined Software Engineering Lecture #7 Software Engineering.
Static Technique. Static Technique - Review  A way of testing software work products  Program code, requirement spec., design spec.  Test plan, test.
Testing Without Executing the Code Pavlina Koleva Junior QA Engineer WinCore Telerik QA Academy Telerik QA Academy.
Requirements Engineering n Elicit requirements from customer  Information and control needs, product function and behavior, overall product performance,
Code Inspections CS 414 – Software Engineering I Donald J. Bagert Rose-Hulman Institute of Technology January 23, 2003.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 28 Slide 1 Process Improvement.
1 Info 1409 Systems Analysis & Design Module Lecture 5 - Feasibility HND Year /9 De Montfort University.
SE 450 Software Processes & Product Metrics 1 Defect Removal.
CSE USC Fraunhofer USA Center for Experimental Software Engineering, Maryland February Empiricism in Software Engineering Empiricism:
Copyright 2004 Prentice-Hall, Inc. Essentials of Systems Analysis and Design Second Edition Joseph S. Valacich Joey F. George Jeffrey A. Hoffer Chapter.
The Software Product Life Cycle. Views of the Software Product Life Cycle  Management  Software engineering  Engineering design  Architectural design.
CSE USC Fraunhofer USA Center for Experimental Software Engineering, Maryland February 6, Outline Motivation Examples of Existing.
Verification and Validation
NASA Software Productivity Consortium NASA Office of Safety and Mission Assurance Software Assurance Symposium September 5, 2002 Robert Ling Johnson Space.
1 Software Inspections and Walkthroughs Author: A. Frank Ackerman Presented by Cynthia Johnson EEL6883.
Diploma of Project Management Course Outline NSW Course Number Qualification Code BSB51407.
Copyright 2004 Prentice-Hall, Inc. Essentials of Systems Analysis and Design Second Edition Joseph S. Valacich Joey F. George Jeffrey A. Hoffer Chapter.
Copyright 2002 Prentice-Hall, Inc. Modern Systems Analysis and Design Third Edition Jeffrey A. Hoffer Joey F. George Joseph S. Valacich Chapter 6 Initiating.
Software Inspections and Walkthroughs By. Adnan khan.
Diploma of Project Management Course Outline NSW Course Number Qualification Code BSB51407.
Requirements Analysis
1 IDI, NTNU Programvarekvalitet og prosessforbedring vår 2000, Forrest Shull et al., Univ. Maryland and Reidar Conradi, NTNU (p.t. Univ.
October 21 st TMD Meeting MW-COG/Marriott Telework Update Robert Brown; Telecommuting Advantage Group.
Chapter 14: Inspection  Basic Concept and Generic Process  Fagan Inspection  Other Inspection and Related Activities.
Software Inspection A basic tool for defect removal A basic tool for defect removal Urgent need for QA and removal can be supported by inspection Urgent.
1PBI_SAS_08_Exec_ShullSeptember 2008MAC-T IVV Dr. Forrest Shull, FCMD Kurt Woodham, L-3 Communications OSMA SAS 08 Infusion of Perspective-Based.
Copyright 2002 Prentice-Hall, Inc. Modern Systems Analysis and Design Third Edition Jeffrey A. Hoffer Joey F. George Joseph S. Valacich Chapter 6 Initiating.
Software Engineering - Spring 2003 (C) Vasudeva Varma, IIITHClass of 39 CS3600: Software Engineering: Standards in Process Modeling CMM and PSP.
SAS_08_Preventing_Eliminating_SWfaults_Goseva-Popstojanova Preventing and Eliminating Software Faults through the Life Cycle PI: Katerina Goseva-Popstojanova.
Contents 1 Description of 1 Description of Initiative Initiative 3 Results: 3 Results: Characterization Characterization 2 Description of 2 Description.
1PBI_SAS_08_Tech_ShullSeptember 2008MAC-T IVV Dr. Forrest Shull, FCMD Kurt Woodham, L-3 Communications OSMA SAS 08 Infusion of Perspective-Based.
Copyright 2001 Prentice-Hall, Inc. Essentials of Systems Analysis and Design Chapter 3 Systems Planning and Selection 3.1.
NASA Software Productivity Consortium Affiliation NASA Office of Safety and Mission Assurance Software Assurance Symposium September 5, 2001 Cynthia Calhoun.
January Software Research and Technology Infusion 14 January 2008 Presented by Lisa Montgomery, NASA Pavan Rajagopal,
United States Department of Agriculture Food Safety and Inspection Service 1 National Advisory Committee on Meat and Poultry Inspection August 8-9, 2007.
2  Mission Statement.  Company’s overall purpose and direction, products, services and values.  Goals.  That accomplish the mission. E.g. 5 year plan.
BSBPMG505A Manage Project Quality Manage Project Quality Project Quality Processes Diploma of Project Management Qualification Code BSB51507 Unit.
Formal Technical Reviews Matt Graham 18 November 2004 EECS 814 University of Kansas.
Process Assessment Method
CHAPTER 9 INSPECTIONS AS AN UP-FRONT QUALITY TECHNIQUE
Systems Life Cycle A2 Module Heathcote Ch.38.
Formal Methods in Software Engineering
ISERN Survey & Benchmark 10 th anniversary meta-experiment project Session Chair, Stefan Biffl Marcus Ciolkowski, Forrest Shull, and Dieter Rombach 1.Strategy.
1 © 2009 Fraunhofer Center - Maryland Dr. Forrest Shull, FCMD Verification of Software Architectures via Reviews.
Component 8 Installation and Maintenance of Health IT Systems Unit 4 Structured Systems Analysis and Design This material was developed by Duke University,
Sept Software Research and Technology Infusion 2007 Software Assurance Symposium.
1 Technology Infusion of the Software Developer’s Assistant (SDA) into the MOD Software Development Process NASA/JSC/MOD/Brian O’Hagan 2008 Software Assurance.
Inspection and Review The main objective of an Inspection or a Review is to detect defects. This activity and procedure was first formalized by Mike Fagan.
Overview of RUP Lunch and Learn. Overview of RUP © 2008 Cardinal Solutions Group 2 Welcome  Introductions  What is your experience with RUP  What is.
Safety and Mission Assurance Directorate, Goddard Space Flight Center Supply Chain Management Panel Session: NASA Supplier Assessments: Processes, Results.
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.
© Michael Crosby and Charles Sacker, 2001 Systematic Software Reviews Software reviews are a “quality improvement process for written material”.
Contents 1 Description of 1 Description of Initiative Initiative 3 Defining Inspection 3 Defining Inspection Perspectives Perspectives 2 Overview of 2.
Advances In Software Inspection
Contents 1 Session Goals 1 Session Goals 3 Design Levels 3 Design Levels 2 Design Goals 2 Design Goals 4 Known Issues 4 Known Issues 5 Picking a Specific.
T EST T OOLS U NIT VI This unit contains the overview of the test tools. Also prerequisites for applying these tools, tools selection and implementation.
1 An Overview of Process and Procedures for Health IT Collaboration GSA Office of Citizen Services and Communications Intergovernmental Solutions Division.
Group iv MBARARA UNIVERSITY OF SCIENCE AND TECHNOLOGY INSTITUTE OF COMPUTER SCIENCE DEPARTMENT OF COMPUTER SCIENCE COURSE: BACHELOR OF COMPUTER SCIENCE.
Copyright 2002 Prentice-Hall, Inc. Modern Systems Analysis and Design Third Edition Jeffrey A. Hoffer Joey F. George Joseph S. Valacich Chapter 6 Initiating.
Standard Design Process (SDP) Interfacing Procedures Ashley Taylor TVA
Solving Problems with the BPCH
Object-Oriented Software Engineering Using UML, Patterns, and Java,
Version 0.1Assessment Method Overview - 1 Process Assessment Method An objective model-independent method to assess the capability of an organization to.
QA Reviews Lecture # 6.
Experimental Software Engineering (ESE)
WALKTHROUGH and INSPECTION
Presentation transcript:

Contents 1 Description of 1 Description of Initiative Initiative 3 Year 2: Updated 3 Year 2: Updated Training/Metrics Training/Metrics 2 Year 1: NASA 2 Year 1: NASA Lessons Learned Lessons Learned 4 Year 3: Tech 4 Year 3: Tech Transfer Transfer 5 Request for 5 Request for Participation Participation Slide 1 Forrest Shull &Fraunhofer Center for Experimental Software Patricia LarsenEngineering - Maryland Mike Stark,GSFC State-of-the-Art Software Inspections at NASA

Contents 1 Description of 1 Description of Initiative Initiative 3 Year 2: Updated 3 Year 2: Updated Training/Metrics Training/Metrics 2 Year 1: NASA 2 Year 1: NASA Lessons Learned Lessons Learned 4 Year 3: Tech 4 Year 3: Tech Transfer Transfer 5 Request for 5 Request for Participation Participation Slide 2 Outline Introduction to this Initiative Summary of year 1 work: Assessing NASA lessons learned Current (year 2) work –Updating training course –Metrics collection plan –Controlled experiment Preview of year 3 work and request for participation

Contents 1 Description of 1 Description of Initiative Initiative 3 Year 2: Updated 3 Year 2: Updated Training/Metrics Training/Metrics 2 Year 1: NASA 2 Year 1: NASA Lessons Learned Lessons Learned 4 Year 3: Tech 4 Year 3: Tech Transfer Transfer 5 Request for 5 Request for Participation Participation Slide 3 Project Information This project –a collaboration between JPL, GSFC, CSC, and FC-MD –funded by the Office of Safety and Mission Assurance (OSMA) Software Assurance Research Program Major objectives include: –A lessons learned report about current state-of-the-practice in inspections at NASA –Providing training in effective inspection techniques –Running of studies to provide support for new inspection techniques and measure their effectiveness 

Why Inspections? Long-term benefits GSFC SEL: Steady decrease in error rates. 85% improvement over 15 years. GSFC SEL: Steady decrease in error rates. 85% improvement over 15 years Development Error Rates ( ) Errors per KDLOC Project Midpoint Ada Projects FORTRAN Projects

Contents 1 Description of 1 Description of Initiative Initiative 3 Year 2: Updated 3 Year 2: Updated Training/Metrics Training/Metrics 2 Year 1: NASA 2 Year 1: NASA Lessons Learned Lessons Learned 4 Year 3: Tech 4 Year 3: Tech Transfer Transfer 5 Request for 5 Request for Participation Participation Slide 5 Quick Overview Individual Preparation Team Meeting Author Follow-up Support

Contents 1 Description of 1 Description of Initiative Initiative 3 Year 2: Updated 3 Year 2: Updated Training/Metrics Training/Metrics 2 Year 1: NASA 2 Year 1: NASA Lessons Learned Lessons Learned 4 Year 3: Tech 4 Year 3: Tech Transfer Transfer 5 Request for 5 Request for Participation Participation Slide 6 Types of Inspections Software inspections can be used to review: System Requirements System Design Subsystem Requirements Subsystem Design Software Requirements Architectural Design Detailed Design Source Code Test Plans Test Procedures & Functions Operator’s Manual, Standards, Plans, Etc. (Source: JPL Formal Inspections training)

Contents 1 Description of 1 Description of Initiative Initiative 3 Year 2: Updated 3 Year 2: Updated Training/Metrics Training/Metrics 2 Year 1: NASA 2 Year 1: NASA Lessons Learned Lessons Learned 4 Year 3: Tech 4 Year 3: Tech Transfer Transfer 5 Request for 5 Request for Participation Participation Slide 7 Year 1: Lessons Learned Report Based on interviews with a range of NASA projects from several Centers –17 participants, across 5 Centers (and 7 sites) –Generally highly experienced personnel ( >7 years at current Center, > 10 inspections) Investigated why people use (or decided not to use) inspections; what they inspect; how to introduce inspections effectively Analyzed important issues; perceived benefits; problems and difficulties

Contents 1 Description of 1 Description of Initiative Initiative 3 Year 2: Updated 3 Year 2: Updated Training/Metrics Training/Metrics 2 Year 1: NASA 2 Year 1: NASA Lessons Learned Lessons Learned 4 Year 3: Tech 4 Year 3: Tech Transfer Transfer 5 Request for 5 Request for Participation Participation Slide 8 Year 1: Lessons Learned Report Summary of results –Even informal inspection practices have benefits –More formal practices have more benefits, but require management support and resources –Developers rarely question the utility after their first successful inspection State of the practice: –Fewer groups can afford full formality –Requirements and design reviews are most important and most frequently used –Used to achieve:  Communication (team cohesion, technical understanding)  Training (team building, cross-training)  Defect reduction

Contents 1 Description of 1 Description of Initiative Initiative 3 Year 2: Updated 3 Year 2: Updated Training/Metrics Training/Metrics 2 Year 1: NASA 2 Year 1: NASA Lessons Learned Lessons Learned 4 Year 3: Tech 4 Year 3: Tech Transfer Transfer 5 Request for 5 Request for Participation Participation Slide 9 Year 2 Work Act on the lessons learned report by: –Creating updated training course to address issues –Developing a metrics collection plan to demonstrate ROI in context –Running controlled experiments to evaluate state-of-the-art practices that can be introduced at NASA

Contents 1 Description of 1 Description of Initiative Initiative 3 Year 2: Updated 3 Year 2: Updated Training/Metrics Training/Metrics 2 Year 1: NASA 2 Year 1: NASA Lessons Learned Lessons Learned 4 Year 3: Tech 4 Year 3: Tech Transfer Transfer 5 Request for 5 Request for Participation Participation Slide 10 Year 2: Updated training JPL Formal Inspection training identified as highly beneficial from LLR Working with GSFC’s FSB to adapt JPL materials to address current project constraints: –Modularization  Tailored to roles: moderators, inspectors, metrics collection –Shortened lecture, incorporating actual project work –Tailoring –Less JPL-specificity –Suggested agendas for various project constraints

Contents 1 Description of 1 Description of Initiative Initiative 3 Year 2: Updated 3 Year 2: Updated Training/Metrics Training/Metrics 2 Year 1: NASA 2 Year 1: NASA Lessons Learned Lessons Learned 4 Year 3: Tech 4 Year 3: Tech Transfer Transfer 5 Request for 5 Request for Participation Participation Slide 11 Year 2: Updated training Incorporating lessons learned from synergistic research activities –UMCP: investigating learning curve of inspection practices  Measures of effectiveness vs. time  Applying “observational” empirical methods  Changes in process conformance over time –NSF: level of detail issues related to subject experience  Measures of effectiveness for different procedures  Interaction of detailed procedures with previous expertise

Contents 1 Description of 1 Description of Initiative Initiative 3 Year 2: Updated 3 Year 2: Updated Training/Metrics Training/Metrics 2 Year 1: NASA 2 Year 1: NASA Lessons Learned Lessons Learned 4 Year 3: Tech 4 Year 3: Tech Transfer Transfer 5 Request for 5 Request for Participation Participation Slide 12 Year 2: Updated training –CeBASE/NSF: collection, abstraction, and refinement of industrial data across domains, e.g.:  “Cost savings rule”: Cost to find & fix software defects is about 100x more expensive after delivery than in early lifecycle phases, for certain types of defects.  IBM: 117:1 between code and use  Toshiba: 137:1 between pre- and post-shipment  Data Analysis Center for Software: 100:1  “Inspection effectiveness rule”: Reviews and inspections find more than 50% of the defects in an artifact, regardless of the lifecycle phase applied.  50-70% across many companies (Laitenberger)  64% on large projects at Harris GCSD (Elliott)  60% in PSP design/code reviews (Roy)  50-95%, rising with increased discipline (O’Neill)  … many others Source: F. Shull et al., “What We Have Learned about Fighting Defects,” Proceedings of 8 th International Metrics Software Metrics Symposium, Ottawa, Canada, June 2002.

Contents 1 Description of 1 Description of Initiative Initiative 3 Year 2: Updated 3 Year 2: Updated Training/Metrics Training/Metrics 2 Year 1: NASA 2 Year 1: NASA Lessons Learned Lessons Learned 4 Year 3: Tech 4 Year 3: Tech Transfer Transfer 5 Request for 5 Request for Participation Participation Slide 13 Year 2: Metrics plan Worked with ST5 project to define feasible metrics set answering relevant questions Application to FSB projects Example Goal: Analyze software inspections for the purpose of evaluation with respect to number of defects reaching test phase. –Example Questions: Does introducing inspections in early phases…  …reduce the defect density of software at testing?  …reduce the overall testing effort?  …save more effort than it requires?  …result in less time to find and fix (types of) defects than if they were found through testing?

Contents 1 Description of 1 Description of Initiative Initiative 3 Year 2: Updated 3 Year 2: Updated Training/Metrics Training/Metrics 2 Year 1: NASA 2 Year 1: NASA Lessons Learned Lessons Learned 4 Year 3: Tech 4 Year 3: Tech Transfer Transfer 5 Request for 5 Request for Participation Participation Slide 14 Year 2: Controlled experiment Running of short-term studies at JPL to evaluate candidate state-of-art practices –Controlled experiment between two teams with different approaches –As part of training class: before/after reviews –Re-inspection of artifact with defect history –Case study on live project

Contents 1 Description of 1 Description of Initiative Initiative 3 Year 2: Updated 3 Year 2: Updated Training/Metrics Training/Metrics 2 Year 1: NASA 2 Year 1: NASA Lessons Learned Lessons Learned 4 Year 3: Tech 4 Year 3: Tech Transfer Transfer 5 Request for 5 Request for Participation Participation Slide 15 Year 3: Tech transfer Next year: transfer and dissemination of results –Delivery of train-the-trainers material –Measurement and data collection –Planning to turn over materials to  Projects at GSFC FSB, JPL, IVV directly  JPL SEPG  GSFC SEPG

Contents 1 Description of 1 Description of Initiative Initiative 3 Year 2: Updated 3 Year 2: Updated Training/Metrics Training/Metrics 2 Year 1: NASA 2 Year 1: NASA Lessons Learned Lessons Learned 4 Year 3: Tech 4 Year 3: Tech Transfer Transfer 5 Request for 5 Request for Participation Participation Slide 16 Request for Participation We are looking for: –NASA projects & project leads to directly participate –Civil servants who are overseeing contracts to allow/encourage contractors to participate Controlled experiments: Participants spend 1-2 days for: –Receiving training in state-of-the-art techniques that can be taken away and used on real projects. –Receiving feedback on types of defects detected and effectiveness of the training, and some comparison to their usual approach Pilot studies: Participants work with us on actual projects and: –Receive training in state-of-the-art techniques tailored for their environment & project –Receive extended support for inspections including  data collection  consultation  analysis & feedback

Contents 1 Description of 1 Description of Initiative Initiative 3 Year 2: Updated 3 Year 2: Updated Training/Metrics Training/Metrics 2 Year 1: NASA 2 Year 1: NASA Lessons Learned Lessons Learned 4 Year 3: Tech 4 Year 3: Tech Transfer Transfer 5 Request for 5 Request for Participation Participation Slide 17 Contact Info Contact –Forrest (lead researcher)   –Mike (current government POC for contract)  