|
|
| IST3019 | Software Engineering | 4+0+0 | ECTS:5 | | Year / Semester | Fall Semester | | Level of Course | First Cycle | | Status | Elective | | Department | DEPARTMENT of STATISTICS and COMPUTER SCIENCES | | Prerequisites and co-requisites | None | | Mode of Delivery | Face to face, Group study | | Contact Hours | 14 weeks - 4 hours of lectures per week | | Lecturer | -- | | Co-Lecturer | | | Language of instruction | Turkish | | Professional practise ( internship ) | None | | | | The aim of the course: | | The aim of this course is to be prepared in accordance with certain software development methods, to highlight the differences between the program and to provide an understanding of the method steps. Therefore, we will focus on experimental and numerical methods, analysis and design techniques, project scheduling and management techniques, software testing activities, software documentation details, software engineering, quality assurance and other issues. |
| Learning Outcomes | CTPO | TOA | | Upon successful completion of the course, the students will be able to : | | | | LO - 1 : | To understand the concept of software process and software process models | 6,7,10 | 1,6 | | LO - 2 : | To understand the tasks of software project manager | 5,6,9,10,11 | 1,6 | | LO - 3 : | To select the software requirements | 6,7,9,10,11 | 1,6 | | LO - 4 : | To make software design using UML | 6,7,10,11 | 1,6 | | LO - 5 : | To learn the concepts of software verification and validation testing | 9,10,11 | 1,6 | | LO - 6 : | To create object-oriented design | 7 | 1,6 | | LO - 7 : | To explain the risks of software | 7,9,10,11 | 1,6 | | CTPO : Contribution to programme outcomes, TOA :Type of assessment (1: written exam, 2: Oral exam, 3: Homework assignment, 4: Laboratory exercise/exam, 5: Seminar / presentation, 6: Term paper), LO : Learning Outcome | | |
| This course covers software design, software development, software development methods, software project management, software project metrics, human-computer interaction and design patterns subjects |
| |
| Course Syllabus | | Week | Subject | Related Notes / Files | | Week 1 | Introduction to Computer System Engineering | | | Week 2 | Introduction to Software Engineering | | | Week 3 | Software Engineering Processes | | | Week 4 | Analysis of software requirements | | | Week 5 | Analysis of software requirements | | | Week 6 | Structural Analysis | | | Week 7 | Object Oriented Analysis | | | Week 8 | UML Diagrams | | | Week 9 | Midterm Exam | | | Week 10 | Software Design | | | Week 11 | Software Implementation | | | Week 12 | Software Testing | | | Week 13 | Software Maintenance | | | Week 14 | Quality Assurance | | | Week 15 | Mid-Term project evaluation | | | Week 16 | Final Exam | | | |
| 1 | SARIDOĞAN E. , 2011; Yazılım Mühendisliği Temelleri, Papatya Yayıncılık, İstanbul | | | |
| 1 | Çatal, Ç., 2013; Yazılım Mühendisliği Yöntemleri - İleri Konular, Papatya Yayıncılık, İstanbul | | | 2 | Sommerville, I. 2010; Software Engineering (9th Edition), Pearson | | | |
| Method of Assessment | | Type of assessment | Week No | Date | Duration (hours) | Weight (%) | | Mid-term exam | 9 | 19/11/2016 | 1,5 | 30 | | In-term studies (second mid-term exam) | 15 | 29/12/2016 | | 20 | | End-of-term exam | 16 | 12/01/2017 | 1,5 | 50 | | |
| Student Work Load and its Distribution | | Type of work | Duration (hours pw) | No of weeks / Number of activity | Hours in total per term | | Yüz yüze eğitim | 4 | 14 | 56 | | Sınıf dışı çalışma | 3 | 14 | 42 | | Ödev | 3 | 10 | 30 | | Dönem sonu sınavı için hazırlık | 4 | 1 | 4 | | Dönem sonu sınavı | 1 | 1 | 1 | | Total work load | | | 133 |
|