Definitions, Acronyms, and Abbreviations
Create New Topic
| Thursday, October 2, 2003
Course Description: In this course, the design process for Automated Test Systems is presented using standard systems engineering principles. No prior knowledge of ATE, ATS or TPS development is assumed. A general familiarity with electronic testing techniques is a prerequisite for a full understanding of the material presented. This class will present a series of reference designs as a starting point for ATS and TPS development. Proposed design stages are explained in view of the typical division between hardware and software for the ATS. The process, in which design recommendations are made, can make easier the development of future systems. Thus helping the design team to consider important aspects in decisions taken along the development process and keeping these decisions linked to the requirements defined in initial development stages. Through the use of the proposed process, shorter development cycles can be expected. Text: Handouts Lectures: You are responsible for all material covered in the textbook and in lecture, including any announcements made or special handouts distributed in lecture. If you must be absent during a given lecture, check with a friend to make sure you know what was covered. Reading Assignments: Students are expected to read the relevant text book chapters and all handouts by the assigned class period. Computer Use: Students are expected to use computers to do analyses, to prepare reports, and to conduct out-of ¡Ìclass assignments. Computers will be used to analyze data, prepare engineering graphs for reports, and perform analytic studies. Knowledge of word-processing, spreadsheet, and analysis software (i.e., LabVIEW, CVI, ATEasy, Word, Excel, Matlab, etc.) is required. Homework: The weekly assignments represent by far the most important element of the course, and where you will learn the most. I encourage you to work on them in groups if you like; the assignments will occasionally be difficult and may require more than one head! However, be convinced in the depths of your soul that letting others do the work for you will lead to disaster at test time. A good technique for many students is to try the assignment individually, then to get together with a friend or in a group for the tough ones. Many years of experience have shown that students who do not work the assignments thoroughly do not really understand the material and perform poorly at test time. Reading the text is never sufficient! You are expected to do your homework assignments by their due dates and have them available in class. You may receive help on these or even work with another student. However, if you do this, please indicate the degree of your own involvement. If you simply submit a xerox copy of another student's work, explain your own role in doing the assignment, which should not be limited to just operating the copier. The degree to which students participate in doing homework will be subjectively judged and may influence the final grade by up to a point in either direction in borderline cases, as well as affecting the subjective "class participation" part of the grade. The intent here is to allow any degree of cooperation and help on the homework, and use the pop quizzes as the grading mechanism to motivate doing homework. Grading: You are welcome to discuss the assignments with other students or with the instructor after you have made an effort by yourself. However, you must turn in your own work, not work identical to that of another student. Be sure to credit at the top of your assignment anyone with whom you discussed ideas. It is an honor code violation to simply copy someone else's work or refer to solutions from previous years. All material will be graded on a basis of 0-100. On tests and the examinations some questions may be "compensated" if large numbers of students miss them (indicating possibly a badly posed question or inadequate coverage of the topic in class). On such questions, some proportion of the "lost" credit will be returned. This is the only form of "curving" of grades in the course. All written work is expected to be neat and well presented. A penalty of up to 10% will be assessed for poor presentation, and in extreme cases perhaps more. If you miss an assignment for a valid, verified emergency, see your instructor. Letter grades will not be based on a curve but rather on the following fixed scale:
- Instructor: Dr. David R. Carey
- Email: firstname.lastname@example.org
- Phone: 570-408-4807
- Office: SLC-221
- Office Hours: As posted on office door or by appointment.
- Lecture and Location: R 18:00-2045 SLC 270
The advantage of the fixed scale is that you are not competing with other students to ¡∫get ahead of the curve.¡Ö Everyone who works hard can do well in the class. It is possible that the entire class can receive A¡Ùs (all scores would be 93% or better). Those who do not do the work will score accordingly
- 93-100 = 4.0,
- 88-92 = 3.5,
- 83-87 = 3.0,
- 77-82 = 2.5,
- 70-76 = 2.0,
- 65-69 = 1.5,
- 60-64 = 1.0,
- below 60 = 0.0.
How to succeed in this course:
- Class Participation 10%
- Test 1 15%
- Test 2 15%
- Final Exam 30%
- Homework 10%
- Project 20%
- It is expected that a successful student will invest at least two times the lecture period studying and problem-solving per week. Do not expect a good grade if you are not prepared to work at least this much.
- Read the assigned text before coming to lecture. The importance of this cannot be overemphasized.
- Work as many problems as possible on a weekly basis; the assigned ones represent the minimum recommended. Do these on your own, if possible; then work with other students to solve the problems.
- Keep up on a regular basis; cramming doesn¡Ùt work.
- No late homework will be accepted.
- Plagiarized homework from another student will result in an automatic zero for all parties involved.
- No make-up exams will be given.
- Class attendance is mandatory.
- INTRODUCTION TO AUTOMATED TEST SYSTEMS
- Basic Automated Test System
- Test Program Set
- Relationship between TPS and ATS
- TEST PROGRAMING SOFTWARE LANGUAGES
- LabVIEW Overview
- ATEasy Overview
- LabWindowsCVI Overview
- Measurement Systems
- Measurement Fundamentals
- Measurement Uncertainty and Error
- ATS DESIGN
- INTERFACE DESIGN
- EQUIPMENT RACK
- ATS MANUFACTURING
- ATS DEPLOYMENT
- TEST PROGRAM SET DESIGN
- TPS INTEGRATION
- ATS/TPS ACCEPTANCE