CMP672 - RESEARCH METHODS IN SOFTWARE ENGINEERING
| Course Name | Code | Semester | Theory (hours/week) |
Application (hours/week) |
Credit | ECTS |
|---|---|---|---|---|---|---|
| RESEARCH METHODS IN SOFTWARE ENGINEERING | CMP672 | Any Semester/Year | 3 | 0 | 3 | 9 |
| Prequisites | ||||||
| Course language | English | |||||
| Course type | Elective | |||||
| Mode of Delivery | Face-to-Face | |||||
| Learning and teaching strategies | Lecture Preparing and/or Presenting Reports Problem Solving Project Design/Management | |||||
| Instructor (s) | Vahid GAROUSI (Doçent), Ayça TARHAN (Yrd. Doçent) | |||||
| Course objective | The objective of this graduate course is to provide an understanding of research methods and their implementation in the field of software engineering. Target audience are new/ early-stage MSc and PhD students. | |||||
| Learning outcomes |
| |||||
| Course Content | ? Course introduction and overview ? Introduction to Research Methods in SE ? Systematic Literature Review (SLR) and Systematic Mapping (SM) studies and SM guideline papers ? Presentation of chosen SM papers ? Research design and Planning ? Experiments ? Case Studies ? Presentation of chosen Empirical SE (EMSE) papers ? Presentation of students SM work in the class | |||||
| References | ? Per Runeson, Martin Host, Austen Rainer, Bjorn Regnell, Case-Study Research in Software Engineering - Guidelines and Examples, John Wiley & Sons, 2012 ? R.K. Yin, Case study research: Design and methods (4th Ed.). Thousand Oaks, CA: Sage, 2009 ? Forrest Shull, Janice Singer, Dag I. K. Sjøberg, Guide to Advanced Empirical Software Engineering, Springer, 2007 ? Simon Gieseck, Research Methods in Software Engineering, GITO mbH Verlag, 2006 | |||||
Course outline weekly
| Weeks | Topics |
|---|---|
| Week 1 | Course introduction and overview, Introduction to Research Methods in SE |
| Week 2 | Introduction to Research Methods in SE |
| Week 3 | Research design and Planning |
| Week 4 | Research design and Planning |
| Week 5 | Systematic Literature Review (SLR) and Systematic Mapping (SM) studies and SM guideline papers |
| Week 6 | Systematic Literature Review (SLR) and Systematic Mapping (SM) studies and SM guideline papers |
| Week 7 | Presentation of chosen SM papers |
| Week 8 | Presentation of chosen SM papers |
| Week 9 | Experiments |
| Week 10 | Case Studies |
| Week 11 | Presentation of chosen Empirical SE (EMSE) papers |
| Week 12 | Presentation of students SM work in the class |
| Week 13 | Presentation of students SM work in the class |
| Week 14 | |
| Week 15 | |
| Week 16 | Final exam |
Assesment methods
| Course activities | Number | Percentage |
|---|---|---|
| Attendance | 0 | 5 |
| Laboratory | 0 | 0 |
| Application | 0 | 0 |
| Field activities | 0 | 0 |
| Specific practical training | 0 | 0 |
| Assignments | 0 | 0 |
| Presentation | 1 | 5 |
| Project | 1 | 50 |
| Seminar | 0 | 0 |
| Midterms | 0 | 0 |
| Final exam | 1 | 40 |
| Total | 100 | |
| Percentage of semester activities contributing grade succes | 0 | 50 |
| Percentage of final exam contributing grade succes | 0 | 50 |
| Total | 100 | |
WORKLOAD AND ECTS CALCULATION
| Activities | Number | Duration (hour) | Total Work Load |
|---|---|---|---|
| Course Duration (x14) | 14 | 3 | 42 |
| Laboratory | 0 | 0 | 0 |
| Application | 0 | 0 | 0 |
| Specific practical training | 0 | 0 | 0 |
| Field activities | 0 | 0 | 0 |
| Study Hours Out of Class (Preliminary work, reinforcement, ect) | 14 | 6 | 84 |
| Presentation / Seminar Preparation | 2 | 15 | 30 |
| Project | 1 | 42 | 42 |
| Homework assignment | 3 | 14 | 42 |
| Midterms (Study duration) | 0 | 0 | 0 |
| Final Exam (Study duration) | 1 | 26 | 26 |
| Total Workload | 35 | 106 | 266 |
Matrix Of The Course Learning Outcomes Versus Program Outcomes
| D.9. Key Learning Outcomes | Contrubition level* | ||||
|---|---|---|---|---|---|
| 1 | 2 | 3 | 4 | 5 | |
| 1. Graduates should have a mastery of computer science as described by the core of the Body of Knowledge. | X | ||||
| 2. Graduates need understanding of a number of recurring themes, such as abstraction, complexity, and evolutionary change, and a set of general principles, such as sharing a common resource, security, and concurrency. | X | ||||
| 3. Graduates of a computer science program need to understand how theory and practice influence each other. | X | ||||
| 4. Graduates need to think at multiple levels of detail and abstraction. | X | ||||
| 5. Students will be able to think critically, creatively and identify problems in their research. | X | ||||
| 6. Graduates should have been involved in at least one substantial project. | X | ||||
| 7. Graduates should realize that the computing field advances at a rapid pace. | X | ||||
| 8. Graduates should conduct research in an ethical and responsible manner. | X | ||||
| 9. Graduates should have good command of technical terms in both Turkish and English. | X | ||||
| 10. Graduates should understand the full range of opportunities available in computing. | X | ||||
| 11. Graduates should understand that computing interacts with many different domains. | X | ||||
| 12. Graduates should develop the knowledge acquired at master level and apply scientific methods in order to solve scientific problems. | X | ||||
*1 Lowest, 2 Low, 3 Average, 4 High, 5 Highest