Beruflich Dokumente
Kultur Dokumente
2016
Monday Tuesday
I. OBJECTIVES
III. LEARNING
RESOURCES
A. References
1. Teacher’s Guide pages
https://www.beyourownit.com/identify
2. Learner’s Materials pages https://en.wikipedia.org/wiki/Nonconformit ing-desktop-pc-components/
3. Textbook pages y_(quality) http://www.yourwindow.to/security-
4. Additional Materials from
https://www.qualitysystems.com/support/l policies/ref010702.htm
Learning Resource (LR) earning/non-conformance
portal
B. Other Learning Resources
IV. PROCEDURES
A. Reviewing previous
lesson or
presenting the new lesson
B. Establishing a purpose for the How to decide on what immediate actions Hardware faults are to be recorded
lesson will be taken to correct the problem? and reported to the appropriate
trained staff or maintenance firms for
corrective action.
C. Presenting examples/ Who is responsible for the decision? No procedures in place to handle hardware
instances of the new lesson fault reporting.
D. Discussing new concepts and How reworked items should be checked (if it Insufficient data may result in
practicing new skills #1 is different from normal inspection)? incorrect diagnosis of the fault or a
possible security breach.
Monday Tuesday
E. Discussing new concepts How and where a non-conformance Lack of any proactive preventative
and practicing new skills #2
should be recorded? maintenance.
F. Developing mastery What steps should be taken to identify Differentiate components and functions
(Leads to Formative Assessment 3)
any defective product released to a
customer?
G. Finding practical How a decision will be made on whether Failure to identify a 'pattern' of problems and
applications of concepts further corrective action is necessary? faults can delay remedying the problem.
and skills in daily living
H. Making generalizations and Generalize quality standards. Recording and Reporting Hardware Faults
abstractions about the
lesson
V. REMARKS
VI. REFLECTION