645.632.81 - Applied Analytics for Model Based Systems Engineering

Course Structure

The course materials are divided into modules which can be accessed by clicking Course Modules on the left 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. All modules run for a period of seven (7) days, as noted in the Course Outline.

Course Topics

• Course and Methodology Overview
• Planning the System Modeling Effort
• Stakeholder Needs Analysis
• Functional Architecture and Analysis
• State-Based Behavior Analysis
• Logical Architecture Specification
• Interface Specification and Allocation
• System Requirements Elicitation
• Parametric Analysis and Trade Studies
• Physical Architecture Specification
• System Configurations and Baselines
• Extending the Modeling Language
• Model Verification and Validation
• Reviewing and Assessing the Design

Course Goals

To describe the steps of a widely used methodology for applying model-based systems engineering principles and practices in the context of a typical systems engineering development effort, and then provide hands-on experience using that methodology to create and analyze a system model.

Course Learning Outcomes (CLOs)

• Apply Model-Based Systems Engineering (MBSE) principles and the Systems Modeling Language (SysML) to support the practice of Systems Engineering.
• Employ advanced language and tool features including report generation, model queries and verification, capturing system variations, and parametric analysis.
• Extend the SysML language to allow modeling of concepts specific to a given domain or methodology.
• Customize the Object-Oriented Systems Engineering Methodology (OOSEM) to suit a project’s Systems Engineering needs.
• Create an integrated systems model using a system modeling tool by applying advanced language and tool features.

Textbooks

Delligatti, L. (2014). SysML distilled: A brief guide to the systems modeling language. Upper Saddle River, NJ: Addison-Wesley. ISBN-13: 9780321927869

Friedenthal, S., Moore, A., Steiner, R. (2012). A practical guide to SysML: The systems modeling language. Waltham, MA: Elsevier. ISBN-13: 9780123852069

Textbook information for this course is available online through the appropriate bookstore website: For online courses, search the MBS website.

Required Software

Cameo Enterprise Architecture

You will need access to Cameo Enterprise Architecture version 19.0 from No Magic, Inc. This license is provided at no cost to you, through an Academic License Agreement between JHU and No Magic. Detailed instructions for downloading/installing the software and for requesting a license key from JHU are listed in the file named “645.632.81 Applied Analytics for MBSE – Installing Cameo EA.pdf” in the Help & Support area on the course Blackboard site.

Student Coursework Requirements

It is expected that each module will take approximately 7–10 hours per week to complete. Here is an approximate breakdown: reading the assigned sections of the texts (approximately 1–2 hours per week) as well as some outside reading, listening to the audio annotated slide presentations (approximately 2–3 hours per week), and modeling assignments (approximately 4–5 hours per week).

This course will consist of the following basic student requirements:

Module Discussion (15% of Final Grade Calculation)

You are responsible for carefully reading all assigned material and being prepared for discussion. The majority of readings are from the course texts. Additional reading may be assigned to supplement text readings.

Post your initial response to the discussion questions by the evening of day 5 for that module week. Posting a response to the discussion question is part one of your grade for Module Discussions (i.e., Timeliness).

Part two of your grade for Module Discussion is your interaction (i.e., responding to classmate postings with thoughtful responses) with at least one other classmates (i.e., Critical Thinking). Just posting your response to a discussion question is not sufficient; we want you to interact with your classmates. Be detailed in your postings and in your responses to your classmates' postings. Feel free to agree or disagree with your classmates. Please ensure that your postings are civil and constructive.

I will monitor Module Discussions and will respond to some of the discussions as discussions are posted. In some instances, I will summarize the overall discussions and post the summary for the module.

Evaluation of Module Discussion is based on contribution to discussions. Module Discussion is evaluated by the following grading elements:

1. Timeliness (50%)
2. Critical Thinking (50%)

Preparation and participation is graded as follows:

• 100–90 = A—Timeliness [regularly participates; all required postings; early in discussion; throughout the discussion]; Critical Thinking [rich in content; full of thoughts, insight, and analysis].
• 89–80 = B—Timeliness [frequently participates; all required postings; some not in time for others to read and respond]; Critical Thinking [substantial information; thought, insight, and analysis has taken place].
• 79–70 = C—Timeliness [infrequently participates; all required postings; most at the last minute without allowing for response time]; Critical Thinking [generally competent; information is thin and commonplace].

Assignments (25% of Final Grade Calculation)

Assignments will be exercises involving the creation of model artifacts using the Systems Modeling Language (SysML) and the Cameo Enterprise Architecture modeling tool. These exercises will take the form of updates or additions to an in-class, case study example model. After completing the assigned modeling task, you will submit your model file (*.mdzip file format) to Blackboard. Include your name and assignment identifier in the filename (e.g. “Module 3 Jones.mdzip”).

All assignments are due according to the dates in the Calendar.

Late submissions will be reduced by one letter grade for each week late (no exceptions without prior coordination with the instructors).

If, after submitting an 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.

Assignments are evaluated by the following grading elements:

1. Each part of the modeling task is addressed (40%)
2. Model elements and relationships cover required scope and depth to satisfy task (40%)
3. Model elements are organized in a logical fashion (20%)

• 100–90 = A—All parts of question are addressed; All assumptions are clearly stated; All intermediate derivations and calculations are provided; Answer is technically correct and is clearly indicated; Answer precision and units are appropriate.
• 89–80 = B—All parts of question are addressed; All assumptions are clearly stated; Some intermediate derivations and calculations are provided; Answer is technically correct and is indicated; Answer precision and units are appropriate.
• 79–70=C—Most parts of question are addressed; Assumptions are partially stated; Few intermediate derivations and calculations are provided; Answer is not technically correct but is indicated; Answer precision and units are indicated but inappropriate.
• <70=F—Some parts of the question are addressed; Assumptions are not stated; Intermediate derivations and calculations are not provided; The answer is incorrect or missing; The answer precision and units are inappropriate or missing.

Course Project (60% of Final Grade Calculation)

An individual course project will be assigned during the first week of the course that will be continuously and iteratively designed, modified, and enhanced throughout the semester. Each student will make 4 submissions of project deliverables throughout the semester: a progress submission in Module 4 (5% of Final Grade Calculation), a mid-term submission in Module 7 (15% of Final Grade Calculation), a progress submission in Module 10 (10% of Final Grade Calculation), and a final submission in Module 14 (30% of Final Grade Calculation). For all 4 submissions, each student will submit a single system model that they have progressively enhanced with each submission. In addition, for the mid-term and final submission, each student will record a video screen capture of themselves navigating through the model and highlighting key elements of the design.

The video recording must be submitted with the model and must be no longer than 15 minutes in length.

Details on the Course Project submission requirements, expectations, and grading rubric can be found in the Course Project document on your Blackboard course site.

Grading Policy

Online Discussion Posts, Assignments, and Course Project Submissions are due according to the dates posted in your Blackboard course site and the Course Outline. You may check these due dates in the Course Calendar or the Assignments in the corresponding modules. I 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.

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

97-94 = A

93-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

Final grades will be determined by the following weighting:

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.