Prerequisite: CS 253. An examination of the software development process from the initial requirement analysis to the operation and maintenance of the final system. The scope of the course includes the organization of software development projects, the verification and validation of systems, the problems of security and privacy, and the legal aspects of software development, including software protection and software liability.
|Instructor||Dr. Stan Kurkovsky, Professor of Computer Science|
|Office hours||TWR 1000-1140, booking info TBA|
|Class meetings||TR 1340-1455 @ WebEx/online|
Textbook and other things you will need
- Software Engineering by Ian Sommerville, 10th edition.
Pearson, 2015, ISBN 0133943038
- Textbook supplements available at http://iansommerville.com/software-engineering-book/
- Instructor's web site available at http://www.cs.ccsu.edu/~stan/ and other web sites recommended by the instructor
- Course project document
Course learning outcomes
Program educational objectives and student outcomes are supported by the following course learning outcomes achieved by students upon a successful completion of this course:
- CLO-1: Analyze a complex software problem and to apply principles of computer science to identify solutions (ABET SO-1);
- CLO-2: Design, implement, and evaluate a software solution to meet a given set of functional, non-functional, and domain requirements (ABET SO-2);
- CLO-3: Communicate technical information orally and in writing (ABET SO-3);
- CLO-4: Understand professional, ethical, and social responsibilities of a software engineering professional (ABET SO-4);
- CLO-5: Function effectively as a member or leader of a software development team (ABET SO-5);
- CLO-6: Apply computer science theory and software engineering fundamentals to produce software solutions (ABET SO-6).
Please take care of yourselves and your loved ones. Your physical and mental well-being is the most important thing. It has always been (or should have been) so, even before the current pandemic and economic crisis. Some of you may be essential workers or live with essential workers. If you or someone you love gets sick or needs to work; if you have childcare or elder care responsibilities; if any essential technology such as wifi/power/laptop/etc is down, take care of those things first. Please email/message me to check in if I won’t see you or hear from you on a day we have class or an assignment is due. We can meet individually most any time on WebEx. I will work with you to make arrangements that would enable you to stay on top of things without jeopardizing your academic standing and other responsibilities. As long as you complete assignments and keep in touch with me, we will all be good here.
Reference: S - Sommerville, Software Engineering, 10th edition
Week 1: August 26 - August 28
- Topic: Introduction and course project overview
Week 2: August 31 - September 4
- Topic: What is software engineering?
Reading: S 1
- Activity: course project discussion
Course project: team info sheet is due by EOD
Week 3: September 7 - September 11
- September 7 - Labor Day
- Topic: Software processes
Reading: S 2
- Course project: meet project clients
Week 4: September 14 - September 18
- Topic: Agile software development
Reading: S 3
Course project: project proposal is due by EOD
- Activity: project proposal review
Week 5: September 21 - September 25
- Hands-on introduction to Scrum
- Hands-on introduction to Scrum (cont.)
Week 6: September 28 - October 2
- Topic: Requirements engineering
Reading: S 4
- Course project: system requirements are due by 0900
Activity: system requirements review
Week 7: October 5 - October 9
- Topic: System modeling
Reading: S 5
- Course project: product backlog is due by 0900
Activity: product backlog review
Week 8: October 12 - October 16
- Topic: Architectural design
Reading: S 6
Course project: sprint 1 starts
- Course project: midterm presentation
Week 9: October 19 - October 23
- Topic: Design and implementation
Reading: S 7
Course project: work on sprint 1
Week 10: October 26 - October 30
- Topic: Software testing
Reading: S 8
Course project: sprint 1 report is due by EOD; sprint 2 starts
- Activity: sprint 1 retrospective
Week 11: November 2 - November 6
- Topic: Software evolution
Reading: S 9
Course project: work on sprint 2
- Activity: TBA
Week 12: November 9 - November 13
- Topic: TBA
Course project: sprint 2 report is due by EOD; sprint 3 starts
- Activity: sprint 2 retrospective
Week 13: November 16 - November 20
- Topic: TBA
Course project: work on sprint 3
- Activity: Course project feedback
Week 14: November 23 - November 27
- Activity: sprint 3 retrospective
Course project: sprint 3 report is due by EOD
- November 26-29 - Thanksgiving Recess
Week 15: November 30 - December 4
- Activity: final project demonstrations
- Activity: final project demonstrations
Course project: user manual is due
Week of final exams
- Final exam: Thursday, December 10, 1300-1500
Midterm and final exams
Each test will focus on the most recent material. However, each test will very likely include some questions aimed at the material covered by the earlier test(s). Make-up tests may only be given if a student can provide a written proof of a serious reason for missing a test (such as illness or accident).
While working on the course project, students will use the knowledge and skills obtained in this course covering many if not all of the course topics. Working in teams, students will design, implement and document a software system to meet the requirements of an external customer.
Course project is described in detail in this document.
All students are expected to demonstrate integrity in the completion of their coursework. Academic integrity means doing one's own work and giving proper credit to the work and ideas of others. It is the responsibility of each student to become familiar with what constitutes academic dishonesty and plagiarism and to avoid all forms of cheating and plagiarism. Students who engage in plagiarism and other forms of academic misconduct will face academic and possibly disciplinary consequences. Academic sanctions can range from a reduced grade for the assignment to a failing grade for the course. From a disciplinary standpoint, an Academic Misconduct Report may be filed and a Faculty Hearing Board may impose sanctions such as probation, suspension or expulsion.
All students are expected to attend class sessions regularly. However, recognizing individual differences, each student is responsible for his/her own attendance and for making-up any missed study or work. Limited assistance will be offered to those with plausible reasons for absences; unexcused absences will result in the student being totally responsible for the make-up process.
Students with disabilities
Please contact me privately to discuss your specific needs if you believe you need course accommodations based on the impact of a disability, medical condition, or if you have emergency medical information to share. I will need a copy of the accommodation letter from Student Disability Services in order to arrange your class accommodations. Contact Student Disability Services if you are not already registered with them. Student Disability Services maintains the confidential documentation of your disability and assists you in coordinating reasonable accommodations with the faculty.
Here's a link to a document containing information about other policies and resources.
Grades and evaluation
Students will be evaluated regularly during the semester and should be aware of their progress continuously during the semester. The final course grade will be reported according to the stated University policy.
The final course grade will be calculated according to the following distribution of points:
Course letter grade will be determined as follows: