Course quality improvement : From the market and new subjects in the Course Content Chapter in Week Topics Text Introduction to software engineering 1 ,2 Chapter 1 Software Processes 3, 4 Chapter 2 Agile Software Development 5, 6 Chapter 3 6, 7 Chapter 4 Requirements Engineering Exam 7, 8 Chapter System Modeling 5 Chapter 9, 10 Architectural Design 6 11 Second Exam 11, 12 Chapter Design and Implementation 7 Software Testing 12,13 Chapter 8 Software Evolution Chapter 14,15 9 Final Exam 16 From the monitoring of students feedback (Evaluation sheet). Cooperation on Assignments: For both homework assignments, I strongly believe that discussion with your peers is an excellent way to learn. If you don’t understand something, discussing it with someone who does can be far more productive than beating your head against the wall. Having advocated discussion, then, I must be about clear what is allowed, and what is not. In general, students are allowed to cooperate as follows: you are allowed to discuss with other students the assignment, and general methods for solving the assignment. However, you are not allowed to work with someone else to actually the assignment, or anyone else’s solution; doing any of these things solve copy will be considered cheating, and will constitute grounds for failing the course. Note that there is a fine line between discussion and cheating. If you are unsure what is allowed and what isn’t, feel free to discuss the distinction with me, but if something feels uncomfortable, it’s probably not allowed. Late Policies: : no late exams, no make-up exams; Exams : no late assignments; Assignments no make-up quizzes. However, if you let me know in advance of an expected absence, Quizzes: we can attempt to schedule some alternative. Late work will be accepted as stated above. I may waive the late policy conditions only in case of a documented illness or another extraordinary circumstance. In either case you have to contact me
Course Content Week Topics Chapter in Text 1 ,2 Introduction to software engineering Chapter 1 3, 4 Software Processes Chapter 2 5, 6 Agile Software Development Chapter 3 6, 7 Requirements Engineering Chapter 4 Exam 7, 8 System Modeling Chapter 5 9, 10 Architectural Design Chapter 6 11 Second Exam 11, 12 Design and Implementation Chapter 7 12,13 Software Testing Chapter 8 14,15 Software Evolution Chapter 9 16 Final Exam Course quality improvement : From the market and new subjects in the From the monitoring of students feedback (Evaluation sheet). Cooperation on Assignments: For both homework assignments, I strongly believe that discussion with your peers is an excellent way to learn. If you don’t understand something, discussing it with someone who does can be far more productive than beating your head against the wall. Having advocated discussion, then, I must be about clear what is allowed, and what is not. In general, students are allowed to cooperate as follows: you are allowed to discuss with other students the assignment, and general methods for solving the assignment. However, you are not allowed to work with someone else to actually solve the assignment, or copy anyone else’s solution; doing any of these things will be considered cheating, and will constitute grounds for failing the course. Note that there is a fine line between discussion and cheating. If you are unsure what is allowed and what isn’t, feel free to discuss the distinction with me, but if something feels uncomfortable, it’s probably not allowed. Late Policies: Exams : no late exams, no make-up exams; Assignments : no late assignments; Quizzes: no make-up quizzes. However, if you let me know in advance of an expected absence, we can attempt to schedule some alternative. Late work will be accepted as stated above. I may waive the late policy conditions only in case of a documented illness or another extraordinary circumstance. In either case you have to contact me
SE_SYLLABUS.docx