Course Title
Informatics 43
Intro to Software Engineering
Fall 2014
Professor
Emily Navarro
http://www.ics.uci.edu/~emilyo
emilyo@uci.edu
DBH 5221
Professor's Office Hours
By appointment (generally before or after class)
TAs
Rohan Achar
rachar@uci.edu
Office hours: Thursdays 1-2pm, Tech Garden, DBH 5054
Anirudh Sethi
aniruds@uci.edu
Office hours: Tuesdays 11am-12pm, Java City
Readers
Yang Feng
yang.feng@uci.edu
Office hours: Fridays 5-6pm ICS 424
Wen Shen
wen.shen@uci.edu
Office hours: Wednesdays 1:30-2:30pm, ICS 408B
Consuelo Lopez
consuell@uci.edu
Office hours: Mondays 4-5pm, ICS 414
Logistics
Location: ELH 100
Day and time: Tuesday and Thursday, 5:00-6:20pm
Catalogue Description
IN4MATX 43. Introduction to Software Engineering (4). Concepts, methods, and current practice of software engineering. Large-scale software production, software life cycle models, principles and techniques for each stage of development.
Required Textbook
Tsui, Karam, Bernal, "Essentials of Software Engineering," Third Ed.
Quiz Dates
There will be 6 quizzes, as shown in the schedule below. Quizzes will generally be held from 6:05-6:20. Additional quizzes may be given without prior notice, and the time and length of the quizzes may change.
Grades
Grades are based on an "overall average" for each student that is computed at the end of the quarter. The overall average is a weighted average of the following:
The overall average, on a 0-100 scale, is converted to a letter grade as follows: A or A- for 90 or up; B+, B, or B- for 80 to 89; C+, C, or C- for 70 to 79, and so on. These ranges may be modified slightly.
Course Mailing List
To send mail: 37000-F14@classes.uci.edu
To view the archive: https://eee.uci.edu/classmail/f14/37000/
Course Piazza page
https://piazza.com/uci/fall2014/in4matx43
Policies
Late Work
Late work will not be accepted, except in truly extenuating circumstances for which the student can produce documentation validating their circumstance (e.g., a doctor's note, a police report, etc.)
Adding and Dropping
Last day to add, drop, or change grade option: October 17. Work missed because the student was not yet enrolled cannot be made up.
Academic Dishonesty
Academic Dishonesty will not be tolerated in any shape or form. You will be held responsible for any and all actions whether they were performed indirectly (i.e. you left your computer unmonitored, someone stole your password, you left a printed version of your work in the lab). Remember, the burden of proof is on you. The staff must solely determine that academic dishonesty has occurred, and hope that those responsible will own up to their actions. In cases where neither student admits their participation, both will receive the same sanctions on a course-level (Note: campus-wide sanctions are determined by the Associate Dean of your department). Cheating will be detected by TurnItIn.com. Please note that instances of academic dishonesty will be reflected in the final grade because dishonesty devalues the learning experience for the whole class.
Students with Disabilities
Any student who feels he or she may need an accommodation based on the impact of a disability should contact me privately to discuss his or her specific needs. Please also contact the Disability Services Center at (949) 824-7494 as soon as possible to better ensure that such accommodations are implemented in a timely fashion.
Schedule
Note: This schedule is subject to change.
|
Week |
Date |
Topic |
Slides |
Readings (complete by start of lecture) |
Item(s) due |
|
0 |
October 2 Lecture |
Course Introduction, Introduction to Software Engineering |
|
|
|
|
|
October 3 Discussion |
NO DISCUSSION |
|
|
|
|
1 |
October 7 Lecture |
What is Software Engineering? Software Principles No Silver Bullet |
1.1, 1.2, 1.3, 2.1, 3.2, 3.4 |
|
|
|
|
October 9 Lecture |
Failing Big: CA SW fiascos Requirements Engineering |
3.1, 6.1, 6.2, 6.3 |
|
|
|
|
October 10 Discussion |
Software Failures and No Silver Bullet |
|
|
|
|
2 |
October 14 Lecture |
Client interview |
|
6.4, 6.5, 6.6 |
|
|
|
October 16 Lecture |
Client interview QUIZ 1 |
|
|
|
|
|
October 17 Discussion |
Mythical Man Month |
|
|
|
|
3 |
October 21 Lecture |
Use Cases |
|
Homework 1 draft due, 11:55pm |
|
|
|
October 23 Lecture |
Software Architecture QUIZ 2 |
|
7.1, 7.2 |
|
|
|
October 24 Discussion |
Use Cases |
|
|
|
|
4 |
October 28 Lecture |
Software Architecture |
|
|
Homework 1 (final version) due, 11:55pm |
|
|
October 30 Lecture |
Software Process Models QUIZ 3 |
4.1, 4.2 |
|
|
|
|
October 31 Discussion |
Git |
|
|
|
|
5 |
November 4 Lecture |
Software Process Models |
(No new slides) |
5.1, 5.2, 5.3.1 |
|
|
|
November 6 Lecture |
TBD QUIZ 4 |
|
|
|
|
|
November 7 Discussion |
Software Process Models |
Download SimSE game (instructions) |
||
|
6 |
November 11 Lecture |
Veteran's Day: NO CLASS |
|
|
|
|
|
November 13 Lecture |
TEST 1 |
|
|
|
|
|
November 14 Discussion |
NO DISCUSSION |
|
|
|
|
7 |
November 18 Lecture |
Design, Models, Notations |
7.3.1, 7.3.3 |
Homework 2, Part A due, 11:55pm |
|
|
|
November 20 Lecture |
User Orientation QUIZ 5 |
8.5 |
|
|
|
|
November 21 Discussion |
User Orientation |
|
|
|
|
8 |
November 25 Lecture |
Testing |
10.1, 10.2, 10.3 (with less emphasis on 10.3.3 and 10.3.6) |
Homework 2, Part B due, 11:55pm |
|
|
|
November 27 Lecture |
Thanksgiving: NO CLASS |
|
|
|
|
|
November 28 Discussion |
Thanksgiving break: NO DISCUSSION |
|
|
|
|
9 |
December 2 Lecture |
Testing |
10.4, 10.5, 10.6, 10.7, 10.8 |
|
|
|
|
December 4 Lecture |
Testing QUIZ 6 |
|
Homework 2, Part C due, ***5:00pm in class (hard copy)*** |
|
|
|
December 5 Discussion |
Assignment/exam return |
|
|
|
|
10 |
December 9 Lecture |
Moore' Law Project Estimation Review |
13.3.1 |
Homework 3 due, ***5:00pm in class (hard copy)*** |
|
|
|
December 11 Lecture |
TEST 2 |
|
|
|
|
|
December 12 Discussion |
NO DISCUSSION |
|
|
|
Homeworks
Examples of "real" requirements documents:
WhatTimeIsIt from Joel On Software
Ambulance Dispatch System by Rohleder, Smith, and Dix
Claw Design Bible (At the Computer Game Design Conference on May 6, 1998, there was a panel on design docs. Moderator Alex Dunne referenced a game design document which was submitted by panelist John Jack, a producer at Monolith. This design doc was from the company's computer game, "Claw".)
|
|
|