Test Plan SP1: Time To Train User Plan: Gather a group of 10-15 people and teach them individually how to use the system. Document how long it takes each.

Slides:



Advertisements
Similar presentations
The Aged Care Standards and Accreditation Agency Ltd Continuous Improvement in Residential Aged Care.
Advertisements

Damian Gordon.  Static Testing is the testing of a component or system at a specification or implementation level without execution of the software.
Software Development Life Cycle
Chapter 10 Schedule Your Schedule. Copyright 2004 by Pearson Education, Inc. Identifying And Scheduling Tasks The schedule from the Software Development.
Software Quality Assurance Inspection by Ross Simmerman Software developers follow a method of software quality assurance and try to eliminate bugs prior.
Testing Without Executing the Code Pavlina Koleva Junior QA Engineer WinCore Telerik QA Academy Telerik QA Academy.
P11511 Project Review. Project Team, Faculty, and Customer Project Team: – Project Lead: Kevin Argabright (ME) – Team Members: John Fitch Dean (ME) Mike.
Software Quality Metrics
Compressor ReVamp and Fabrication PO9452. Update Revised Concept Generation Selected some concepts Scheduled Conference call with Dresser Rand Schedules.
IGen Fuser Bearing Project P Agenda Meeting Timetable Start Time Review Topic 2:20Introductions 2:25Project Description 2:35Customer Needs 2:40Risk.
SE 450 Software Processes & Product Metrics Assessments.
1 Software Testing and Quality Assurance Lecture 30 - Introduction to Software Testing.
System Implementation
The Software Product Life Cycle. Views of the Software Product Life Cycle  Management  Software engineering  Engineering design  Architectural design.
8 February 2013P Xerox Bearing Tester Detailed Design Review [1]
Measuring Learning Outcomes Evaluation
Assessment College of Engineering A Key for Accreditation February 11, 2009.
Effectively applying ISO9001:2000 clauses 5 and 8
Rapid Prototyping Model
The Software Development Cycle Defining and understanding the problem.
University of Palestine software engineering department Testing of Software Systems Fundamentals of testing instructor: Tasneem Darwish.
Instructional Design Eyad Hakami. Instructional Design Instructional design is a systematic process by which educational materials are created, developed,
1 Software Testing (Part-II) Lecture Software Testing Software Testing is the process of finding the bugs in a software. It helps in Verifying and.
Software Engineering Chapter 15 Construction Leads to Initial Operational Capability Fall 2001.
RUP Fundamentals - Instructor Notes
Teaching material for a course in Software Project Management & Software Engineering – part II.
Feasibility Study.
Process Assessment Method
Essential knowledge and skills for effective participation in the Child Outcome Summary Process Be able to describe and differentiate the three child outcomes.
Systems Life Cycle. Know why it is necessary to evaluate a new system Understand the need to evaluate in terms of ease-of- use, appropriateness and efficiency.
Product Evaluation & Quality Improvement. Overview  Objectives  Background  Materials  Procedure  Report  Closing.
TESTING LEVELS Unit Testing Integration Testing System Testing Acceptance Testing.
Software Testing. Software testing is the execution of software with test data from the problem domain. Software testing is the execution of software.
ISAT FREQUENTLY ASKED QUESTIONS. Why is OSBE making so many changes to the ISAT? The contract between NWEA & OSBE was due to expire. Even if the contractor.
Introduction to Loops For Loops. Motivation for Using Loops So far, everything we’ve done in MATLAB, you could probably do by hand: Mathematical operations.
Chair of Software Engineering Exercise Session 6: V & V Software Engineering Prof. Dr. Bertrand Meyer March–June 2007.
A Metrics Program. Advantages of Collecting Software Quality Metrics Objective assessments as to whether quality requirements are being met can be made.
Connecting with Computer Science2 Objectives Learn how software engineering is used to create applications Learn some of the different software engineering.
Engineering Design Process Brookville Intermediate School 7 th Grade.
Integration testing Integrate two or more module.i.e. communicate between the modules. Follow a white box testing (Testing the code)
EG1003: Introduction to Engineering and Design Product Evaluation & Quality Improvement.
Yazd University, Electrical and Computer Engineering Department Course Title: Advanced Software Engineering By: Mohammad Ali Zare Chahooki The Project.
May 10, 2013P Xerox Bearing Tester Final Project Review.
Teaching slides Chapter 3
1 The Software Development Process ► Systems analysis ► Systems design ► Implementation ► Testing ► Documentation ► Evaluation ► Maintenance.
Introduction to Software Engineering Muhammad Nasir Agile Software Development(2)
Research And Evaluation Differences Between Research and Evaluation  Research and evaluation are closely related but differ in four ways: –The purpose.
1 Determining How Costs Behave. 2 Knowing how costs vary by identifying the drivers of costs and by distinguishing fixed from variable costs are frequently.
Advanced Software Engineering Dr. Cheng
Understanding Standards: Nominee Training Event
Product Validation Adapted from the NASA Systems Engineering Handbook for CSULB EE 400D by Alia Bonetti.
Methodologies By Akinola Soyinka.
Xerox Bearing Tester Final Project Review
Science Fair Project: Basic Outline
Version 0.1Assessment Method Overview - 1 Process Assessment Method An objective model-independent method to assess the capability of an organization to.
Product Evaluation & Quality Improvement
Product Evaluation & Quality Improvement
Introduction to pseudocode
CLINICAL INFORMATION SYSTEM
What and How are Science, Engineering, and Technology Related?
Engineering Design Process
Xerox Bearing Tester Systems Level Design Review
Software Development Process
Software life cycle models
Product Evaluation & Quality Improvement
Product Evaluation & Quality Improvement
Welcome to Corporate Training -1
System Construction and Implementation
Power Steering Test Stand
Design Document Review
Presentation transcript:

Test Plan SP1: Time To Train User Plan: Gather a group of people and teach them individually how to use the system. Document how long it takes each person to gain competence with the system. Ideally, the group will contain a broad range of knowledge bases with regards to vibration and mechanical systems. This will help to get a better estimation on the time it would take to train someone with no engineering background. The individuals who were trained will be asked about areas that were unclear or difficult to understand. From their feedback, efforts will be made to streamline the process. This will occur whether or not the specification is met. SP8: Use Xerox’s Machine to Get a Pass Fail Criterion on the Test Bearings Plan: Xerox’s Acoustic machine will be setup and run according to the manual specifications. Pass or fail values will be collected for all of the test bearings. Four tests will be conducted on each bearing to make sure the result is repeatable since the machine has failed an MSA. The purpose of collecting these readings will be to compare them against the results from the vibration test stand that is being developed. SP9: Measurement System Analysis on Vibration Machine Plan: A measurement system analysis (MSA) will be conducted on the vibration machine. If the vibration machine fails the MSA, efforts will be made to identify areas where there are inconsistencies. These inconsistencies will be fixed and the MSA will be conducted again. This process will iterate until the vibration machine passes the MSA or until no other areas of improvement can be identified without redesigning the entire fixture. SP10: Results of Vibration Collection Plan: The results of the vibration collection will be dependent upon the pass and fail criteria that is developed using the test bearings. Vibration measurements will be conducted on each of these bearings and they will be correlated to the tests that were already conducted by Arnprior. The developed pass and fail criteria will then be input into the LabView interface and a pass or fail reading will be output at the end of each test.

Risk Assessment

LabVIEW Interface