About SE602 Assignment 1
SE602 Assignment No 1 for Spring 2026 is from Software Re-Engineering. It covers lesson 3: Week-3 : Software Maintenance, carries 20 marks and is due on VULMS by 11:59 pm on Monday 9 November 2026. You can request the solution from this page.
- Course
- SE602 Software Re-Engineering
- Assignment
- Assignment No 1
- Semester
- Spring 2026
- Lesson
- 3: Week-3 : Software Maintenance
- Total marks
- 20
- End date
- Mon 9 Nov, 11:59 pm
What SE602 Assignment 1 asks
This assignment requires the application of software re-engineering principles to two distinct scenarios involving legacy systems. You will analyze maintenance categories and evolution processes for a Core Banking System and evaluate architectural degradation in a healthcare management system. The work involves mapping change requests, designing implementation plans, and applying Lehman's Laws to real-world software challenges. You must produce a structured document addressing these specific maintenance and refactoring tasks.
-
1
Question 1: Maintenance Identification & Evolution Process Implementation
10 marksPart 1 requires mapping four specific banking system change requests to their correct maintenance categories with a one-sentence justification for each. Part 2 asks for a structured, non-coding implementation plan for the tax regulation update, covering impact analysis, system understanding, and release planning phases.
-
2
Question 2: Architectural Re-engineering & Lehman's Law Scenario Analysis
10 marksPart 1 involves explaining how Lehman's Law of Continuing Change and Lehman's Law of Increasing Complexity apply to the healthcare system, citing two symptoms for each. Part 2 requires proposing a re-engineering strategy to decompose the monolithic system, including methods for system decomposition, risk mitigation, and improving long-term maintainability.
- What to submit
- One doc or docx document with clear headings for each task.
- Topics covered
- Software maintenance categories Evolution process implementation Lehman's Laws Architectural refactoring System decomposition Legacy system analysis
A summary of the assignment file, Fall 2026_SE602_1.docx. Download the file for the full wording before you start.
Lesson covered
The questions in this assignment come from this lesson. Read it in the SE602 handout before you open the assignment file, then practise it with the MCQs and past papers.
Solution
The solution has not been added yet. Request it from the download box and it will be added to this page, usually within a day.
Before you submit on VULMS
- 1 Start on the questions in the assignment file now. The solution will be added to this page once it is written.
- 2 Write the final answer in your own words. VU checks assignments for copying, and copied work gets zero marks.
- 3 Save your answer in the file type the assignment file asks for, and name it with your student ID, for example BC260012345.
- 4 Open the file once more to check it is not empty or corrupted, then upload it on VULMS before 11:59 pm on Mon 9 Nov.
Questions about this assignment
When is SE602 Assignment 1 due?
Monday 9 November 2026 at 11:59 pm. VULMS does not accept files after the deadline.
When will the solution be added?
Most solutions are up within a day of a request. Requests tell us which ones to write first, and 0 students have asked for this one so far.
Can I submit the solution as it is?
No. VU checks assignments for copying, and copied work gets zero marks. Use the solution to check your method, then write your own answer.
What file do I submit?
The assignment file says which file type to upload and lists any extra instructions from your instructor. Name the file with your student ID before you upload it on VULMS.