#WEEK 3: RELIABILITY-TEST DOCUMENTATION AND OTHER ITEMS NEEDED FOR RELIABILITY TESTING 2 August 2006.

Slides:



Advertisements
Similar presentations
Configuration Management
Advertisements

DISTRICT FIVE CONSTRUCTION CONTRACT ADMINISTRATION UPDATE TRAINING Submission of Working Schedule Specification SP A.
Ninth Lecture Hour 8:30 – 9:20 pm, Thursday, September 13
MODELING THE TESTING PROCESS Formal Testing (1.0) Requirements Software Design Risk Data Approved, Debugged, Eng. Tested Code Automated Test Tools Tested.
Modeling the Process and Life Cycle CSCI 411 Advanced Database and Project Management Monday, February 2, 2015.
Chapter 4 Quality Assurance in Context
Project Control Techniques
CSCU 411 Software Engineering Chapter 2 Introduction to Software Engineering Management.
Overview Lesson 10,11 - Software Quality Assurance
Software Development Process. Process Improvement Using the Shewhart Cycle 1.PLAN - Plan a change aimed at improvement, collect data, and establish a.
COMP8130 and 4130Adrian Marshall 8130 and 4130 Test Execution and Reporting Adrian Marshall.
SE 555 Software Requirements & Specification Requirements Validation.
Fact-Finding Fact-Finding Overview
Section 4.0 Project Implementation. Factors that Ensure Success  Update the project plan  Stay within scope  Authorized change implementation  Providing.
Stoimen Stoimenov QA Engineer QA Engineer SitefinityLeads,SitefinityTeam6 Telerik QA Academy Telerik QA Academy.
Development and Quality Plans
© 2006 Thomson-Wadsworth. Learning Objectives State the purpose of employee discipline. List common reasons why employees are disciplined. Identify the.
Procurement and Food Service Contracts Pages
The chapter will address the following questions:
University of Palestine software engineering department Testing of Software Systems Fundamentals of testing instructor: Tasneem Darwish.
S/W Project Management
© Mahindra Satyam 2009 Project Metrics QMS Training.
1 Software Quality Engineering CS410 Class 5 Seven Basic Quality Tools.
Collecting, processing and using… The Importance of Data.
Testing. Definition From the dictionary- the means by which the presence, quality, or genuineness of anything is determined; a means of trial. For software.
LBTO IssueTrak User’s Manual Norm Cushing version 1.3 August 8th, 2007.
Galin, SQA from theory to implementation © Pearson Education Limited 2004 Review objectives Formal design reviews (FDRs) Participants Preparations The.
PPMT CE-408T Engr. Faisal ur Rehman CED N-W.F.P UET P.
Understand Application Lifecycle Management
Tingxuan Liu Risk Management in Software engineering.
Production Planning Group 4 Claudia· David· Lisa· Shakeia· Vicky.
Extreme/Agile Programming Prabhaker Mateti. ACK These slides are collected from many authors along with a few of mine. Many thanks to all these authors.
CHAPTER#08 MANAGEMENT OF TECHNICAL PROPOSALS AND SPECIFICATIONS Lecture No. 08 Course: Engineering Management 19 april 2013 MED DEPARTMENT, U.E.T TAXILA.
TESTING SERVICES Overview Testing Accommodations is a collaborative process between the DRC student, the Professor, and DRC. COMMUNICATION IS ESSENTIAL.
Applied Software Project Management
1 Chapter Nine Conducting the IT Audit Lecture Outline Audit Standards IT Audit Life Cycle Four Main Types of IT Audits Using COBIT to Perform an Audit.
PLANNING ENGINEERING AND PROJECT MANAGEMENT By Lec. Junaid Arshad 1 Lecture#03 DEPARTMENT OF ENGINEERING MANAGEMENT.
Affordable Computerized Maintenance Management Solutions (CMMS) Gabi Miles Hach Company May 22, 2009.
THE AGILE MENTALITY CHAPTER Topics  Why Use Agile and Scrum?  Agile Development –Manifesto for Agile Software Development  Scrum Methodology.
STEP 4 Manage Delivery. Role of Project Manager At this stage, you as a project manager should clearly understand why you are doing this project. Also.
Improving Production Through Reliability – Assessment with Limited Information 9 Steps to Improved Manufacturing Reliability.
Copyright 2010, The World Bank Group. All Rights Reserved. Statistical Project Monitoring Section A 1.
Project Launch Presentation. Overview  Group Members: Joshua Booth Jiajia Jiang Weijuan Shi  Client: G & T Security.
Connecting with Computer Science2 Objectives Learn how software engineering is used to create applications Learn some of the different software engineering.
Chapter 1: Fundamental of Testing Systems Testing & Evaluation (MNN1063)
Oktalia Juwita, S.Kom., M.MT. SYSTEMS DEVELOPMENT Dasar-dasar Sistem Informasi – IKU1102.
Software Quality Assurance SOFTWARE DEFECT. Defect Repair Defect Repair is a process of repairing the defective part or replacing it, as needed. For example,
1 Commissioned by PAMSA and German Technical Co-Operation National Certificate in Paper & Pulp Manufacturing NQF Level 2 Produce paper, board or tissue.
Requirements Workshop Techniques for E-Business Projects
HNDIT23082 Lecture 09:Software Testing. Validations and Verification Validation and verification ( V & V ) is the name given to the checking and analysis.
SCOPE DEFINITION,VERIFICATION AND CONTROL Ashima Wadhwa.
Development Processes Chapter Study Questions Q1: How are business processes, IS, and applications developed? Q2: How do organizations use business.
1 Chapter 8 karvaytMélKMerag nig kareFVIr)aykarN_ nig karbiTKMerag Project Evaluation, Reporting, and Termination.
BSBPMG501A Manage Project Integrative Processes Manage Project Integrative Processes Project Integration Processes – Part 2 Diploma of Project Management.
JRA1 Meeting – 09/02/ Software Configuration Management and Integration EGEE is proposed as a project funded by the European Union under contract.
TMP3413 Software Engineering Lab Lab 01: TSPi Tool Support.
Welcome. Contents: 1.Organization’s Policies & Procedure 2.Internal Controls 3.Manager’s Financial Role 4.Procurement Process 5.Monthly Financial Report.
Adaptive Software Development Process Framework. Version / 21 / 2001Page Project Initiation 2.0 Adaptive Cycle Planning 5.0 Final Q/A and.
1 March 19, Test Plans William Cohen NCSU CSC 591W March 19, 2008.
Software Project Configuration Management
Software Engineering (CSI 321)
Global Supplier Quality Early Production Containment Training
Lecture 09:Software Testing
  Aptiv Global Supplier Quality Early Production Containment Training.
