First Contact Patterns: Read All the Code in One Hour and Skim

Lecture 27 of SE602 Software Re-Engineering investigates the 'First Contact' pattern cluster, which equips software engineers with rapid assessment techniques upon encountering an unfamiliar, undocumented million-line legacy codebase for the first time. Students study the celebrated Read all the Code in One Hour pattern: rather than getting lost in intricate algorithmic details, the engineer skims class names, file structures, and comments in a strictly time-boxed pass to gain intuitive architectural impressions and flag major problem areas. The lecture explores Skim the Documentation (validating whether existing manuals reflect current reality), Interview During Demo (observing end users operate the system to discover unwritten operational quirks), and Do a Mock Installation (testing build scripts and environmental dependencies to assess deployment fragility and configuration discipline). Consistent evaluation of control flow graphs, call graph hierarchies, and database schemas ensures robust preparation for academic assessments. Students investigate the trade-offs between system replacement, wrapping legacy components, and iterative code refactoring transformations. The discussion highlights how Lehman laws of evolution, system complexity growth, and declining quality necessitate continuous code restructuring. Key concepts including static program analysis, dynamic execution tracing, and characterization test safety nets are thoroughly demystified. The lecture details classical object-oriented re-engineering patterns demonstrated across standard enterprise software architectures. Structured refactoring methodologies are demonstrated using Martin Fowler catalogs, method extraction, and polymorphism replacement. Software quality attributes, maintainability index equations, and technical debt principal valuations are evaluated alongside empirical benchmarks. Architectural recovery processes are explored through module dependency analysis, component clustering, and high-level design reconstruction. Database schema normalization, legacy record migration, and automated ETL extraction pipelines are systematically analyzed. Monolithic application decomposition strategies including service-oriented architecture (SOA) and the Strangler Fig pattern are examined in depth. Scholars examine program slicing algorithms, forward and backward dependency slices, and impact assessment for proposed modifications. Automated tool support, bytecode instrumentation, and static code analyzers are evaluated to detect architectural violations across repositories. Risk management frameworks, business case evaluations, and cost estimation models such as COCOMO II are analyzed for migration projects.