SE 311 | Course Introduction and Application Information

Course Name
Software Architecture
Code
Semester
Theory
(hour/week)
Application/Lab
(hour/week)
Local Credits
ECTS
SE 311
Spring
2
2
3
7

Prerequisites
  SE 116 To succeed (To get a grade of at least DD)
Course Language
English
Course Type
Required
Course Level
First Cycle
Course Coordinator
Course Lecturer(s)
Assistant(s)
Course Objectives The goal of this course to arm the students with the knowledge needed in architecting effective and maintainable complex software systems of high quality by applying design patterns. Each pattern represents a best practice solution to a software problem in some context. The course will sensitize the student that there is rarely one "right" design and an engineer is faced with a spectrum of posibilities representing tradeoffs. The course will cover the rationale and benefits of design patterns in architecting software systems. The course includes a brief review of object oriented design principles and UML. Programming assignments and a project in the C++ language will provide experience in the use of these patterns.
Course Description The students who succeeded in this course;
  • Be able to identify the classification of a pattern
  • Be able to state the intention of the pattern and show in UML notation.
  • Be able to identify the participants and their responsibilities.
  • Be able to contrast the difference in intentions between structurally similar patterns.
  • Be able to apply several appropriate patterns in the design of small programming assignments.
  • Be able to select appropriate design patterns to improve an existing design.
Course Content This course covers the principals behind the software design patterns and their application in constructing software components.

 



Course Category

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 to Design Patterns “Design patterns: Elements of Reusable ObjectOriented Software” by E. Gamma, R. Helm, R. Johnson and J. Vlissides. GHJV. Chapter 1.
2 A refresher on Object Oriented Design and UML. Any book on object oriented design and programming. Instructor notes.
3 Iterator Pattern (Behavioral) Design Patterns Gamma, Helm, Johnson and Vlissides (GHJV) pp 257 271
4 Composite Pattern (Structural) Design Patterns GHJV pp 163 173
5 Command Pattern (Behavioral) Design Patterns GHJV pp 233 242
6 Factory and Abstract Factory (Creational) Design Patterns GHJV pp 87 95, 107 116
7 Singleton Pattern (Creational) Design Patterns GHJV pp 127 134
8 MIDTERM EXAM
9 Facade Pattern (Structural) Design Patterns GHJV pp 185 193
10 Adapter Pattern (Structural) Design Patterns GHJV pp 139 150
11 Template Pattern (Structural) Design Patterns GHJV pp 325 330
12 Observer Pattern (Behavioral) Design Patterns GHJV pp 293 303
13 Visitor Pattern (Behavioral) Design Patterns GHJV pp 331 344
14 Review Design Patterns GHJV
15 Project Discussions and Presentations Source Code and Project Report
16 Review of the Semester  

 

Course Notes/Textbooks “Design patterns: Elements of Reusable ObjectOriented Software” by E. Gamma, R. Helm, R. Johnson and J. Vlissides. AddisonWesley. 1995.Instructor notes and materials.
Suggested Readings/Materials Metseker and Wake “Design Patterns in Java”, AddisonWesley, 2006.

 

EVALUATION SYSTEM

Semester Activities Number Weigthing
Participation
Laboratory / Application
1
20
Field Work
Quizzes / Studio Critiques
Homework / Assignments
1
-
Presentation / Jury
Project
1
20
Seminar / Workshop
Oral Exams
Midterm
1
30
Final Exam
1
30
Total

Weighting of Semester Activities on the Final Grade
3
70
Weighting of End-of-Semester Activities on the Final Grade
1
30
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
Study Hours Out of Class
16
2
Field Work
Quizzes / Studio Critiques
Homework / Assignments
1
15
Presentation / Jury
Project
1
49
Seminar / Workshop
Oral Exam
Midterms
1
20
Final Exam
1
20
    Total
200

 

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.

X
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.

X
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.

X
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.

X
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.

X

*1 Lowest, 2 Low, 3 Average, 4 High, 5 Highest