645.764.81 - Software Systems Engineering

Course Structure

The Course week is structured from Tuesday through Monday, and assignments/tests are due just before midnight Eastern Time on Monday evenings.

Each week has a separate module of instructional materials, including readings, videos, and discussions.

Course Topics

• Programming (Develop - Implement)
• Design and System Modeling (Develop - Design)
• Software Requirements (Specify)
• Software Testing, Verification and Validation (V&V)
• Software Processes
• Agile Development
• Software Planning and Business Process
• Dependability and Nonfunctional Requirements
• Software Reuse and Components
• Networking and Distributed Systems
• Service Oriented Architecture (SOA), Embedded Systems, and Configuration Management
• Configuration Management

Course Goals

To identify and describe the roles and responsibilities of Software Systems Engineers, and then apply that knowledge to analyze and solve software systems engineering problems, including a semester-long use of discussion forums. Discussion forums will highlight certain topics relevant to software systems engineering not covered in the text.

Course Learning Outcomes (CLOs)

• Describe how software development (programming) must be combined with higher-level concepts (Software Systems Engineering) to yield successful software development efforts.
• Identify and utilize the steps in the software engineering process to develop a software intensive system.
• Critique and optimize the software systems process and activities for a project.
• Explain and apply modern software technologies to systems engineering efforts involving software systems.

Textbooks

Sommerville, Ian, Software Engineering, 10th ed. New York: Addison Wesley, 2015.

Textbook information for this course is available online through the appropriate bookstore website: For online courses, search the MBS website at http://bookstore.mbsdirect.net/jhu-ep.htm.

Required Software

Canvas

For Canvas system requirements, please go here: 

Web Browser Plugins

You will need the Adobe Flash Player plugin to view videos in this course. Go to http://get.adobe.com/flashplayer/.

PDF Viewer

You will need the free Adobe PDF viewer software to view PDF files in this course. Go to http://www.adobe.com/products/acrobat/readstep.html.

Other Software

You will need access to word processing and spreadsheet applications. Microsoft Office will, of course, work—however, an open source alternative is OpenOffice.org. http://download.openoffice.org/other.html#en-US.

Zoom

You will be using Zoom, a web-based conferencing system, to participate in classes you cannot attend in person, and also to replay class recordings.

To use Zoom, please perform a connection test on your computer to make sure your software is current by going to https://zoom.us/test and selecting Connection Test. If you have any trouble connecting to a Zoom meeting, please contact the JHU EP Online Help Desk (see below).

Python Development Environment

The Python 3 programming language is used for several examples, exercises, and homework assignments. Module 0 describes the software requirements in order to participate in these activities.

Student Coursework Requirements

It is expected that the class will take approximately 7–9 hours per week: reading the assigned sections of the texts (approximately 2–3 hours per week) as well as some outside reading, listening to the audio recordings of lecture presentations (approximately 3 hours per week), and writing homework assignments (approximately 1–2 hours per week).

This course will consist of four basic student requirements:

Homework Assignments (40% of Final Grade Calculation)

Text reading assignments will be important sources of material for your homework assignments, as well as for exams and the discussion forum assignments.

In preparing your written homework assignments, please put the class assignment number and your name on each assignment, even though it will also be submitted electronically. Written homework assignments have several questions are 1 to 2 pages in length (12-point font). The question should be repeated, in full, before answering the question. The purpose of the homework assignments is to give the students the opportunity to demonstrate their understanding of the course concepts.

All homework assignments are due according to the dates in the Schedule and Assignments tools.

There will be a total of five assignments. The first assignment will not be graded, but each of the remaining four assignments will be worth 10% of the final grade. All assignments will be either essay questions, or exercises involving software/ software systems engineering technologies.

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

Written work is expected to be clear and understandable, although points are not usually deducted for minor grammar or spelling mistakes.

Writing more does not necessarily result in a better grade.

All work submitted must be your own individual work. All sources must be cited.

Writing assignments are evaluated by the following grading elements:

1. Each part of question is answered (25%)
2. Writing clarity and technical accuracy (30%) (Writing is expected to 
meet or exceed accepted graduate-level English and scholarship standards).
3. Rationale for answer is provided (25%)
4. Examples are included to illustrate rationale (20%) (If a student 
does not have direct experience related to a particular question, then the student is to provide analogies versus examples).

Homework is graded in accordance with the Systems Engineering program’s standard grading schema.

Discussion Forum Assignments (15% of Final Grade Calculation)

Each student is responsible for carefully reading all assigned material and being prepared for discussion. The majority of readings are from the course text. Additional reading may be assigned to supplement text readings. Post your response to the questions, using the "Post New Thread" button, by Saturday evening of that week. Posting a response to the discussion question is part one of your grade for class 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 two 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. The references listed in the annotated bibliography in the course text present supporting or contrasting views of concepts discussed in the text. In some cases, these references present a detailed discussion of topics not treated in depth or only touched upon in the course text. The annotated bibliography also provides web sites that can provide additional information on topics covered in the course. Each student is encouraged to exploit these resources in preparing for discussions and in his/her homework. Please see the following links:

IEEE Computer Society - http://www2.computer.org/portal/web/guest/home.

Association for Computing Machinery (ACM) - http://www.acm.org/.

Software Engineering Institute (SEI) - http://www.sei.cmu.edu/.

Software Technology Support Center (STSC) - http://www.stsc.hill.af.mil/index.html.

Evaluation of preparation and participation is based on contribution to discussions.

Preparation and participation is evaluated by the following grading elements:

1. Initial Posting, thoughtful answer to the question, 6 points.
2. Interaction, reflective comments on other student's answers, two are graded, 2 points each.

Exams (40% of Final Grade Calculation: 20% Mid-Term + 20% Final)

The Mid-Term Exam will emphasize information introduced in all class sessions before the Mid-Term Exam date, and the Final Exam will emphasize information introduced in sessions between the Mid-Term Exam date and the end of the course. The Mid-Term and Final Exams will be available according to the dates in the Schedule and Assignments tools. The exams will be a take-home exam. Students will use their notes, lecture slides, and text to provide the ‘foundation’ to every exam answer. Only then can supplemental information for each answer be included from external sources (e.g., WWW, personal experience, etc.). The Canvas Assignment system and/or email will be used to submit the exams, as well as all Homeworks and Forums.

The exams are evaluated by the following grading elements:

1. Each part of question is answered (20%)
2. Writing clarity and technical accuracy (30%) (Writing is expected to 
meet or exceed accepted graduate-level English and scholarship standards).
3. Rationale for answer is provided (25%)
4. Examples are included to illustrate rationale (25%) (If a student 
does not have direct experience related to a particular question, then the student is to provide analogies versus examples).

Exams are graded in accordance with the Systems Engineering program’s standard grading schema.

Self-check quizzes (5% of Final Grade Calculation)

Each student is responsible for carefully reading all assigned material and being prepared for the weekly self-check quizzes. These multiple-choice quizzes are available on Canvas with the release of each module. The content of the quiz is exclusively on the topic of the associated module. The self-check quizzes are evaluated by the following grading elements:

1. The correct answer to the multiple-choice question (100%) 
   

Grading Policy

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.