GRADUATE SCHOOL
M.SC. in Computer Engineering (With Thesis)
CE 612 | Course Introduction and Application Information
| Course Name |
Software Evolution and Maintenance
|
|
Code
|
Semester
|
Theory
(hour/week) |
Application/Lab
(hour/week) |
Local Credits
|
ECTS
|
|
CE 612
|
Fall/Spring
|
3
|
0
|
3
|
7.5
|
| Prerequisites |
None
|
|||||
| Course Language |
English
|
|||||
| Course Type |
Elective
|
|||||
| Course Level |
Third Cycle
|
|||||
| Mode of Delivery | - | |||||
| Teaching Methods and Techniques of the Course | - | |||||
| Course Coordinator | - | |||||
| Course Lecturer(s) | ||||||
| Assistant(s) | - | |||||
| Course Objectives | This course provides doctoral students an in-depth knowledge of the various aspects of software evolution and maintenance. It covers the laws of software evolution and the means to control them, evolution and maintenance models, reengineering, refactoring and reuse techniques and processes for migration of legacy information systems. |
| Learning Outcomes |
The students who succeeded in this course;
|
| Course Description | This course specifies definitions and concepts, software evolution and maintenance processes, reengineering, refactoring and reuse techniques in software engineering. |
|
|
Core Courses | |
| Major Area Courses | ||
| Supportive Courses | ||
| Media and Management Skills Courses | ||
| Transferable Skill Courses |
WEEKLY SUBJECTS AND RELATED PREPARATION STUDIES
| Week | Subjects | Related Preparation |
| 1 | Introduction, IEEE Std 1219 | |
| 2 | The context of software evolution and maintenance | Grubb and Takang, ch.1; Tripathy and Naik ch. 1 |
| 3 | The maintenance framework. | Grubb and Takang, ch.2; Tripathy and Naik ch. 2; Pressman, ch. 29 |
| 4 | Software change | Grubb and Takang, ch.3 |
| 5 | Limitations and economic implications to software change | Grubb and Takang, ch.4 |
| 6 | Maintenance process | Grubb and Takang, ch.5; ISO/IEC 14764 |
| 7 | Program understanding | Grubb and Takang, ch.6 |
| 8 | Reverse engineering | Grubb and Takang, ch.7; Tripathy and Naik ch. 4 |
| 9 | Midterm exam | |
| 10 | Reuse and reusability | Grubb and Takang, ch.8 |
| 11 | Management and organizational issues | Grubb and Takang, ch.10 |
| 12 | Legacy Information Systems | Tripathy and Naik ch. 5 |
| 13 | Software sustainability | |
| 14 | Review | |
| 15 | Review | |
| 16 | Fınal |
| Course Notes/Textbooks | |
| Suggested Readings/Materials | Grubb P. and Takang A.A., Software Maintenance Concepts and Practice, 2e, World Scientific, 2003. Sommerville I., Software Engineering, 10e, AddisonWesley, 2016. Pressman R.S., Software Engineering: A Practitioners Approach, 7e, McGrawHill, 2010. SWEBOK V3.0, Guide to the Software Engineering Body of Knowledge: 2014, Ed: Bourque P. and Fairley R.E., IEEE, 2014. April, Abran & Dumke, What do you need to know about Software Maintenance? Maintenance and assest management, 2005, vol. 20, no 2, pp. 32-37. Lanubile and Visaggio, Iterative Reengineering to compensate for QuickFix Maintenance, IEEE, 1995, International Conference on Software Maintenance, pp.140-146. Canfora and Cimitile, Software Maintenance, 2000, http://www.compaid.com/caiInternet/ezine/maintenancecanfora.pdf. Jones C., The Economics of Software Maintenance in the Twenty First Century, 2006. Tripathy P. and Naik K., Software evolution and maintenance: a practitioner’s approach, Wiley, 2015. |
EVALUATION SYSTEM
| Semester Activities | Number | Weigthing |
| Participation | ||
| Laboratory / Application | ||
| Field Work | ||
| Quizzes / Studio Critiques | ||
| Portfolio | ||
| Homework / Assignments |
1
|
25
|
| Presentation / Jury | ||
| Project | ||
| Seminar / Workshop | ||
| Oral Exams | ||
| Midterm |
1
|
25
|
| Final Exam |
1
|
50
|
| Total |
| Weighting of Semester Activities on the Final Grade |
2
|
60
|
| Weighting of End-of-Semester Activities on the Final Grade |
1
|
40
|
| 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 |
15
|
4
|
60
|
| Field Work |
0
|
||
| Quizzes / Studio Critiques |
0
|
||
| Portfolio |
0
|
||
| Homework / Assignments |
1
|
30
|
30
|
| Presentation / Jury |
0
|
||
| Project |
0
|
||
| Seminar / Workshop |
0
|
||
| Oral Exam |
0
|
||
| Midterms |
1
|
30
|
30
|
| Final Exam |
1
|
57
|
57
|
| Total |
225
|
COURSE LEARNING OUTCOMES AND PROGRAM QUALIFICATIONS RELATIONSHIP
|
#
|
Program Competencies/Outcomes |
* Contribution Level
|
||||
|
1
|
2
|
3
|
4
|
5
|
||
| 1 | Accesses information in breadth and depth by conducting scientific research in Computer Engineering; evaluates, interprets and applies information. |
|||||
| 2 | Is well-informed about contemporary techniques and methods used in Computer Engineering and their limitations. | |||||
| 3 | Uses scientific methods to complete and apply information from uncertain, limited or incomplete data; can combine and use information from different disciplines. |
|||||
| 4 | Is informed about new and upcoming applications in the field and learns them whenever necessary. | |||||
| 5 | Defines and formulates problems related to Computer Engineering, develops methods to solve them and uses progressive methods in solutions. |
|||||
| 6 | Develops novel and/or original methods, designs complex systems or processes and develops progressive/alternative solutions in designs | |||||
| 7 | Designs and implements studies based on theory, experiments and modelling; analyses and resolves the complex problems that arise in this process. |
|||||
| 8 | Can work effectively in interdisciplinary teams as well as teams of the same discipline, can lead such teams and can develop approaches for resolving complex situations; can work independently and takes responsibility. |
|||||
| 9 | Engages in written and oral communication at least in Level B2 of the European Language Portfolio Global Scale. |
|||||
| 10 | Communicates the process and the results of his/her studies in national and international venues systematically, clearly and in written or oral form. |
|||||
| 11 | Is knowledgeable about the social, environmental, health, security and law implications of Computer Engineering applications, knows their project management and business applications, and is aware of their limitations in Computer Engineering applications. |
|||||
| 12 | Highly regards scientific and ethical values in data collection, interpretation, communication and in every professional activity. |
|||||
*1 Lowest, 2 Low, 3 Average, 4 High, 5 Highest