The design of reliable and testable systems, both analog and digital, is considered at the component, circuit, system, and network levels. Using numerous real-world examples, the trade-offs between redundancy, testability, complexity, and fault tolerance are explored. Although the emphasis is predominantly on electronics, related examples from the aerospace and software industries are included. The concepts of fault lists, collapsed fault lists, and other techniques for reducing the complexity of fault simulation are addressed. A quantitative relationship between information theory, error correction codes, and reliability is developed. Finally, the elements of a practical quality assurance system are presented. In addition to homework assignments, students will conduct an in-depth, quantitative case study of a practical system of personal interest.
The course will be based on case studies, as is often done for law and management courses. However, it will have a strong quantitative and experimental focus.
Illustrative assignments (actual assignments will be described in class and posted on Canvas):
Browse the entire book. Keep the text for future reference. Pay special attention to:
Read and report on another book, read for enrichment, such as:
Assignment 1, due June 17th
Identify as many features of your current living location, a family member’s house, etc. and identify safety features that are either present, missing, etc. Also, check the date stamp for one or more of the toilets. Explore whether there is asbestos, lead paint, ungrounded outlets, missing “drip traps”, un-tempered door glass, etc.
Nominal Content summary, by lecture (one lecture per week for twelve weeks):
To teach both the subjective and objective aspects of reliability, supported by an understanding of probability distributions that can be used for modeling, simulation, and prediction of the performance characteristics and reliability properties of a wide variety of systems. To learn the fundamentals of test vectors, fault lists, and test “coverage”. To learn about single stuck fault models for digital systems. To develop a healthy skepticism about open-source technical literature. To learn how to design and execute tests, particularly under an accelerated testing protocol.
Required
O’Connor, Patrick P., Practical Reliability Engineering, 5th Edition, Wiley & Sons, 2012.
Author: | O'Connor, Patrick P. |
ISBN-13: | 978-0-470-97981-5 |
ISBN-10: | 0-470-97981-X |
Textbook information for this course is available online through the appropriate bookstore website: For online courses, search the MBS website at http://ep.jhu.edu/bookstore.
Accessibility to online resources and the ability to attend occasional online sessions using Zoom, with a headset and microphone (to eliminate feedback when speaking) is necessary.
MatLab is optional, but you can gain access to a recent version of MATLAB with the Signal Processing Toolkit. The MATLAB Total Academic Headcount (TAH) license is now in effect. This license is provided at no cost to you. Send an email to software@jhu.edu to request your license file/code. Please indicate that you need a standalone file/code. You will need to provide your first and last name, as well as your Hopkins email address. You will receive an email from Mathworks with instructions to create a Mathworks account. The MATLAB software will be available for download from the Mathworks site.
Excel is always useful, as are any other programs/tools that you have experience with (Circuitmaker, MathCAD, etc.)
It is expected that each class, with preparation and homework, will take approximately 7–10 hours per week to complete (but compressed by 2x when the course is offered over a seven week period).
This course will consist of four basic student requirements:
You are responsible for attending class on a regular basis, although you do not need to notify the instructor if you need to miss an occasional class for work or personal reasons.
Preparation and participation is graded as follows:
10 points per class attended, normalized to 20 points when computing its impact on the final grade.
Assignments will include a mix of qualitative assignments (e.g. literature reviews, model summaries), quantitative problem sets, case study updates, and reading assignments. Include your name and assignment identifier, but not a separate cover page. Please upload the assignments to Canvas, although they can be submitted in hard-copy during class sessions.
Restate the problem succinctly. Also include your name and a page number indicator (i.e., page x of y) on each page of your submissions.
Each problem should have the problem statement, assumptions, computations, and conclusions/discussion presented with explanation, in expository form.
Equations or computations presented without explanation will be given a 1 and returned for resubmission. All Figures and Tables should be captioned and labeled appropriately. Use graphics. Under no circumstances submit long lists of numbers, or more than one file per assignment. The assignments can be handwritten, and should be submitted as either .doc, .docx, or .pdf files.
All assignments are due in a timely fashion (typically 1 – 2 class sessions after being assigned). Do not turn in a massive collection of assignments the last week. They will be penalized for lateness. In general, turn in your assignments when they are complete to your satisfaction and as you would turn them into your management at a career level position.
If, after submitting a written assignment you are not satisfied with the grade received, you are encouraged to redo the assignment and resubmit it. If the resubmission results in a better grade, that grade will be substituted for the previous grade. However, “gaming the system” will not be rewarded.
As a general example for Whiting courses, but to be taken here as general guidance, and using the percentages listed below also as general guidance, is a detailed grading rubric. For the purposes of this term, however, the following simplified simplified rubric will be used:
10 points. Assignment is above and beyond what is normally expected (an A+).
Typical grade for a competent, adequate submission similar to what constitutes an acceptable technical memo in an engineering environment (an A).
Assignment is incomplete or lacking in some significant way. It should be considered a B-, and resubmitted if possible.
A placeholder for an incomplete submission.
A place holder for no submission or an unacceptable submission.
For reference per Whiting guidelines:
Qualitative assignments are evaluated by the following grading elements:
Quantitative assignments are evaluated by the following grading elements:
A course project will be assigned several weeks into the course. The final few weeks will include in-class presentations of the course projects. Specifically, students will be asked to submit a summary of their project to the Canvas discussion forum for projects, and to present a short summary in class using ppt, handouts, whiteboard, etc. (A single presentation document is all that is required. An additional report is not required).
The course project is evaluated using the 10-8-6-5-1 rubric using the following grading elements:
Grading turnaround for assignments: Assignments are nominally due as stated above, and graded on Canvas within one week. There is typically one assignment per week.
Deadlines for Adding, Dropping and Withdrawing from Courses
Students may add a course up to one week after the start of the term for that particular course. Students may drop courses according to the drop deadlines outlined in the EP academic calendar (https://ep.jhu.edu/student-services/academic-calendar/). Between the 6th week of the class and prior to the final withdrawal deadline, a student may withdraw from a course with a W on their academic record. A record of the course will remain on the academic record with a W appearing in the grade column to indicate that the student registered and withdrew from the course.
Academic Misconduct Policy
All students are required to read, know, and comply with the Johns Hopkins University Krieger School of Arts and Sciences (KSAS) / Whiting School of Engineering (WSE) Procedures for Handling Allegations of Misconduct by Full-Time and Part-Time Graduate Students.
This policy prohibits academic misconduct, including but not limited to the following: cheating or facilitating cheating; plagiarism; reuse of assignments; unauthorized collaboration; alteration of graded assignments; and unfair competition. Course materials (old assignments, texts, or examinations, etc.) should not be shared unless authorized by the course instructor. Any questions related to this policy should be directed to EP’s academic integrity officer at ep-academic-integrity@jhu.edu.
Students with Disabilities - Accommodations and Accessibility
Johns Hopkins University values diversity and inclusion. We are committed to providing welcoming, equitable, and accessible educational experiences for all students. Students with disabilities (including those with psychological conditions, medical conditions and temporary disabilities) can request accommodations for this course by providing an Accommodation Letter issued by Student Disability Services (SDS). Please request accommodations for this course as early as possible to provide time for effective communication and arrangements.
For further information or to start the process of requesting accommodations, please contact Student Disability Services at Engineering for Professionals, ep-disability-svcs@jhu.edu.
Student Conduct Code
The fundamental purpose of the JHU regulation of student conduct is to promote and to protect the health, safety, welfare, property, and rights of all members of the University community as well as to promote the orderly operation of the University and to safeguard its property and facilities. As members of the University community, students accept certain responsibilities which support the educational mission and create an environment in which all students are afforded the same opportunity to succeed academically.
For a full description of the code please visit the following website: https://studentaffairs.jhu.edu/policies-guidelines/student-code/
Classroom Climate
JHU is committed to creating a classroom environment that values the diversity of experiences and perspectives that all students bring. Everyone has the right to be treated with dignity and respect. Fostering an inclusive climate is important. Research and experience show that students who interact with peers who are different from themselves learn new things and experience tangible educational outcomes. At no time in this learning process should someone be singled out or treated unequally on the basis of any seen or unseen part of their identity.
If you have concerns in this course about harassment, discrimination, or any unequal treatment, or if you seek accommodations or resources, please reach out to the course instructor directly. Reporting will never impact your course grade. You may also share concerns with your program chair, the Assistant Dean for Diversity and Inclusion, or the Office of Institutional Equity. In handling reports, people will protect your privacy as much as possible, but faculty and staff are required to officially report information for some cases (e.g. sexual harassment).
Course Auditing
When a student enrolls in an EP course with “audit” status, the student must reach an understanding with the instructor as to what is required to earn the “audit.” If the student does not meet those expectations, the instructor must notify the EP Registration Team [EP-Registration@exchange.johnshopkins.edu] in order for the student to be retroactively dropped or withdrawn from the course (depending on when the "audit" was requested and in accordance with EP registration deadlines). All lecture content will remain accessible to auditing students, but access to all other course material is left to the discretion of the instructor.