605.681.81 - Principles of Enterprise Web Development

Expanded Course Description

This course examines major topics in the development of applications for the World Wide Web and covers foundation concepts for Enterprise Web Development. While it assumes little to no prior experience with web development, it does expect and require a reasonable background in Java and Object Oriented Programming. Follow on courses are available in the department to explore many of the modules we cover in much more detail. A summary of topics touched upon in this course (not necessarily in the order they will be introduced) includes:

• Implementation of desktop applications using the Java programming language, including user interface development, asynchronous event handling, multi-threaded programming that will lead us into network programming using sockets. It also introduces distributed database access via JDBC.
• Client side development using HTML 5, CSS and JavaScript
• The design and implementation of server-side web applications, for which students will examine the underlying Web protocol (HTTP), the development of client-side interfaces (e.g., via HTML forms, JavaScript), and the implementation of server-side programs (e.g., via Java servlets, JavaServer Pages, ReSTful Web Services).
• Application of build tools (using Maven) to compile, install and deploy web applications.

This course is designed to be taken online. While not completely self-paced, it has been designed to be used at your convenience. Everything that I would have shown you in class, or discussed, has been written down or captured via screen shot or video. I believe this makes for the best online experience, and it seems that past classes have been very pleased with this format.

We cover Java in this course for several good reasons.

1. It is ubiquitous in the Web Application field
2. It is a very flexible language, which provides a variety of APIs that allows us to cover a lot of material without having to learn a new language for each one.
3. Many of the follow on courses in this program utilize Java as well.

Despite the rationale above, this is not to say that Java is the "end-all"for Enterprise Web Development. There are many other languages and web development solutions out there. In many cases, solutions developed using other languages may work just as well and still follow the same protocols and patterns with different programming syntax and interfaces.

Prerequisites

Experience with Java/C/C++/Pascal/C#.

I expect all students to have experience programming and to understand the basics of software design, debugging and data structures. I am also assuming a reasonable familiarity with Java, though we do review basic language concepts during the first few weeks. If you have not worked with Java recently, or need to brush up, it is expected that you become proficient quickly (by the third week). I also do not assume that you know much about HTML, HTTP, Servlets or JavaServer Pages. If you are not strong with Java, or it has been many years since you have used it, you will want to carefully review the chapters that introduce basic Java syntax and object-oriented programming. In addition, you can expect to spend significantly more time and effort on the class assignments. I also assume you can use a Web browser, understand the difference between a "client" and a "server" and have a basic understanding of protocols like ssh and sftp to interface with the class server for deploying and testing your work.

It is not uncommon for some students taking this course to already be familiar with many of the topics covered. While this may mean that some of this material is a bit "basic" for some of you, there are other students who are not as experienced with Java, HTML, etc, so please be patient, and use your knowledge to help each other with any questions and issues using the class discussion forums. It is a good way to satisfy your forum participation while providing additional resources for those looking for assistance.

Course Structure

The course materials are divided into modules which can be accessed by clicking Modules on the course menu.  A module will have several sections including the overview, content, readings, discussions, and assignments. You are encouraged to preview all sections of the module before starting. Most modules run for a period of seven (7) days, exceptions are noted in the Course Outline. You should regularly check the Calendar and Announcements for assignment due dates.  Each module will run from Saturday through Friday during the semester, with assignments and discussion participation deadlines being Friday evenings at 1159PM EST.  You can jump directly to the course content page here.

Course Topics

• Introduction to the class/Java review
  
• Object oriented programming review
• Advanced Java review (Exceptions, Collections, Generics)
• Patterns for Event Handling and User Interfaces
  
• Basic input/output with Java
  
• Java Networking
• Multi-threaded Programming
• HTML
• CSS
  
• Web interfaces (Forms)
  
• Servlets
• JavaScript
• JavaServer pages
• Model View Controller II Architecture
• Databases and Java
• ReST Services
• ReST and JSON
• Build tools, Maven
• Web security

Course Goals

When you have completed the course, you will be able to

1. Design and create a basic HTML that uses the following:
   1. Basic HTML 5 tags
   2. Tables
   3. Cascading Style Sheets
2. Validate an HTML page for proper format
3. Design and code a Java application that can include the following technologies (Please note that these concepts apply to many modern environments, so this will be more beneficial than you might believe)
   1. Frames
   2. Basic Swing Components
   3. Event Handling
   4. Exceptions
