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 |
SEN4931 | Special Topics in Software Engineering I | Fall Spring |
3 | 0 | 3 | 6 |
This catalog is for information purposes. Course status is determined by the relevant department at the beginning of semester. |
Language of instruction: | English |
Type of course: | Departmental Elective |
Course Level: | Bachelor’s Degree (First Cycle) |
Mode of Delivery: | Face to face |
Course Coordinator : | Assist. Prof. TAMER UÇAR |
Course Lecturer(s): |
Prof. Dr. NAFİZ ARICA |
Recommended Optional Program Components: | None |
Course Objectives: | Study of various topics, like advanced design patterns with current technical developments in software engineering. Applications in software engineering concepts with enterprise systems and their solution techniques. Teaching Methods and Techniques Used in the Course: Lecture, reading, individual study |
The students who have succeeded in this course; 1. Describe SOA basics 2. Describe timeline of SOA 3. Analyze web services framework 4. Define SOA principles 5. Analyze SOA layers 6. Analyze SOA lifecycle phases 7. Describe service analysis 8. Describe service modeling 9. Analyze service oriented design |
The course content is composed of introducing service oriented architecture (soa), evolution of soa, the web services framework, web services and contemporary soa, principles of service orientation, soa application and business service layers, soa orchestration service layer and agnostic services, soa delivery lifecycle phases, service oriented analysis, service modeling, service oriented design, wsdl. |
Week | Subject | Related Preparation |
1) | Introducing Service Oriented Architecture (SOA) | |
2) | Evolution of SOA | |
3) | The Web Services Framework | |
4) | Web Services and Contemporary SOA | |
5) | Principles of Service Orientation | |
6) | SOA Application and Business Service Layers | |
7) | SOA Applications / Midterm I | |
8) | SOA Orchestration Service Layer and Agnostic Services | |
9) | SOA Delivery Lifecycle Phases | |
10) | Service Oriented Analysis | |
11) | Service modeling | |
12) | Service Modeling / Midterm II | |
13) | Service Oriented Design | |
14) | WSDL |
Course Notes / Textbooks: | Service-Oriented Architecture (SOA): Concepts, Technology, and Design, Thomas Erl 978-0131858589 |
References: | Yok |
Semester Requirements | Number of Activities | Level of Contribution |
Quizzes | 2 | % 10 |
Homework Assignments | 2 | % 10 |
Midterms | 2 | % 40 |
Final | 1 | % 40 |
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 |
Study Hours Out of Class | 3 | 5 | 15 |
Homework Assignments | 2 | 5 | 10 |
Quizzes | 2 | 3 | 6 |
Midterms | 2 | 14 | 28 |
Final | 1 | 17 | 17 |
Total Workload | 118 |
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. |