| SOFTWARE ENGINEERING | |||||
| Bachelor | TR-NQF-HE: Level 6 | QF-EHEA: First Cycle | EQF-LLL: Level 6 | ||
| Course Code | Course Name | Semester | Theoretical | Practical | Credit | ECTS |
| COP4429 | Wissen Akademi Advanced Network Systems Engineering | Fall Spring |
3 | 0 | 3 | 6 |
| The course opens with the approval of the Department at the beginning of each semester |
| Language of instruction: | En |
| Type of course: | Departmental Elective |
| Course Level: | Bachelor |
| Mode of Delivery: | Face to face |
| Course Coordinator : | MEHMET ŞÜKRÜ KURAN |
| Course Lecturer(s): |
Prof. Dr. TAŞKIN KOÇAK Dr. Öğr. Üyesi TARKAN AYDIN |
| Course Objectives: | This course will help the student to become an advanced network engineer. The course will be taught with the state-of-the-art Cisco devices. And hands-on experimenting is a must in this class. Student will learn advanced features of networking and have a broader view of advanced wide area networks used by enterprises and service providers. This course will be offered by Wissen Akademie. |
|
The students who have succeeded in this course; Advanced networking features, learning, Improving students' practical experiences, Enhanced learning area networks |
| This course covers advanced topics of Cisco networking such as 1) EIGRP, 2) Multi-Area OSPF, 3) Security and WAN Implementation. |
| Week | Subject | Related Preparation | |
| 1) | IEEE 802.q Trunking | ||
| 2) | STP, MSTP, RSTP Protocols | ||
| 3) | Inter-vlan routing | ||
| 4) | Implementing EIGRP | ||
| 5) | Configuring EIGRP | ||
| 6) | Multi-Area OSPF | ||
| 7) | Configuring and troubleshooting Multi-Area OSPF | ||
| 8) | BGP Basics and Concepts | ||
| 9) | Configuring BGP | ||
| 10) | Troubleshooting BGP | ||
| 11) | Configuring VPNs(IPSEC, GRE, Tunnel) | ||
| 12) | Multi-layer switch configuration | ||
| 13) | Redundancy Protocols (HSRP, VRRP, GLBP) | ||
| 14) | (HSRP, VRRP, GLBP) | ||
| 15) | Fundementals of MPLS | ||
| 16) | Final Exam | ||
| Course Notes: | None-Yok |
| References: | None-Yok |
| Semester Requirements | Number of Activities | Level of Contribution |
| Attendance | 16 | % 10 |
| Laboratory | 16 | % 20 |
| Application | % 0 | |
| Field Work | % 0 | |
| Special Course Internship (Work Placement) | % 0 | |
| Quizzes | % 0 | |
| Homework Assignments | 5 | % 10 |
| Presentation | % 0 | |
| Project | 1 | % 10 |
| Seminar | % 0 | |
| Midterms | 2 | % 20 |
| Preliminary Jury | % 0 | |
| Final | 1 | % 30 |
| Paper Submission | % 0 | |
| Jury | % 0 | |
| Bütünleme | % 0 | |
| Total | % 100 | |
| PERCENTAGE OF SEMESTER WORK | % 60 | |
| PERCENTAGE OF FINAL WORK | % 40 | |
| Total | % 100 | |
| Activities | Number of Activities | Duration (Hours) | Workload |
| Course Hours | 14 | 3 | 42 |
| Laboratory | 0 | 0 | 0 |
| Application | 0 | 0 | 0 |
| Special Course Internship (Work Placement) | 0 | 0 | 0 |
| Field Work | 0 | 0 | 0 |
| Study Hours Out of Class | 12 | 3 | 36 |
| Presentations / Seminar | 0 | 0 | 0 |
| Project | 1 | 20 | 20 |
| Homework Assignments | 5 | 4 | 20 |
| Quizzes | 0 | 0 | 0 |
| Preliminary Jury | 0 | ||
| Midterms | 2 | 2 | 4 |
| Paper Submission | 0 | ||
| Jury | 0 | ||
| Final | 1 | 2 | 2 |
| Total Workload | 124 | ||
| No Effect | 1 Lowest | 2 Low | 3 Average | 4 High | 5 Highest |
| Program Outcomes | Level of Contribution | |
| 1) | Be able to specify functional and non-functional attributes of software projects, processes and products. | |
| 2) | Be able to design software architecture, components, interfaces and subcomponents of a system for complex engineering problems. | |
| 3) | Be able to develop a complex software system with in terms of code development, verification, testing and debugging. | |
| 4) | Be able to verify software by testing its program behavior through expected results for a complex engineering problem. | |
| 5) | Be able to maintain a complex software system due to working environment changes, new user demands and software errors that occur during operation. | |
| 6) | Be able to monitor and control changes in the complex software system, to integrate the software with other systems, and to plan and manage new releases systematically. | |
| 7) | Be able to identify, evaluate, measure, manage and apply complex software system life cycle processes in software development by working within and interdisciplinary teams. | |
| 8) | Be able to use various tools and methods to collect software requirements, design, develop, test and maintain software under realistic constraints and conditions in complex engineering problems. | |
| 9) | Be able to define basic quality metrics, apply software life cycle processes, measure software quality, identify quality model characteristics, apply standards and be able to use them to analyze, design, develop, verify and test complex software system. | |
| 10) | Be able to gain technical information about other disciplines such as sustainable development that have common boundaries with software engineering such as mathematics, science, computer engineering, industrial engineering, systems engineering, economics, management and be able to create innovative ideas in entrepreneurship activities. | |
| 11) | Be able to grasp software engineering culture and concept of ethics and have the basic information of applying them in the software engineering and learn and successfully apply necessary technical skills through professional life. | |
| 12) | Be able to write active reports using foreign languages and Turkish, understand written reports, prepare design and production reports, make effective presentations, give clear and understandable instructions. | |
| 13) | Be able to have knowledge about the effects of engineering applications on health, environment and security in universal and societal dimensions and the problems of engineering in the era and the legal consequences of engineering solutions. |