Forrest Shull, Fraunhofer Center for Experimental Software
Patricia Larsen, Engineering -Maryland
Rose Pajerski,
Ioana Rus,

Mike Stark, GSFC

Allen Nikora, JPL
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
Currently in the third of three years

Major objectives:
Improve software inspection practice and support projects in their use
To reduce cost of achieving high-quality software.
Project Plan
Project Reality
Inspection process overview

Project Reality
Project Reality
Example of project perspective definition
Keck Interferometer (JPL) goals:
Inspect a reusable class library to make sure that existing and future stakeholders will be satisfied with the code and documentation
Get inspections reintroduced on the project
Get individuals to take ownership of different parts of the process
Achieving these through use of perspective-based reviews:
Provides a framework for identifying stakeholders and their quality interests
Tie inspection activities to project activities
Example of project perspective definition
Stakeholder analysis identifies perspectives:

Example of guidance (Dev/Author):
From your point of view as author, consider which classes/methods were most complex or contained the most functionality Use these questions to check whether the documentation matches the functionality implemented
We are measuring # of defects, amount of effort, etc., to show that efficient perspectives and roles can be constructed
Example of project defect definition
Swift BAT (GSFC FSB) in late-lifecycle code inspections and testing.
Goals: Examine discrepancy report database to:
Find out what defects took the longest to close so that we can add these ‘high priority’ items to the inspection checklists.
Analyze which defects were caused by problems in the requirements and understand how long they stayed in the system, so that we can feed requirements recommendations forward.

Expected result:
Improved defect taxonomy used to focus inspections within FSB
Improved requirements inspection process in FSB

Example of using model for decision support
Inspections Process Model and Simulator goal:
To estimate the effect of adding inspections in some/all early lifecycle phases on test effort and total rework.
To help project managers understand the cost/benefits of different ways of planning inspections.
Example of using model for decision support
Examine effects of possible V&V activity effort as you move through the development phases:
Example of using model for decision support
Production Activity Data

V&V Activity Data

Rework Data

Test Data

Work Product (Type, Size)
EffortPerItem
StaffAvailable
Duration
DefectsInjected (Type, Severity, Number)
Work Product (Type, Size)
EffortPerItem
StaffAvailable
Duration
Effectiveness (Type, Severity)
DefectsDetected (Type, Severity, Number)
Work Product (Type, Size)
EffortPerDefect (Type, Severity)
StaffAvailable
Duration
TestCases (Number)
EffortPerTestCase
Duration
Effectiveness (Type, Severity)
DefectsRemaining (Type, Severity, Number)
StaffAvailable
Conclusions
About this initiative:
We have other potential projects – all results will be included in final report.
Research direction and results have been driven by project needs
About the software development technology:
Work with projects is showing feasibility of the perspective-based approach.
Tailorability is helping to address project needs in different contexts.
Data collection (ongoing) will demonstrate whether similar levels of efficiency are being achieved compared to historical baselines.

Categories: News