FACULTY OF ENGINEERING
Department of Software Engineering
SE 375 | Course Introduction and Application Information
Course Name |
System Programming
|
Code
|
Semester
|
Theory
(hour/week) |
Application/Lab
(hour/week) |
Local Credits
|
ECTS
|
SE 375
|
Spring
|
2
|
2
|
3
|
7
|
Prerequisites |
|
|||||||
Course Language |
English
|
|||||||
Course Type |
Required
|
|||||||
Course Level |
First Cycle
|
|||||||
Mode of Delivery | - | |||||||
Teaching Methods and Techniques of the Course | - | |||||||
Course Coordinator | ||||||||
Course Lecturer(s) | ||||||||
Assistant(s) |
Course Objectives | The goal of this course is to extend students’ knowledge in systems programming by focusing on practical network and multi threaded programming. Topics such as communication protocols, synchronization primitives, deadlocks, information security, authentication, confidentiality, integrity and digital signing are introduced in this course. The Java programming language will be used throughout the course.All laboratory exercises and assignments will be performed in Java; therefore, to be able to complete this course, a student should have good programming skills in Java. |
Learning Outcomes |
The students who succeeded in this course;
|
Course Description | To acquaint students with basic knowledge to develop systems programs that involves multi-threading and computer networks. It provides an introduction to multi-threading, socket programming and information security. |
|
Core Courses |
X
|
Major Area Courses | ||
Supportive Courses | ||
Media and Management Skills Courses | ||
Transferable Skill Courses |
WEEKLY SUBJECTS AND RELATED PREPARATION STUDIES
Week | Subjects | Related Preparation |
1 | Introduction | Instructor Notes |
2 | Processes, Threads, Concurrency | Horstmann & Cornell, Chapter 14, pp. 716-722 |
3 | Thread Programming Constructs | Horstmann & Cornell, Chapter 14, pp. 730-735 |
4 | Synchronization, Race Conditions, Deadlocks | Horstmann & Cornell, Chapter 14, pp. 736-762 |
5 | Thread-safe Collections, Swing | Horstmann & Cornell, Chapter 14, pp. 771-806 |
6 | Networking Basics-Introduction | Hortsmann, Chapter 20, pp.818-823 |
7 | Reference Models OSI-TCP/IP | Hortsmann, Chapter 20, pp.818-823 |
8 | Network Protocol Basics: IP/TCP/UDP | Hortsmann, Chapter 20, pp.818-823 |
9 | Socket Programming Constructs | Hortsmann, Chapter 20, pp. 823-842 |
10 | MIDTERM EXAM | |
11 | Security Basics. General overview and definitions of information security. | Oaks, Chapter 1 |
12 | Practical information security: authentication, hashing, symmetric and asymmetric encryption and decryption techniques, digital signature. | Oaks , Chapters 7,9,11. |
13 | Security Programming | Lecturer Notes |
14 | LAB EXAM | |
15 | Review of the Semester | |
16 | Review of the Semester |
Course Notes/Textbooks | 1) Core Java, Volume I Fundamentals, 8/e, Horstmann & Cornell, 2008 , Prentice Hall , ISBN10: 0132354764, ISBN13: 978-0132354769 |
Suggested Readings/Materials | 1) Big Java, Horstmann, 4th edition, 2010, Wiley, ISBN13: 978-0470553091 2) Java Security, Scott Oaks, 2nd Edition, 2013,O'Reilly Media, ISBN13: 978-0596001575, ISBN10: 0596001576 |
EVALUATION SYSTEM
Semester Activities | Number | Weigthing |
Participation | ||
Laboratory / Application |
1
|
30
|
Field Work | ||
Quizzes / Studio Critiques | ||
Portfolio | ||
Homework / Assignments | ||
Presentation / Jury | ||
Project | ||
Seminar / Workshop | ||
Oral Exams | ||
Midterm |
1
|
30
|
Final Exam |
1
|
40
|
Total |
Weighting of Semester Activities on the Final Grade |
2
|
60
|
Weighting of End-of-Semester Activities on the Final Grade |
1
|
40
|
Total |
ECTS / WORKLOAD TABLE
Semester Activities | Number | Duration (Hours) | Workload |
---|---|---|---|
Theoretical Course Hours (Including exam week: 16 x total hours) |
16
|
2
|
32
|
Laboratory / Application Hours (Including exam week: '.16.' x total hours) |
16
|
2
|
32
|
Study Hours Out of Class |
16
|
6
|
96
|
Field Work |
0
|
||
Quizzes / Studio Critiques |
0
|
||
Portfolio |
0
|
||
Homework / Assignments |
0
|
||
Presentation / Jury |
0
|
||
Project |
0
|
||
Seminar / Workshop |
0
|
||
Oral Exam |
0
|
||
Midterms |
1
|
25
|
25
|
Final Exam |
1
|
25
|
25
|
Total |
210
|
COURSE LEARNING OUTCOMES AND PROGRAM QUALIFICATIONS RELATIONSHIP
#
|
Program Competencies/Outcomes |
* Contribution Level
|
||||
1
|
2
|
3
|
4
|
5
|
||
1 | To have adequate knowledge in Mathematics, Science, Computer Science and Software Engineering; to be able to use theoretical and applied information in these areas on complex engineering problems. |
X | ||||
2 | To be able to identify, define, formulate, and solve complex Software Engineering problems; to be able to select and apply proper analysis and modeling methods for this purpose. |
X | ||||
3 | To be able to design, implement, verify, validate, document, measure and maintain a complex software system, process, or product under realistic constraints and conditions, in such a way as to meet the requirements; ability to apply modern methods for this purpose. |
|||||
4 | To be able to devise, select, and use modern techniques and tools needed for analysis and solution of complex problems in software engineering applications; to be able to use information technologies effectively. |
X | ||||
5 | To be able to design and conduct experiments, gather data, analyze and interpret results for investigating complex Software Engineering problems. |
X | ||||
6 | To be able to work effectively in Software Engineering disciplinary and multi-disciplinary teams; to be able to work individually. |
|||||
7 | To be able to communicate effectively in Turkish, both orally and in writing; to be able to author and comprehend written reports, to be able to prepare design and implementation reports, to be able to present effectively, to be able to give and receive clear and comprehensible instructions. |
|||||
8 | To have knowledge about global and social impact of engineering practices and software applications on health, environment, and safety; to have knowledge about contemporary issues as they pertain to engineering; to be aware of the legal ramifications of Engineering and Software Engineering solutions. |
|||||
9 | To be aware of ethical behavior, professional and ethical responsibility; to have knowledge about standards utilized in engineering applications. |
|||||
10 | To have knowledge about industrial practices such as project management, risk management, and change management; to have awareness of entrepreneurship and innovation; to have knowledge about sustainable development. |
|||||
11 | To be able to collect data in the area of Software Engineering, and to be able to communicate with colleagues in a foreign language. ("European Language Portfolio Global Scale", Level B1) |
|||||
12 | To be able to speak a second foreign language at a medium level of fluency efficiently. |
|||||
13 | To recognize the need for lifelong learning; to be able to access information, to be able to stay current with developments in science and technology; to be able to relate the knowledge accumulated throughout the human history to Software Engineering. |
*1 Lowest, 2 Low, 3 Average, 4 High, 5 Highest