This module is at an early stage of development, but we have created this overview in order to indicate to potential students the scope of the material and how it is planned to be presented. If you have any comments, questions or concerns, please feel free to contact Martin Tarr on +44 (0)1383 723989, or email him at martin@mtarr.co.uk.
Note that the links to module material are not yet functional.
Whatever the product or application, any electronic item needs to be tested before shipment, in order to give both manufacturer and purchaser some assurance that the product will function as intended. The extent and depth of this screening process, and the type of defects that it detects, will depend on the nature of the product, its application environment, and how “mission critical” the application is.
However, whether the product is a simple piece of hardware for a commercial application, or a complex military assembly with embedded software, the screening process needs to be correctly designed in order to give adequate performance at an acceptable cost.
In this module, we are using the term “Design for Test” in its widest possible sense, to embrace both the process of matching the screening strategy as accurately as possible to the requirement, and performing the design of the electronic, mechanical and software aspects of the assembly in such a way as to make the screening task effective and affordable. As we explain in the Module Descriptor, Design for Test considerations will affect, among other things, how the design is partitioned, the design verification process, certain elements of product layout, and the testing of units during manufacture, rework and repair. Such Design for Test is therefore a vital factor in the design process, and one that needs to be considered from the concept stage through to the end of a product’s life.
What we are seeking to do in this module is to give you a broad perspective on testing issues for both hardware and software, from concept and design through to manufacture and reliability screening. The module is therefore designed not to require detailed prior knowledge of electronic design, software engineering, or manufacturing, and the material is deliberately planned to be self-standing, with the focus on the strategic use of test, rather than on the detail of any one topic. However, by using a mixture of simulations, remotely-accessed software, and case studies, we plan to allow you to discover the implementation issues, so that you are able to make appropriate and effective choices in the real world of product development.
Figure 1 shows the module contents in diagrammatic form, with each of the branches of the mind map referenced to outcomes defined within the Module Descriptor.
The three assignments are spread throughout the course and are essentially independent. For all assignments you will be expected to reflect on the learning experience as well as carrying out specific tasks and critical evaluations.
This is a module for those who like both variety and the opportunity to be involved with a range of challenges!
[ back to top ]
As you will see in the timetable below, which is based on a nominal 8–10 hour study week, the first four units are extended, requiring two weeks study, whilst the three final units form a coherent group and are planned to occupy just a week each, despite the impression of their greater importance given by the mind map.
| Study Week | Unit/Assignment | Unit / Assessment |
|---|---|---|
| 1 & 2 | 1 | Overview of the testing process |
| 3 & 4 | 2 | Hardware |
| 4 & 5 | Assignment 1 | |
| 5 & 6 | 3 | Automated test |
| 7 & 8 | 4 |
Software test |
| 8 & 9 | Assignment 2 | |
| 10 & 11 | 5 6 7 |
Methods overview Production hardware Improving reliability |
| 12 | Assignment 3 |
We suggest that you tackle the material in the four groups indicated in Figure 1, skim reading the unit texts to set the scene for subsequent more detailed study, and then completing the relevant assignment work.
Whilst the timetable is not “set in tablets of stone”, we would strongly advise that you attempt to keep to this timetable, making an early start on any work with simulation and remote access software, so that any problems can be ironed out as they arise without jeopardising the final outcome.
The module content may be accessed either from the drop-down menu or the list of contents below:
To help you check that you have found all the materials, or in case you need to download/print information in advance if you are going away on business, we will be creating a map of the module that identifies all the main module elements, as was done for our Design for Thermal Issues module. You might prefer to bookmark the map as an entry point for the module.
At present we have yet to establish exactly what software and hardware will be used in Unit 2 to illustrate the control and operation of test equipment controlled by an industry-standard bus, but it seems likely that this module will give you experience of using LabView, which is the tool most widely used within our industry. For Unit 3, we will be using a JTAG simulation tool.
This module is intended to be self-standing as far as possible, but it makes references to a number of web-based resources. These are relatively stable sites, but please contact us if you find that key materials have disappeared, and we will provide you with access to back-up sources or equivalents.
Where we have linked to external materials, we would encourage you to look at most of those resources, rather than just skip past. Whilst their value varies, there is usually some insight to be gained, and often the sites chosen have visual material that is not directly available for us to incorporate in this module.
During the course of preparing this module, we read a number of books, some of which are listed in the Module Descriptor under Indicative Reading. A fuller list is available at this link, giving both the details of the books and a brief overview.
[ back to top ]
[ back to top ]
Updated 25.5.06 RA
Powered by Google
Site Map