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 |
LAW3007 | Drafting Contracts I | Fall | 0 | 2 | 1 | 4 |
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: | Non-Departmental Elective |
Course Level: | Bachelor’s Degree (First Cycle) |
Mode of Delivery: | |
Course Coordinator : | |
Recommended Optional Program Components: | None |
Course Objectives: | The main objective of the course is to understand the different kinds of contract that can be made and how they are written. WE will discuss contracts as an instrument of commerce, administration and law and we will analyze how contracts are formed via their structure and content. At the end of the course each student should be able to construct and write relevant clauses for a give contract. |
The students who have succeeded in this course; I. Defines the skeleton of an agreement II. Creates the style of an agreement III. Resolves the legal english problems for being able to draft an agreement IV. Forms different clauses which have to be drafted in an agreement V. Gives the ability of interpretation of an agreement |
Week 1: Introduction. Structure. Commencement, Recitals, Operative Part, Definitions Section. Week 2: Paragraphing and reference use Week 3: Vocabulary and Style of contracts Week 4: Dealing with mathematical formula and time periods Week 5: Legal English constructions Week 6: Legal English translational tools Week 7: Various forms of Clause Week 8: midterm exam Week 9: Access and Adapt model clauses for purpose Week 10: Understanding how a contract may be interpreted Week 11: Different methods of interpretation Week 12: Translational skills Week 13: Presentation Week 14: Review For Final Exam Week 15: Review For Final Exam Week 16: Final exam |
Week | Subject | Related Preparation |
1) | Week 1: Introduction. Structure. Commencement, Recitals, Operative Part, Definitions Section. | |
2) | Week 2: Paragraphing and reference use | |
3) | Week 3: Vocabulary and Style of contracts | |
4) | Week 4: Dealing with mathematical formula and time periods | |
5) | Week 5: Legal English constructions | |
6) | Week 6: Legal English translational tools | |
7) | Week 7: Various forms of Clause | |
8) | Review | |
9) | Week 9: Access and Adapt model clauses for purpose | |
10) | Week 10: Understanding how a contract may be interpreted | |
11) | Week 11: Different methods of interpretation | |
12) | Week 12: Translational skills | |
13) | Week 13: Presentation | |
14) | Week 14: Review For Final Exam |
Course Notes / Textbooks: | Ders notları derste öğrencilere verilecektir. |
References: |
Semester Requirements | Number of Activities | Level of Contribution |
Attendance | 14 | % 10 |
Presentation | 1 | % 20 |
Midterms | 1 | % 25 |
Final | 1 | % 45 |
Total | % 100 | |
PERCENTAGE OF SEMESTER WORK | % 55 | |
PERCENTAGE OF FINAL WORK | % 45 | |
Total | % 100 |
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) | Be able to design software architecture, components, interfaces and subcomponents of a system for complex engineering problems. | |
3) | Be able to develop a complex software system with in terms of code development, verification, testing and debugging. | |
4) | Be able to verify software by testing its program behavior through expected results for a complex engineering problem. | |
5) | Be able to maintain a complex software system due to working environment changes, new user demands and software errors that occur during operation. | |
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. | |
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. | |
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. | |
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. | |
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. | |
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. | |
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. |