CANADIAN PATROL FRIGATE SOFTWARE MAINTENANCE TESTING BY LCDR T.L. WILLIAMS.

Slides:



Advertisements
Similar presentations
Configuration Management
Advertisements

Ninth Lecture Hour 8:30 – 9:20 pm, Thursday, September 13
Automated Software Testing: Test Execution and Review Amritha Muralidharan (axm16u)
1 SOFTWARE TESTING Przygotował: Marcin Lubawski. 2 Testing Process AnalyseDesignMaintainBuildTestInstal Software testing strategies Verification Validation.
Software Engineering CSE470: Process 15 Software Engineering Phases Definition: What? Development: How? Maintenance: Managing change Umbrella Activities:
Chapter 7: Key Process Areas for Level 2: Repeatable - Arvind Kabir Yateesh.
More CMM Part Two : Details.
1 State of Michigan Achieving Software Process Improvement with Capability Maturity Model (CMM)
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)
Stepan Potiyenko ISS Sr.SW Developer.
Documentation Testing
Chapter 15 Design, Coding, and Testing. Copyright © 2005 Pearson Addison-Wesley. All rights reserved Design Document The next step in the Software.
Project Support Function PM Planning Organizing Staffing Monitoring Controlling and Leading Project Support Functions Monitoring Controlling.
Software Project Transition Planning
Illinois Institute of Technology
Copyright  Larry Dribin, Ph.D. SE470_EngFlows_v1.ppt SE470 EngFlows - 1 Excellence in Software Engineering Repeatable Level Defined Level Manage.
Computer Security: Principles and Practice
Configuration Management
COMP8130 and 4130Adrian Marshall 8130 and 4130 Test Management Adrian Marshall.
Software Engineering Institute Capability Maturity Model (CMM)
Capability Maturity Model
Software Quality Assurance (SQA) Monitor the methods and standards used during the software development and verify their correct usage. What is Quality?
System Testing There are several steps in testing the system: –Function testing –Performance testing –Acceptance testing –Installation testing.
The Key Process Areas for Level 2: Repeatable Ralph Covington David Wang.
PMP® Exam Preparation Course
Chapter 2 The process Process, Methods, and Tools
Dillon: CSE470: SE, Process1 Software Engineering Phases l Definition: What? l Development: How? l Maintenance: Managing change l Umbrella Activities:
N By: Md Rezaul Huda Reza n
Software Configuration Management
-Nikhil Bhatia 28 th October What is RUP? Central Elements of RUP Project Lifecycle Phases Six Engineering Disciplines Three Supporting Disciplines.
Software Quality Assurance Activities
1 Chapter 2 The Process. 2 Process  What is it?  Who does it?  Why is it important?  What are the steps?  What is the work product?  How to ensure.
Understand Application Lifecycle Management
S Q A.
1.  Describe an overall framework for project integration management ◦ RelatIion to the other project management knowledge areas and the project life.
Testing Workflow In the Unified Process and Agile/Scrum processes.
By Ritesh Reddy Nagaram.  Organizations which are developing software processes are facing many problems regarding the need for change of already existing.
BSBPMG505A Manage Project Quality Manage Project Quality Project Quality Processes Diploma of Project Management Qualification Code BSB51507 Unit.
Georgia Institute of Technology CS 4320 Fall 2003.
Formal Methods in Software Engineering
CMMI. 1.Initial - The software process is characterized as ad hoc, and occasionally even chaotic. Few processes are defined, and success depends on individual.
Construction, Testing, Documentation, and Installation Chapters 15 and 16 Info 361: Systems Analysis and Design.
What is Testing? Testing is the process of exercising or evaluating a system or system component by manual or automated means to verify that it satisfies.
Configuration Management and Change Control Change is inevitable! So it has to be planned for and managed.
Level 1 Level 1 – Initial: The software process is characterized as ad hoc and occasionally even chaotic. Few processes are defined, and success depends.
“How to Measure the Impact of Specific Development Practices on Fielded Defect Density” by Ann Marie Neufelder Presented by: Feride Padgett.
Rational Unified Process Fundamentals Module 4: Core Workflows II - Concepts Rational Unified Process Fundamentals Module 4: Core Workflows II - Concepts.
Independent Expert Program Review (IEPR) February 2006.
1 Software Testing Strategies: Approaches, Issues, Testing Tools.
Process Asad Ur Rehman Chief Technology Officer Feditec Enterprise.
Configuration Management (II) Copyright, 2000 © Jerzy R. Nawrocki Requirements.
HNDIT23082 Lecture 09:Software Testing. Validations and Verification Validation and verification ( V & V ) is the name given to the checking and analysis.
What Causes Software Vulnerabilities? _____________________ ___________ ____________ _______________   flaws in developers own code   flaws resulting.
Project Planning Goal 1 - Estimates are documented for use in tracking and planning project. Goal 2 - Project Activities and commitments planned and documented.
Capability Maturity Model. CS460 - Senior Design Project I (AY2004)2 Immature Organisations Software processes are often rigorously followed. Organisation.
Cmpe 589 Spring Fundamental Process and Process Management Concepts Process –the people, methods, and tools used to produce software products. –Improving.
LECTURE 5 Nangwonvuma M/ Byansi D. Components, interfaces and integration Infrastructure, Middleware and Platforms Techniques – Data warehouses, extending.
Chapter 9 Testing the System 9.1 Principles of System Testing Focus A: The objective of unit and integration ensure the code implemented the design.
Computer Security: Principles and Practice First Edition by William Stallings and Lawrie Brown Lecture slides by Lawrie Brown Chapter 17 – IT Security.
Configuration Management
Software Project Configuration Management
State of Michigan Achieving Software Process Improvement with
CS4311 Spring 2011 Process Improvement Dr
Testing Process Roman Yagodka ISS Test Leader.
Configuration Management
Level 1 Level 1 – Initial: The software process is characterized as ad hoc and occasionally even chaotic. Few processes are defined, and success depends.
Software Engineering Lecture 16.
Software Engineering I
Capability Maturity Model
Capability Maturity Model
Presentation transcript:

