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 |
SEN4925 | Independent Study | Spring | 0 | 6 | 3 | 6 |
This catalog is for information purposes. Course status is determined by the relevant department at the beginning of semester. |
Language of instruction: | English |
Type of course: | Departmental Elective |
Course Level: | Bachelor’s Degree (First Cycle) |
Mode of Delivery: | Face to face |
Course Coordinator : | Prof. Dr. MEHMET ALPER TUNGA |
Course Lecturer(s): |
Prof. Dr. NAFİZ ARICA |
Recommended Optional Program Components: | None |
Course Objectives: | The unique advantage of Independent Study via written correspondence is its flexibility. Students select their own hours of study and work at their own pace in surroundings most desirable to them. In addition to providing academic credit toward educational goals, independent study is a means of improving professional skills, acquiring knowledge for upgrading job skills, or satisfying intellectual and cultural curiosity. |
The students who have succeeded in this course; I. Prepare a project proposal by using IEEE Req. Engineering document format II. Gather information and data through interviews, questionnaires, surveys and observations of current client system III. Use UML diagrams to analyze system which will be designed IV. Define usability metrics V. Create database schemas and tables VI. Apply unit tests for each developed program units VII. Deploy the modules and software components VIII. Finalize the software development life cycle |
1st Week: Preparing Project proposal forms 2nd Week: Gathering information using interviews questionnaires, surveys and observations. 3rd Week: Project Presentation I 4th Week: Analyzing system using UML 5th Week: Working on usability metrics 6th Week: Constructing initial prototype 7th Week: Project Presentation II 8th Week: Applying unit tests 9th Week: Improving prototype 10th Week: Applying unit tests 11th Week: Project Presentation III 12th Week: Software module deployment 13th Week: Finalizing software development life cycle 14th Week: Project Presentation IV |
Week | Subject | Related Preparation |
1) | Preparing Project proposal forms | |
2) | Gathering information using interviews questionnaires, surveys and observations. | |
3) | Project Presentation I | |
4) | Analyzing system using UML | |
5) | Working on usability metrics | |
6) | Constructing initial prototype | |
7) | Project Presentation II | |
8) | Applying unit tests | |
9) | Improving prototype | |
10) | Applying unit tests | |
11) | Project Presentation III | |
12) | Software module deployment | |
13) | Finalizing software development life cycle | |
14) | Project Presentation IV |
Course Notes / Textbooks: | Software Engineering, Roger Pressman, ISBN-9780071267823 Software Architecture, Taylor, Medvidovic, Dashofy, ISBN-9780470167748 |
References: | Yok |
Semester Requirements | Number of Activities | Level of Contribution |
Quizzes | 2 | % 10 |
Homework Assignments | 1 | % 10 |
Presentation | 4 | % 40 |
Final | 1 | % 40 |
Total | % 100 | |
PERCENTAGE OF SEMESTER WORK | % 60 | |
PERCENTAGE OF FINAL WORK | % 40 | |
Total | % 100 |
Activities | Number of Activities | Duration (Hours) | Workload |
Application | 14 | 6 | 84 |
Presentations / Seminar | 4 | 8 | 32 |
Final | 1 | 10 | 10 |
Total Workload | 126 |
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. | 2 |
2) | Be able to design software architecture, components, interfaces and subcomponents of a system for complex engineering problems. | 2 |
3) | Be able to develop a complex software system with in terms of code development, verification, testing and debugging. | 2 |
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. | 2 |
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. | 3 |
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. | 2 |
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. | |
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. |