| 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 |
| SEN3006 | Software Architecture | Spring | 2 | 2 | 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 : | Dr. Öğr. Üyesi YÜCEL BATU SALMAN |
| Course Lecturer(s): |
Prof. Dr. NAFİZ ARICA RA MERVE ARITÜRK RA SEVGİ CANPOLAT Dr. Öğr. Üyesi YÜCEL BATU SALMAN Instructor DUYGU ÇAKIR YENİDOĞAN Dr. Öğr. Üyesi TAMER UÇAR |
| Recommended Optional Program Components: | None. |
| Course Objectives: | Provides in depth the concepts, principals, methods, and best practices in software architectures; emphasizes on team projects to architect domain-specific architectures, service-oriented architectures, product-line architectures, adaptive and generative architectures. This course provides an overview for software engineering concepts and architectures. Students will work in small groups to design and implement software applications. The course will also provide a high-level overview of the software engineering discipline: software requirements, software design, software construction, software management, and software quality and testing. |
|
The students who have succeeded in this course; 1. Define the phases of the software development lifecycle 2. Describe the difference between project and process metrics 3. Define the terms version control and change control 4. Apply the methods for performing requirements elicitation and requirements analysis 5. Discuss important design principles such as information hiding and abstraction 6. Discuss the differences between structured and object oriented analysis and design 7. Define key testing terms such as black box testing and white box testing 8. Construct the activities of the software lifecycle for a small to medium software project |
| The course content is composed of product, process, project management, metrics, project planning, systems engineering, analysis concepts, analysis modeling, risk, sqa, project scheduling, scm, design concepts, architecture design, user interface design, technical metrics, oo concepts, ooa, ood, software testing techniques and strategies, software maintenance, software testing techniques and strategies , oo metrics and a case study in software architecture – the a-7e operational flight program. |
| Week | Subject | Related Preparation |
| 1) | Product, Process | |
| 2) | Project Management, Metrics, Project Planning | |
| 3) | Systems Engineering | |
| 4) | Analysis Concepts, Analysis Modeling | |
| 5) | Risk, SQA, Project Scheduling, SCM | |
| 6) | Design Concepts | |
| 7) | Architecture Design, User Interface Design, Other Design Topics | |
| 8) | Design Topics | |
| 9) | Technical Metrics, OO Concepts, OOA, OOD | |
| 10) | Software Testing Techniques and Strategies | |
| 11) | Software maintenance, Software Testing Techniques and Strategies , OO Metrics | |
| 12) | OO Metrics | |
| 13) | A Case Study in Software Architecture – the A-7E Operational Flight Program | |
| 14) | Project Presentations |
| Course Notes / Textbooks: | Craig Larman Applying UML and Patterns: An Introduction to Object-Oriented Analysis and Design and Iterative Development, 3/E ISBN-10: 0131489062 | ISBN-13: 9780131489066 Roger S. Pressman Software Engineering: A Practitioner's Approach, Sixth Edition , McGraw-Hill Software Architecture in Practice, 2/e Bass, Clements & Kazman 2003 | Addison-Wesley Professional | Cloth; 560 pp ISBN-10: 0321154959 | ISBN-13: 9780321154958 |
| References: | Yok - None. |
| Semester Requirements | Number of Activities | Level of Contribution |
| Quizzes | 2 | % 10 |
| Project | 1 | % 15 |
| Midterms | 1 | % 25 |
| Final | 1 | % 50 |
| Total | % 100 | |
| PERCENTAGE OF SEMESTER WORK | % 35 | |
| PERCENTAGE OF FINAL WORK | % 65 | |
| Total | % 100 | |
| Activities | Number of Activities | Duration (Hours) | Workload |
| Course Hours | 14 | 2 | 28 |
| Laboratory | 14 | 2 | 28 |
| Study Hours Out of Class | 2 | 20 | 40 |
| Project | 1 | 15 | 15 |
| Quizzes | 2 | 10 | 20 |
| Midterms | 1 | 16 | 16 |
| Final | 1 | 20 | 20 |
| Total Workload | 167 | ||
| 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. | 2 |
| 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. | 2 |
| 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. | 3 |
| 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. | 2 |
| 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. |