CANADIAN PATROL FRIGATE SOFTWARE MAINTENANCE TESTING BY LCDR T.L. WILLIAMS

CPF SOFTWARE 1,100,000 SLOC 223 MODULES 10 YEAR DEVELOPMENT TESTED AS PART OF SIX YEAR AT SEA TRIALS PROGRAM BUILD 36 FINAL CPF CONTRACT BUILD

CPF MAINTENANCE CONTRACT ISSUES GOVERNMENT OWNED CONTRACTOR OPERATED (GOCO) MOVE PGC TO HALIFAX CM REMAINED IN MONTREAL NAVY VERSION 1.0 PROMISE DND REORGANIZATION/STAFFING TRANSITION OF CPF SOFTWARE TO IN-SERVICE AUTHORITY

COMMS TECHNICAL AUTHORITY SOFTWARE MANAGER SENSORS PROGRAM GENERATION CENTER CMSUPPORTTEWA ASW COMMAND SUPPORT TRACK MANAGEMENT QA ADMIN ASSISTANT SMaRT NAVAL COMMUNITY HSSF ORGANIZATION

TESTING “TESTING SHALL BE AT THE SAME LEVEL AS THE CPF PRIME CONTRACT” CPF MAINTENANCE CONTRACT STATED:

NAVY VERSION 1.0 PROBLEMS REQUIREMENTS WORK SPLIT BETWEEN SITES POOR PLANNING FACILITY SCHEDULING VERSION RELEASE DOCUMENT

NAVY VERSION 1.0 PROBLEMS (CONT) RELEASING AUTHORITY CONTRACTOR TESTING AT SEA TESTING NUMEROUS DEFECTS STAFFING/EXPERIENCE LEVELS NO MEANINGFUL METRICS COLLECTED

SUCCESS OR FAILURE? POLITICALLY FACILITY WAS JUDGED TO BE A SUCCESS STANDING UP THE FACILITY –SUCCESS PRODUCING THE FIRST IN- SERVICE BUILD –FAILURE

CHANGES TO FACILITY REQUIREMENTS GROUP STOOD-UP CONTINUOUS IMPROVEMENT GROUP ESTABLISH INDEPENDENT TESTING GROUP ESTABLISHED INCREASED STAFFING FOR SMaRT