4. Be able to describe and use Object Oriented programming methods, including inheritance and interfaces
   1. Compare the advantages between classes and interfaces
5. Design and code a simple GUI application
6. Be able to describe and use basic multi-threading in Java
7. Understand the use of Java I/O and design a simple client/server application using TCP sockets.
8. Design and code Servlets
9. Design and code JavaServer Pages
10. Understand and be able to build an application that satisfies the MVC2 architecture
11. Design and code a simple Java REST service application
12. Be able to use Java to pass serialized JSON data between clients and servers
13. Describe and use JDBC for database access
14. Be able to compare and contrast different programming methods related to Principles of Enterprise Web Development.
15. Understand the fundamentals of creating and building projects using Maven

Textbooks

There are no required textbooks for this class. However, there are numerous free books and resources available on the internet. While many may be somewhat dated, they still provide a good reference and foundation for material presented in the class. Also did I mention that they were FREE? It is also my understanding that as JHU students, you have free access to books via Safari Books Online. I have provided a short list of text books that you may find helpful during the class and beyond.

Since all books are optional, you may purchase them anywhere. (Amazon, Barnes and Nobels, or even from the Johns Hopkins bookstore at http://johns-hopkins.bncollege.com)

Other Materials & Online Resources

There are also many sites on the world wide web that provide very good tutorials and references that complement material covered in the class. Here is a short list of some that I have found to be informative and helpful:

Required Software

You will need the following hardware for the class:

Computer

You may use a Windows, Mac or Linux computer to do this class. However, if you use a Mac, you do so at your own risk as I don't have access to a Mac so I cant help troubleshoot if you have problems that are a result of the platform or operating system.

You will need the following software for the class:

Web Browser

Any common browser should work fine for the class. I typically use Chrome and/or Firefox, so when I look at the final assignment, this won't affect me.

• Chrome Download
  
• Firefox
  

Canvas

This is the tool that links to the class website, provides access to discussion forums and your grades and is where your homework submissions will be uploaded.

HTML Editor

You will need something to edit HTML. This can be something as simple as Wordpad/Emacs or a higher level product like NVU or WebStorm. Note that some provide community editions, while others are commercial and the free downloads are for trial versions only.

• SeaMonkey
  
• Sublime Text
  
• Jet Brains WebStorm
  

Most developer IDEs (Eclipse as referenced below) also provide good HTML editors.

Java Compiler

Okay, Oracle has made a mess with it's past Java licensing and support. Since Java 17, Oracle has relented from it's previous licensing restrictions and again have a free license for both commercial and personal use. We are currently using Oracle Java version 18 on the class server. It is not the latest and greatest, but does support concepts and techniques used in the class. Since you will be deploying to that class server, it would be in your best interest to make sure your projects are built for that version, even if you are using a more recent version of Java.

Prior to the fall Oracle change, Any version of Java beyond 1.8 through 16 was available for personal use from Oracle, but it was not available for other purposes or redistribution in any way without paying the monthly licensing fees. As a result there are now two options for acquiring the Java Development Kit:

• Download the latest version of Java from Oracle. You can use Java 18 (or later) and just make sure that the work you submit to the class server is only compiled to Java 18 through your IDE. This is demonstrated for Eclipse in the lecture notes. If you wish to download an earlier version, you may do that as well (though I am not sure why). With regard to earlier versions, I am not a lawyer, but as I read the current licensing, you are using Java for personal development, so it is free for you to use. Please pay attention to the licensing, because if you use those earlier versions for anything but development, testing, etc, you may need to get a PAID license. Regardless of the version you download, when you configure your IDE, you will need to produce Java 18 compatible code for use on the class server.
• Download OpenJDK : the advantage here is that this is under the GPL, so it is absolutely free, which is good. However, Oracle, has removed any installer, so this is just a zip file of the Java directory structure. This means that you need to set the "path" on your system to point to your Java installation and usually set the JAVA_HOME environmental variable. Details on this will be given later on.

Java Editor

You will need something to edit Java source code. You can use anything you want as we aren't teaching "how to use" a tool. For many years, this class used Netbeans, which was once a well supported IDE. Once again, Oracle has sloughed off a product on Open Source, so Netbeans no longer has as much integration as it once did with Java. That being the case, Eclipse is used as the "default" demonstration and teaching IDE for the class and is strongly recommended.

Ultimately, you can use any editor/IDE you are comfortable with. However, if you don't use Eclipse, I can't promise you help with configuration or other issues for other IDEs that I may not be familiar with.

J2EE Environment

The class server currently is running Tomcat 9 as it's web server.  As such you will also need to be using the Tomcat 9 web server for your local development. You don't need any special J2EE support, the standard Java SE environment you downloaded above will work fine.  Tomcat version 10 is available and provides support for later versions of the Servlet and JSP APIs.  However, the additional capability under those specifications is marginal (and beyond the scope of this class) and it does alter the package names of the API libraries that are used in the class, so we have maintained a stable Tomcat 9 on the class server and for teaching.  Using Tomcat 10 or later will NOT work with the code as developed for the class material because of the package name changes so you MUST use Tomcat 9 for your local development for the class.  Details for download and installation will be in the class notes later in the semester.

SSH Client

For command line access and related work on the class web server, you will need an SSH client (SSH supports secure-encrypted connections). SSH clients are included with Linux distributions. Please note that SSH connects to port 22 on the server. Putty is an excellent free Windows SSH client. You can get it from here. Another good SSH client is MobaXterm which includes a built in X11 server so you can actually bring up GUI based applications from the class web server if you wish. MobaXterm is available here.

SFTP Tool

While SSH will give you command line access to view and work in directories and editors on the class server, you will need another network protocol to physical move files between your local machines and the class server. In order to upload and download files from the class web server you will need an additional tool that uses SFTP (Secure File Transfer Protocol) or SCP (Secure Copy). MobaXterm does provide SFTP capability but there are others that are convenient as well. A popular SFTP utility is FileZilla which can be found at http://filezilla-project.org/. FileZilla is a nice graphical, Drag and Drop, application that can run on Windows, Mac or Linux. This really does make uploading files much easier. Please note that when you connect to the class computer using FileZilla, you will need to use the SSH port, port 22. I strongly recommend setting the option on FileZilla to not store passwords. The default behavior is to store passwords, and unfortunately they are stored as cleartext files on your computer. This is a significant security vulnerability. Easiest workaround....Don't store the password.

Other good options for Windows users includes WinSCP, and MobaXterm

Zip Software

You will also need software for "zipping" and "unzipping" (compressing and un-compressing) files. Windows 7 and later and the Mac does have zip support built in or you can download applications that might be easier to work with. Here are instructions and suggestions for compression on both platforms:

1. Rar format will not be supported in this class.
2. For Windows - WinZip at http://www.winzip.com/.
3. For Macintosh - Instructions for compression/decompression using zip on a Mac.

Zoom

You will be using Zoom, a web-based conferencing system, to participate in real time office hours. Training guides for Zoom is found here:

JHU School of Engineering Zoom Page

I will be using Zoom to provide Office Hours for the class.

Computer Account

Most of the development for your homework can be done locally on your own machine. Executables for most assignments will need to be uploaded to the class computer (see Course Resources  for details).

Note this is NOT the Canvas server where you will upload source code for your assignments to be graded.

Your login to the class computer will be your JHED ID, with an initial password L3tMeIn!. YOU MUST CHANGE THE PASSWORD after your initial login (using SSH) by typing the command "passwd" at the prompt. Remember, with linux, case matters! Additionally, after you change the password, you will be the only one who knows it (I won't know it). If you forget the password I can reset it to the initial default password and you will have to change it again. Your home directory will include a public_html directory which tomcat will use to serve up web resources. So it is a good location for your early HTML work. Later in the semester you will be deploying web applications directoy to the tomcat server and not your public_html directory.

For every project, you will need to upload source material to the Canvas server for grading, and in many cases you will have to upload executable code to the class server.

Please note that the class server has no email server on it. So you will not have email associated with this class. You will have your JHU account for the program. If asked to email (like in the first assignment) you can just send me an email from an account of your choice.

Student Coursework Requirements

Much of the material in this class is foundational. Having said that it is being taught at a Graduate level so the expectations on students may differ from what you are accustomed to from your Undergraduate experience. Here is a brief list of what I expect from you during the semester.

PLEASE MAKE SURE YOU READ THROUGH AND UNDERSTAND THESE EXPECTATIONS to avoid pitfalls during the semester.

• Most of us (you and I) have "day jobs" and families that we are balancing while teaching/taking this course, so good time management skills are imperative for success. I expect (at this Graduate level) that all of us understood our time commitments prior to adding this class to our schedules. As such, "work" or "vacation" is generally not a reasonable excuse for failing to satisfy our obligations to the class. However, I do understand that "life happens" and unexpected events occur that can impact the ability to meet deadlines. If something unexpected does arise (at work or at home) that will impact your ability to get course work done, I would urge you to let me know ASAP so we can make accommodations to help you out. If you are proactive I will work with you. However, if you wait to tell me on the day an assignment is due (or later) that "you were sick" (or other excuse) that week and couldn't get things done, there will be little flexibility or sympathy from me. The more PROACTIVE you are in working with me, the more likely I will be to accommodate your situation.
• As a graduate class, you will typically find the lecture material and assignments to NOT provide step-by-step instructions for working through each assignment. You will be expected to use all of the lecture notes as a baseline of knowledge to complete the assignments. However, there are many ways to solve problems in computer science and as graduate students I expect that you will be able to "figure things out" if there is something that is included in the lecture but not explicitly called out. I also expect that you can take concepts from previous lectures and build on them without step-by-step instructions. I also firmly believe in Academic Integrity, so input from Discussion Forums and my emails is permitted, but accessing solutions from other sources without referencing them CLEARLY in your submission is a violation of the University Academic Misconduct Policy and will not be tolerated. Just an obvious FYI, other sources DO NOT INCLUDE accessing or purchasing homework that may be posted from previous semesters and it certainly doesn't permit the use of "hired guns" on the internet to do your work for you. In order to minimize this, I do try to alter assignments between semesters to invalidate previous solutions.
• I expect that you will fully investigate and try to work through issues on your work before reaching out for help. In other words, if you get a compiler error trying to build your assignment or if your runtime code results in errors, I expect that you will use all resources at hand (assignment, lecture notes, internet) to figure out the issue and how to resolve it BEFORE bringing it to a discussion forum for myself and the class to resolve for you. I am here to help you to think critically and logically about solving problems with software and that won't happen if I just walk you through issues without you trying to work through them first.
• If you do get to the point where you require assistance, please don't just email me with a screenshot of your failed output and ask "what's wrong?" It is usually far too little information provide more than a guess from me. Please provide screenshots, full stack traces of errors, steps you took to investigate to that point, and even code where the issue is occurring.
• You will find my grading can be very specific to the "requirements" called out in the homework assignments. A critical part of any software engineer's job is to ascertain the requirements of the customer. I see my homework assignments as a customer declaration of what is needed. As a result, I expect you to follow those requirements and will penalize assignments for missing any of them. The role of the software engineer is to interpret those requirements and, if there is any ambiguity in their understanding, reach out to the customer for clarification. In the current situation that means posting any questions to the discussion forum for clarification from me. I am not very tolerant of grading challenges stating, "you never said that in the assignment", or "it was not clearly stated" when the rest of the class had no issue, and you had the opportunity to get clarification prior to turning it in. Of course, if you do feel I made a mistake in grading (which I have been known to do from time to time) on your assignment, you are welcome to raise it with me for correction and I will evaluate it for regrading.
• For those of you who may already have significant experience with Enterprise Web Applications, while you may be able to work through assignments with technologies that are not covered in the class, they are not going to be accepted as grade-able approaches under the guidelines of the class. I expect that your assignments will reflect the material covered in the lectures and satisfy any stated technology requirements or constraints highlighted in the assignment or my announcements or feedback in the discussion forums.

Links to all of the class notes and homework assignments are available in the Canvas modules.  You will see that each week's module is given a time period in which to complete the material (though you should feel free to address it earlier if you would like) and a due date for the homework. For most sections, these dates will begin on Saturday just after midnight and end an 11:59PM on the following Friday. It is during the period defined by those two dates when you are expected to complete the homework and satisfy the discussion posting requirement.

This course will consist of two basic student requirements, Homework and Discussion Forum Participation

Homework - VERY IMPORTANT YOU FOLLOW ALL PARAGRAPHS HERE

There will be a homework for each week's lecture that will be due at 1159PM on the Friday of the week it was assigned. Except for the final week of class homework may be turned in up until the following Tuesday. However, it will incur a 5% penalty PER DAY for each day late according to the following schedule:

Homework will not be accepted after the deadline for the final assignment unless prior arrangements have been made with me. As I said, the reason I start my lecture weeks on Saturday and have Friday deadlines for homework is to facilitate a rapid turnaround of grades for your submissions. In MOST cases, you will have grades and feedback by Sunday evening for submissions turned in the previous Friday. If I had a Sunday deadline, it would be difficult to turn around grades that quickly since I do have a day job. I believe that any disadvantages of a Friday deadline are offset by the benefit of the rapid feedback for assignments and material that follows.

Even though you will be working on your own computer, most homework (but not all) must eventually run on the class server (see Course Resources for where this computer is). One of the reasons I do this is to eliminate the "but it was running on my machine" explanation. If you see it running on the class computer, I'll see it running. Don't forget the important step of testing your submissions on the class computer as there are large penalties for it not running there.

When you upload your assignment to Canvas I expect a zipped package including your ENTIRE project. This facilitates my ability to reproduce and evaluate your code. Please DO NOT just submit your source files and overlook other files. In addition if you use an IDE like Eclipse (class supported) please upload the ENTIRE IDE project. If you don't use an IDE make sure your project is structured and includes any scripts you use to facilitate compilation, deployment, etc. If you fail to provide all necessary files (configuration, etc), even if they are not being graded, it could impact the overall grading of the assignment.

Make sure your submission is zipped (please don't use other compression formats beside zip). Use the following naming convention for your submission:

lastname_firstinit_hw#.zip

So, my submission for homework 5 would be named as follows:

spiegel_r_hw5.zip

Just to be explicit, the format is all lower case, starting with your last name, followed by an underscore, than your first initiial, followed by another underscore, followed by the letters "hw" followed by the assignment number.

If there are other attachments beside your project (aka images, word/openoffice documents) please include them in the zip file at the top (same) level as the project submission. So you should be submitting a SINGLE zip file with ALL of the artifacts (project, readme files, etc) to Canvas.

Although it may seem like this naming convention is nitpicking. It is very straightforward and you WILL be penalized if you fail to follow it. I expect every submission to have the name pattern discussed above. Again, if I was to submit assignment number 3 it would be submitted using the name spiegel_r_hw3. This naming convention is to be applied to the zip file you upload as well as the name of your overall project (if you use and IDE). When we start uploading web applications (aka java war files) I expect that your web application file follows the same convention as well. If not there could be naming conflicts that over-write previously submitted projects.

Discussion Forum    

You will likely find that I put much more thought into my discussion forums that most instructors that you have had. In the past, I have followed the typical forum participation structure that required a fixed number of posts each week to get course credit, and I would give credit to just about anything that was posted to the forum regardless of the quality of content. As you may realize from your own experience, this format is not conducive to learning or even generating interesting conversation. As a result I have spent time developing a forum strategy to not only improve student participation but also make it more beneficial to the student. You will be graded on your contribution in terms of quality and not quantity. Each week there will be 3 points available for the discussion forum. Those three points will be allocated across the week long grading period with one point granted for participation during different time periods to ensure that there are relevant "conversations" throughout the week. Here is a breakdown of each week's schedule and the distribution of discussion credits:

There is also a THIRD (3rd) post (original or response to another) that is required and can occur at anytime during the week's grading cycle. However, at the end of each week's discussion cycle you must have met the minumum three posting requirement with one post in each time period AND you must have a post on at least THREE (3) distinct days during the grading cycle for the week.

I will typically post material to be read for the forums to stimulate open discussion. The topics will attempt to relate the lecture material to real world topics, advances and issues. Beside your initial post each week, you can start conversations or continue others as often as you wish and feel free to post beyond the minimum requirements. Your overall discussion grade at the end of the semester will account for 20% of your overall grade. Additionally, if you find yourself on a borderline between two grades at the end of the semester, one of the factors used to consider moving to the higher grade is your overall forum participation.

Beyond the minimum discussion requirements, each week's discussion area will also be where you should go to post insights and ideas about the lecture material. It should also be the prime place when looking for assistance with issues you have with lectures or assignments. As a participant I will be there to provide feedback but am also interested in what other students might offer as well. Make sure that if you have questions on assignments/material that you post them in the appropriate week's discussion. I prefer to discuss issues there so that the entire class can benefit from the resulting feedback and insights from myself or others. I will typically also offer cited references from the internet for you to review and offer insights on. They may cover advanced technologies in software or just some articles that present more opinion based content on technologies and practices that get you to think and maybe get exposure to "other ways" of thinking as well. My overall goal is to make the discussion forums a part of the class that offers additional knowledge and insight and not just a place for you to meet a requirement for a grade.

As a last point with regard to the forums. I do read them daily and will address homework and lecture questions/issues in the forum within 24 hours (same turnaround as I do for email), but often more quickly. I will also jump in on the topic conversations from time to time, but that is dependent upon how busy I am with other class matters like grading, course maintenance, etc. Regardless of whether you see me post, do know that I DO review the forum material daily (at least).

As a last point with regard to the forums. I do read them daily and will address homework and lecture questions/issues in the forum within 24 hours (same turnaround as I do for email), but often more quickly. I will also jump in on the topic conversations from time to time, but that is dependent upon how busy I am with other class matters like grading, course maintenance, etc. Regardless of whether you see me post, do know that I DO review the forum material daily (at least).

One thing to be aware of. This is an online class and it will be up to you to ensure you have computer access throughout the semester. Having computer problems is not a valid excuse for falling behind in class. It is a very good idea to have some type of backup computer available "just in case".

Grading Policy

Homework

      Final grades are based on the following scale:

Course Evaluation

I welcome feedback (especially constructive criticism) throughout the class.  In addition to providing an additional discussion forum topic to collect that feedback, I also typically use one of the week's discussion topics to collect feedback with regard to the discussion forum structure.  Know that I do read and take the feedback seriously and even if it doesn't impact the current class, it may have an impact on future classes.

Course Policies

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. You may request a paper copy of this policy at this by contacting jhep@jhu.edu.

Regarding Academic standards and this class, students are free to look in any textbook, public WWW page, Usenet Group, or communicate with anybody about any assignment. As in all courses, these sources MUST be cited if you use the code as is. However, if you look at a WWW page, and gain understanding about how to do the problem, and then do it yourself without "cutting and pasting" code from the site, then you do not need to cite the source. You can (and actually are encouraged to) use the online class discussion forum to gain understanding about how to do the problem, but you can't just "get the answer" from the forum and use it.

Copying of code from individuals, whether or not they are or ever have been students in this class, is not allowed without prior permission. If you have a question about how to use a source, ask it via email or the group Discussion forum.

Plagiarism

Plagiarism is defined as taking the words, ideas or thoughts of another and representing them as one's own. If you use the ideas of another, provide a complete citation in the source work; if you use the words of another, present the words in the correct quotation notation (indentation or enclosed in quotation marks, as appropriate) and include a complete citation to the source. See the course text for examples.

Policy on Disability Services

Johns Hopkins University (JHU) is committed to creating a welcoming and inclusive environment for students, faculty, staff and visitors with disabilities. The University does not discriminate on the basis of race, color, sex, religion, sexual orientation, national or ethnic origin, age, disability or veteran status in any student program or activity, or with regard to admission or employment. JHU works to ensure that students, employees and visitors with disabilities have equal access to university programs, facilities, technology and websites.

Under Section 504 of the Rehabilitation Act of 1973, the Americans with Disabilities Act (ADA) of 1990 and the ADA Amendments Act of 2008, a person is considered to have a disability if c (1) he or she has a physical or mental impairment that substantially limits one or more major life activities (such as hearing, seeing, speaking, breathing, performing manual tasks, walking, caring for oneself, learning, or concentrating); (2) has a record of having such an impairment; or (3) is regarded as having such an impairment class. The University provides reasonable and appropriate accommodations to students and employees with disabilities. In most cases, JHU will require documentation of the disability and the need for the specific requested accommodation.

The Disability Services program within the Office of Institutional Equity oversees the coordination of reasonable accommodations for students and employees with disabilities, and serves as the central point of contact for information on physical and programmatic access at the University. More information on this policy may be found at the Disability Services Website or by contacting (410)516-8075.

Disability Services

Johns Hopkins Engineering for Professionals is committed to providing reasonable and appropriate accommodations to students with disabilities.

Students requiring accommodations are encouraged to contact Disability Services at least four weeks before the start of the academic term or as soon as possible. Although requests can be made at any time, students should understand that there may be a delay of up to two weeks for implementation depending on the nature of the accommodations requested.

Requesting Accomodation

New students must submit a Disability Services Graduate Registration Form along with supporting documentation from a qualified diagnostician that:

• Identifies the type of disability
• Describes the current level of functioning in an academic setting
• Lists recommended accommodations

Questions about disability resources and requests for accommodation at Johns Hopkins Engineering for Professionals should be directed to:

EP Disability Services
Phone: 410-516-2036
Fax: 410-516-8049
E-mail: ep-disability-svcs@jhu.edu

Academic Policies

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.