CIS 573 Course Overview (Fall 2013)


Course Objectives

On the first day at your new job as a software engineer, your boss says to you "Here's 6,000 lines of code. Find the bugs. Fix them. Then make the software better." Would you even know where to begin?

This course seeks to answer questions like: How would you test a program you didn't write? How would you know when you were done testing it? How would you locate and fix the bugs? And make sure that your fixes didn't break other stuff? How would you modify existing code to make it better? What does "better" even mean?

Once you have completed this course, you will be able to answer those questions, and you will understand how to apply academic research to real-world software engineering problems.

This course is currently open only to graduate students in the CIS department. CIS undergraduates are encouraged to take CIS 350 instead. Undergrads and students in other departments may sign up on the wait list and will be notified if a spot opens up for them.

 


Class Meeting Times

Mon/Weds 4:30-6:00pm, Moore 216

Back to Top


Textbooks

There will be no required textbook for this course. There will be numerous assigned readings over the course of the semester, but they will be made available to you via Canvas.

Back to Top


Grading

Note that these are only guidelines, but final course grades will likely be based on the following:

  • Midterm exam (15%)
    • This will be scheduled for sometime in late October.
    • The exam will be open-book and open-notes, but you cannot use electronic devices.
  • Final exam (25%)
    • This is scheduled by the university registrar.
    • The exam will be open-book and open-notes, but you cannot use electronic devices.
    • The exam will be comprehensive, but will focus on material covered after the midterm.
  • Homework assignments (30%)
    • There will be 4-5 short assignments (2-3 weeks each) related to the major themes of the course: testing, debugging, refactoring, and design.
  • Group project (30%)
    • You will work in groups of 3-4 people to either: test, improve, and add functionality to an existing application; develop a tool that could be used by software engineers; or conduct research in software engineering.

Important: 

Credit for work will be recorded only as reported by the TA in the Gradebook in Canvas. It is your responsibility to make sure that your work has been properly recorded in the Gradebook.

Make sure you notify the TA of any problems regarding missing records or incorrectly entered scores; the grade entries in Canvas will be considered permanent one week subsequent to their posting.

Our TAs will be responsible for adjudicating problems related to grading; the instructor will only be involved as a possible court of last appeal in case there is some truly difficult decision to make (i.e., in most cases, I will not be willing to second guess the TAs' decisions). To submit a request to the TA for a regrade of an assignment, email the TA stating the nature of the problem and the remedy you desire. You must submit this adjustment request within one week of the return of the material in question. The TAs will not consider any requests for grade adjustments that are submitted later than this one week grace period.


Back to Top


Academic Integrity

All work submitted for this class is expected to be your own, unless otherwise noted in the assignment instructions. If you are caught submitting work that is completely copied from some other source, or that has been prepared by somebody other than you, you will face severe discipline by the university.

Homework assignments are to be completed individually unless explicitly stated. You may talk to fellow classmates regarding the assignment and share ideas on Piazza, but keep in mind what is appropriate and inappropriate about your collaboration:

Appropriate:

  • Person A doesn't understand what exactly the problem is asking, e.g. writing actual C code vs. pseudocode. He discusses this with Person B to arrive at one or the other.
  • Person A does not understand a particular concept. Person B explains the concept using an example, other than one asked on the homework.

Inappropriate:

  • A attempts half the problem, and B attempts the other half. A and B copy the solutions to half the assignment that the other person wrote.
  • Together, A and B work out each homework problem on chalk/white board; then they separately copy down their work and turn it in.
  • Person A completed a programming assignment and just before turning it in, he deleted his program - oh no!!!. In desperation, he asks Person B if he can turn in a copy of her program.
  • Person A happens to be in the lab working on the assignment and notices that Person B is working on the same assignment. Person A is having trouble compiling his program, and asks Person B to fix the problem for him. Sounds safe, right? It's not.

Note: When in doubt always ask the instructor or TA first, to avoid any potential collabration that can lead to academic dishonesty.

You can further read Penn's Code of Academic Integrity page on this subject matter, as well as the SEAS Graduate Student guidelines on the code of ethics.


Back to Top


Homework turn-in procedure

You will turn-in all homework assignments using Canvas.

You may submit multiple times, but only the last submission will be graded.

Submissions after the deadline are subject to a 10% per day penalty, up to seven days, after which the submission will not be accepted.

Back to Top