Re-Engineering Decision Frameworks and Portfolio Analysis

Lecture 4 of SE602 Software Re-Engineering explores decision-making frameworks and portfolio analysis techniques that guide organizational modernization strategies. Students examine the classic 2x2 legacy portfolio matrix evaluating systems along two orthogonal axes: Technical Quality and Business Value. Systems with high business value and low technical quality represent prime candidates for comprehensive re-engineering; systems with low business value and low technical quality are marked for immediate scrapping; systems with high quality and high value require continued routine maintenance; while systems with low value and high quality should be frozen or replaced with commercial off-the-shelf (COTS) alternatives. The lecture covers quantitative Return on Investment (ROI) models, risk assessment matrices, and technical debt principal calculations that justify re-engineering investments to executive steering committees in commercial software engineering contexts. Legal and ethical constraints surrounding reverse engineering, clean-room design implementations, and software intellectual property rights are reviewed. By engaging with solved past papers by Moaaz and Waqar Siddhu, learners gain actionable insights into recurrent university exam questions. Interactive quiz assessments on VU SIGMA facilitate rapid knowledge verification and retention of critical software re-engineering concepts. Comprehensive coverage of standard academic benchmarks ensures learners communicate with technical precision across software engineering disciplines. Detailed analysis of code smell topologies highlights the imperative of eradicating duplicate logic, long methods, and bloated god classes. Test harness construction including characterization testing and regression suites are contrasted with traditional unit testing strategies. Students evaluate the trade-offs between big-bang system rewrites and progressive evolutionary refactoring in mission-critical environments. The lesson explores cognitive program comprehension models, top-down hypothesis validation, and mental mappings of complex legacy architectures. Practical code illustrations demonstrate safe code transformations, automated refactoring preconditions, and behavioral equivalence preservation. Scholars analyze Chidamber-Kemerer object-oriented metrics including WMC, CBO, and RFC to quantify the architectural impact of refactoring. Cloud migration pathways including rehosting, replatforming, and cloud-native refactoring are examined as extensions of legacy modernization. The relationship between technical debt accumulation, architectural degradation, and long-term enterprise software viability is reinforced.