Research Publications
Teaching Students CV Software Funding Activities

CS 130: Software Engineering, Spring 2015

Instructor: Dr. Miryung Kim (BH 4532H)
    Lectures: MW 12PM to 2PM, FRANZ 2258A   
    Office Hours: MW 11 AM to 11:45 AM or by appointment
    Final Exam: Monday, June 8, 2015, 8:00am-11:00am

General Description  

We focus on providing hands-on experience in designing and developing large-scale software systems. You will generate concrete software engineering artifacts at all stages of the software life-cycle. You will learn systematic engineering methods for large-scale software development: design and modeling methods; collaborative development environment; object-oriented design patterns and refactoring; build & integration; unit testing & regression testing; bug finding; software inspection and verification.   

My goal is to teach systematic software development methods and tools in the context of developing a software system in collaboration with other students. Systematic design, construction, verification, and evolution methods include
  • Object-oriented design patterns
  • Refactoring
  • Unit testing, test coverage and test generation
  • Hoare logic, preconditions, post-conditions, and loop invariants 

Practical development tools include

  • Analysis tools (e.g., debuggers, automated bug-finders, JUnit)
  • Construction tools (e.g., compilation managers and build scripts)
  • Tool support for collaboration (e.g., version control systems, SVN, GIT)
  • GNU/Linux operating system environment, command-line utilities, bash shell scripting 
In the beginning of the class, I will ask you to fill out a background survey on what you are hoping to learn from this class. In the subsequent lecture, I will discuss how your expectations are aligned with and/or different from what to be covered and emphasized in the class.

Class Schedule, Reading List, and Project Milestones

Reading, Assignments, Tutorials
Week 1
Version Control System
SVN, Git, Diff
Lecture 1--Overview
Lecture 1--Collaboration
Unix Commands and Shell Scripting
Lecture 2-Unix and Scripting
Lecture 2-Shell
Subversion Tutorial
Git Tutorial
Unix and Scripting Tutorial
Lab: Part A Requirements
Week 2
Design Notation
Use Case and State chart in UML
Class Diagram, Sequence Diagram
Lecture 3-UML
Design Principles: Information Hiding
Lecture 4-Information Hiding
Overview of UML
UML Tutorial

Article: On the Criteria to be used in decomposing systems into modules
Lab: Discussion on Requirements
Week 3
Design Patterns
Strategy, Observer, Mediator
Abstract Factory, Factory Method
Lecture 5-Design Patterns Part A
Lecture 6-Design Patterns Part B
Head First Chapter 1. Overview and Strategy
Head First Chapter 2. Observer
Head First Chapter 4. Factory
Design Patterns: Strategy, Mediator, Observer, FactoryMethod
Lab: Part B Requirements (Part A is Due) 
Week 4
Design Patterns
Singleton, Command, Adaptor
Template Method, State, Flyweight
Lecture 7-Design Patterns Part C
Lecture 8-Design Patterns Part D
Design Pattern Skeleton Code Snippets
Head First Chapter 5. Singleton
Head First Chapter 6. Command
Head First Chapter 7. Adapter and Facade
Head First Chapter 8. Template Method
Head First Chapter 10. State
Design Patterns:  Singleton, Adapter, Flyweight
Code: Java Code examples of Head First Design Patterns
Lab: Discussion on Design Patterns
Week 5
Build Management
Lecture 9-Build Management
Midterm (4/29 in Class)
Assignment 1 is due on Wednesday 11:59 PM.

Lab: Part C Requirements
Week 6
Statement, Branch, and Path Coverage
Bounded Iteration, Infeasible Paths, Test Generation, and Symbolic Execution
Lecture 10-Testing Part 1
Lecture 11-Testing Part 2
Regression Test Selection
Testing Activity Notes and Solutions
Article: Symbolic Execution and Program Testing
JUnit Tutorial
Lab: Part B is Due.
Week 7

Hoare Logic
Weakest Precondition and Loop Invariant
Lecture 12-Hoare Logic Part 1
Lecture 13-Hoare Logic Part 2
Assignment 2 is due on Wednesday 11:59 PM.
Code Inspection Activity Notes and Solutions
Weakest Precondition-HandwrittenNote1.pdf
Weakest Precondition-HandwrittenNote2.pdf
Weakest Precondition-HandwrittenNote3.pdf

Lab: Discussion on Agile Process / XP Programming

Week 8
5/20 (ICSE)
Hoare Logic
Weakest Precondition and Loop Invariant
No class on 5/20. 
Lab: Bug Reproducing Activity
Week 9
5/25 Memorial Day

No class on 5/25.
Discussion on Modern Code Review and Testing
Modern Code Review Practices
Model Based Testing
Mutation Testing
Lecture 14-Code Review and Testing Discussion
FindBug Tutorial
Lab: Final Project is Due
Week 10
Effective Java
Creating and Destroying Objects
Methods Common to All Objects
Classes and Interfaces
Lecture 15-Effective Java Part 1
Lecture 16-Effective Java Part 2
Final Exam Review
Assignment 3 is Due on Wed.
Code: Effective Java Code Examples Demonstrated in Class
Effective Java Book:
Creating and Destroying Objects
Methods Common to All Objects
Classes and Interfaces

