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 |
BA2224 | Principles of Accounting II | Spring | 3 | 0 | 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: | Non-Departmental Elective |
Course Level: | Bachelor’s Degree (First Cycle) |
Mode of Delivery: | Face to face |
Course Coordinator : | Prof. Dr. FATMA ÖZKUL |
Course Lecturer(s): |
Prof. Dr. FİGEN TÜRÜDÜOĞLU Assoc. Prof. HÜMEYRA ADIGÜZEL Prof. Dr. FATMA ÖZKUL |
Recommended Optional Program Components: | Industrial Engeneering, Financial Economics, Lojistics. |
Course Objectives: | Principles of Accounting II course is the complementary course of Principles of Accounting I. This course is designed to provide knowledge about current and fixed asset management, short and long term liabilities and shareholders’ equity, cash flow statement and financial statement analysis. |
The students who have succeeded in this course; The students who have succeeded in this course; 1.To learn the accounting terminology. 2. To learn the table of accounts 3. To learn how to record the accounts 4. To learn the effects of transactions on the financial statements 5. To have enough knowledge about receivables 6. To have enough knowledge about long term assets 7. To have enough knowledge about long term debts 8. To have enough knowledge about paid-in capital 9. To have enough knowledge about shareholders’ equity 10. To have enough knowledge about cash flow statements 11. To have enough knowledge about financial statement analysis |
1) Receivables 2) Plant Assets 3) Intangibles 4) Current Liabilities, Payroll 5) Long Term Liabilities 6) Partnerships 7) To be continued 8) Midterm 9) Corporations: Paid-in Capital 10) Balance Sheet 11) Corporations: Effect on Retained Earnings and the Income Statement 12) Income Statement 13) The Statement of Cash Flows 14) Financial Statement Analysis |
Week | Subject | Related Preparation |
1) | Receivables: An Introduction | |
2) | Allowance method, Direct method and notes receivables | |
3) | Plant assets and Depreciation | |
4) | Intangibles and Natural Resources | |
5) | Current liabilities: sales tax | |
6) | Stock and Bonds | |
7) | Review and Problem Session | |
8) | Corporations: An overview | |
9) | Issuing stocks, Retained Earnings, Cash dividends | |
10) | Corporations: stock dividends, Treasury Stocks, Retained Earnings | |
11) | The Statement of Cash Flow | |
12) | Financial Statement Analysis: Vertical and Horizontal Analysis | |
13) | Financial Statement Analysis: Ratio Analysis | |
14) | Review and Problem Session |
Course Notes / Textbooks: | Accounting, Authors: Horngren, Harrison, Oliver, 2009, 8.Edition ISBN: 13-978-0-13-609342-8 |
References: | Financial Accounting, Authors: Jan R. Williams, Susan F. Haka, Mark S. Bettner |
Semester Requirements | Number of Activities | Level of Contribution |
Quizzes | 10 | % 20 |
Homework Assignments | 14 | % 10 |
Midterms | 1 | % 20 |
Final | 1 | % 50 |
Total | % 100 | |
PERCENTAGE OF SEMESTER WORK | % 50 | |
PERCENTAGE OF FINAL WORK | % 50 | |
Total | % 100 |
Activities | Number of Activities | Workload |
Course Hours | 14 | 42 |
Study Hours Out of Class | 14 | 72 |
Homework Assignments | 14 | 14 |
Quizzes | 11 | 11 |
Midterms | 1 | 2 |
Final | 1 | 2 |
Total Workload | 143 |
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. |