| Lectures: | Tuesday and Thursday, 9:30am – 10:45pm, GOODW 155 |
| Instructor: | Francisco Servant [fservant@vt.edu] |
| Instructor Office hours: | After class, or by email appointment |
| Teaching Assistants: | Farhan Ibrahim [farhani8@vt.edu], Mohammed Elarnaoty [marnaoty@vt.edu] |
| Teaching Assistant Office hours: | Monday, Wednesday, 9:00am – 11am. McBryde 106, McBryde 110 |
Description
Software engineering is concerned with developing and maintaining software systems that behave reliably and efficiently, and satisfy all requirements that customers have defined for them. In this course, we will first introduce software process and then go over every phase in the process: requirements analysis, software design, implementation, testing, and maintenance. Finally, we will briefly introduce some advanced concepts in software engineering. We will learn-by-doing to strengthen our understanding of materials covered in lectures. Class attendance and participation are highly encouraged to improve critical thinking and communication skills of students. Students will do a group project (up to 4 people per group) following all the stages of the software development lifecycle. Students will: document software requirements, design software, implement code, and test the functionality of a software project.
Prerequisites
CS 3114 (Minimum grade of C).
Textbook
The textbook for the course concentrates on the tasks of specification, requirements and object-oriented design. The supplemental texts listed here are NOT REQUIRED for the course, but contain a broader set of materials about software engineering. Hard or electronic copies of these books are available at VT library. Class lectures and the books will provide the material to use as you build your projects. Some of the material will be in your textbook; some will not. Additional materials will be available online.
- Craig Larman, Applying UML and Patterns: An Introduction to Object-oriented Analysis and Design, Edition 3, Prentice Hall, 2005. (LAR)
- Roger S. Pressman, Software Engineering: A Practitioner’s Approach, McGraw Hill, 2005. SUPPLEMENTAL (PRE)
- Ian Sommerville, Software Engineering, Addison Wesley, 2007. SUPPLEMENTAL. (SOM)
- Eric Freeman, Elisabeth Robson, Kathy Sierra, and Bert Bates, Head First Design Patterns. SUPPLEMENTAL.
Grading and Evaluation
Distribution of points:
| Midterm | 20% |
| Final Exam | 30% |
| Group Project | 50% |
Submission guidelines:
Assignments must be submitted as follows:
- through Canvas. Use the folder for the corresponding assignment.
- by 23:59pm Eastern time on the due date
Late submission policy:
Unexcused late assignments will be penalized 1% per 1-hour period.
Grading scale:
| ≥ 93% → A | ≥ 83% → B | ≥ 73% → C | ≥ 63% → D | |||
| ≥ 90% → A- | ≥ 80% → B- | ≥ 70% → C- | ≥ 60% → D- | |||
| ≥ 87% → B+ | ≥ 77% → C+ | ≥ 67% → D+ | ≥ 0% → F |
Schedule (tentative)
| Week | Date | Topic | Reference Materials | Assignment |
|---|---|---|---|---|
| 1 | 01/16 | Introduction to Software Engineering | * Standish Group Report 1995 * Fred Brooks, “No Silver Bullet - essence and accident in Software Engineering” * They write the right stuff |
|
| 01/18 | Introduction to Software Engineering | |||
| 2 | 01/23 | Project Management | PRE Ch 6 | Group selections due before class |
| 01/25 | Project Management | PRE Ch 6 | ||
| 3 | 01/30 | Requirements | LAR Ch 2, 5, 6, 9 | Project selections due before class |
| 02/01 | Requirements | LAR Ch 2, 5, 6, 9 | ||
| 4 | 02/05 | Assignment 1 - Group contract. Due by 23:59pm on Canvas | ||
| 02/06 | Requirements | LAR Ch 2, 5, 6, 9 | ||
| 02/08 | Requirements | LAR Ch 2, 5, 6, 9 | ||
| 5 | 02/13 | Software Process | PRE Ch 3, 4. SOM Ch4 | |
| 02/15 | Software Process | PRE Ch 3, 4. SOM Ch4 | ||
| 6 | 02/20 | High-level Design | PRE Ch 10, 12. SOM Ch 11 | |
| 02/22 | High-level Design | PRE Ch 10, 12. SOM Ch 11 | Assignment 2 - Requirements. Due by 23:59pm on Canvas | |
| 7 | 02/27 | Instructor on travel. No class. | ||
| 03/01 | Midterm | Midterm exam | ||
| 8 | 03/06 | No class - Spring Break | ||
| 03/08 | No class - Spring Break | |||
| 9 | 03/13 | Detailed Design | LAR Ch 14, 15, 17, 19 | |
| 03/15 | Detailed Design | LAR Ch 16 | ||
| 10 | 03/20 | Detailed Design | Beginning Database Design Solutions Ch 1, 9 | |
| 03/22 | Detailed Design | Beginning Database Design Solutions Ch 1, 9 | Assignment 3 - High-level Design. Due by 23:59pm on Canvas | |
| 11 | 03/27 | Detailed Design | PRE Ch 15 | |
| 03/29 | Detailed Design | LAR Ch 26 | ||
| 12 | 04/03 | Testing | PRE Ch 22 | |
| 04/05 | Testing | PRE Ch 22 | Assignment 4 - Detailed Design. Due by 23:59pm on Canvas | |
| 13 | 04/10 | Testing | PRE Ch 23 | |
| 04/12 | Testing | PRE Ch 24 | ||
| 14 | 04/17 | Refactoring | Refactoring: Improving the Design of Existing Code | Assignment 5 - Implementation and Testing. Due by 23:59pm on Canvas |
| 04/19 | Project Presentations | Groups: Data Visualization, Music composer, Budget Manager | ||
| 15 | 04/24 | Project Presentations | Groups: Party Music Scheduler 1, Movie Theater 2, Personal Expense Manager 1 | |
| 04/26 | Instructor on travel. No class. | |||
| 16 | 05/01 | Project Presentations | Groups: Personal Expense Manager 3, Personal Expense Manager 2, Movie Theater 1, Library Manager, Party Music Scheduler 2 | |
| 05/03 | Reading Day. No class. | Assignment 6 - Presentation Slides. Due by 23:59pm on Canvas | ||
| Exam | 05/08 | Exam in class 10:05am – 12:05am | Final exam |
Policies
Virginia Tech Honor Code:
The work you turn in must be your own. Consequences of cheating in this class: a letter in your academic file, and the course grade is lowered, most likely to F. Material that is copied from books or Web pages needs to be quoted and the source must be given. If you plagiarize, you run the severe risk of failing the class, in a most disgraceful manner.
Accommodations:
If you need special accommodations, please contact the instructor during the first week of classes.