Home
Research profile
Teaching profile
Professional profile
Personal profile
Contact information

Course title

EECS448: Software Engineering -- Fall 2022 (10794)
Tuesdays and Thursdays, 2:30 pm - 3:45 pm, Eaton 2
Teaching website: people.eecs.ku.edu/~saiedian/Teaching

Labs

M 01:00 - 02:50 PM EATN 1005C
Tu 09:00 - 10:50 AM EATN 1005C
W 09:00 - 10:50 AM EATN 1005C
W 02:00 - 03:50 PM EATN 1005A
Th 09:00 - 10:50 AM EATN 1005C
Th 12:00 - 01:50 PM EATN 1005A
F 02:00 - 03:50 PM EATN 1005C

Instructor

Professor Hossein Saiedian
Office: Eaton Hall 3012
Telephone: 785-864-8812
E-Mail: saiedian AT ku.edu
WWW: people.eecs.ku.edu/~saiedian
Office Hours: Tuesdays and Thursdays, 1:00-2:00 PM (and by appointment)

Teaching assistants

Arnab Mukherjee (arnabmukherjee91 AT ku.edu)
Anjali Pare (anjali.pare AT ku.edu)
Liangqin Ren (liangqinren AT ku.edu)

Course description

This course is an introduction to software engineering, and it covers the systematic development of software products. It outlines the scope of software engineering, including life-cycle models, software process, teams, tools, testing, planning, and estimating. It concentrates on requirements, analysis, design, implementation, and maintenance of software products. The laboratory covers CASE tools, configuration control tools, UML diagrams, integrated development environments, and project specific components. Prerequisite: EECS 268 and upper-level EECS eligibility.

Course outcomes

The course outcomes are as follows:

  1. Understand software engineering in terms of requirements, design, and implementation.
  2. Work effectively in a team and deliver a software product (includes a demo and presentations).
  3. Produce a software design based on requirements, a software prototype to explore a particular design, and conduct coherent testing and documentation.
  4. Learn and practice software testing including unit testing, and acceptance testing.
  5. Learn and use version control.

Textbooks

The first textbook is a required textbook and other textbooks are excellent references.

Ian Sommerville
Engineering Software Products: An Introduction to Modern Software Engineering,
Pearson, 2020.
Martin Fowler
UML Distilled: A Brief Guide to the Standard Object Modeling Language
3rd edition, Pearson, 2004.
Roger Pressman and Bruce Maxim
Software Engineering: A Practitioner's Approach
9th edition, McGraw-Hill, 2020.
Ian Sommerville
Software Engineering
10th edition, Pearson, 2016.

Students are responsible for lecture notes, reading assignments, as well as items distributed during the classroom sessions. Important reading materials as well as lecture slides will be placed on the class website.

Lecture notes

Readings

Project resources

Evaluation criteria (subject to revision)

Students will be evaluated as follows:

Exams and quizzes: 50%
Term project: 30%
Homework labs: 20%

Grading scale:
A = 90%..100%
B = 80%..89%
C = 70%..79%
D = 60%..69%

Exams and quizzes will be closed book and notes and on Canvas. Always bring a device that allows you to connect to Canvas and take the exam or quiz. No other devices is to be used other than the device used for connecting to Canvas. No other app other than Canvas should be used.

  • On exams, quizzes, and homework: Avoid a single paragraph response for a question that has multiple parts. If a question says "name three parts of ..." then give three paragraphs, one for each part to prevent ambiguous or intertwining responses. Better yet, start each paragraph as (1), (2), (3). If you provide more than three parts, only the first three will be graded.

  • On exams, quizzes, and homework: Give responses that were discussed and presented in class and are in lecture notes. We are not interested in Wikipedia or similar responses; we will be rewarding students who attend class, take notes, and study their own notes.

  • On exams, quizzes, and homework: Your response will have to be precise and complete and technical. Avoid vague and incomplete responses. We have to make sure you understood the concepts to give full credit. An answer that's basically correct but perhaps vague or incomplete or an answer that has something to do with a correct answer but is not precise or is somehow off the mark will not receive full credit. One way that I judge a good answer: if someone did not know the answer, could they read what you wrote and then understand the answer?

  • No make-up quizzes are given. No late work will be accepted. Certain exceptions may be made for family emergencies, religious observance, and illnesses.

