██████╗ ███████╗██╗ ██╗███████╗██████╗ ███████╗███████╗
██╔══██╗██╔════╝██║ ██║██╔════╝██╔══██╗██╔════╝██╔════╝
██████╔╝█████╗ ██║ ██║█████╗ ██████╔╝███████╗█████╗
██╔══██╗██╔══╝ ╚██╗ ██╔╝██╔══╝ ██╔══██╗╚════██║██╔══╝
██║ ██║███████╗ ╚████╔╝ ███████╗██║ ██║███████║███████╗
╚═╝ ╚═╝╚══════╝ ╚═══╝ ╚══════╝╚═╝ ╚═╝╚══════╝╚══════╝
███████╗███╗ ██╗ ██████╗ ███████╗███╗ ██╗ ██████╗
██╔════╝████╗ ██║██╔════╝ ██╔════╝████╗ ██║██╔════╝
█████╗ ██╔██╗ ██║██║ ███╗█████╗ ██╔██╗ ██║██║ ███╗
██╔══╝ ██║╚██╗██║██║ ██║██╔══╝ ██║╚██╗██║██║ ██║
███████╗██║ ╚████║╚██████╔╝███████╗██║ ╚████║╚██████╔╝
╚══════╝╚═╝ ╚═══╝ ╚═════╝ ╚══════╝╚═╝ ╚═══╝ ╚═════╝
🎮 CASE OPENED: X-Ray a Legacy Codebase & Extract the Blueprint 🔬
MISSION BRIEFING 📡
You've been assigned to investigate the TransFleet Logistics application — a complex corporate fleet management system with decades of accumulated business logic, technical debt, and architectural mysteries. Your task: use Spec2Cloud to reverse-engineer this beast, extract API contracts, map data flows, document business rules, and create a comprehensive modernization blueprint.
This isn't your typical greenfield development. This is digital archaeology 🏛️. You're diving into:
- 🔥 150+ database tables of vehicle tracking madness
- 💀 1200-line service classes with nested business rules
- 👻 WCF services haunting the integration layer
- 🧩 Entity Framework EDMX with implicit relationships everywhere
- ⚡ Quartz.NET job chains triggering like dominos
- 📡 SignalR hubs broadcasting real-time vehicle positions
THE TWIST: Unlike surface-level analysis, Spec2Cloud performs deep code forensics to extract the hidden architecture, buried contracts, and undocumented business rules that make this application tick.
🕵️ INVESTIGATION TECHNIQUES
- ✅ Perform deep static analysis of complex enterprise codebases
- ✅ Extract API contracts from legacy Web API controllers & WCF services
- ✅ Reverse-engineer data models from Entity Framework EDMX & migrations
- ✅ Identify and catalog business rules embedded in service layer code
- ✅ Map integration points and external system dependencies
- ✅ Generate bounded context maps for microservice boundary discovery
- ✅ Create a complete modernization blueprint from extracted specs
💡 DETECTIVE SKILLS ACQUIRED
- 🔍 Code pattern recognition for specification extraction
- 📊 Dependency mapping and architecture visualization
- 🧩 Domain model reconstruction from scattered entities
- 🎯 Bounded context identification from code organization
- 📝 Technical debt documentation and migration planning
🔐 CLEARANCE LEVEL REQUIRED
- 🎓 C# & .NET Experience — You can read C# code without a decoder ring
- 🏗️ Enterprise Patterns Knowledge — Repository, Specification, Domain Services don't scare you
- 🌟 Spec2Cloud Basics — Complete the Spec2Cloud Introduction Lab first (recommended)
- 💻 Visual Studio 2022 — With .NET Framework 4.7.2 support installed
- 🐙 Git & GitHub — For cloning the evidence and pushing your findings
🎮 OPTIONAL POWER-UPS
- 🧠 Understanding of WCF services (legacy integration tech)
- 🗃️ SQL Server knowledge (for schema analysis)
- 🚀 Azure familiarity (for modernization target understanding)
🚨 CASE ACTIVATION SEQUENCE
# 🔍 Step 1: Clone the crime scene
git clone https://github.com/EmeaAppGbb/appmodlab-reverse-engineering-legacy-apps-with-spec2cloud.git
cd appmodlab-reverse-engineering-legacy-apps-with-spec2cloud
# 📂 Step 2: Checkout the legacy branch (the original codebase)
git checkout legacy
# 🔧 Step 3: Open the solution in Visual Studio
start TransFleet.sln
# 🏗️ Step 4: Build the project (compile the evidence)
# In Visual Studio: Build > Build Solution (Ctrl+Shift+B)
# 🎯 Step 5: Launch investigation mode
gh copilot-cli
# Then: "Let's analyze this codebase with Spec2Cloud!"🎬 EXPECTED OUTCOME:
You'll have the TransFleet application running locally, ready for deep analysis. Time to put on your detective hat! 🎩🔍
🗂️ EVIDENCE LOCKER LAYOUT
appmodlab-reverse-engineering-legacy-apps-with-spec2cloud/
│
├── 📋 APPMODLAB.md # Complete lab walkthrough & instructions
├── 📖 README.md # You are here! 👋
├── 🔧 .github/workflows/ # CI/CD pipelines for legacy build validation
│
├── 🏛️ TransFleet/ # THE LEGACY APPLICATION (branch: legacy)
│ ├── TransFleet.sln # Main solution file
│ ├── TransFleet.WebApi/ # 25+ API controllers (HTTP endpoints)
│ ├── TransFleet.Core/ # Service layer (1200-line classes 😱)
│ ├── TransFleet.Data/ # EF6 EDMX with 150+ entities
│ ├── TransFleet.WcfServices/ # WCF service contracts (legacy integrations)
│ ├── TransFleet.Jobs/ # Quartz.NET background jobs
│ └── TransFleet.Tests/ # 300+ unit tests (mostly green ✅)
│
├── 📊 SpecAnalysis/ # Spec2Cloud output (branch: solution)
│ ├── architecture-overview.md # Dependency maps & system diagrams
│ ├── api-contracts/ # OpenAPI specs extracted from controllers
│ ├── data-model/ # Reverse-engineered entity relationships
│ ├── business-rules/ # Cataloged business logic
│ ├── integration-specs/ # WCF & external system contracts
│ └── modernization-blueprint/ # Migration recommendations & strategy
│
└── 🎯 BoundedContexts/ # Discovered microservice boundaries
├── VehicleManagement/ # Partial implementation from specs
├── MaintenanceScheduling/ # Spec-driven microservice design
└── ComplianceReporting/ # DOT HOS compliance domain
🌳 BRANCH STRUCTURE (Investigation Checkpoints)
| Branch | Purpose | Emoji | Status |
|---|---|---|---|
main |
Complete lab with documentation | ✅ | Final Report |
legacy |
TransFleet application (as-is) | 🏛️ | Crime Scene |
solution |
Generated specs + partial implementation | 📊 | Case Solved |
step-1-static-analysis |
Code structure analysis output | 🔬 | Evidence #1 |
step-2-api-extraction |
API contracts & data contracts | 📡 | Evidence #2 |
step-3-data-modeling |
Data model from EDMX & migrations | 🗃️ | Evidence #3 |
step-4-business-rules |
Extracted business rule specs | 📜 | Evidence #4 |
step-5-integration-mapping |
WCF & integration specifications | 🔌 | Evidence #5 |
step-6-modernization-blueprint |
Complete modernization suite | 🎯 | Final Blueprint |
⚙️ TECHNOLOGY FOUND AT THE CRIME SCENE
The TransFleet application is built on a classic enterprise .NET stack from the mid-2010s era:
- 💀 ASP.NET Web API 2 on .NET Framework 4.7.2 (not .NET Core!)
- 🗄️ Entity Framework 6 with Database-First (EDMX files everywhere)
- 📡 WCF Services for telematics device communication
- 🐘 SQL Server 2014 with 150+ tables (some with 100M+ rows)
- 🔄 Hangfire — Background job processing
- 📻 SignalR — Real-time vehicle tracking updates
- 💉 AutoFac — Dependency injection container
- ⏰ Quartz.NET — Scheduled maintenance alerts
- 📊 SSRS — SQL Server Reporting Services for compliance reports
- 🏛️ Repository pattern over EF6
- 📋 Specification pattern for business rules
- 🎯 Domain services with complex orchestration
- 🔌 Adapter pattern for external integrations
- 🌐 Hub pattern for SignalR real-time messaging
- 1200-line
VehicleService.cswith deeply nested logic 🤯 - Business rules scattered across 60+ domain entities
- 200+ Entity Framework migrations (evolution history)
- Federal DOT regulations hardcoded in
ComplianceService.cs - Geofencing rules engine with spatial calculations
🚀 MODERNIZATION DESTINATION
After reverse-engineering with Spec2Cloud, you'll have a complete modernization blueprint guiding the transformation:
- ☁️ .NET 9 Microservices on Azure Container Apps
- 📊 Bounded Contexts discovered from legacy codebase analysis
- 🔌 Clean API Contracts extracted and refined
- 🗃️ Modern Data Models based on reverse-engineered entities
- 📜 Documented Business Rules ready for reimplementation
- 🏗️ Architecture Overview — System diagrams & dependency maps
- 📡 API Contracts — OpenAPI 3.0 specs for all endpoints
- 🗄️ Data Model Specs — Entity relationships & schema documentation
- 📋 Business Rules Catalog — Extracted logic in readable format
- 🔌 Integration Specs — External system contracts & protocols
- 🎯 Bounded Context Map — Recommended microservice boundaries
- 📝 Migration Blueprint — Step-by-step modernization strategy
🎓 THE GOAL:
Quality and completeness of reverse-engineered specifications — the blueprint that makes modernization predictable, plannable, and successful! 🏆
🔍 INVESTIGATION PHASES
This lab uses GitHub Copilot CLI in agent mode to perform the reverse engineering. You'll work interactively with Copilot to analyze the codebase and extract specifications.
# EVIDENCE FOUND: Understanding the domain
@github copilot "Analyze the TransFleet solution structure and summarize the main components"
@github copilot "What business domain does this application serve? List the key workflows"# INTEL GATHERED: Code structure & dependencies
@github copilot "Use Spec2Cloud to analyze the code structure and generate a dependency map"
@github copilot "Identify the layers, patterns, and architectural style used in TransFleet"# MYSTERY SOLVED: API endpoints documented
@github copilot "Extract OpenAPI specifications from all Web API controllers"
@github copilot "Document the WCF service contracts in the WcfServices project"# BLUEPRINT ACQUIRED: Database schema mapped
@github copilot "Analyze the EDMX file and extract entity relationships"
@github copilot "Map the migration history to understand database evolution"# RULES OF ENGAGEMENT: Logic cataloged
@github copilot "Extract business rules from VehicleService, MaintenanceService, and ComplianceService"
@github copilot "Document the DOT Hours of Service compliance calculations"# EXTERNAL CONNECTIONS: Integration specs documented
@github copilot "Catalog all WCF service dependencies and external system integrations"
@github copilot "Document the telematics device communication protocol"# CONTEXT MAPPING: Microservice boundaries discovered
@github copilot "Analyze the codebase and suggest bounded context boundaries for microservices"
@github copilot "Group the entities and services into logical domains"# HUMAN INSIGHT: Spec validation & enhancement
@github copilot "Review the generated specifications for accuracy and completeness"
@github copilot "Add domain knowledge and correct any misinterpretations in the specs"# CASE CLOSED: Complete specification suite assembled
@github copilot "Generate a comprehensive modernization blueprint with migration recommendations"
@github copilot "Prioritize the bounded contexts for implementation order"📋 DETAILED INSTRUCTIONS:
See APPMODLAB.md for the complete step-by-step walkthrough with screenshots, sample outputs, and troubleshooting tips! 🚀
🎯 ESTIMATED INVESTIGATION TIME
- ⚡ Quick Scan: 3 hours (core analysis only)
- 🔍 Full Investigation: 5–7 hours (complete spec extraction)
- 🏆 Deep Dive: 8+ hours (with refinement & validation)
⏰ BREAKDOWN:
| Phase | Time | Description |
|---|---|---|
| 🕵️ Explore Codebase | 45 min | Build, run, understand domain |
| 🔬 Static Analysis | 1 hour | Dependency mapping & architecture |
| 📡 API Extraction | 1.5 hours | OpenAPI specs from controllers & WCF |
| 🗃️ Data Modeling | 1.5 hours | EDMX analysis & entity relationships |
| 📜 Business Rules | 2 hours | Service layer logic extraction |
| 🔌 Integration Mapping | 1 hour | External system documentation |
| 🎯 Bounded Contexts | 1 hour | Microservice boundary discovery |
| 🧠 Review & Refine | 1 hour | Spec validation & enhancement |
| 🏆 Blueprint Assembly | 30 min | Final modernization strategy |
💡 PRO TIP: Take breaks between phases! This is an investigation marathon, not a sprint. Your brain needs time to process the architecture patterns. 🧠☕
🔗 INTEL LINKS & REFERENCES
- 🌟 Spec2Cloud Official Docs — Tool capabilities & usage
- 🎯 GitHub Copilot CLI Guide — Agent mode instructions
- 🏗️ Modernization Patterns — Azure architecture guidance
- 🌟 Spec2Cloud Introduction Lab — Learn the basics first!
- 🔄 Legacy to Modern Migration Lab — Next step after specs
- ☁️ Azure Container Apps Deployment — Deploy your microservices
- 💻 Visual Studio 2022 — IDE for .NET development
- 🐙 GitHub CLI — GitHub Copilot CLI integration
- 🗃️ SQL Server Express — Database for local testing
- 🏛️ Entity Framework 6 EDMX — Database-First modeling
- 📡 WCF Services — Legacy service technology
- 🎯 Domain-Driven Design — Bounded contexts explained
- 🔄 Strangler Fig Pattern — Incremental modernization
- 💬 GitHub Discussions — Ask questions, share findings
- 🐛 Report Issues — Found a bug? Let us know!
- 🌟 Contribute — Improve this lab for others
🔍 WHAT MAKES THIS LAB SPECIAL?
This isn't a toy application. TransFleet is a realistic enterprise system with:
- ✅ Real complexity — 1200-line service classes, 150+ tables, WCF integrations
- ✅ Real patterns — Repository, Specification, Domain Services, Adapters
- ✅ Real challenges — Technical debt, scattered business rules, implicit dependencies
- ✅ Real value — Skills that transfer directly to modernization projects
🎯 YOU'LL WALK AWAY WITH:
- 🧠 Confidence in analyzing complex legacy codebases
- 🛠️ Spec2Cloud expertise for reverse engineering
- 📊 A complete modernization blueprint
- 🚀 Skills for your next enterprise migration project
🕵️ MYSTERY AWAITS...
The TransFleet codebase holds decades of business knowledge. Your mission: extract it, document it, and make it modern.
CASE STATUS: 🔓 OPEN
LEAD INVESTIGATOR: YOU 🎯
OBJECTIVE: EXTRACT THE BLUEPRINT 🏆
👉 BEGIN LAB: Open APPMODLAB.md 👈
🌟 BUILT WITH ❤️ BY THE EMEA APP GBB TEAM 🌟
╔═══════════════════════════════════════════════════════════╗
║ 🕹️ PRESS START TO BEGIN YOUR INVESTIGATION 🕹️ ║
║ ║
║ 🔍 EVIDENCE GATHERED · 📡 INTEL ANALYZED · 🎯 CASE ║
║ SOLVED WITH SPEC2CLOUD! 🏆 ║
╚═══════════════════════════════════════════════════════════╝