| 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 |
| SEN2001 | Programming Languages | Fall | 3 | 0 | 3 | 7 |
| Language of instruction: | English |
| Type of course: | Must Course |
| Course Level: | Bachelor’s Degree (First Cycle) |
| Mode of Delivery: | Face to face |
| Course Coordinator : | Instructor DUYGU ÇAKIR YENİDOĞAN |
| Course Lecturer(s): |
Instructor DUYGU ÇAKIR YENİDOĞAN Dr. Öğr. Üyesi ÖVGÜ ÖZTÜRK ERGÜN Dr. Öğr. Üyesi BETÜL ERDOĞDU ŞAKAR Dr. Öğr. Üyesi SERKAN AYVAZ |
| Recommended Optional Program Components: | None |
| Course Objectives: | The students will have basic understanding of some of the fundamental concepts that underlie programming language syntax and semantics through a comparative study of several languages and their features. The students will be aware of several new programming language features and paradigms to gain the ability to study general conceptual linguistic issues of designing new languages and compilers. |
|
The students who have succeeded in this course; 1. Define basic concepts and categories of programming languages 2. Identify formal methods of describing syntax, attribute grammars and dynamic semantics 3. Describe the concept of binding, type checking, type equivalence, scoping and referencing environments 4. Define features of primitive variables, character string, ordinal, array, associative array, record, union, pointer and reference data types 5. Define arithmetic, relational and boolean expressions, type conversions, assignment statements, selection and iterative statements and unconditional branching 6. Describe fundamentals of subprograms, design issues for subprograms, local referencing environments, parameter-passing methods, overloaded subprograms and design issues for functions 7. Define the concept of abstraction, describing data abstraction and desing issues for abstract data types 8. Defining design issues for object-oriented languages and describing support for object-oriented programming in various programming languages such as Smalltalk, C++, Java, C#, Ruby 9. Analyse mathematical functions, fundamentals of functional programming languages such as Lisp, Scheme, ML, Haskell and Describing predicate calculus and theorem proving, features of logic programming and the basic elements of Prolog 10. Define exception and event handling in various programming languages such as Ada, C++, Java. |
| The course content is composed of describing syntax and semantics, names, bindings, type checking and scopes, data types, expressions and assignment statements, control structures, subprograms, abstract data types, object-oriented programming, functional programming, logic programming, exception handling and event handling |
| Week | Subject | Related Preparation |
| 1) | Introduction | Read the Syllabus and lecture notes of Chapter#1 & 2 |
| 2) | Describing Syntax and Semantics I | Read the lecture notes of Chapter#3 |
| 3) | Describing Syntax and Semantics II | Read the lecture notes of Chapter#4 |
| 4) | Names, Bindings, Type Checking and Scopes | Read the lecture notes of Chapter#5 |
| 5) | Data Types | Read the lecture notes of Chapter#6 |
| 6) | Expressions and Assignment Statements | Read the lecture notes of Chapter#7 |
| 7) | Control Structures | Read the lecture notes of Chapter#8 |
| 8) | Subprograms I | Read the lecture notes of Chapter#9 |
| 9) | Subprograms II | Read the lecture notes of Chapter#10 |
| 10) | Abstract Data Types | Read the lecture notes of Chapter#11 |
| 11) | Object-oriented Programming | Read the lecture notes of Chapter#12 |
| 12) | Exception Handling and Event Handling | Read lecture notes of Chapter#13 & 14 |
| 13) | Functional Programming | Read the lecture notes of Chapter#15 |
| 14) | Logic Programming | Read the lecture notes of Chapter#16 |
| Course Notes / Textbooks: | Robert W. Sebesta, Concepts of Programming Languages, 8e, Pearson Education, Addison Wesley, 2008, ISBN 978-0-321-50968-0 |
| References: | Yok |
| Semester Requirements | Number of Activities | Level of Contribution |
| Quizzes | 4 | % 20 |
| Project | 1 | % 25 |
| Midterms | 1 | % 15 |
| Final | 1 | % 40 |
| Total | % 100 | |
| PERCENTAGE OF SEMESTER WORK | % 35 | |
| PERCENTAGE OF FINAL WORK | % 65 | |
| Total | % 100 | |
| Activities | Number of Activities | Duration (Hours) | Workload |
| Course Hours | 14 | 3 | 42 |
| Study Hours Out of Class | 8 | 4 | 32 |
| Project | 1 | 28 | 28 |
| Midterms | 1 | 28 | 28 |
| Final | 1 | 35 | 35 |
| Total Workload | 165 | ||
| 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. | 4 |
| 2) | Be able to design software architecture, components, interfaces and subcomponents of a system for complex engineering problems. | 5 |
| 3) | Be able to develop a complex software system with in terms of code development, verification, testing and debugging. | 5 |
| 4) | Be able to verify software by testing its program behavior through expected results for a complex engineering problem. | 2 |
| 5) | Be able to maintain a complex software system due to working environment changes, new user demands and software errors that occur during operation. | 1 |
| 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. | 1 |
| 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. | 1 |
| 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. | 4 |
| 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. | 3 |
| 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. | 3 |
| 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. | 1 |
| 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. | 4 |
| 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. |