CHANGES TO FALICITY (CONTINUED) MINI-SYSTEM INSTALLED AUTOMATED CONFIGURATION MANAGEMENT CLOSER TIES TO REQUIREMENTS GROUP DEVELOPED TRANSITION OF SOFTWARE TO IN- SERVICE AUTHORITY FACILITY REORGANIZED

TECHNICAL AUTHORITY CSST(H) SOFTWARE MANAGER ADMIN ASSISTANT SOFTWARE SYSTEM ENGINEER SOFTWARE DEVELOPMENT MANAGER SPECIAL PROJECTS MANAGER INTEGRATED SUPPORT MANAGER ASW/COMM/TM TEWA/SENSOR LINK SUPPORT COMMAND SUPPORT QUALITY ASSURANCE CONFIGURATION MANAGEMENT INFORMATION TECHNOLOGY TESTING NAVAL COMMUNITY HSSF(H) REORGANIZATION

SOFTWARE SYSTEMS ENGINEER RESPONSIBILITIES ASSESS IMPACT OF SOFTWARE AND SYSTEM CHANGES COORDINATE SYSTEM STUDIES AND INVESTIGATIONS REVIEW TEST PLANS AND TEST PROCEDURES OBSERVE ALL FORMAL TESTS

QUALITY ASSURANCE QUALITY MANAGEMENT –DOCUMENT, V & V SOFTWARE PROCESS –INCREASE PROCESS CAPABILITY AND MATURITY –RAISE QUALITY AWARENESS AND PROVIDE TRAINING –CONTINUOUS IMPROVEMENT

QUALITY ASSURANCE (CONTINUED) QUALITY CONTROL –VERIFY ALL DEFECTS AND ENHANCEMENTS ARE DOCUMENTED AND TRACKED –WITNESS SPR CLOSURES, DELTA, AND SYSTEM TESTS –MONITOR SOFTWARE BUILDS AND DELIVERY PREPARATION

CONTINUOUS IMPROVEMENT HIGHLIGHTS REQUIREMENTS REVIEW PEER REVIEWS TRAINING –247 HOURS PROGRAMMERS –173 HOURS TESTERS NEW VERSION RELEASE PROCESS INCREMENTAL BUILDS NEW TESTING PROCESS

SOFTWARE TEST PROCESS Beta Site Testing SPR Closure Program Debug Shipboard At Sea Testing Shipboard Alongside Testing Beta Site Testing Development Testing Operational Evaluation System Test Delta Test Survivability Test Version Testing

BETA TESTING OCCURS ON A CONTINUOUS BASIS CFNOS AND CFNES INVOLVED DEFECTS ARE DOCUMENTED –ATTEMPT TO REPRODUCE ON PREVIOUS VERSION FREE PLAY

VERSION TESTING VERSION SURVIVABILITY TEST –COMPARES SYSTEM PERFORMANCE WITH PREVIOUS VERSION PERFORMANCE –FULLY AUTOMATED –FOCUSES ON MISSILE THREAT PROFILES, TEWA PROCESSING –REPORT PRODUCED AND REVIEWED

DELTA TEST INTEGRATION TESTING WHITE BOX FOCUS DEMONSTRATES ALL CHANGES FUNCTION CORRECTLY IN THE SAME BUILD TEST REPORT PRODUCED/REVIEWED

SYSTEM TEST NORMALLY STATIC FOUR PHASES –EW/ASW (8 HRS) –AWW/RADAR (8 HRS) –FULL LOAD TRACKING (2 HRS) –OVERALL (6 HRS) REPORT PRODUCED/REVIEWED

TESTING IMPROVEMENT S TEST CELL ENHANCEMENT STUDY –FULLY DOCUMENT PROCESS DEVELOMENT AND USE OF METRICS FORMALIZATION OF PEER REVIEWS AUTOMATED TESTING DEFECT REPORTING DEFECT DATA COLLECTING TESTING/PROGRAMMING TOOLS

CONCLUSION INITIAL TESTING POOR TRYING TO DO TOO MUCH AT ONCE TESTING PROCESS NOW IN PLACE OBTAINING REPEATABLE RESULTS FINE TUNING PROCESS STAGE