Prerequisite: CS 510. Study of the software lifecycle including requirements analysis, specification, design, coding, testing, and maintenance. Includes proofs of correctness and techniques of formal specification.
|Instructor||Dr. Stan Kurkovsky, Professor of Computer Science|
|Office hours||TWR 1000-1140, booking info TBA|
|Class meetings||MW 1505-1620 @ WebEx/online|
Textbook and other things you will need
- Software Engineering by Ian Sommerville, 10th edition.
Pearson, 2015, ISBN 0133943038
- In-class handouts
- 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
Upon a successful completion of this course, the students will be able to:
- CLO-1: Analyze a complex software problem and to apply modern software engineering techniques to identify solutions;
- CLO-2: Design, implement, and evaluate a software solution to meet a given set of functional, non-functional, and domain requirements;
- CLO-3: Communicate technical information orally and in writing;
- CLO-4: Understand and follow professional, ethical, and social responsibilities of a software engineering professional;
- CLO-5: Function effectively as a member or leader of a software development team;
- CLO-6: Apply fundamental and advanced software engineering principles to produce software solutions.
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 (Introduction)
Project: Q&A with the product owner
Week 2: August 31 - September 4 (Inception)
- Topic: Software Reuse (S 15)
Reading: A large-scale empirical study on software reuse in mobile apps
Project: Project team info sheet is due by EOD
- Project: Product backlog draft is due by 0900
Project: Product backlog draft discussion
Week 3: September 7 - September 11 (Inception)
- September 7 - Labor Day
- Topic: Component-based Software Engineering (S 16)
Reading: Component Stacks for Enterprise Applications
Project: Updated product backlog is due by EOD
Week 4: September 14 - September 18 (Sprint 1)
- Project: Sprint 1 planning
- Topic: Distributed Software Engineering (S 17)
Reading: Global Software Engineering: An Industry Perspective
Week 5: September 21 - September 25 (Sprint 1)
- Project: Sprint 1 update
- Topic: Service-oriented Software Engineering (S 18)
Reading: Infrastructure as a Service and Cloud Technologies
Week 6: September 28 - October 2 (Sprint 2)
- Project: Sprint 1 review & retrospective
Project: Sprint 2 planning
Project: Sprint 1 report is due by EOD
- Topic: Systems Engineering (S 19)
Reading: From Minecraft to Minds
Week 7: October 5 - October 9 (Sprint 2)
- Project: Sprint 2 update
- Topic: Systems of Systems (S 20)
Reading: Service Orientation and Systems of Systems
Week 8: October 12 - October 16 (Midterm point)
- Project: Sprint 2 review & retrospective
Project: Sprint 2 report is due by EOD
Week 9: October 19 - October 23 (Sprint 3)
- Project: Sprint 3 planning
- Topic: Real-time Software Engineering (S 21)
Reading: Embedded Software in Crisis
Week 10: October 26 - October 30 (Sprint 3)
- Project: Sprint 3 update
- Topic: Project Management (S 22)
Reading: Team Performance in Software Development
Week 11: November 2 - November 6 (Sprint 4)
- Project: Sprint 3 review & retrospective
Project: Sprint 4 planning
Project: Sprint 3 report is due by EOD
- Topic: Project Planning (S 23)
Reading: Scaling Agile
Week 12: November 9 - November 13 (Sprint 4)
- Project: Sprint 4 update
- Topic: Quality Management (S 24)
Reading: Improving Software Quality as Customers Perceive It
Week 13: November 16 - November 20 (Sprint 5)
- Project: Sprint 4 review & retrospective
Project: Sprint 5 planning
Project: Sprint 4 report is due by EOD
- Topic: Configuration Management (S 25)
Reading: DevOps: Making It Easy to Do the Right Thing
Week 14: November 23 - November 27 (Sprint 5)
- Project: Sprint 5 update
- November 26-29 - Thanksgiving Recess
Week 15: November 30 - December 4 (Sprint 5)
- Project: Sprint 5 update
- Project: Sprint 5 review & retrospective
Week 16: December 7 (Release)
Week of final exams
- Final exam: Monday, December 14, 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).
During each discussion session, one students will present the paper from a trade publication identified in the corresponding reading section. All students are expected to actively participate in each discussion session by asking questions and expressing their opinions.
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.
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: