| School/Faculty/Institute | Graduate School | ||||
| Course Code | ITC 504 | ||||
| Course Title in English | Agile Methods and DevOps | ||||
| Course Title in Turkish | Agile Methods and DevOps | ||||
| Language of Instruction | EN | ||||
| Type of Course | Flipped Classroom | ||||
| Level of Course | Intermediate | ||||
| Semester | Spring | ||||
| Contact Hours per Week |
|
||||
| Estimated Student Workload | 187 hours per semester | ||||
| Number of Credits | 7.5 ECTS | ||||
| Grading Mode | Standard Letter Grade | ||||
| Pre-requisites | None | ||||
| Expected Prior Knowledge | None | ||||
| Co-requisites | None | ||||
| Registration Restrictions | Only Graduate Students | ||||
| Overall Educational Objective | To learn the fundamentals of Agile Methods and DevOps and to be able to analyze and describe their main components. | ||||
| Course Description | DevOps describes a culture and set of processes that bring development and operations teams together to complete software development. It allows organizations to create and improve products at a faster pace than they can with traditional software development approaches. This course provides a comprehensive introduction to DevOps Software Development Method. The following topics are covered: (1) Microservice Architecture, (2) Agile Software Development, (3) Test Automation, (4) Containers, (5) Cloud, (6) Product Management, (7) Organization Change required for DevOps. | ||||
| Course Description in Turkish | Bu derste DevOps Yazılım Geliştirme Yöntemine kapsamlı bir giriş sağlanmaktadır. Derste işlenen konular: (1) Mikroservisler, (2) Çevik Yazılım Geliştirme, (3) Test Otomasyonu, (4) Konteynerlar, (5) Bulut, (6) Ürün Yönetimi, (6) DevOps için gerekli organizasyonal değişiklikler |
Course Learning Outcomes and CompetencesUpon successful completion of the course, the learner is expected to be able to:1) Describe and make use of microservice architecture 2) Describe Agile Software Development 3) Analyze test automation, containers, and cloud systems 4) Perform product management and apply organization change required for DevOps. |
| Program Learning Outcomes/Course Learning Outcomes | 1 | 2 | 3 | 4 |
|---|---|---|---|---|
| 1) An ability to develop and deepen one's knowledge in the field of mechatronics and robotics engineering at the level of expertise based on acquired undergraduate level qualifications. | ||||
| 2) An ability to acquire scientific and practical knowledge in mechatronics and robotics. | ||||
| 3) A comprehensive knowledge about analysis and modeling methods in mechatronics and their limitations. | ||||
| 4) An ability to design and apply analytical, modeling and experimental based research by analyzing and interpreting complex situations encountered in the design process. | ||||
| 5) An ability to transmit the process and results of the work of mechatronics and robotics systems systematically and clearly in written and oral form in national and international environments. | ||||
| 6) An ability to recognize social, scientific and ethical values in the stages of designing and realizing mechatronics and robotic systems and in all professional activities. | ||||
| 7) An ability to follow new and developing practices in the profession and to apply them in their work. | ||||
| 8) An ability to take leadership in multi-disciplinary teams, taking responsibility in the design and analysis of mechatronics and robotic systems in complex situations. | ||||
| 9) An ability to communicate verbally and in writing in English at least at the level of B2 of European Language Portfolio. | ||||
| 10) An understanding of the social and environmental aspects of mechatronics and robotics applications. |
| N None | S Supportive | H Highly Related |
| Program Outcomes and Competences | Level | Assessed by | |
| 1) | An ability to develop and deepen one's knowledge in the field of mechatronics and robotics engineering at the level of expertise based on acquired undergraduate level qualifications. | N | |
| 2) | An ability to acquire scientific and practical knowledge in mechatronics and robotics. | N | |
| 3) | A comprehensive knowledge about analysis and modeling methods in mechatronics and their limitations. | N | |
| 4) | An ability to design and apply analytical, modeling and experimental based research by analyzing and interpreting complex situations encountered in the design process. | N | |
| 5) | An ability to transmit the process and results of the work of mechatronics and robotics systems systematically and clearly in written and oral form in national and international environments. | N | |
| 6) | An ability to recognize social, scientific and ethical values in the stages of designing and realizing mechatronics and robotic systems and in all professional activities. | N | |
| 7) | An ability to follow new and developing practices in the profession and to apply them in their work. | N | |
| 8) | An ability to take leadership in multi-disciplinary teams, taking responsibility in the design and analysis of mechatronics and robotic systems in complex situations. | N | |
| 9) | An ability to communicate verbally and in writing in English at least at the level of B2 of European Language Portfolio. | N | |
| 10) | An understanding of the social and environmental aspects of mechatronics and robotics applications. | N |
| Prepared by and Date | , |
| Course Coordinator | İLKER BEKMEZCİ |
| Semester | Spring |
| Name of Instructor | Öğr. Gör. ORHAN KALAYCI |
| Week | Subject |
| 1) | General Introduction |
| 2) | Fundamental Concepts |
| 3) | Microservices-I |
| 4) | Microservices-II |
| 5) | Agile/Scrum I |
| 6) | Agile/Scrum II |
| 7) | Test Automation / TDD I |
| 8) | Test Automation / TDD II |
| 9) | Containers/Cloud I |
| 10) | Containers/Cloud II |
| 11) | Product Management vs Project Management I |
| 12) | Product Management vs Project Management II |
| 13) | Re-Organizing to Support Microservice Architecture I |
| 14) | Re-Organizing to Support Microservice Architecture I |
| 15) | Final Examination Period |
| 16) | Final Examination Period |
| Required/Recommended Readings | The Phoenix Project, 2013, by George Spafford, Kevin Behr, Gene Kim, IT Revolution Press, ISBN: 9780988262508 Building Microservices, 2015, Sam Newman, O'Reilly Media, Inc., ISBN: 9781491950357 Clean Code, 2008, Robert C. Martin, Prentice Hall, ISBN: 9780136083238 Domain-Driven Design: Tackling Complexity in the Heart of Software, 2003, Eric Evans, Addison-Wesley Professional, ISBN: 0321125215 Design Patterns: Elements of Reusable Object-Oriented Software, 1994, John Vlissides, Ralph Johnson, Richard Helm, Erich Gamma, Addison-Wesley Professional,ISBN: 0201633612 Learn Docker - Fundamentals of Docker 18.x, 2018, Gabriel N. Schenker, Packt Publishing ISBN: 9781788997027 | |||||||||||||||
| Teaching Methods | Lectures/contact hours using “flipped classroom” as an active learning technique | |||||||||||||||
| Homework and Projects | None | |||||||||||||||
| Laboratory Work | None | |||||||||||||||
| Computer Use | Required | |||||||||||||||
| Other Activities | None | |||||||||||||||
| Assessment Methods |
|
|||||||||||||||
| Course Administration |
Missing a midterm: Provided that proper documents of excuse are presented, each missed midterm by the student will be given the grade of the final exam. No make-up will be given. Academic dishonesty and plagiarism will be subject to Law on Higher Education Article 54. |
|||||||||||||||
| Activity | No/Weeks | Hours | Calculation | ||||
| No/Weeks per Semester | Preparing for the Activity | Spent in the Activity Itself | Completing the Activity Requirements | ||||
| Course Hours | 14 | 1 | 3 | 1 | 70 | ||
| Homework Assignments | 3 | 15 | 2 | 51 | |||
| Quiz(zes) | 3 | 15 | 1 | 48 | |||
| Final Examination | 1 | 16 | 2 | 18 | |||
| Total Workload | 187 | ||||||
| Total Workload/25 | 7.5 | ||||||
| ECTS | 7.5 | ||||||