Whereas many software engineering courses focus on building new systems from scratch, in industrial practice software developers are often confronted with already existing software systems that need to be maintained, reused or evolved. This requires specific skills to understand the design and implementation of an existing system and which parts need to be modified, to build software systems that are easier to maintain, and to design systems with reuse and evolution in mind from the very start.
This course will thus study a variety of techniques, tools and methodologies to help building software systems that are easier to understand, maintain, reuse and evolve:
- Software development in the context of an existing code base as opposed to "green field" development
o Software comprehension and concern location
o Change impact analysis
o Reverse engineering
- Software Maintenance
o Best programming practices
o Coding standards
o Design principles and heuristics
o Design patterns
- Software Reuse and Evolution
o The laws of software evolution
o Reuse techniques and design for reuse
o Libraries vs. application frameworks
- Software product lines, domain and feature modelling
Given the learning outcomes of the "Master in Computer Science and Engineering" program, this course contributes to the development, acquisition and evaluation of the following learning outcomes:
- INFO1.1 , INFO1.3
Given the learning outcomes of the "Master  in Computer Science" program, this course contributes to the development, acquisition and evaluation of the following learning outcomes:
Students completing successfully this course will be able to
- Understand the difficulties of developing code in a change context as opposed to 'green field' development
- Assess the impact of a change request to an existing product of medium size.
- Describe techniques, coding idioms and other mechanisms for implementing designs that are more maintainable.
- Understand how design patterns can improve the design of a software system.
- Refactor an existing software implementation to improve some aspect of its design.
- Identify the principal issues associated with software evolution and explain their impact on the software lifecycle.'
- Discuss the advantages and disadvantages of different types of software reuse.
The contribution of this Teaching Unit to the development and command of the skills and learning outcomes of the programme(s) can be accessed at the end of this sheet, in the section entitled “Programmes/courses offering this Teaching Unit”.
The course will be organized in 3 different modules that address a variety of techniques, tools and methodologies to help building software systems that are easier to understand, maintain, reuse and evolve:
- Software understanding : how to understand existing systems
- Software maintenance : how to build software that is more maintainable, or how to improve existing software to make it more maintainable
- Software reuse and evolution : how to build reusable software and how to reuse existing software
Theory sessions covering the different course topics
Practical sessions to apply the concepts in practice
- developing and evolving a maintainable and reusable software system
Missions to complete the application developed during the practical sessions
- [10%] Obligatory participation during practical sessions
- reviewing work of other groups
- [40%] intermediate missions in-between practical sessions
- presentation and demo of deliverables produced
- 2 missions (10% + 20%) throughout semester
- demo of 3rd mission (10%) at end of semester
- [50%] during exam session
- [25%] written exam
- [25%] presentation and discussion
- on 3rd mission + overall lessons learned throughout course
Even though good quality software may be easier to maintain and evolve, software quality assurance techniques will not be addressed explicitly in this course as they are the topic of a separate course on Software Quality Assurance [LINGI2251]
- Having a good knowledge of and experience with object-oriented programming concepts, algorithms and data structures.
- Having prior or simultaneous experience with the development of a medium- to large-scale software system.
The course slides as well as other relevant and practical information related to the course will be accessible on Moodle. The same platform will also be the means of communication between the teacher(s) and the students.