The development of large, complex, software-intensive hardware systems has become extremely challenging for systems engineers. Some examples are virtually all modern military systems, commercial automotive and aeronautical industries, even medical devices, each containing an extensive set of interconnected, software-driven electrical and mechanical components and are digitally connected to the outside world. This course will show you how to effectively lead teams capable of addressing this complexity using deliberate, incremental learning intervals throughout the system’s development and improvement lifecycles. You will explore how to successfully lead your team in executing these learning intervals using Agile methods, modular hardware and software architectures, integrated descriptive and analytic modeling, Lean and Design Thinking all integrated with the foundational principles of systems engineering. This course will show you how the increasingly ubiquitous, cross-industry digital transformation supports these learning intervals using Digital Threads, Digital Twins and development pipelines called DEVSECOPS. All of the lectures in this course are available asynchronously as recorded videos along with a textbook and other learning material.
The course materials are divided into modules. The modules can be accessed by clicking Course Modules on the left menu in your course Canvas site. A module will have several sections including the overview, content, readings, a short quiz, and assignments. Please preview all sections of the module before starting. All modules run for a period of seven (7) days beginning on Tuesday and ending at midnight on Monday. You should regularly check the Announcements for emerging information.
All assignments are graded and released in the Grade Center and notifications of grade release and/or grade distribution are sent to the email address that appears in the course roster. As assignment grades are posted, they are automatically added to the gradebook.
The Announcements tool will be used for important bulletins, grade distributions, reminders, and assignment clarifications and, again, are sent to the email address that appears in the course roster.
To identify and describe the characteristics and responsibilities of a systems engineer engaged with a project using Agile Methods, and then apply that knowledge to create a set of systems-engineering-specific recommendations to the corporate CEO of a fictitious company in a semester-long simulation.
This course will use:
as the primary textbook, supplemented with reprints of relevant articles, papers, selected textbook chapters and videos.
All additional course readings are available directly through the Canvas course site as eReserves or are provided as pdfs.
Webcam and microphone are required (if provided with computer, this is usually sufficient along with adequate lighting and no background sound interference). Word, PowerPoint, no pdfs.
It is expected that each module will take approximately 10-13 hours per week to complete. Here is an approximate breakdown: complete the assigned readings and watch/listen to video lectures and other posted videos (4-5 hours /week); work with teammates and individually on assignments, essays, and presentations (3-5 hours/week); attend Zoom live events (~bi-weekly) -- to present findings and analysis for deliverables listed below (2-3 hours/week).
All assignments are released and due on Eastern Time. All homework assignments are submitted electronically via the Assignments section of the module in which they are due. A comprehensive list of assignments is provided in the Course Outline.
Homework is expected to be turned in as indicated in the Assignment section of each module; it will be categorized as late if it is received after that time. Unexcused late submissions will be reduced by 10 percentage points for each day they are submitted late. After a week, if the student hasn't contacted the instructor to develop a suitable course of action, these homework assignments will receive a zero score. Please coordinate with the instructor as early as possible so that a reasonable course of action can be determined. Special circumstances (e.g., temporary lack of Internet access, extended illness of several days, etc.) can be cheerfully accommodated if you inform us in advance.
We remain baffled at how often students will not notify us of some problem at work or at home until after the deadline – this is too late for you to not be penalized. If you show the courtesy of contacting us prior to the deadline, at least we can discuss what might be possible.
Team Action Assignment (TAA) and Team Presentation (TP) MS Teams recordings
Both TAAs and TPs are pre-recorded homework (i.e., average length ~60 minutes) submitted at the end of the module.
Individual Essay Assignments
Approximately every 2 weeks each student will submit an essay averaging 1200 words in length. We generally do not directly grade spelling and grammar. However, you are in a graduate course: we expect you to be able to construct written communication appropriate for this level of education. We particularly abhor colloquial, sloppy language that does not comport with the quality of education you should expect from The Johns Hopkins University – such performance will detract from your grade. Although there are several great sources to help you write better, here is one for your consideration: https://owl.english.purdue.edu/owl/.
Essay assignments will involve critical thinking problems, case study analysis, hypotheticals, and so on. For individual submitted assignments, please include a cover sheet with your name and assignment identifier. For submitted team assignments please include a cover sheet with the names of each group member and assignment identifier. Each submitted assignment should also include a page number indicator (i.e., page x of y) on each page of your submissions. All assignments are due by the end of the module (e.g., Monday night) they are assigned in. We will provide feedback on assignments within one week after the assignment due date – We will strive to provide you feedback earlier if possible.
We encourage you to consider the following elements for each of your assignments:
In preparing your homework, please put the name of the assignment, along with your name, in the document filename. We make use of Canvas' capability to do a batch download of the assignments - they lose their association with you without having your name on the assignment and submitted file. For example, for the Essay #1 we might create the filename bob_cameron_esssay_1.doc if Dr. Bob were a student. Please submit all assignments either in Microsoft Word or PowerPoint not Adobe pdfs.
The first of two team presentations is assigned in Module 2 and presented in Module 5 while the second one is assigned in Module 5 and presented in Module 14. We will ask to see what you have accomplished so far during Module 9.
The team presentation will be graded according to the rubric provided within the applicable module.
Implemented on alternating weeks with the team action assignments, this assessment will consist of five ~bi-weekly written assignments in which you will have a challenge question to address.
These written assignments will be graded according to the rubric that is available on the Syllabus & Course Information page in Canvas.
Score Range | Letter Grade |
---|---|
100-97 | = A+ |
96-93 | = A |
92-90 | = A− |
89-87 | = B+ |
86-83 | = B |
82-80 | = B− |
79-77 | = C+ |
76-73 | = C |
72-70 | = C− |
69-67 | = D+ |
66-63 | = D |
<63 | = F |
Assignments are due according to the dates posted in your Canvas course site. You may check these due dates in the Course Calendar or the Assignments in the corresponding modules. I/We will post grades one week after assignment due dates.
We generally do not directly grade spelling and grammar. However, egregious violations of the rules of the English language will be noted without comment. Consistently poor performance in either spelling or grammar is taken as an indication of poor written communication ability that may detract from your grade.
A grade of A+ indicates achievement of consistent excellence and distinction throughout the course—that is, conspicuous excellence in all aspects of assignments and discussion in every week.
A grade of B indicates work that meets all course requirements on a level appropriate for graduate academic work. These criteria apply to both undergraduates and graduate students taking the course.
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.