Advanced Software Engineering
CS 530 - Summer 2019
Catalog description:
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.
Logistics
Instructor | Dr. Stan Kurkovsky, Professor of Computer Science |
Office | MS 303-06 |
Phone | (860) 832-2720 |
kurkovsky@ccsu.edu | |
Office hours | TBA |
Class meetings | MW 5:00 pm - 7:00 pm @ MS 203 |
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.
Tentative schedule
Reference: S - Sommerville, Software Engineering, 10th edition
Week 1: May 28 - 31 (Introduction)
- Introduction
Project: Q&A with the product owner
Week 2: June 3 - 7 (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 - Topic: Component-based Software Engineering (S 16)
Reading: Component Stacks for Enterprise Applications
Project: Product backlog is due
Week 3: June 10 - 14 (Sprint 1)
- Project: Sprint 1 planning
- Topic: Distributed Software Engineering (S 17)
Reading: Global Software Engineering: An Industry Perspective
Week 4: June 17 - 21 (Sprint 1)
- Topic: Service-oriented Software Engineering (S 18)
Reading: Infrastructure as a Service and Cloud Technologies - Topic: Systems Engineering (S 19)
Reading: From Minecraft to Minds
Week 5: June 24 - 28 (Sprint 2)
- Project: Sprint 1 review and retrospective
Project: Sprint 2 planning - Topic: Systems of Systems (S 20)
Reading: Service Orientation and Systems of Systems - Test 1
- Project: Sprint 1 report is due
Week 6: July 1 - 5 (Sprint 2)
- Topic: Real-time Software Engineering (S 21)
Reading: Embedded Software in Crisis - Topic: Project Management (S 22)
Reading: Team Performance in Software Development
Week 7: July 8 - 12 (Sprint 3)
- Project: Sprint 2 review and retrospective
Project: Sprint 3 planning - Topic: Project Planning (S 23)
Reading: Scaling Agile
- Project: Sprint 2 report is due
Week 8: July 15 - 19 (Sprint 3)
- Topic: Quality Management (S 24)
Reading: Improving Software Quality as Customers Perceive It - Topic: Configuration Management (S 25)
Reading: DevOps: Making It Easy to Do the Right Thing
Week 9: July 22 - 26 (Release)
- Test 2
- Project: Final demo
Project: Sprint 3 report is due
Project: User manual is due
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).
Readings/discussions
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.
Course project
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.
Academic misconduct
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.
For further information on academic misconduct and its consequences, please consult the Student Code of Conduct and the Academic Misconduct Policy.
Attendance
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.
Other statements
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:
Discussions | 15 |
Project | 40 |
Midterm exam | 20 |
Final exam | 25 |
Total | 100 |
Course letter grade will be determined as follows:
A | A- | B+ | B | B- | C+ | C | C- | D+ | D | D- | F |
---|---|---|---|---|---|---|---|---|---|---|---|
94-100 | 90-93.99 | 87-89.99 | 84-86.99 | 80-83.99 | 77-79.99 | 74-76.99 | 70-73.99 | 67-69.99 | 64-66.99 | 60-63.99 | 0-59.99 |