Lifecycle roadmap is presented and different types of evolution and maintenance activities are placed on it. Status within industry and research is mapped out. Evolution laws are discussed and analyses in different contexts (the traditional, component-based, and open-source). Predelivery and transition maintenance models are studied and criteria for their success are identified. Impact analysis is studied. Different ways to manage customer problems are surveyed, both the critical (emergency) and non-critical ones. Retirement process model is considered. Finally, the quality attribute "maintainability" is discussed and compared to "bad smells".
ID2006 Software Evolution and Maintenance 7.5 credits
This course has been discontinued.
Last planned examination: Spring 2000
Decision to discontinue this course:
No information insertedInformation per course offering
Course offerings are missing for current or upcoming semesters.
Course syllabus as PDF
Please note: all information from the Course syllabus is available on this page in an accessible format.
Course syllabus ID2006 (Autumn 2007–)Content and learning outcomes
Course contents
Intended learning outcomes
After the accomplished course, the student should be able to
- plan for the whole software lifecycle in the initial phases of software development
- identify all support line levels involved in evolution and maintenance
- identify problems within the industry and research
- choose appropriate problem management method. The choice should be based on software criticality and problem urgency.
- explain differences among all the types of maintenance categories
- make decisions and manage legacy systems
- identify retirement activities
- evaluate agile methods from the lifecycle perspective
- motivate why it is important to build in evolvability/maintainability in a system
- describe and motivate evolution laws.
Literature and preparations
Specific prerequisites
- basic knowledge in software engineerign
Recommended prerequisites
Equipment
Literature
Kajko-Mattsson, Software Evolution and Maintenance, Compendium, DSV.
Examination and completion
If the course is discontinued, students may request to be examined during the following two academic years.
Grading scale
Examination
- INL1 - Assignment, 3.0 credits, grading scale: P, F
- TEN1 - Examination, 4.5 credits, grading scale: A, B, C, D, E, FX, F
Based on recommendation from KTH’s coordinator for disabilities, the examiner will decide how to adapt an examination for students with documented disability.
The examiner may apply another examination format when re-examining individual students.
Other requirements for final grade
- written exam, 4,5 credit points
- assignment, 3 credit points
Opportunity to complete the requirements via supplementary examination
Opportunity to raise an approved grade via renewed examination
Examiner
Ethical approach
- All members of a group are responsible for the group's work.
- In any assessment, every student shall honestly disclose any help received and sources used.
- In an oral assessment, every student shall be able to present and answer questions about the entire assignment and solution.
Further information
Course room in Canvas
Offered by
Main field of study
Education cycle
Add-on studies
Contact
Supplementary information
The course occasion in period P4, spring term 2011, will be canceled due to too few applicants.