675.754.81 - Flight Software for Space Systems

Expanded Course Description

Some familiarity with the C programming language is presumed for this course, as there exist several programming assignments that must be completed in the C language and run in a Linux environment. 

Course Structure

The course materials are divided into modules which can be accessed by clicking Modules on the 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.

Course Topics

• Skills Review
• Embedded Systems Components
• Real-Time Operating Systems
• Embedded Software Requirements, Architecture, and Design
• Application Frameworks
• Flight Systems Data Communications
• Memory Handling
• Inter-Process Communications
• Scheduling and Multi-Tasking
• Command and Data Handling
• Telemetry Production and Spacecraft Interfaces
• Autonomy and Fault Management
• Software Unit Testing

Course Goals

The goal of this course is to describe the activities of requirements analysis, design, implementation, and testing of spacecraft flight software systems. 

Course Learning Outcomes (CLOs)

• Explain the function and interconnectedness of the logical components of a spacecraft Command and Data Handling (CDH) system.
• Examine the principles of flight software engineering, (including the importance of safety, reliability, and efficiency) in designing and implementing flight software.
• Explain the challenges of developing and maintaining flight software, such as real-time performance, hardware constraints, and changing requirements.
• Operate an open-source flight software system.
• Demonstrate critical thinking skills in analyzing and solving complex problems related to flight software engineering, including debugging and testing.
• Evaluate flight software requirement specifications, architectural designs, and verification activities for completeness and correctness.
• Create implementations (in the C programming language) of important algorithms and concepts and debug those implementations with common Linux development tools.

Textbooks

This course does not have a required textbook. Required readings are included in the course modules and other resources on Canvas.

Student Coursework Requirements

It is expected that each module will take approximately 9 - 13 hours per week to complete, as follows.

• Reading assigned sections of texts/materials (0 - 2 hours per week)
• Listening to the audio annotated slide presentations (4 hours per week)
• Completing weekly knowledge checks (1 hour per week)
  
• Completing module assignments (4-6 hours per week)

All knowledge checks and assignments are due according to the dates in the Calendar. Late submissions will be reduced by one letter grade for each week late. If, after submitting an assignment (programming, lab, or analysis) you are not satisfied with the grade received, you may resubmit the assignment for the opportunity to receive up to half of the missing credit back. Knowledge checks cannot be retaken. 

This course will consist of the following basic student requirements:

Knowledge Checks (30% of Final Grade Calculation)

Knowledge checks are graded quizzes at the end of each module used to assess the understanding of the materials and show preparedness for the assignments and project activities based on the module.

Programming Assignments (30% of Final Grade Calculation)

Lab Assignments (10% of Final Grade Calculation)

Analysis Assignments (30% of Final Grade Calculation)

The rubric for grading each assignment will be included in each assignment document.

Course Discussions (5% of Extra Credit)

Each module defines a qualitative question that is meant to be answered/discussed in the context of the discussion forum defined for that module. The nature of these questions is to stimulate thinking about difficult problems as they relate to the design/development of spacecraft flight software.  In that sense, the answers are not graded in terms of  “correct/incorrect”, but rather as  “consistent/inconsistent with the presented material” and “defended/undefended in their points of view”.

Module discussion answers (and student responses) are typically due at the end of the module week, unless otherwise notes in the Course Outline, Course Announcements, or other course communications during the semester.

Each discussion module will be worth 5 points and graded in accordance with the following rubric:

• Answer consistent with presented material: +2 points
• Answer defended (e.g. with examples, explanations): +3 points

Grading Policy

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 will attempt to post grades within two weeks after assignment due dates.

I generally do not directly grade spelling and grammar. However, egregious violations of the rules of the English language that impede my understanding of your work may result in a grade deduction. 

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.

EP uses a +/- grading system (see “Grading System”, Graduate Programs catalog, p. 10).

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.