| Week |
Subject |
Related Preparation |
| 1) |
Fundamentals of Test and Analysis
|
Software Test and Analysis in a Nutshell, A Framework for Test and Analysis |
| 2) |
Fundamentals of Test and Analysis |
Basic Principles, Test and Analysis Activities Within a Software Process |
| 3) |
Finite Models |
Finite Models |
| 4) |
Finite Models
|
Dependence and Data Flow Models |
| 5) |
Finite State Verification
|
Symbolic Execution and Proof of Properties |
| 6) |
Finite State Verification |
Finite State Verification |
| 7) |
Software Testing Concepts
|
Black Box Testing and White Box Testing |
| 8) |
Software Testing Principles
|
Software Testing Levels |
| 9) |
Test Case Selection and Adequacy
|
Adequacy Criteria and Coverage Criteria |
| 10) |
Functional Testing
|
Partition Testing Strategies |
| 11) |
Combinatorial Testing
|
Pairwise Combination Testing |
| 12) |
Structural Testing and Data Flow Testing |
Statement Testing, Branch Testing, Condition Testing, Path Testing, Data Flow Testing
|
| 13) |
Process
|
Planning and Monitoring the Process |
| 14) |
Test-Driven Development and Model Checking
|
System, Acceptance, and Regression Testing; Automating Analysis and Test; Documenting Analysis and Test; Finite State Verification |
| |
Program Outcomes |
Level of Contribution |
| 1) |
Be able to specify functional and non-functional attributes of software projects, processes and products. |
5 |
| 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. |
5 |
| 5) |
Be able to maintain a complex software system due to working environment changes, new user demands and software errors that occur during operation. |
5 |
| 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. |
5 |
| 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. |
5 |
| 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. |
5 |
| 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. |
5 |
| 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. |
5 |