Sample Final Exams
(1) Practice Exam 1
(2) Practice Exam 2
(3) Practice Exam 3
Student Projects Video
Üdder (Spontaneous Event Schedule and Coordination iOS App, CS 130 Team Project Award Winner)
Photo Hangout (Real Time Collaborative Photo Editing Mobile App, Runner Up)
Eventful (Spontaneous Event Schedule and Coordination Android App, Honorable Mention, Nice Video)
BitBoard (Web App and iOS App for Collaborative Whiteboard Sketching, Honorable Mention)

Barter (Improved Craigslist+Tinder like experience for iOS Buy-Sell-Trade)
Beat Maker (Real Time Audio Editing Mobile App for Dance Choreography)
Book Cycle (Textbook Buy and Sell Web App)
Diet&Fit Motivation (Calorie Counting and Fitness Recommendation Web App)
Game Set Match (Improved with Games)
Hera (Real Time Music Animation based on Web Audio Characteristics)
MMM My Meal Manager (Recipe Suggestions based on Inventory Management)
PackManager (Packing Suggestion App for Travels based on Historical Weather Patterns)
Pantry (Pantry Inventory Food Expiration Notification)
PiCast  (Video Streaming using Raspberry Pi)
TutorU (Tutor Finding and Payment Web App)
Vantage (Social Photo Album Mobile App)


Project 35%
Quizzes and Class Discussion 15%
Midterm 15%
Final 25%
Homework 10%

Class Discussion: Think Pair Share

How Does It Work?
1) Think. The teacher provokes students' thinking with a question or prompt or observation. The students should take a few moments (probably not minutes) just to THINK about the question.

2) Pair. Using designated partners (such as with Clock Buddies), nearby neighbors, or a deskmate, students PAIR up to talk about the answer each came up with. They compare their mental or written notes and identify the answers they think are best, most convincing, or most unique.

3) Share. After students talk in pairs for a few moments (again, usually not minutes), the teacher calls for pairs to SHARE their thinking with the rest of the class. She can do this by going around in round-robin fashion, calling on each pair; or she can take answers as they are called out (or as hands are raised). Often, the teacher or a designated helper will record these responses on the board or on the overhead

Team Project

You will work in teams of four to six students in the same TA section. You should demonstrate that the proposed application is new and a unique creation. If you implement a feature that already exists or is very similar to an existing feature in any past or later version, it will be considered as plagiarism. When proposing a project, you should investigate whether it is feasible to implement and test it. You are expected to perform a live demonstration of your project during your project presentations. Students in the same team will not always receive the same grades, and project grades will account for individual effort and contribution. In each phase of the projects, students will rate and rank individual contributions within the teams and will rate the quality of projects for other teams. The teaching team will consider these peer evaluation reports when assigning individual grades. Your TAs will be in charge of setting project requirements and grading your projects. The instructor will also attend your midterm and final project presentations and provide additional assessments of your projects. Project activities will include the following but not limited to:

  1. a new feature proposal and presentation (3%)
  2. a midpoint implementation and testing progress report and presentation (10%)
  3. a final demonstration and presentation (10%)
  4. a youtube video about your project demo (5%): For example, you can take a look at sample videos created by my graduate students (Critics, LASE, Cookbook, RefDistiller)   
  5. participation and peer evaluation (7%)


The instructor will assign reading materials and tool tutorials to read before the next class. We will have a short quiz in every Wednesday's lecture. We will count the best 6 quizzes out of 8 quizzes. Each quiz should not take more than 10 minutes and will not exceed 5 questions. I hope this workload is reasonable given that we do not have homework assignments in this class. 

Project report and presentation grading scheme


During this course, I will be asking you to give me feedback on your learning in both informal and formal ways, e.g., including anonymous midpoint survey about how my teaching strategies are helping or hindering your learning. It is very important for me to know your reaction to what we are doing in the class, so I encourage you to respond to these surveys, ensuring that we can create an environment effective for teaching and learning.  Occasionally, at the end of the lecture, I will hand out index cards to ask "what is the most important thing you have learned in this class session?" and "what questions do you still have?" This feedback will be anonymous and this is to check your understanding and promote Q&A.

Academic Integrity

Each member of the university is expected to uphold these values through integrity, honesty, trust, fairness, and respect toward peers and community. In your first week, you must read and sign UCLA's Academic Integrity Statement.

Frequently Asked Questions

Q: Why aren't there many programming assignments? I want to improve my programming skill through this class.
My goal is to help you experience a software project life cycle by creating concrete artifacts in each stage. Thus, while software implementation is an important part of the life cycle, coding is not the main focus of this class. If you are excited about coding and want to practice more, please select a project with a significant implementation component or volunteer to play a key role in implementing your team project. I can also share pointers to open source projects, books, and references that could help you to practice your programming skills further.

Q: Why are we emphasizing theories (such as discrete math, logic, proof by induction, and program analysis) in a project-based software laboratory course?
I hope that you can not only get a good job as an entry level software engineer, but succeed in the future as a lead, principal engineer and architect. This requires you to have not only a solid coding skill but a theoretical foundation for systematic design, analysis, testing, and verification methods. In my opinion, these foundations cannot be easily attained while you are on the jobs; they are best taught at University.

Class Policy 

  • You can use your laptops to take notes (no smart phones please).
  • I promise to return graded assignments within two weeks to provide timely feedback to you.
  • Class announcements will be made through Piazza. Not every class announcement will be made available via electronic means.
  • Please use Assembla or GitHub or BitBucket for version control and project management. Please provide a read permission to us, so that we can access and grade your project. 
  • Review questions are to help you review concepts and to prepare for quizzes. If you do not know answers to the questions, I'd be happy to go through them with you during my office hours.