Fundamental software engineering techniques and methodologies commonly used during software development are studied. Topics include various life cycle models, project planning and estimation, requirements analysis, program design, construction, testing, maintenance and implementation, software measurement, and software quality. Emphasized are structured and object-oriented analysis and design techniques, use of process and data models, modular principles of software design, and a systematic approach to testing and debugging. The importance of problem specification, programming style, periodic reviews, documentation, thorough testing, and ease of maintenance are covered. Course Note(s): The required foundation courses may be taken in any order but must be taken before other courses in the degree.
The course materials are divided into sections on requirements development, design and umbrella processes. Each section consists of a sequence of lectures on various topics accompanied by an in-class exercise and a graded assignment. Assignments require individual and group contributions.
The purpose of this course is to introduce students to the engineering processes that accompany the development of software, including requirements analysis, software modeling, architecture and design.
Pressman, R. (2014). Software Engineering: A Practitioner’s Approach. McGraw-Hill Education
ISBN 978-0078022128.
Textbook information for this course is available online through the appropriate bookstore website: For online courses, search the MBS website at http://ep.jhu.edu/bookstore.
It is expected that each week’s preparation will take approximately 7–10 hours per week to complete. Here is an approximate breakdown: reading the assigned sections of the text (approximately 2-3 hours per week), participation in class lectures exercises (approximately 2.5 hour per week), and implementing assignments (approximately 3-5 hours per week).
This course will consist of three basic student requirements:
You are responsible for carefully reading all assigned material and being prepared for participation in class exercises following introductory lectures. The readings are from the course text.
Assignments generally require the production of appropriate software engineering artifacts similar to the in-class exercises.
All assignments are due according to the dates in the Calendar.
Late submissions will be reduced by 10% 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, however resubmitted assignments will be treated as late per the preceding paragraph.
A midterm exam will be conducted during the second half of the sixth class of the semester. A final exam will be conducted during the final class occupying the entire period. The final exam covers material from the entire course with a greater emphasis on the content of the second half of the course. Both exams are multiple choice, and most questions have multi-part answers. That is, you must select all of the correct answers, and a question may have 0 through 5 correct answers. Each exam includes one short-answer or design question.
The completed requirements documents from assignment 4 will be distributed to all of the teams, and during class 7 we will conduct a formal technical review of each team’s document. The review will not contribute to the grade for the document, instead the review participation and written comments are graded themselves.
Assignments are due according to the dates posted in the Canvas course site. You may check these due dates in the Course Calendar or the Assignments. I will post grades within one week after assignment due dates.
I generally do not directly grade spelling and grammar. However, egregious violations of the rules of the English language will be noted without comment. Use of grammar or spelling that makes understanding of the work difficult or impossible will affect the 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.
Score Range | Letter Grade |
---|---|
100-98 | = A+ |
97-94 | = A |
93-90 | = A− |
89-87 | = B+ |
86-83 | = B |
82-80 | = B− |
79-70 | = C |
<70 | = F |
Final grades will be determined by the following weighting:
Item | % of Grade |
Assignments | 60% |
Formal Technical Review | 5% |
Mid-term Exam | 15% |
Final Exam | 20% |
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.