Quality Measurable characteristic Cyclomatic complexity Cohesion
Brainstorming & Project Management
Adaptive Product Development Process Framework
Onboarding and Training
Global Supplier Quality Early Production Containment Training
Managing Project Work, Scope, Schedules, and Cost
Presentation transcript:

#WEEK 3: RELIABILITY-TEST DOCUMENTATION AND OTHER ITEMS NEEDED FOR RELIABILITY TESTING 2 August 2006

Documentation Test Articles Test Equipment Reliability Test Procedure Test Log Book Failure Reporting Implementing Corrective Action Final Test Report

Test Articles Obtained the test articles/units for a reliability test Sometimes if a new program starts to run behind schedule – there is a delay to deliver the test articles/units for reliability test Will cause bigger problems later on in production (a risk with regards to potential design problems not being discovered quickly)

Test Equipment The unit under test has to be powered by a piece of test equipment while it is undergoing thermal and vibration cycling Usually have a cable/wire harness that is long enough to connect to the unit Have switches that can exercise certain functions on the unit, as well as an automated test sequence that tests the major functions of the unit Problem-test equipment is in demand during the early stages of new product development between engineers and production and software developers

Reliability Test Procedure Will provide a description of the ground rules for the test, including the test setup, how many units are to be tested, the duration of thermal cycling, and how many hours of vibration are to be performed, exact thermal profile and vibration profile, process of failure notification to the customer and failure reports

Test Log Book Documented - Date and time tracking each portion of the thermal profile that is completed, any functional tests completed in the thermal chamber, each thermal cycle and vibration session that is completed, any failures that occur, failure report number Tests are usually halted at the point of failure See example of Fig 4-6

Failure Reporting Failure reports are formally closed when the cause of failure has been identified and the corrective action that was incorporated to prevent reoccurence of the failure in the future Documented all environmental conditions when the failure occurred See example Fig 4-7 All failure reports should be resolved or closed by end of the reliability test

Implementing Corrective Action After a failure occurs during a reliability development test and agreement is reached by all parties involved on what the fix or corrective action should be, the test is allowed to continue with the fix incorporated into the test units in most cases

Implementing Corrective Action The general consensus in this process of incorporating and testing with corrective action implemented is that sufficient test time is accrued to prove out the effectiveness of the corrective action

Final Test Report After completing a reliability test, a summary of the test results along with failure summary and other documentation is provided Typically, most customers require full test documentation be collected during a reliability test

Final Test Report Includes log sheets, thermal charts, and vibration profile printouts to be included with the report, typically in the appendix section Prior to a final test report being written and submitted to the customer as a formal data item, a final failure review is held internally in the company to discuss and close out all failures and action items that occurred during testing