[{"data":1,"prerenderedAt":564},["ShallowReactive",2],{"site-schema":3,"article-zh-tw-ai-coding-tools-legacy-system-refactoring":106,"article-related-zh-tw-ai-coding-tools-legacy-system-refactoring":550},{"@context":4,"@graph":5},"https:\u002F\u002Fschema.org",[6,85,97],{"@type":7,"@id":8,"name":9,"alternateName":10,"description":17,"knowsAbout":18,"legalName":27,"foundingDate":28,"numberOfEmployees":29,"taxID":30,"url":31,"logo":32,"founder":33,"contactPoint":35,"address":49,"location":55,"sameAs":75},"Organization","https:\u002F\u002Fjoinx.co\u002F#organization","JoinX哲煜科技",[11,12,13,14,15,16],"JoinX","TWJOIN","哲煜科技","哲煜科技股份有限公司","TWJOIN 哲煜科技","twjoin.com","JoinX 哲煜科技（原品牌名 TWJOIN）是 2016 年在台北成立的軟體開發公司，80+ 人自有團隊，承接客製系統、APP、AI 導入與 IoT 開發，以及軟體外包與既有系統接手維運，服務 220+ 客戶、完成 520+ 專案。",[19,20,21,22,23,24,25,26],"軟體外包","客製化系統開發","APP 開發","AI 導入","AI Agent 開發","IoT APP 開發","ERP 系統整合","既有系統接手維運","JoinX Co., Ltd.","2016-04-28",80,"43774383","https:\u002F\u002Fjoinx.co","https:\u002F\u002Fjoinx.co\u002Fimages\u002Flogo-with-name.png",{"@id":34},"https:\u002F\u002Fjoinx.co\u002F#person-jack-lee",[36],{"@type":37,"contactType":38,"url":39,"telephone":40,"email":41,"areaServed":42,"availableLanguage":45},"ContactPoint","customer service","https:\u002F\u002Fjoinx.co\u002Fcontact-us","+886-2-8771-9095","service@joinx.co",[43,44],"TW","JP",[46,47,48],"zh-Hant","en","ja",{"@type":50,"streetAddress":51,"postalCode":52,"addressLocality":53,"addressRegion":54,"addressCountry":43},"PostalAddress","民生東路二段170號8樓","104","台北市中山區","台灣",[56,63,69],{"@type":57,"name":58,"address":59},"Place","JoinX 台中辦公室",{"@type":50,"streetAddress":60,"postalCode":61,"addressLocality":62,"addressRegion":54,"addressCountry":43},"台灣大道二段360號21樓C室","40453","台中市北區",{"@type":57,"name":64,"address":65},"JoinX 高雄辦公室",{"@type":50,"streetAddress":66,"postalCode":67,"addressLocality":68,"addressRegion":54,"addressCountry":43},"民族一路80號2樓之一","807","高雄市三民區",{"@type":57,"name":70,"address":71},"JoinX 東京辦公室",{"@type":50,"streetAddress":72,"postalCode":73,"addressLocality":74,"addressCountry":44},"東五反田5-22-37 Office Circle N 五反田 9樓","141-0022","東京都品川區",[76,77,78,79,80,81,82,83,84],"https:\u002F\u002Fwww.crunchbase.com\u002Forganization\u002Ftwjoin","https:\u002F\u002Fwww.facebook.com\u002FJoinX.TW","https:\u002F\u002Ftw.linkedin.com\u002Fcompany\u002F%E5%93%B2%E7%85%9C%E7%A7%91%E6%8A%80","https:\u002F\u002Fwww.youtube.com\u002Fc\u002Fjoinstuido%E5%93%B2%E7%85%9C%E7%A7%91%E6%8A%80","https:\u002F\u002Fmedium.com\u002Ftwjoin","https:\u002F\u002Fwww.104.com.tw\u002Fcompany\u002F1a2x6bjomb","https:\u002F\u002Fclutch.co\u002Fprofile\u002Fjoinx","https:\u002F\u002Fwww.goodfirms.co\u002Fcompany\u002Ftwjoin","https:\u002F\u002Ftwjoin.com",{"@type":86,"@id":34,"name":87,"alternateName":88,"jobTitle":89,"worksFor":90,"url":91,"sameAs":92},"Person","李秉哲","Jack Lee","創辦人暨執行長",{"@id":8},"https:\u002F\u002Fjack88.joinx.co\u002F",[93,94,95,96],"https:\u002F\u002Fwww.instagram.com\u002Fjack88.podcast\u002F","https:\u002F\u002Fwww.threads.net\u002F@jack88.podcast","https:\u002F\u002Fjoinx.co\u002Fjack88\u002F","https:\u002F\u002Fwww.linkedin.com\u002Fin\u002Fjacklee-taiwan\u002F",{"@type":98,"@id":99,"url":31,"name":9,"alternateName":100,"publisher":101,"inLanguage":102},"WebSite","https:\u002F\u002Fjoinx.co\u002F#website",[11,13,9],{"@id":8},[103,104,105],"zh-Hant-TW","en-US","ja-JP",{"id":107,"title":108,"body":109,"category":512,"cover":513,"dateModified":514,"description":515,"extension":516,"faq":514,"hasCoverTitle":517,"locale":518,"meta":519,"navigation":520,"need":521,"path":522,"seo":523,"seoDescription":514,"seoTitle":514,"sources":524,"stem":540,"takeaways":541,"time":547,"type":548,"__hash__":549},"content\u002Fzh-tw\u002Farticle\u002Fai-coding-tools-legacy-system-refactoring.md","用 Claude Code 這類 AI 工具改版既有系統：盤點、測試、逐步替換與審查",{"type":110,"value":111,"toc":493},"minimark",[112,120,125,128,131,134,138,141,144,178,187,191,194,197,200,204,207,210,249,252,256,259,348,351,354,358,361,364,390,393,397,400,454,457,462,465,469,472,476,479,483,486,490],[113,114,115,119],"p",{},[116,117,118],"strong",{},"既有系統可以用 Claude Code 這類 AI 寫程式工具來改版，但要照順序來：先盤點、再建立測試保護網、接著逐步替換，每一次修改都由人審查後才合併。"," 跳過前兩步、直接叫 AI 把舊系統重寫一遍，最常見的結果是新程式看起來比較乾淨，卻漏掉了舊系統裡多年累積的例外規則。下面從開發團隊的角度，說明每一步 AI 能做什麼、人要負責什麼，以及 JoinX 使用 AI 工具時的實際做法。",[121,122,124],"h2",{"id":123},"ai-寫程式工具適合用在既有系統改版嗎","AI 寫程式工具適合用在既有系統改版嗎？",[113,126,127],{},"適合，但它的價值在讓改版更完整、更不容易漏，而不是讓人少看程式。既有系統的風險在看不見的規則，AI 能幫忙把規則找出來、寫成測試，最後判斷仍要由人來做。",[113,129,130],{},"Claude Code 是在終端機裡運作的 AI 寫程式工具，可以讀取整個專案、搜尋程式碼、執行指令與測試，並依指示修改檔案。這類工具和只在編輯器裡補完一行程式的工具不同，它能一次看懂跨檔案的關聯，所以特別適合用在改版前的盤點與改版中的重構。",[113,132,133],{},"但既有系統和新專案不一樣。新專案的規格寫在需求文件裡；既有系統的規格，有一大部分只存在程式碼、資料與資深同仁的記憶裡。Michael Feathers 在《Working Effectively with Legacy Code》裡把「沒有測試的程式碼」直接定義為舊程式碼，因為沒有測試，就沒辦法確認修改有沒有改壞東西。AI 工具改的速度越快，這個風險就越大，所以順序比工具本身更重要。",[121,135,137],{"id":136},"改版前ai-能怎麼協助盤點既有系統","改版前，AI 能怎麼協助盤點既有系統？",[113,139,140],{},"AI 能快速讀完整個程式庫，整理出模組、資料流、外部串接與高風險區域，讓團隊在動手前就知道系統長什麼樣子。盤點的產出要經過工程師與使用者確認，不能直接當成規格。",[113,142,143],{},"盤點時我們會請 AI 協助整理下列項目，再由工程師逐項核對：",[145,146,147,154,160,166,172],"ul",{},[148,149,150,153],"li",{},[116,151,152],{},"模組與相依關係："," 哪些模組互相呼叫、哪些共用同一張資料表，改一處會牽動哪裡。",[148,155,156,159],{},[116,157,158],{},"資料流："," 一筆訂單、一張單據從建立到結案經過哪些程式與資料表。",[148,161,162,165],{},[116,163,164],{},"外部串接："," 和 ERP、金流、帳號系統或其他服務交換資料的位置與格式。",[148,167,168,171],{},[116,169,170],{},"高風險區域："," 沒有測試、邏輯特別長、近期常出錯，或寫死了日期、金額規則的地方。",[148,173,174,177],{},[116,175,176],{},"疑似商業規則："," 看起來很奇怪的條件分支，列成清單請使用者確認是規則還是錯誤。",[113,179,180,181,186],{},"最後一項最重要。AI 看得出某個分支「很奇怪」，但看不出那是十年前某個大客戶的特殊合約，還是當年的錯誤。這份清單要拿去問實際使用系統的同仁，答案寫回規格裡。完整的接手盤點項目，可以參考",[182,183,185],"a",{"href":184},"\u002Farticle\u002Flegacy-system-takeover-guide\u002F","舊系統接手、重構與重寫的完整指南","。",[121,188,190],{"id":189},"為什麼改程式之前要先建立測試保護網","為什麼改程式之前要先建立測試保護網？",[113,192,193],{},"因為測試是唯一能證明「改完之後行為沒變」的方法。先用測試把現有行為固定下來，之後不管是人還是 AI 修改程式，只要測試沒過就不合併，改版的風險才控制得住。",[113,195,196],{},"舊系統常常完全沒有測試。這時候要先補的不是理想中的單元測試，而是「特性測試」（characterization test）：把系統現在的實際輸出記錄下來，當成基準。即使現在的行為有錯，也先照實記錄，等確認是錯誤之後再另外修正，避免重構和修錯混在同一次修改裡。",[113,198,199],{},"AI 很適合協助補這類測試：讀懂一段計算邏輯之後，列出邊界條件，產生測試資料與測試案例。但測試要測什麼，由工程師依商業風險決定。帳務、權限、庫存這類出錯代價高的流程優先，畫面排版這類容易看出問題的地方可以晚一點。測試資料一律使用假資料或去識別化的資料，不放真實的客戶個資。",[121,201,203],{"id":202},"怎麼用-sdd-tdd-逐步替換舊模組","怎麼用 SDD + TDD 逐步替換舊模組？",[113,205,206],{},"一次替換一個模組，每個模組都先寫規格、再寫測試、最後才改程式，新舊並行確認一致後才切換。這種逐步替換的方式，讓系統在改版期間一直保持可用，出問題也只影響一小塊。",[113,208,209],{},"JoinX 的開發流程是 SDD + TDD：SDD（規格驅動開發）先把要改的行為寫成規格，TDD（測試驅動開發）再用測試驗證程式符合規格。用在既有系統改版時，每個模組的步驟如下：",[211,212,213,219,225,231,237,243],"ol",{},[148,214,215,218],{},[116,216,217],{},"選出第一個模組。"," 挑邊界清楚、測試補得起來、出錯影響範圍可控的模組，不要第一步就挑最核心的帳務。",[148,220,221,224],{},[116,222,223],{},"寫規格。"," 把盤點結果與使用者確認過的規則寫成規格，包含例外情況與要保留的舊行為。",[148,226,227,230],{},[116,228,229],{},"補測試。"," 依規格寫測試，並確認測試在舊程式上全部通過，證明測試描述的是現在的行為。",[148,232,233,236],{},[116,234,235],{},"替換實作。"," 由工程師拆好任務，AI 協助產生新程式，跑同一組測試直到全部通過。",[148,238,239,242],{},[116,240,241],{},"新舊並行。"," 必要時讓新舊模組同時處理同一批資料，比對結果一致後才把流量切過去。",[148,244,245,248],{},[116,246,247],{},"人工審查後合併。"," 審查通過、測試全過、部署有回復方案，才合併並上線。",[113,250,251],{},"Martin Fowler 在《Refactoring》中強調，重構是一連串「小步、不改變外部行為」的修改，每一步都要有測試保護。AI 讓每一步走得更快，但步伐不能因此變大；一次修改的範圍越小，審查越看得清楚。",[121,253,255],{"id":254},"ai-產出的程式碼要怎麼審查","AI 產出的程式碼要怎麼審查？",[113,257,258],{},"和人寫的程式碼走同一套審查，標準不因為是 AI 寫的而降低。審查重點放在規則有沒有保留、權限與資料有沒有被改動、相依套件是否可靠，這些都要由負責的工程師簽核。",[260,261,262,278],"table",{},[263,264,265],"thead",{},[266,267,268,272,275],"tr",{},[269,270,271],"th",{},"審查項目",[269,273,274],{},"AI 可以協助",[269,276,277],{},"人負責的判斷",[279,280,281,293,304,315,326,337],"tbody",{},[266,282,283,287,290],{},[284,285,286],"td",{},"規則是否保留",[284,288,289],{},"比對新舊程式的分支差異，列出可能遺漏的條件",[284,291,292],{},"確認每條差異是刻意修改還是遺漏",[266,294,295,298,301],{},[284,296,297],{},"測試是否足夠",[284,299,300],{},"指出沒被測試覆蓋的程式路徑，補邊界案例",[284,302,303],{},"決定哪些風險一定要測、哪些可以接受",[266,305,306,309,312],{},[284,307,308],{},"權限與資料存取",[284,310,311],{},"找出新增或變更的查詢、欄位與權限檢查",[284,313,314],{},"確認沒有越權讀取，個資存取符合規範",[266,316,317,320,323],{},[284,318,319],{},"相依套件",[284,321,322],{},"列出新增的套件與版本、已知弱點",[284,324,325],{},"決定是否採用，確認授權條款",[266,327,328,331,334],{},[284,329,330],{},"效能與相容性",[284,332,333],{},"找出可能的大量查詢或迴圈",[284,335,336],{},"用實際資料量驗證，確認舊資料相容",[266,338,339,342,345],{},[284,340,341],{},"部署與回復",[284,343,344],{},"整理變更清單與設定差異",[284,346,347],{},"核准上線時間與回復方案",[113,349,350],{},"美國 NIST 的安全軟體開發框架（SP 800-218）把程式碼審查、弱點檢查與第三方元件管理列為基本要求，不論程式碼由誰產生。JoinX 交付前會自行完成原始碼掃描與弱點掃描；需要黑箱測試時委由第三方執行，JoinX 可協助聯繫、推薦廠商，並在修補找到的弱點後再交付。",[352,353],"article-cta",{},[121,355,357],{"id":356},"把原始碼放進-ai-工具資料安全怎麼管","把原始碼放進 AI 工具，資料安全怎麼管？",[113,359,360],{},"JoinX 會把原始碼放進 AI 工具，使用的是企業版或商用方案，依合約或服務條款不會拿客戶資料訓練模型；帳號密碼、金鑰與個人資料等機敏內容不放進 AI 工具。這些做法會在合作前跟客戶說清楚。",[113,362,363],{},"具體的做法有四點：",[145,365,366,372,378,384],{},[148,367,368,371],{},[116,369,370],{},"原始碼會放進 AI 工具。"," 盤點、補測試與重構都需要 AI 讀到程式碼，這是我們的實際做法，不會隱瞞。",[148,373,374,377],{},[116,375,376],{},"使用企業版，不拿資料訓練模型。"," 我們使用企業版或商用方案的 AI 工具，依合約或服務條款，客戶的資料不會被用來訓練模型。",[148,379,380,383],{},[116,381,382],{},"機敏資料不放進 AI 工具。"," 帳號密碼、API 金鑰、憑證、正式環境的連線設定與個人資料，都不放進 AI 工具；測試使用假資料或去識別化的資料。個人資料的處理依《個人資料保護法》辦理。",[148,385,386,389],{},[116,387,388],{},"做不到全程不使用 AI。"," 我們的開發流程已經以 AI 協作為基礎，如果客戶要求整個專案完全不使用 AI，我們做不到，會在報價與簽約前說清楚，不會先答應再想辦法。",[113,391,392],{},"客戶有自己的 AI 使用政策時，例如某些目錄不能放進外部工具，或要求使用指定的服務，可以在合作前一起確認範圍。",[121,394,396],{"id":395},"這篇和-ai-協作開發舊系統接手的文章有什麼不同","這篇和 AI 協作開發、舊系統接手的文章有什麼不同？",[113,398,399],{},"這篇只談一件事：既有系統改版時，怎麼安全地使用 AI 寫程式工具。AI 協作開發的整體流程、成本結構，以及舊系統接手的評估方式，各有專文說明。",[260,401,402,412],{},[263,403,404],{},[266,405,406,409],{},[269,407,408],{},"想了解的問題",[269,410,411],{},"建議閱讀",[279,413,414,425,436,446],{},[266,415,416,419],{},[284,417,418],{},"AI 協作開發的整體流程與人機分工",[284,420,421],{},[182,422,424],{"href":423},"\u002Farticle\u002Fai-assisted-development-process\u002F","為什麼 AI 協作開發能省 30% 成本：JoinX 的實際流程公開",[266,426,427,430],{},[284,428,429],{},"AI 協作開發怎麼兼顧成本與品質",[284,431,432],{},[182,433,435],{"href":434},"\u002Farticle\u002Fai-assisted-development-cost-reduction\u002F","AI 協作開發是什麼？在控制成本的同時提升品質的方法",[266,437,438,441],{},[284,439,440],{},"系統沒人維護時，該接手、重構還是重寫",[284,442,443],{},[182,444,445],{"href":184},"系統沒人維護怎麼辦？舊系統接手、重構與重寫的完整指南",[266,447,448,451],{},[284,449,450],{},"既有系統改版時，AI 工具怎麼用才安全",[284,452,453],{},"本文",[121,455,456],{"id":456},"常見問題",[458,459,461],"h3",{"id":460},"我們的系統很舊技術也過時ai-工具看得懂嗎","我們的系統很舊、技術也過時，AI 工具看得懂嗎？",[113,463,464],{},"大多看得懂。主流的 AI 寫程式工具能讀懂 ASP.NET、PHP、Java 等常見的舊技術，也能協助整理沒有文件的程式。但看得懂程式不等於知道規則的由來，盤點出來的疑點仍要和使用者確認。",[458,466,468],{"id":467},"可以要求整個專案全程不使用-ai-嗎","可以要求整個專案全程不使用 AI 嗎？",[113,470,471],{},"JoinX 做不到。我們的開發流程以 AI 協作為基礎，無法拆掉 AI 另外用一套流程交付。如果貴公司的政策要求全程不使用 AI，我們會在合作前說清楚，不會先答應。",[458,473,475],{"id":474},"原始碼放進-ai-工具會被拿去訓練模型嗎","原始碼放進 AI 工具，會被拿去訓練模型嗎？",[113,477,478],{},"JoinX 使用企業版或商用方案的 AI 工具，依合約或服務條款，客戶的資料不會被用來訓練模型。帳號密碼、金鑰與個人資料等機敏內容，則一律不放進 AI 工具。",[458,480,482],{"id":481},"系統完全沒有測試要從哪裡開始改版","系統完全沒有測試，要從哪裡開始改版？",[113,484,485],{},"從補特性測試開始：先把最重要流程的現有行為記錄成測試，例如帳務計算或權限判斷，再開始改程式。補測試本身就是改版的一部分，AI 可以協助加快這一步。",[458,487,489],{"id":488},"用-ai-工具改版費用與時程怎麼估","用 AI 工具改版，費用與時程怎麼估？",[113,491,492],{},"先做盤點，再依模組估。依 JoinX 承接專案的經驗，初步程式與系統健檢約 NT$5 萬至 20 萬，單一模組重構約 NT$50 萬至 200 萬。AI 工具讓盤點與補測試更完整，但不能跳過這些步驟。",{"title":494,"searchDepth":495,"depth":495,"links":496},"",2,[497,498,499,500,501,502,503,504],{"id":123,"depth":495,"text":124},{"id":136,"depth":495,"text":137},{"id":189,"depth":495,"text":190},{"id":202,"depth":495,"text":203},{"id":254,"depth":495,"text":255},{"id":356,"depth":495,"text":357},{"id":395,"depth":495,"text":396},{"id":456,"depth":495,"text":456,"children":505},[506,508,509,510,511],{"id":460,"depth":507,"text":461},3,{"id":467,"depth":507,"text":468},{"id":474,"depth":507,"text":475},{"id":481,"depth":507,"text":482},{"id":488,"depth":507,"text":489},"技術分享","\u002Fimages\u002Fblog\u002Fai-coding-tools-legacy-system-refactoring.webp",null,"Claude Code 這類 AI 寫程式工具可以用在既有系統的改版與重構，但順序不能反過來：先讓 AI 協助盤點程式與資料流，再用測試把現有行為固定下來，接著一個模組一個模組替換，每次修改都經過人工審查才合併。本文從開發團隊的角度，說明這四個步驟怎麼做、哪些事情不能交給 AI，以及 JoinX 把原始碼放進 AI 工具時的實際做法與限制。","md",false,"zh-tw",{},true,"舊系統","\u002Fzh-tw\u002Farticle\u002Fai-coding-tools-legacy-system-refactoring",{"title":108,"description":515},[525,528,531,534,537],{"name":526,"issuer":527},"Working Effectively with Legacy Code","Michael Feathers，Prentice Hall",{"name":529,"issuer":530},"Refactoring: Improving the Design of Existing Code","Martin Fowler，Addison-Wesley",{"name":532,"issuer":533},"NIST SP 800-218 Secure Software Development Framework (SSDF)","美國國家標準暨技術研究院（NIST）",{"name":535,"issuer":536},"《個人資料保護法》","法務部",{"name":538,"issuer":539},"Claude Code 官方文件","Anthropic","zh-tw\u002Farticle\u002Fai-coding-tools-legacy-system-refactoring",[542,543,544,545,546],"AI 寫程式工具用在既有系統改版時，順序是盤點、建立測試保護網、逐步替換、人工審查，不能直接叫 AI 重寫。","AI 最適合協助讀懂舊程式、整理資料流與補測試，但哪些奇怪的分支是商業規則、哪些是錯誤，要由人和使用者確認。","先用測試把現有行為固定下來，再改程式；測試沒過的修改不合併，這是改版不出事的關鍵。","JoinX 的開發流程是 SDD + TDD：先把要改的行為寫成規格，再用測試驗證，AI 產出的程式和人寫的程式走同一套審查。","JoinX 會把原始碼放進企業版 AI 工具，依合約不拿資料訓練模型；帳號密碼、金鑰與個人資料不放進 AI 工具；客戶要求全程不用 AI 時，我們做不到，會在合作前說清楚。","2026\u002F11\u002F04","blog","8UWEWFtESEk_7GxmsUz7dx2yjLpzzjG1qKbnPxBvnuU",[551,555,559],{"slug":552,"title":553,"time":547,"cover":554,"need":521},"app-revamp-takeover-guide","APP 改版與接手：改版前要盤點什麼、誰來維運、要不要做 Design System","\u002Fimages\u002Fblog\u002Fapp-revamp-takeover-guide.webp",{"slug":556,"title":445,"time":557,"cover":558,"need":521},"legacy-system-takeover-guide","2026\u002F07\u002F28","\u002Fimages\u002Fblog\u002Flegacy-system-takeover-guide.webp",{"slug":560,"title":561,"time":562,"cover":563,"need":521},"2026-system-maintenance-5-benefits-digital-assets","系統維運能為企業帶來哪些優勢？掌握 5 大好處確保數位資產穩定增值","2026\u002F04\u002F17","\u002Fimages\u002Fblog\u002F2026-system-maintenance-5-benefits-digital-assets.webp",1794558627559]