FACULTY OF ENGINEERING
Department of Software Engineering
SE 482 | Course Introduction and Application Information
Course Name |
E-Business: Administration, Security and Marketing
|
Code
|
Semester
|
Theory
(hour/week) |
Application/Lab
(hour/week) |
Local Credits
|
ECTS
|
SE 482
|
Fall/Spring
|
3
|
0
|
3
|
5
|
Prerequisites |
None
|
|||||
Course Language |
English
|
|||||
Course Type |
Elective
|
|||||
Course Level |
First Cycle
|
|||||
Mode of Delivery | - | |||||
Teaching Methods and Techniques of the Course | - | |||||
Course Coordinator | ||||||
Course Lecturer(s) | ||||||
Assistant(s) | - |
Course Objectives | The main objective of this course is to provide the students with basic definition of e-business and e-commerce as well as understanding concepts of SCM and CRM |
Learning Outcomes |
The students who succeeded in this course;
|
Course Description | The purpose of this course is to inform the how e-business will be implemented under different conditions and environments. |
|
Core Courses | |
Major Area Courses |
X
|
|
Supportive Courses | ||
Media and Management Skills Courses | ||
Transferable Skill Courses |
WEEKLY SUBJECTS AND RELATED PREPARATION STUDIES
Week | Subjects | Related Preparation |
1 | Introduction to ebusiness and ecommerce | Chaffey, Ch.1 |
2 | Ecommerce fundamentals | Chaffey, Ch.2 |
3 | Ebusiness infrastructure | Chaffey, Ch.3 |
4 | Eenvironment | Chaffey, Ch.4 |
5 | Ebusiness strategy | Chaffey, Ch.5 |
6 | Supply chain management | Chaffey, Ch.6 |
7 | E-procurement | Chaffey, Ch.7 |
8 | Midterm Exam | |
9 | E-marketing | Chaffey, Ch.8 |
10 | Customer relationship management | Chaffey, Ch.9 |
11 | Analysis and design I | Chaffey, Ch.10 |
12 | Analysis and design II | Chaffey, Ch.11 |
13 | Implementation and maintenance | Chaffey, Ch.12 |
14 | Security and privacy | Stallings |
15 | Course Review | |
16 | Course Review |
Course Notes/Textbooks | Chaffey. D., EBusiness and ECommerce Management, 5/E, Prentice Hall, 2011, ISBN: 9780273752011. |
Suggested Readings/Materials | Turban, Efraim, Electronic Commerce 2012, Prentice Hall, 2012. |
EVALUATION SYSTEM
Semester Activities | Number | Weigthing |
Participation | ||
Laboratory / Application | ||
Field Work | ||
Quizzes / Studio Critiques |
2
|
30
|
Portfolio | ||
Homework / Assignments | ||
Presentation / Jury | ||
Project | ||
Seminar / Workshop | ||
Oral Exams | ||
Midterm |
1
|
30
|
Final Exam |
1
|
40
|
Total |
Weighting of Semester Activities on the Final Grade |
3
|
50
|
Weighting of End-of-Semester Activities on the Final Grade |
1
|
50
|
Total |
ECTS / WORKLOAD TABLE
Semester Activities | Number | Duration (Hours) | Workload |
---|---|---|---|
Theoretical Course Hours (Including exam week: 16 x total hours) |
16
|
3
|
48
|
Laboratory / Application Hours (Including exam week: '.16.' x total hours) |
16
|
0
|
|
Study Hours Out of Class |
16
|
2
|
32
|
Field Work |
0
|
||
Quizzes / Studio Critiques |
2
|
10
|
20
|
Portfolio |
0
|
||
Homework / Assignments |
0
|
||
Presentation / Jury |
0
|
||
Project |
0
|
||
Seminar / Workshop |
0
|
||
Oral Exam |
0
|
||
Midterms |
1
|
20
|
20
|
Final Exam |
1
|
30
|
30
|
Total |
150
|
COURSE LEARNING OUTCOMES AND PROGRAM QUALIFICATIONS RELATIONSHIP
#
|
Program Competencies/Outcomes |
* Contribution Level
|
||||
1
|
2
|
3
|
4
|
5
|
||
1 | To have adequate knowledge in Mathematics, Science, Computer Science and Software Engineering; to be able to use theoretical and applied information in these areas on complex engineering problems. |
|||||
2 | To be able to identify, define, formulate, and solve complex Software Engineering problems; to be able to select and apply proper analysis and modeling methods for this purpose. |
|||||
3 | To be able to design, implement, verify, validate, document, measure and maintain a complex software system, process, or product under realistic constraints and conditions, in such a way as to meet the requirements; ability to apply modern methods for this purpose. |
|||||
4 | To be able to devise, select, and use modern techniques and tools needed for analysis and solution of complex problems in software engineering applications; to be able to use information technologies effectively. |
X | ||||
5 | To be able to design and conduct experiments, gather data, analyze and interpret results for investigating complex Software Engineering problems. |
|||||
6 | To be able to work effectively in Software Engineering disciplinary and multi-disciplinary teams; to be able to work individually. |
|||||
7 | To be able to communicate effectively in Turkish, both orally and in writing; to be able to author and comprehend written reports, to be able to prepare design and implementation reports, to be able to present effectively, to be able to give and receive clear and comprehensible instructions. |
|||||
8 | To have knowledge about global and social impact of engineering practices and software applications on health, environment, and safety; to have knowledge about contemporary issues as they pertain to engineering; to be aware of the legal ramifications of Engineering and Software Engineering solutions. |
X | ||||
9 | To be aware of ethical behavior, professional and ethical responsibility; to have knowledge about standards utilized in engineering applications. |
|||||
10 | To have knowledge about industrial practices such as project management, risk management, and change management; to have awareness of entrepreneurship and innovation; to have knowledge about sustainable development. |
X | ||||
11 | To be able to collect data in the area of Software Engineering, and to be able to communicate with colleagues in a foreign language. ("European Language Portfolio Global Scale", Level B1) |
|||||
12 | To be able to speak a second foreign language at a medium level of fluency efficiently. |
|||||
13 | To recognize the need for lifelong learning; to be able to access information, to be able to stay current with developments in science and technology; to be able to relate the knowledge accumulated throughout the human history to Software Engineering. |
X |
*1 Lowest, 2 Low, 3 Average, 4 High, 5 Highest