All written work must be typeset and submitted on Canvas.

Term project. The term project will be team-based (teams of 4-6 individuals). The team project requirements will be discussed in-depth in class. The student teams will have to decide what computing platform and programming language to choose. The TAs will provide direction and support for the project artifacts or labs but are not expected to be expert on programming, programming languages, or computing platforms. Project code should be maintained on GitHub.

Technical problems. If you experience technical problems with your EECS account or the EECS servers or the lab equipment, please submit a support request help at: https://tsc.ku.edu/request-support-engineering-tsc.

Attendance. Attendance is important and required. Throughout the semester, attendance may randomly be taken; three absences or three zeros on lab assignments will result in a failing grade for the course. Furthermore, if a student misses a class session, he or she will be entirely responsible for learning the materials missed without the benefit of a private lecture on the instructor's part. Furthermore, the student will be responsible for finding out what assignments may have been given and when they are due, any updates to the project, schedule or the course syllabus.

Tentative weekly schedule (review for updates)

Overview of the course
Striving for Successful Team (Intro to Git and GitHub)
Software Life Cycle

All lecture notes (slides) are on Canvas

Software Development Models
Chapter 1: Sofftware Products
Chapter 2: Agile Software Engineering
Agile Software Development

Lab 1: Git and GitHub [Check out Github's education pack]

All lecture notes (slides) are on Canvas

Agile Development (lecture notes)
Chapter 2: Agile Software Engineering
Minimal Product (Project) Management
Domain Engineering
Requirements Engineering

Project part 1: Team profiles

All lecture notes (slides) are on Canvas

Why Modeling
Modeling with UML
UML Use Case Modeling
Chapter 3: Features, Scenarios, and Stories

Project: Vision statement

All lecture notes (slides) are on Canvas

UML class modeling
UML state transition modeling (will be covered at later time)
Thursday September 22: Exam 1

Lab: Use case modeling

All lecture notes (slides) are on Canvas

More on UML class modeling
From requirements to design: architectural selection

All lecture notes (slides) are on Canvas

Chapter 4: Software Architecture

Tuesday October 11: No class (last day of fall break)

The SDLC revisited: The Unified Process
UML diagrams for software design

All lecture notes (slides) are on Canvas

Detailed-design concepts: Modular design, object-oriented design, design patterns

Thursday October 20: Exam 2

All lecture notes (slides) are on Canvas

Detailed-design concepts: Modular design, object-oriented design, design patterns

Concepts related to writing programs (documentation, self-describing programs, coding conventions, pre- and post-conditions, interpreters vs compiled programs, the compilation process, "make" and "git")

All lecture notes (slides) are on Canvas

Chapter 5. Cloud-based Software
Chapter 6. Microservices Architecture

All lecture notes (slides) are on Canvas

Software quality assurance
Chapter 9. Software Testing
Testing coverage criteria
Black box test case generation techniques

All lecture notes (slides) are on Canvas

White box test case generation techniques (continued)
Chapter 9. Software Testing

All lecture notes (slides) are on Canvas

Examples of code-based testing

Thursday November 24: No class (Thanksgiving break)

All lecture notes (slides) are on Canvas

Chapter 8. Reliable Programming
Chapter 7. Security and Privacy

All lecture notes (slides) are on Canvas

UML revisited: modeling behavioral properties
Chapter 10. DevOp and Code Management
Emerging trends in software engineering

All lecture notes (slides) are on Canvas

Comprehensive final December 14 1:30-4:00 pm

Attendance, late work, and makeup policies

Attendance expectation. Regular attendance is essential for success in this course and its lab components. Attendance will be be recorded throughout the semester via iClicker. Three or more unexcused absences will result in a one-letter grade reduction in the final course grade, reflected when grades are posted at the end of the term.

Excused absence requests. Requests for excused absences must be submitted in advance and approved by the instructor, except in cases of emergency. For emergencies, notify the instructor as soon as possible following the absence. Supporting documentation must be included with the request. Examples of excusable absences are listed below.

Responsibility for missed work. Students who miss class without a valid excuse are responsible for obtaining missed materials. The instructor or the TAs will not provide individual makeup lectures or one-on-one instruction. It is the student's responsibility to stay informed about course content and course updates.

Late-work, makeup policy. Late work will not be accepted under any circumstances. Make-up options for labs, quizzes, and exams are unavailable except in cases of excused and verified absences. Exceptions will be made for excusable absences.

Timing of make-up assessments. Make-up quizzes and exams for excused absences must be completed before the class session in which the quiz or exam content will be reviewed or its answer key released. Make-up labs must be completed within one week of the excused absence.

Make-up assessment integrity statement. ff granted permission to take a quiz or exam at a later time due to an officially excused absence, the student must affirm the following: “I acknowledge that I have been granted the opportunity to complete this assessment as a result of an officially excused absence from its original administration. I hereby affirm—without reservation—that I have not sought, received, or accessed any information regarding the content, structure, or subject matter of this quiz or exam from any individual who previously completed it. This includes, but is not limited to, verbal conversations, written notes, online discussions, messaging apps, shared files, or any other form of communication. I understand that violating this pledge constitutes academic misconduct and will result in immediate disciplinary action, including a failing grade on the assessment and referral to the School of Engineering disciplinary committees.”

Common policies

Technical problems. If you experience technical problems with your EECS account or the EECS servers or the lab equipment, please submit a support request help at: https://tsc.ku.edu/request-support-engineering-tsc.

Inside classroom policy. Students are expected to come to the class on time, be attentive and engaged, conduct themselves professionally, and avoid anything that could cause a distraction or detrimental either for other students learning or for the instructor's presentations. Profanity and swearing is not allowed.

Students are expected to actively participate in all classroom presentations and discussions, ask questions, and regularly make contributions such as offering comments, responding with good answers, and providing feedback.

Canvas announcements. Announcements is a Canvas tool to post important information and updates to all members of a course. It is your responsibility to regularly check your Canvas account for such announcements (students may also receive an email notification when a new announcement is posted).

Email communications E-mail communication is fast, flexible, and effective. You have an @ku.edu email account and you are expected to regularly check it. Important information may also be communicated via email.

You are a student registered in a course offered by the School of Engineering at the University of Kansas, a top regional and a nationally ranked institution. Your communications, especially written communications (composition, grammar, spelling, punctuation, etc), should reflect that status. Please follow these email guidelines and etiquettes.

Send text-only emails in text-only format. All classroom assignments, labs, or projects should be typeset and submitted on Canvas. Other documents (e.g., documents for an excusable absence) shoud be emailed in PDF or a well-known image format (e.g., JPG or PNG). See the Guidelines for submitting electronic documents.

Grade and absence clarification or correction. If you believe your grades on an assignment, lab, quiz, or exam are incorrect, you should formally submit a grade appeal via email to the instructor within one week of receiving the graded work. Similarly, if you have an excusable absence, and you did not provide documentation prior to the absence, submit relevant documentation within one week of the absence. Failure to address concerns within these timeframes will result in the decision becoming final. This timeline ensures timely resolution and fairness for all parties involved.

Cell phone policy. Cell phones should be turned off before coming to the classroom. Cell phone use for the purposes of texting, email or other social media should be avoided. Earphones for music are OK during lab work or individualized problem solving, as long as the volume allows you to hear announcements. Also cell phone or other cameras may be used to photograph projects and the whiteboard but avoid shots that include the presenter or other students.

Laptop/electronic device policy. The use of laptops, tablets or similar devices is common for taking notes but turn off audio and avoid any possible uses that could cause distraction for others (e.g., Web surfing or social media visits).

Incomplete grade policy. "Incomplete (I) grades are used to note, temporarily, that students have been unable to complete a portion of the required course work during that semester due to circumstances beyond their control. Incomplete work must be completed and assigned an A-F or S/U grade within the time period prescribed by the course instructor. After one calendar year from the original grade due date, an Incomplete (I) grade will automatically convert to a grade of F or U, or the lapsed grade assigned by the course instructor."

Also please review change of grade policy here and here.

Accommodations for students with disabilities. The University of Kansas is committed to providing equal opportunity for participation in all programs, services and activities. Requests for special accommodations may be made thru the KU Student Access Services.

The Provost's freedom of expression statement . "Our IRISE values will guide us and our students as we all engage with each other in respectful freedom of expression.

In a setting as diverse as KU, we will inevitably encounter ideas, opinions and philosophies that are different than our own and which some personally find uncomfortable or offensive. To be clear, threats, incitement of violence and targeted harassment are not protected speech under the First Amendment. Offensive speech, although it can be painful, is generally considered protected speech. We need to strongly encourage and facilitate civil and respectful discussion and interaction. We simply must not inhibit or penalize expression protected by the First Amendment."

KU's diversity policy statement. "As a premier international research university, the University of Kansas is committed to an open, diverse and inclusive learning and working environment that nurtures the growth and development of all. KU holds steadfast in the belief that an array of values, interests, experiences, and intellectual and cultural viewpoints enrich learning and our workplace. The promotion of and support for a diverse and inclusive community of mutual respect require the engagement of the entire university..."

Please also see: KU's statement on diversity and inclusion.

KU's nondiscrimination, equal opportunity. "The University of Kansas prohibits discrimination on the basis of race, color, ethnicity, religion, sex, national origin, age, ancestry, disability, status as a veteran, sexual orientation, marital status, parental status, gender identity, gender expression, and genetic information in the University's programs and activities."

Please also see: KU's statement on nondiscrimination and on racial and ethnic harassment policy.

KU's sexual harassment policy. "The University of Kansas prohibits sexual harassment and is committed to preventing, correcting, and disciplining incidents of unlawful harassment, including sexual harassment and sexual assault."

Please also see KU's statement on sexual harassment.

KU's mandatory reporter statement. "The University of Kansas has decided that all employees, with few exceptions, are responsible employees or mandatory reporters who must report incidents of discrimination, harassment, and sexual violence that they learn of in their employment at KU to the Office of Civil Rights and Title IX. This includes faculty members. As such, if you share information about discrimination, harassment, or sexual violence with me, I will have to relay that information to the Office of Civil Rights and Title IX. I truly value your trust in me to share that information and I want to be upfront about my requirement as a mandatory reporter. If you are interested in contacting KU’s confidential resources (those who do not have to make disclosures to OCRTIX), there are: the Care Coordinator, Melissa Foree; CAPS therapists; Watkins Health Care Providers; and the Ombuds Office."

Please see KU's statement on mandatory reporting.

KU's commercial note-taking ventures. "Pursuant to the University of Kansas’ Policy on Commercial Note-Taking Ventures, commercial note-taking is not permitted in this course. Lecture notes and course materials may be taken for personal use, for the purpose of mastering the course material, and may not be sold to any person or entity in any form. Any student engaged in or contributing to the commercial exchange of notes or course materials will be subject to discipline, including academic misconduct charges, in accordance with University policy. Please note: note-taking provided by a student volunteer for a student with a disability, as a reasonable accommodation under the ADA, is not the same as commercial note-taking and is not covered under this policy."

Please see KU's statement on commercial note-taking.

Concealed handguns. "Individuals who choose to carry concealed handguns are solely responsible to do so in a safe and secure manner in strict conformity with state and federal laws and KU weapons policy. Safety measures outlined in the KU weapons policy specify that a concealed handgun:

  • Must be under the constant control of the carrier.
  • Must be out of view, concealed either on the body of the carrier, or backpack, purse, or bag that remains under the carriers custody and control.
  • Must be in a holster that covers the trigger area and secures any external hammer in an un-cocked position.
  • Must have the safety on, and have no round in the chamber."

LLM and generative AI tools

Generative AI tools—such as ChatGPT, GitHub Copilot, Gemini , and others—can be valuable resources for learning. When used appropriately, they may assist in brainstorming, exploring ideas, and refining drafts. However, they must never replace your own intellectual work.

These tools are akin to the writing center consultants, the EECS programming tutors, and lab assistants: they can guide and support but must not generate final submissions. Submitting content primarily generated by AI is a violation of academic integrity, comparable to submitting work completed by someone else.

Unless explicitly permitted, all coursework must reflect your original understanding, reasoning, and expression. If you use AI tools at any stage of an assignment, you are required to disclose that use via a brief reflection, which must include:

  • A description of how and why AI was used
  • The specific prompts you entered
  • How you validated and revised the AI output
  • The challenges or limitations you faced while using AI

Failure to disclose use of AI tools or submitting AI-generated work as your own will be treated as academic misconduct. Minimum consequences include a zero on the assignment. Depending on severity, further penalties may include failure in the course and formal referral to the School of Engineering disciplinary committee.

This course is designed to build your skills—not evaluate the performance of generative tools. Authentic engagement with course challenges leads to meaningful growth. Overreliance on AI undermines both your learning and the integrity of our academic community.

Intellectual honesty is not optional—it defines your identity as an engineer, a scholar, and a professional.
.

Academic integrity policy

The University of Kansas, the School of Engineering, and the Department of Electrical Engineering & Computer Science (EECS) maintain a zero-tolerance policy toward academic dishonesty and misconduct. All students enrolled in this course are expected to uphold the highest standards of integrity and professionalism in their academic work.

Academic dishonesty includes, but is not limited to:

  • Plagiarism: Representing another person’s work, writing, or ideas—whether published, unpublished, or submitted by another student—as one’s own, without proper attribution.
  • Unauthorized collaboration: Giving or receiving unapproved help on assignments, projects, quizzes, or exams.
  • Misrepresentation: Knowingly presenting false information or misattributing the source of academic work.
  • Cheating: Using unauthorized resources during assessments or submitting work completed by someone else.
  • Falsification of research or data: Fabricating results, manipulating data, or misreporting findings.

The minimum consequence for an academic integrity violation is a zero on the item in question (e.g., lab, assignment, quiz, or exam). Depending on severity, penalties may include a grade reduction, a failing grade for the course, and formal referral to the School of Engineering's disciplinary committee for further review and sanctions.

All definitions and procedures follow institutional policy and guidance outlined by the University of Kansas Office of Student Affairs and the EECS Department. Students are expected to be familiar with and adhere to these standards at all times.

Please also see KU's academic misconduct policy

LMS features. During exams or quizzes, only one device should be used, with solely the Canvas app or a single browser tab for Canvas open. Having any other app or file open will be considered a violation of academic integrity. To further facilitate academic integrity, the following features of Canvas will be utilized:

  • Each exam and quiz will be conducted synchronously in classroom, will be scheduled on a regular weekly session.
  • Each exam or quiz will have a limited and narrow time (set via a timer) to be completed and each person will get only one chance to do it.
  • Exam and quiz questions will be randomly numbered for each person. Furthermore, the multiple choice, matching and similar questions will have randomized choice selections. As a result, a choice like "All of the above" or "None of the above" may not be the last choice and refers to the other choices.
  • Exam and quiz questions will be displayed one-at-a time, with no backtracking.
  • The "originality checking" mechanisms of LMS will be utilized for exams but also assignments. LMS is able to check written responses against online databases of previously published works and trace sentences or clauses to other sources.
  • LMS features to prohibit printing, copying/pasting of exams will be turned on.
  • LMS lockdown feature will be employed.

Code of student rights and responsibility: Code of Student Rights and Responsibilities

The School of Engineering statement on EdTech

"With the switch to online teaching as a result of the Coronavirus pandemic, professors and instructors at the KU School of Engineering are aware that some students are actively posting assignments, laboratory, and exam questions and responses to EdTech services (e.g., Chegg) even during exam time frames.

Keep in mind that when a person signs up to participate by either uploading, and/or downloading, and/or using posted material from these sites, the “terms of service” that are agreed to do not protect the person when KU and/or the School of Engineering decide to conduct investigations related to academic misconduct (e.g., plagiarism and/or cheating).

In fact, EdTech services, like Chegg, retain contact information of students who use their services and will release that information, which is traceable, upon request. Using these services constitutes academic misconduct, which is not tolerated in the School of Engineering. It violates Article 3r, Section 6 of its Rules & Regulations, and may lead to grades of F in compromised course(s), transcript citations of academic misconduct, and expulsion from the University of Kansas.

If unsure about assignments, it is important that students use the allowable available resources, such as instructor office hours, graduate teaching assistants, and/or tutoring. The School of Engineering wants students to be successful; cheating is not the way to attain that success."